I have tried doing what was suggested to resolve ctds but still seem to get them.
I have
- the latest display drivers
- the latest sound drivers
- and it makes no difference whether I use Basic or Full sound acceleration
- It makes no difference whether I disable background tasks (Internet connection, ZoneAlarm, Creative Taskbar)
Strangely, the ctds seem to be tied to the individual patrol missions... in particular, I now cannot run the first corvette training mission ... it starts ok, you get the TRAINING OFFICER messages at the bottom of the screen, and then every time a second or so after it has printed "The red dots on your tactical map are your targets. Destroy them in the course of your cruise" the game blows out - without exception - no matter what I do beforehand, i.e. whether I issue commands vocally or by clicking, or by doing absolutely nothing at all.
Other patrol missions seem to play ok, but then may drop out at some unpredictable point. I only had a go at the first campaign mission and couldnt hit a damned sub with my dcs or hh, so wanted to go back to training to practice.
Its a shame cos I think this game is excellent. Please help!
To whom should I send a dxdiag report?
mailto: east@warfleet.net
Your issue sounds very strange, what are your specs.
I just came up with another idea, to see if/why E:RT crashes, ill be posting it in the a thread here. within a few secs
I just emailed you my DXDiag ... sorry, I hadnt noticed the tech support forum before
Please don't tell me my machine is under spec...
mailed me or EAST ???
Heheh I have no use of it:lol:
ok ok I mailed to East (east@warfleet.net). I meant "you" in the Tesseraction sense...mailed me or EAST ???
Hheheh I have no use of it
I'll send you an App log error too. I don't see an error in Eventvwr when the game crashes as described above, but I do get one sometimes when I try and start the game (double-click the icon, start via the CD autorun, or via the program menu).
Normally when the game starts I get the morse beeps and the GMX logo appears, but about 25% of the time the beeps start but I have a black screen, then the music kicks in (still have a black screen), and then finally the full screen disppears, I briefly have a window visible, then that goes bye-byes too. The eventvwr I send you will show the message I get in that case...
Cheers
well its pretty simple to see if there was an error via your events log (if it was recorded).
you will see a RED CIRCLE with a WHITE X, just double click on it to see what caused the problem and what was involved:
Ill post a snapshot of an example:
It could look like this
It could also say that blahblah.dll caused an error in enigma.exe or whatever...
Be sure to look in the system logs aswell.
um, yes I know that ...
thats why I said there are NO errors when I get the mission crash, but there IS one when the game fails to start . I've emailed EAST the eventvwr app log that pertains to that. there are no errors in the system log.
FYI I also tried setting the sound accel to NONE and the mission crashed in the same place. The only other effect was that the sound was naff and sounded truncated.
Cheers
can I see the "when the game starts" it crashes log ?
or just tell which file caused the error