[ATP]

Hey,
Is there any way to check wich thread caused a crash of the game? Or even where in the thread the crash happens?

ATP

[Deji]

The best way is to simply add "breakpoints" in your script or debug messages... The script can not always be directly routed to the crash. For example, you set an invalid flag which is used somewhere else in the game. That invalid flag will cause no problems until it's used for something important, which doesn't happen until the next break in the script (the next wait or any other opcode which causes the script parser to finish on the current script).

Common sense, regular testing and debug code is always the best solution. I usually always end up creating a few debug scripts each time I start some new code.

[ATP]

Hey,
Yes, I usually debug in that way you explained. For single scripts it is ok. My Problem is I have a whole bunch of threads and missions, wich work without crashs in single. But combined to an main.scm I get some complications or "interaction" between the scripts. I could work here with the method mentioned above, and enable/disable single scripts or parts of them. But the problem is that crashs only happens in special constelations, wich are random and you can not reproduce them.

[Deji]

Then it most-likely will not be tracable to the opcode... but try SCM Log from the CLEO Website.

[ATP]

Well, I tested scmlog and I think it is very helpful. If you analyze the order and params of the opcodes, you can trace back from wich script they must be.