1.1p : EXE crashes during precompile from Torsion - LOGGED (THREED-3173)
by Ken Finney · in Torque 3D Professional · 05/17/2011 (8:29 am) · 12 replies
This is driving me nuts - I've searched through here twice, and no one else seems to be having this problem.
When I launch my game (also tested and verified with a fresh install of FPS Example), the .exe crashes during the pre-compile stage. This happens whenever exporting takes place as well. The game seems to run fine after that, but of course, all results are now suspect.
EDIT
* behaviour is the same for debug or release builds
/EDIT
* It only happens when launching from Torsion (because of the pre-compile) and not when launching from desktop.
* The crash happens before the script manager leaps into action.
Any ideas?
Suspecting an environment issue, I checked by DX version - it's June '10.
Compile with Visual C++ 2008 standard, and Visual C++ 2010 Express. Same error.
In fact, it does this right out of the box, without me compiling anything.
When I launch my game (also tested and verified with a fresh install of FPS Example), the .exe crashes during the pre-compile stage. This happens whenever exporting takes place as well. The game seems to run fine after that, but of course, all results are now suspect.
EDIT
* behaviour is the same for debug or release builds
/EDIT
* It only happens when launching from Torsion (because of the pre-compile) and not when launching from desktop.
* The crash happens before the script manager leaps into action.
Any ideas?
Suspecting an environment issue, I checked by DX version - it's June '10.
Compile with Visual C++ 2008 standard, and Visual C++ 2010 Express. Same error.
In fact, it does this right out of the box, without me compiling anything.
#2
05/17/2011 (9:37 am)
Thanks red-faced-cookie-monster guy! Dunno how I missed that thread, I went farther back than that. I'll try some re-installs.
#3
05/17/2011 (9:51 am)
okay, re-installing Torsion alone didn't help. 
#5
<shrug>
05/17/2011 (11:30 am)
I'm having this issue as well, but though I find it annoying my testers never see it. I think I'll look into the dso output code - it seems to precompile and then crash, but I would expect every script to output as it was compiled so this would still seem strange.<shrug>
#6
05/17/2011 (4:37 pm)
Can you double check that all of the executables are there and that the Torsion project targets are pointing at the correct location? 
#7
In fact, another test I just did:
I ran my 1.1b3 project with my 1.1b3 release build. No problems.
Then I replaced my 1.1b3 PanicSector.exe & PanicSector.dll with the 1.1p PanicSector.exe & PanicSector.dll, and launched from my 11b3 torsion project.
It asplodes, on the precompile, but then runs fine when TOrsion relaunches the exe. It will crash on every instance of the pre-compile being invoked - when re-exporting, or using the manual pre-compiles as well.
Finally, I copied the fresh outa-the-box FPS Example.exe and FPS Example.dll into my 1.1b3 project, and renamed them to PanicSector... etc.
Kablooie on the pre-compile.
So that establishes, to me, that it isn't my 1.1p project that is the source of the trouble. The pristine FPS Example for 1.1p does this to me as well.
And happening where it does, it's very tricky to trap it in the debugger.
05/17/2011 (6:36 pm)
Michael: yup, done and done. Everything is correct.In fact, another test I just did:
I ran my 1.1b3 project with my 1.1b3 release build. No problems.
Then I replaced my 1.1b3 PanicSector.exe & PanicSector.dll with the 1.1p PanicSector.exe & PanicSector.dll, and launched from my 11b3 torsion project.
It asplodes, on the precompile, but then runs fine when TOrsion relaunches the exe. It will crash on every instance of the pre-compile being invoked - when re-exporting, or using the manual pre-compiles as well.
Finally, I copied the fresh outa-the-box FPS Example.exe and FPS Example.dll into my 1.1b3 project, and renamed them to PanicSector... etc.
Kablooie on the pre-compile.
So that establishes, to me, that it isn't my 1.1p project that is the source of the trouble. The pristine FPS Example for 1.1p does this to me as well.
And happening where it does, it's very tricky to trap it in the debugger.
#8
05/17/2011 (6:42 pm)
One more tidbit - it most definitely is the dll and not the exe that has the problem. (which makes sense, since the precomiple happens in the dll)
#9
also - I was mistaken in my OP - the behavior is the same in the debug build for 1.1p as in the release build for 1.1p.
05/17/2011 (6:46 pm)
Woops! the above 2 ^ were by me logged in with a studio acct.also - I was mistaken in my OP - the behavior is the same in the debug build for 1.1p as in the release build for 1.1p.
#10
01/11/2012 (2:51 pm)
Logged as THREED-3173. 
#11
08/16/2014 (12:50 am)
I'm sorry, but the only solution I know of is to switch to a newer release. I had the same problem, but moving on to the 1.1 final and further did the trick.
#12
08/17/2014 (10:05 am)
That's really odd - I haven't had this issue in years. It never happened to me with anything 1.2 pro or later. 
Torque 3D Owner Lunacy