CTD in GWX 2
 

Not sure if this is a bug or not, but twice now when a torp impacts on a target I get a CTD. The last time really frustrated me in that i had a destroyer and TWO cruisers waiting to be sunk and i hit the destroyer and it crashed to desktop. I was in the process of swinging about to let all 4 of my front fish loose on the cruisers at close range.. :(

Any ideas on this?

Tool.

Are you using any other mods on top of GWX?

Nope, no mods at all. This just started happening..maybe has something to do with the event camera being on?

Tool.

What cruiser class were you firing at?

I was firing at a destroyer and hit it. The cruisers weren't the typical battle cruiser (I forget the name of them), but looked like some sort of retrofitted ones..

Tool.

Unfortunately to recreate the circumstances and confirm whether or not there is a problem relating to GWX... we have to know the exact vessel and timeframe involved.

Roger that.:D We need:

Date/Time (local & GMT)
Location
Ships involved

It's a big ocean out there.:rotfl:

2 Auxiliary Cruisers and a destroyer (not sure of the type)
18 Oct. 1939, Approx. 0800 local
Quandrant to the East of AM19 (approx. 80km into it)

Unfortunately i was unable to locate them again after reloading the save. I made the mistake of not saving for an 800km cruise and even though i followed the exact same route, this time they were a no show. Lost out on about 30k tons worth :(

Hope that helps.
Tool.

Just bumping it up to keep this alive...

Thanx
Tool.

Noted... I may have a save near there at about that time (my favorite hunting ground) will have a look-see

you sure they were auxiliary cruisers?

They were large, 4 stacks, looked like a converted supply ship or something. Here is a screenshot.. kinda distant in the background though..
http://mysite.verizon.net/turnkey1/i...h3/cruiser.jpg

Maybe that will help..
Tool.

Guys, I just set up a single mission to test the Aux cruiser. This mission has about ten of them.

Tool, you should try this mission found on the DL link below.

I just sunk three of them with no problems at all.

http://rapidshare.com/files/77750923/AUX_Cruiser_Test.zip.html

It wasn't when a torp hit the cruiser, it was when it hit the destroyer at the lead. As soon as it exploded it CTD, and i had event camera on and saw it on there. Maybe that is the issue? This isn't the first time this has happened, as it did the night before with a AWS (?) trawler. Maybe something on my end is corrupt.

Tool.

I think so, I don't use the event camera and have sunk numerous trawlers and DDs without problems

could you try with the event camera off?

the one in your picture looks like a C&D or A&B class, I just sank one of those no worries.

I'll try to finish my patrol of AM19 then see if i can find one more target as i only have 6 fish left and see if it crashes. If so, i'll quit and return to port, and start the next patrol with the cam off. I'll keep you updated.

Thanks for all the help.
Tool.

One other suggestion, take a look at your dxdiag and see if your sound acceleration slider is toward the high end (to the right). I have an idea some heavily loaded CPUs can be pushed over the edge if sound acceleration is set too high. Try running it all the way to the left (no acceleration) or maybe the first notch to the right.

This sounds very similar to my CTD issue that I posted about earlier. I put the error report in the post.

I would hit a destroyer and it would go nuts...panic firing starburst shells non stop really fast.
A few moments later CTD. If I decided not to shoot the crash would not occurr.
The target does not have to be a DD for the crash to occurr for me but there does always seem to be one nearby.

It almost seems like an "aggro" problem. For example if my noise meter is green and Im undetected after I have struck my target the crash does not occur but if there is a DD nearby and and my meter is red it seems to happen.

This has definitely happened to me b4 GWX 2.0. Chances are good this is an SH3 issue.
The last time this happened, I started a new patrol and it never returned.

I have just started a new patrol in GWX 2, so hopefully this weirdness will just go away.

Only mods Im using are a subskin and the final torp dmg mod

Oh in case its needed my system is : AMD 64 3400 2.20ghz / 3GB of Ram / Nvidia 7800 GS / Windows XP

I'll check that but i'm sure my dual core with 2 gigs of DDR2 can handle things fine :)

Plus I'm not using onboard sound, so it shouldn't be hitting the CPU that hard. Too bad SH3 doesn't support the duals/quads.

Thanks for the advice Hanomag, and i'll try to keep a closer eye on things and see if there is a key element in each CTD. Funny thing is i never had this before and if need be i'll ditch this career and try a fresh start, but i hope i won't have to. I had issues early on with saves and saying "war is over" and i couldn't continue.. oddness all around.

Tool.

I use a 64-bit dual core system with no issues whatsoever concerning SH3.:hmm:

Regarding the old "war is over" bug... That was corrected by the 1.4b patch for SH3.

Also, if you didn't delete your SH3 folder in "My Documents" prior to running GWX... that would explain a great deal in reference to the issues you are describing.

Old careers are not fully compatible with GWX 2.0.