1 reply to this topic

[lostincarnation]

I currently have a CTD in an area.

And i know that certain lines in the area script are the reason of the CTD.

But how do i find out?

This area script is a huge one.

Is there anyway to trace the script execution output?

[The Imp]

I currently have a CTD in an area.

And i know that certain lines in the area script are the reason of the CTD.

But how do i find out?

This area script is a huge one.

Is there anyway to trace the script execution output?

Yes, the LStest, hih hihihi, not what you are probably looking for as of course that will only give out the print before it crashes. Which won't help much.

What you need to do is to install the ToBEx mod if you have not yet, and then make it print the trouble shoot info and then reproduce the crash and tell what it says... and then we can go and hunt down the kil... crasher thingy.

The readme tells this:

 

Troubleshooting
....
For more debugging information:
1. Open TobEx_ini/TobExCore.ini in a simple text editor.
2. Under the [Debug] section, set all values of 0 to 1.
3. Try to reproduce your error in-game. TobEx may sometimes reports some extra information about the error.
4. Report any errors you find on the Spellhold Studios forums. Expect to be asked to attach a .zip of your saved game folder, WeiDU.log, TobEx.log, TobExCore.ini, and TobExTweak.ini.