Game Development Community

Crashing on DirectInput

by Shon Gale · in Torque Game Engine · 05/13/2007 (9:05 am) · 6 replies

Help!! I am crashing on load of mission at DirectInput.
Here is the trace.
Entering [CanvasCursor]GuiCanvas::setContent(Canvas, PlayGui)
      Entering PlayGui::onWake(1205)
          Activating DirectInput...
          keyboard0 input device acquired.
Then it crashes.
Any help is appreciated. Is this a directx problem?

#1
05/13/2007 (10:14 am)
First, is it modified or stock binary (EXE file) ?
second, on what OS are you running this?
#2
05/13/2007 (10:36 am)
To bank
Sorry I was so vague and thanks for the response.
There are no .exe mods and we are using win xp Professional x64 edition service pack 1 running AMD Athlon 64 3000+ processor and 1 gig ram. It's not the latest and we keep it that way for backward compatibility issues, also it is our rendering computer. We can run up to TGE version 1.5 but not TGE 1.5.1 so we're a little mystified at the crash. We have had no problems previously.
#3
05/13/2007 (11:03 am)
Try commenting out the two lines in playGui.cs to see if it still crashes.
#4
05/14/2007 (3:53 am)
Thanks for the response guys.We found the problem and thought it had been resolved before. It was the OpenAL32.dll file that was crashing only some of our computers. We went back to the 1.3.5 version of TGE and OpenAL32.dll and now it works on all computers we have tested it with. We thought this problem was solved in TGE 1.5 because it seemed to work on all computers until this one. This seems to be a continuing issue and it would be nice if we had a choice of Audio Systems such as Audiere, it works on all our systems without a hiccup. It's not like GG has anything to do with it. If it's buggy we are at their mercy. Maybe GG needs their own Audio System.
#5
05/20/2007 (5:42 am)
We have done more testing on this problem and have found that the OpenAL32.dll from 1.5.1 only has problems with AMD processor machines. It works flawlessly with Intel processors.
This may be the actual problem but it appears to be when tested with several different machines.
I understand this is a OpenAL problem and not GG.
#6
05/20/2007 (6:37 am)
Does OpenAL have problems or is the machine in question one of those where the user forgot to install the Cool'n'quite CPU driver from the AMD page to remove the serious timing issues?

Intel does not need such a thing as speed step is part of Windows but AMD users must install their CPU drivers since AMD x64 or will get some funny results.