In addition to Malice's response.
You need to create better debug messages.
First, have standard debug messages such as...
DebugLog "Have entered/exited function xxx"
at the start and end of each function (along with timer messages for optimisation tests).
If you get a problem add further debug messages which are output when set and when leaving functions.
Rather than
DebugLog fotogramma2
use something like...
DebugLog "Fotogramma2 on exit of function xxx is " +
fotogramma2
Consider using text commands for items such as player x/y and names which appear on screen.
Finally, get used to setting checkpoint messages in your main loop such as...
DebugLog "Main_loop4"
With all these you can trace any errors to specific code by checking which messages have been written.
p.s. I tend to have a comment such as TGDEBUG so I can delete lines later.
You need to create better debug messages.
First, have standard debug messages such as...
DebugLog "Have entered/exited function xxx"
at the start and end of each function (along with timer messages for optimisation tests).
If you get a problem add further debug messages which are output when set and when leaving functions.
Rather than
DebugLog fotogramma2
use something like...
DebugLog "Fotogramma2 on exit of function xxx is " +
fotogramma2
Consider using text commands for items such as player x/y and names which appear on screen.
Finally, get used to setting checkpoint messages in your main loop such as...
DebugLog "Main_loop4"
With all these you can trace any errors to specific code by checking which messages have been written.
p.s. I tend to have a comment such as TGDEBUG so I can delete lines later.