wait(1);


That is the code. even at the beginning of the function and have the function end via return immediately afterwards it would crash. It's important to note I have used that code for over a year until it just decided to crash this time when I would try to publish.

Other situations I would have to add random meaninless functions in certain scripts to get it to publish right.

And again, this all works perfectly from Sed and I just checked to see if Wed was any different and it's not.

Could be that compiler issue too: http://www.opserver.de/ubb7/ubbthreads.php?ubb=showflat&Number=455540&#Post455540

Ok well wait(1); isn't likely the issue. Wait adds the current function to the schedule list and then allows other functions to run. Isn't it more likely that during the wait() the next running function cause the crash.


Anyway. Good luck

you may have a memmory bug , it usually runs fine in SED environment , but will crash outside of this environment , that is common memmory bug results , but I am guessing I don't know your code .

Other questions: Are you using the latest version? Do you start the game with SED from a higher/ custom nexus and without NX settings in the published version?

all valid questions there. ^

I would like to express the reason why I lean towards the possibility of memmory bug , the reason is , I have experienced this type of behaviour specifically where changing a function name or adding/removinh code to parts which shouldn't do anything , actually resulted in the application randomly behaving correct and incorrect at other times , I figured out I was removing a pointer and directly after that I was accessing it without checking if its valid , which was just a memmory bug ..

It's possible there is a memory bug, however I do not do anything "special" everything I run is normal A7 stuff. I like to keep things simple if possible. The only weird thing is sometimes I will see an image jump from one set to another. Not sure how that happens. The project is huge though. Possible issues to get through.

Right now I am going with that rare compiler issue that Superku listed.

The most interesting thing in my project is a custom animation setup. It loads multiple images into multiple panels and moves and rotates them to simulate complex animation while keeping file size very low. I use the same file loading system between this and the animator I built which has no issue.

Then fix that weird "image jumping" issue. That's a warning sign for some deep code issue, overwriting memory or faulty pointers and such.

I've once written a program (or... 10+ programs) to solve a 16x16 tile puzzle called Eternity II. I've experienced some weird bugs doing so, for example the program going through the board in a weird and seemingly not programmed way/ routine after ~100 iterations. All bugs where either memory related (wrong array index access) or - what I didn't know back then - limited stack memory size. I called a recursive function which used local arrays, like data[1024], not knowing that the allocation of such "big" arrays fails after some levels into the recursion.

I'm constantly trying to fix the issue, just no idea where this could be coming from. It's doubtful the two are connected tough.

The game loads 500 images right off the start and then another 500 other files (images and text files) once it gets going, as the custom animations are not part of this list.

is there any kind of error message like a E1513 ?