Error Message: Random Data

Started by KHAeon, December 25, 2009, 01:50:43 AM

Previous topic - Next topic

KHAeon

Ok, so I made a few changes in coding in one of my characters, simply for optimization and readability.
Then, when i tested the character, MUGEN crashed, and I got this message:

Spoiler (click to show)
Error detected.

Library error message: Random data

I've never had any problems like this one before, so  have no idea how to fix it.
Could someone please tell me what this means, and/or how to fix it?  :wall:

Cyanide

Nope, never seen that before.

Revert some of your changes (hope you didn't make too many) and see if it goes away.


In M.U.G.E.N there is no magic button

They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.

KHAeon

Sadly, I didn't make that many changes... I made MORE than that many changes!
PLUS, i lost the undo data...  :toilet:

Cyanide

Add the .cns to KFM. If he works, change it back and add your .air. Do that with all the files.

See which one causes KFM to die. You can limit it down that way.

Other things to do, Split your .cns into a multitude of files and turn them off and on. See which one makes it break. You can then work it down state by state a little easier.

Do the KFM bit first though.


In M.U.G.E.N there is no magic button

They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.

KHAeon

Wait a minute, i'm narrowing down the problem in a similar way...
I am deleting a stateno in the group i recently edited... and trying mugen.
If it still doesn't work, i will undo to get the data back, and move on to deleting the next stateno.....

OK, I've found the stateno in my character, now to isolate and fix the problem

KHAeon

I HAVE FOUND THE PROBLEM!
It was in one of the hitdefs...
ground.velocity = cond((p2dist X>15),0.25,0)

Personally, i don't see any error, because i only changed the 'ifelse' (working fine)
that was previously there to the updated 'cond' (broken?).

oh well, maybe the system just misread it or i'm missing something...
SOLVED!  :woeh: