Matrix Games Forums

This game seems way cool but I didn't realize it was quite so buggy. [:(] Hope it's fixed soon.

Here's the errorlog.

well
mines as well dump mine 2

both of these are with the b5 mod so it could be causing it

*********************************************
FATAL EXCEPTION:

Registers:
EAX: 1ca6f540
EBX: 18298820
ECX: 1cab0120
EDX: 005fc9a4
EDI: 00000000
ESI: 183019b0
EBP: 0012f9b8

CS:EIP: 001b:00503355
SS:ESP: 0023:0012f910
DS: 0023
ES: 0023
FS: 003b
GS: 0000
Flags: 00010202

Exception Code: c0000005 ACCESS_VIOLATION
Exception Addr: 00503355
Program attempted to READ from address 0x1cab02b0

Loaded IMAGEHLP.DLL

Stack Trace (Symbolic):
Address Frame
00503355 0012f9b8 0001:00102355 D:\-=Games=-\Matrix Games\Starshatter\Stars.exe

*********************************************
PROGRAM TERMINATED.


MusicDirector::SetMode() old: MENU new: FLIGHT
TIME 2:00
TIME 3:00
VideoDX7::RecoverSurfaces()
* Restoring All Surfaces
* Marking 0 Surfaces Invalid
* Invalidating Texture Cache
* Vid Mem Free: 56225792
* Recover Surfaces Complete.

VideoDX7::RecoverSurfaces()
* Restoring All Surfaces
* Marking 0 Surfaces Invalid
* Invalidating Texture Cache
* Vid Mem Free: 56225792
* Recover Surfaces Complete.

VideoDX7::RecoverSurfaces()
* Restoring All Surfaces
* Marking 0 Surfaces Invalid
* Invalidating Texture Cache
* Vid Mem Free: 56225792
* Recover Surfaces Complete.

VideoDX7::RecoverSurfaces()
* Restoring All Surfaces
* Marking 0 Surfaces Invalid
* Invalidating Texture Cache
* Vid Mem Free: 56225792
* Recover Surfaces Complete.

VideoDX7::RecoverSurfaces()
* Restoring All Surfaces
* Marking 0 Surfaces Invalid
* Invalidating Texture Cache
* Vid Mem Free: 56225792
* Recover Surfaces Complete.

VideoDX7::RecoverSurfaces()
* Restoring All Surfaces
* Marking 0 Surfaces Invalid
* Invalidating Texture Cache
* Vid Mem Free: 56225792
* Recover Surfaces Complete.

Strike Wing 1 Killed Alpha 2 (03:52.861)

*********************************************
FATAL EXCEPTION:

Registers:
EAX: 19b3bc30
EBX: 25c5fce0
ECX: 25e4dca0
EDX: 005fc9a4
EDI: 00000000
ESI: 25cb18c0
EBP: 0012f9b8

CS:EIP: 001b:00503355
SS:ESP: 0023:0012f910
DS: 0023
ES: 0023
FS: 003b
GS: 0000
Flags: 00010206

Exception Code: c0000005 ACCESS_VIOLATION
Exception Addr: 00503355
Program attempted to READ from address 0x25e4de30

Loaded IMAGEHLP.DLL

Stack Trace (Symbolic):
Address Frame
00503355 0012f9b8 0001:00102355 D:\-=Games=-\Matrix Games\Starshatter\Stars.exe

*********************************************
PROGRAM TERMINATED.

Hi everyone,

The crash problems that appeared with 4.0.1 should be fixed. John did some quick work with 4.0.2 and we tested it over the weekend. We have 4.0.2 ready and I'm just waiting for final word that it's online so that I can post the announcement for you all to go download it. [:)]

Regards,

- Erik

DamoclesX - what version of the game were you playing when you had those crashes?

EDIT:
Nevermind. It's got to be 4.0.2 or else that crash address would make no sense. Something seems to be going wrong with the collision avoidance routine. Can you describe what was happening in the mission when it blew up?

Thanks,

if it is 4.0.2 where is it. would love to have it
randy s

The official 4.0.2 patch should be available for download later today. DamoclesX is a beta tester, so he was using a pre-release copy of the patch.

Thanks for your patience,

hmm

I will try to reproduce it milo, but most of the time it just dumps and its in the middle of a battle.

But I"ll give it a run through today and see if I can pin down exacty what makes it crash

I think blackwolf had it crashing 100% of the time when he did something, so i"m gonna talk to him, he should be around tonight.

It could be that collision avoidance, I noticed a few times my fighter bounced back and blew up like it had hit a cap ship, and although I WAS pointed and going towards said ship I was still a good oh... 2 or 3 shiplengths away

Hello...
I, too, have been experiencing CTDs since applying patch 4.01...but not in the fighter campaigns. I have only CTD-ed when in Campaign 3 as either a Frigate or Destroyer commander...usually when things are starting to "get good" in a mission. I have attached my latest post-crash error log for the technical peoples' attention.

I thank you in advance for your attention, and hope that a fix (4.02?) will be out soon.
Cheers,
Rajenator [:)]

Hi everyone,

4.0.2 is online and available from our Members area. Please read the post pinned to the top of the forum. If you are experiencing any problems, or even if you're not, it's a good idea to update to this new revision as soon as possible. Let us know if it helps out.

Regards,

- Erik

I'm still having CTD problems with 4.0.2. Seems more stable than 4.0.1 (had no crashes in 4.0.0). Can't seem to pinpoint specific triggers, but it seems to happen mostly in larger fleet engagements. . .

ORIGINAL: norstad

I'm still having CTD problems with 4.0.2. Seems more stable than 4.0.1 (had no crashes in 4.0.0). Can't seem to pinpoint specific triggers, but it seems to happen mostly in larger fleet engagements. . .

Could this be a problem with computer specs?

Could this be a problem with computer specs?

It's possible, but seems unlikely given the circumstances. I'm running on a 1.4 gig machine with 512MB ram and 128MB GeForce. But what makes me disinclined to think it's computer specs is that I never had a single CTD in 26+ hours of flying time on 4.0.0. After installing 4.0.1 I had trouble finishing a single mission (either fighter or cap ship) without a CTD. In my brief test last night, I was able to get through two missions (one fighter, one cap ship) before having a CTD on the third (cap ship). I'll test some more tonight, but it looks like they're might still be some minor bugs to quash in 4.0.2.

I CTD when I try to launch any second battle...complete the first, ,the accept the second and CTD.