[RMVX ACE] SYSTEM STACK ERROR
Posts
Pages:
1
Hi guys, I have a scripting problem I can't resolve.
I'm using Theo's sideview battle system, and have implemented a combo system where the player can chain together various attacks.
However, reaching a combo of 16 hits will crash the game with a 'system stack error - stack level too deep'.
I used Hime's stack debugger and it directed me to line 1839 of Theo's 'Implementation' script, that deals with fiber?
Here is a link to a fresh project that replicates the error.
https://www.dropbox.com/s/qyxesuuvahvdilx/HimeStack.exe?dl=0
To trigger the error, use the Crimson thorn skill at full TP and reach a combo of 16.
The script for the move is in 'sequences'.
I left a message on Theo's blog but I noticed he hadn't replied to bug reports for a while. If anyone knows him, please let him know of this thread.
Please help me if you can, it would be greatly appreciated.
I'm using Theo's sideview battle system, and have implemented a combo system where the player can chain together various attacks.
However, reaching a combo of 16 hits will crash the game with a 'system stack error - stack level too deep'.
I used Hime's stack debugger and it directed me to line 1839 of Theo's 'Implementation' script, that deals with fiber?
Here is a link to a fresh project that replicates the error.
https://www.dropbox.com/s/qyxesuuvahvdilx/HimeStack.exe?dl=0
To trigger the error, use the Crimson thorn skill at full TP and reach a combo of 16.
The script for the move is in 'sequences'.
I left a message on Theo's blog but I noticed he hadn't replied to bug reports for a while. If anyone knows him, please let him know of this thread.
Please help me if you can, it would be greatly appreciated.
I would say the information about line 1839 is useless.
Because the crash happened in the code of the fiber (which is similar to a thread). So you need the stack of the fiber to see what was executed when it crashed.
Stack level too deep means you have too many nested function calls.
Because the crash happened in the code of the fiber (which is similar to a thread). So you need the stack of the fiber to see what was executed when it crashed.
Stack level too deep means you have too many nested function calls.
Pages:
1














