TGE 1.5: Torque Demo crashes with very little explanation
by Tom McLean · in Torque Game Engine · 03/16/2007 (4:00 pm) · 5 replies
Got this weird bug that makes the Torque Demo crash upon launching with very little explanation.
Double-clicking the torqueDemo.exe (from a fresh install of the SDK) results in one of those "torqueDemo.exe has encountered a problem and needs to close etc etc" windows.
I built it again from source and ran it in debug mode from VC++ 2005 Express and in the output window I get:
----
HEAP[torqueDemo_DEBUG.exe]: HEAP: Free Heap block 159df8 modified at 159e28 after it was freed
Windows has triggered a breakpoint in torqueDemo_DEBUG.exe.
This may be due to a corruption of the heap, and indicates a bug in torqueDemo_DEBUG.exe or any of the DLLs it has loaded.
----
torqueDemo.exe used to run fine, until I (in an attempt to start a new project) copied torqueDemo.exe, starter.fps/, creator/, common/ and all of the dlls and batch files into a new directory (and adjusted the new main.cs to point to starter.fps). Now neither torqueDemo.exe works, even after reinstalling the SDK.
I realise that this isn't much info to work off but I'm at a loss as to where I can find more.
If anyone has had similar problems or knows where I could get more info to help diagnose that'd be extremely helpful.
Cheers!
Double-clicking the torqueDemo.exe (from a fresh install of the SDK) results in one of those "torqueDemo.exe has encountered a problem and needs to close etc etc" windows.
I built it again from source and ran it in debug mode from VC++ 2005 Express and in the output window I get:
----
HEAP[torqueDemo_DEBUG.exe]: HEAP: Free Heap block 159df8 modified at 159e28 after it was freed
Windows has triggered a breakpoint in torqueDemo_DEBUG.exe.
This may be due to a corruption of the heap, and indicates a bug in torqueDemo_DEBUG.exe or any of the DLLs it has loaded.
----
torqueDemo.exe used to run fine, until I (in an attempt to start a new project) copied torqueDemo.exe, starter.fps/, creator/, common/ and all of the dlls and batch files into a new directory (and adjusted the new main.cs to point to starter.fps). Now neither torqueDemo.exe works, even after reinstalling the SDK.
I realise that this isn't much info to work off but I'm at a loss as to where I can find more.
If anyone has had similar problems or knows where I could get more info to help diagnose that'd be extremely helpful.
Cheers!
#2
Seems to be that it's crashing before it even gets to the stage where it generates that file.
Any ideas, anyone?
03/17/2007 (10:50 pm)
No, I hadn't! And after attempting to follow that advice... I still haven't.Seems to be that it's crashing before it even gets to the stage where it generates that file.
Any ideas, anyone?
#3
03/18/2007 (5:28 am)
Thats a bummer. It does sound like a corrupted file. When you "reinstalled" the SDK did you rename or delete the entire Torque directory to ensure that a bad file isn't hanging around? Also when are you running out of the original directory when you reinstalled?
#4
The program's crashing at ln. 113 in winInput.cc
Commenting out ln. 1313 and 1314 in winWindow.cc...
...fixes the problem although I believe that means it's using a software input handler rather than DirectX...?
Anyway the 'solution' to the problem made me think I just had a corrupt DirectX install although a reinstall of DX9 and a test on my housemate's computer still saw the crash on startup.
Slightly less urgent now as I've got a temporary fix but would still appreciate any and all suggestions for this interesting challenge!
03/19/2007 (4:36 am)
Ok, have done some detective work.The program's crashing at ln. 113 in winInput.cc
112 smManager = new DInputManager
113 if ( !smManager->enable() )
114 {Commenting out ln. 1313 and 1314 in winWindow.cc...
1313: if ( !WinConsole::isEnabled() ) 1314: Input::init(); 1315: InitInput(); // in case DirectInput falls through
...fixes the problem although I believe that means it's using a software input handler rather than DirectX...?
Anyway the 'solution' to the problem made me think I just had a corrupt DirectX install although a reinstall of DX9 and a test on my housemate's computer still saw the crash on startup.
Slightly less urgent now as I've got a temporary fix but would still appreciate any and all suggestions for this interesting challenge!
#5
03/19/2007 (5:25 am)
Have you reinstalled the DX SDK? Reinstalling DirectX 9 doesn't really provide the solution of needing the SDK to develop. 
Torque Owner Dan -