GWX: Fatal Error when ships firing deck gun.

Gildor · 01-14-07, 07:26 PM

I did a search and could not find anything about this.

I snuck up on a convoy. Fired at three ships, sunk 2. I was silent running at 40m and making my way through the convoy without too much attention from the escorts.

As I exited the convoy there was a DD at the back in perfect position for my stern torp. I went to PD and fired. Hit him in the bow.

Here is where it gets bad. He fired all his guns with star shells at one area. There were probably 20 to 30 star shells in the air. Needless to say, I got a fatal exception error of some kind and CTD.

This happened a couple of other times when I was near the Bismark when combat started. When the ships opened fire, and shells started flying I got the CTD. After 3 or 4 reloads, I gave up and stayed out of the area.

I have GWX, SCMD 2.7 and no other mods. Is there something I am missing?:hmm:

monsoonrat · 01-14-07, 07:37 PM

Do you have the 23rd GWX fix installed? I know the fixed some CTD issues.

Gildor · 01-14-07, 08:01 PM

*slaps forehead* DOH!

Installed DEC23 corrections. Thanks. I will see if it happens again.

Tikigod · 01-14-07, 10:35 PM

Also, could be a sound card or driver issue. Always make sure you have latest sound drivers and if you are running hardware acceleration in game and you are using teamspeak, make sure teamspeak is set to software acceleration. I find keeping games and teamspeak seperate in acceleration methods helps game stability if CTD's arrise.

I haven't CTD in sh3 yet. But, I find in other games that alot of sounds can cause instability if you are hardware accelerating on too many devices at once. Also switch the acceleration method to see if it fixes it. If you are running software acceleration switch it to hardware acceleration (if your card supports it) if running hardware acceleration switch it to software (by unchecking hardware acceleration) doing this simple change to your settings fixes most CTD issues.

Rubini · 01-15-07, 11:09 AM

Quote:

Originally Posted by Gildor

*slaps forehead* DOH!

Installed DEC23 corrections. Thanks. I will see if it happens again.

The Dec23 Update fixed this CTD. All GWX users must install it.

Gildor · 01-17-07, 04:58 PM

I have installed the DEC23 fix.

Again, I was in the middle of a convoy at night. A ship was torpedoed and blew up spectacularly.

A DD was pissed I guess because he opened up with all his guns, filling the sky with probably around 30 - 50 star shell; all in the same general area.

I went to my control deck view thinking I wouldnt get a CTD if i couldnt see the shells. Everything was fine for about 10 min. I went to perescope view and took a peek. The DD was still up there firing all guns and filling the sky with starshell. As soon as I went to perescope view and saw the sky I CTD. Not just CTD but a complete crash to reboot.

Is there a way to get them to just fire one or two?

I think I will just stay away from convoys at night at this rate.

ref · 01-17-07, 07:18 PM

What are your system specs?
if the ctd was so bad that the machine rebooted it's probably a drivers problem (or a faulty mem stick), "normally" sh3 doesn't force a reboot when crashing, the problem with GWX is that sometimes it pushes the hardware pretty hard.
The next time that you have a normal ctd and the message of sh3.exe needs to be closed (or something like that) appear click on the details and take note of which module is causing the problem (sh3.exe, sh3sim.act, sh3collisions.act ,etc) it helps to narrow the search.

Ref

Jimbuna · 01-18-07, 09:27 AM

Like Ref said...post up your system specs...a ctd can have many causation factors but they usually occur in the majority of cases because your system has exhausted it's available resources ie: memory

01-14-07, 07:26 PM	#1
Gildor Lieutenant Join Date: Jan 2007 Location: Toronto, Ontario Posts: 251 Downloads: 0 Uploads: 0	GWX: Fatal Error when ships firing deck gun. I did a search and could not find anything about this. I snuck up on a convoy. Fired at three ships, sunk 2. I was silent running at 40m and making my way through the convoy without too much attention from the escorts. As I exited the convoy there was a DD at the back in perfect position for my stern torp. I went to PD and fired. Hit him in the bow. Here is where it gets bad. He fired all his guns with star shells at one area. There were probably 20 to 30 star shells in the air. Needless to say, I got a fatal exception error of some kind and CTD. This happened a couple of other times when I was near the Bismark when combat started. When the ships opened fire, and shells started flying I got the CTD. After 3 or 4 reloads, I gave up and stayed out of the area. I have GWX, SCMD 2.7 and no other mods. Is there something I am missing?:hmm: __________________ U-46: Oct 1943 off Portugal

01-14-07, 08:01 PM	#3
Gildor Lieutenant Join Date: Jan 2007 Location: Toronto, Ontario Posts: 251 Downloads: 0 Uploads: 0	slaps forehead DOH! Installed DEC23 corrections. Thanks. I will see if it happens again. __________________ U-46: Oct 1943 off Portugal

01-14-07, 10:35 PM	#4
Tikigod Grey Wolf Join Date: Mar 2005 Location: United States Posts: 777 Downloads: 28 Uploads: 0	Also, could be a sound card or driver issue. Always make sure you have latest sound drivers and if you are running hardware acceleration in game and you are using teamspeak, make sure teamspeak is set to software acceleration. I find keeping games and teamspeak seperate in acceleration methods helps game stability if CTD's arrise. I haven't CTD in sh3 yet. But, I find in other games that alot of sounds can cause instability if you are hardware accelerating on too many devices at once. Also switch the acceleration method to see if it fixes it. If you are running software acceleration switch it to hardware acceleration (if your card supports it) if running hardware acceleration switch it to software (by unchecking hardware acceleration) doing this simple change to your settings fixes most CTD issues. __________________ My Current Mod Contributions for SHIII

01-17-07, 04:58 PM	#6
Gildor Lieutenant Join Date: Jan 2007 Location: Toronto, Ontario Posts: 251 Downloads: 0 Uploads: 0	I have installed the DEC23 fix. Again, I was in the middle of a convoy at night. A ship was torpedoed and blew up spectacularly. A DD was pissed I guess because he opened up with all his guns, filling the sky with probably around 30 - 50 star shell; all in the same general area. I went to my control deck view thinking I wouldnt get a CTD if i couldnt see the shells. Everything was fine for about 10 min. I went to perescope view and took a peek. The DD was still up there firing all guns and filling the sky with starshell. As soon as I went to perescope view and saw the sky I CTD. Not just CTD but a complete crash to reboot. Is there a way to get them to just fire one or two? I think I will just stay away from convoys at night at this rate. __________________ U-46: Oct 1943 off Portugal

01-17-07, 07:18 PM	#7
ref Grey Wolf Join Date: Nov 2005 Location: Mar del Plata, Argentina Posts: 871 Downloads: 0 Uploads: 0	What are your system specs? if the ctd was so bad that the machine rebooted it's probably a drivers problem (or a faulty mem stick), "normally" sh3 doesn't force a reboot when crashing, the problem with GWX is that sometimes it pushes the hardware pretty hard. The next time that you have a normal ctd and the message of sh3.exe needs to be closed (or something like that) appear click on the details and take note of which module is causing the problem (sh3.exe, sh3sim.act, sh3collisions.act ,etc) it helps to narrow the search. Ref __________________

01-14-07, 07:37 PM	#2
monsoonrat Watch Join Date: Oct 2005 Posts: 30 Downloads: 37 Uploads: 0	Do you have the 23rd GWX fix installed? I know the fixed some CTD issues.

01-18-07, 09:27 AM	#8
Jimbuna Chief of the Boat Join Date: Feb 2006 Location: 250 metres below the surface Posts: 190,525 Downloads: 63 Uploads: 13	Like Ref said...post up your system specs...a ctd can have many causation factors but they usually occur in the majority of cases because your system has exhausted it's available resources ie: memory __________________ Wise men speak because they have something to say; Fools because they have to say something. Oh my God, not again!!