Community
SCI Programming => SCI Development Tools => Topic started by: gumby on January 08, 2012, 05:13:02 PM
-
In my game, when I attempt to do a 'Compile All' it bombs out nearly immediately with the generic Windows message "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.'
I'm using a Windows 7 64-bit machine.
From my troubleshooting, it seems like it's an issue about how many scripts it's attempting to compile, not code related. The tipping point seems to be around 350 scripts. If I edit the game.ini, I can remove scripts from the bottom-up & it will compile once I hit a certain point. Switching the ordering of the scripts in the .ini file makes no difference: it is not a code-related problem, if I use the 'Compile' function on each script individually they will compile.
SCI Studio does not experience this problem.
I'd ask the question if anyone else has run into this problem, but who else has this many scripts in their game?
-
I haven't played around with companion enough to know, but is there a way to do it manually with a batch file? If so, it could be done in sequential batches below the trigger point.
-
Wow more than 350 scripts, that is quite a load indeed. Is this where you've made it to in Zork development or is this something different
-
I haven't played around with companion enough to know, but is there a way to do it manually with a batch file? If so, it could be done in sequential batches below the trigger point.
I don't think there is an external compiling application - I think it's buried within Comp itself (unless maybe there are come command line options?)
Wow more than 350 scripts, that is quite a load indeed. Is this where you've made it to in Zork development or is this something different
It's still Zork. Oh, and those are just my 'procedure' scripts. That doesn't count the rooms (as I recall is over 100).
I may just be forced back over to Studio. Which might actually simplify things because then I won't have to re-code all my goto statements to loops, since assembly isn't supported in Companion.
-
I hadn't remembered any external programs with Companion, but didn't know about any switches with Companion.