Game Development Community

Need help with Options button crash

by Steve Boris · in Torque Game Engine · 07/12/2003 (8:08 am) · 3 replies

Just updated from CVS 6/18
Running Athlon 1.7
with MSI Geforce 4 4800 se
compiled Torque both in Releas and Debug mode with VC7
when i launch Torque and click options button Torque crashes
both in Release and Debug builds

Checking log file gives these errors

--------- Loading MODS ---------
Missing file: common/defaults.cs!

--------- Initializing FPS: Client ---------
Loading compiled script common/client/message.cs.
Loading compiled script common/client/mission.cs.
Compiling common/client/missionDownload.cs...
common/client/missionDownload.cs Line: 67 - Syntax error.
>>> Advanced script error report. Line 133.
>>> Some error context, with ## on sides of error halt:
function clientCmdMissionStartPhase3(%seq,%missionName)

{

onPhase2Complete();

<<<##<##<<< missionDownload.cs

StartFoliageReplication(); //added for Foliage replicator 10/17/02
>>> Error report complete.

OpenAL Driver Init:
OpenAL
Failed to initialize driver.

Compiling common/editor/EditorGui.cs...
common/editor/EditorGui.cs Line: 1137 - Syntax error.
>>> Advanced script error report. Line 2273.
>>> Some error context, with ## on sides of error halt:
%objGroup[1] = "Mission";

%objGroup[2] = "System";

//%objGroup[3] = "AI";



<<<##<##<<< EditorGui.cs

%Environment_Item[0] = "Sky";

%Environment_Item[1] = "Sun";
>>> Error report complete.

Search thru fourm, but didn't find anything similar.

Any clue why just the options button causes crash???

#1
07/13/2003 (5:49 pm)
Found that i didn't have OpenAL driver installed.
#2
07/13/2003 (6:30 pm)
That's weird. Hmmmm.. Very very interesting. That might actually need to be looked into.
#3
09/09/2003 (4:16 pm)
I just updated my install to the latest rev and now I'm getting a crash when I click the options button. I tried the OpenAL installer since my log file also shows that it couldn't start it, but no luck there. The log file shows no abnormalities in the startup and the actual game itself runs perfectly.

I tried tracing it back through the call stack but I don't know enough about the internals of the program during normal execution to figure out what's going on during abnormal execution. :(

Anyway, it appears to happen in dStrLen with a bad pointer being passed to it. Tracing it back on the call stack was particularly non-illuminating. If anyone can suggest something to post that might help track the problem down, I would greatly appreciate it.