Page 1 of 1

Allied sub torp hit -> crash

Posted: Sun Oct 18, 2009 8:35 pm
by EUBanana
Got a weird one here - when an Allied submarine successfully torps something, the game crashes out. Happens repeatedly if the combat file is replayed, always at the same point.

First time it happened I shrugged and considered it a glitch, and forged on using the text combat report rather than looking over the replay.

Second time though is a pattern! fortunately Allied torpedoes don't explode often enough to take the game out as well as the Japs...

I have an offending combat report pws file here if someone can take a look at it?

RE: Allied sub torp hit -> crash

Posted: Sun Oct 18, 2009 9:12 pm
by Don Bowen

A Save!!!!!!!

RE: Allied sub torp hit -> crash

Posted: Sun Oct 18, 2009 9:17 pm
by EUBanana
It's too big to PM unfortunately, I need an email. [:'(]

RE: Allied sub torp hit -> crash

Posted: Sun Oct 18, 2009 9:21 pm
by baghdadbob
Same thing happened in my PBEM game... I am US and my sub torpedoed a Jap CA then CTD.

RE: Allied sub torp hit -> crash

Posted: Sun Oct 18, 2009 9:57 pm
by Don Bowen
ORIGINAL: EUBanana

It's too big to PM unfortunately, I need an email. [:'(]

Attach to this thread.

RE: Allied sub torp hit -> crash

Posted: Sun Oct 18, 2009 10:25 pm
by wdolson
In the tech support forum, the file size limits are relaxed to allow uploading of saved games.

Bill


RE: Allied sub torp hit -> crash

Posted: Sun Oct 18, 2009 10:36 pm
by treespider
ORIGINAL: wdolson

In the tech support forum, the file size limits are relaxed to allow uploading of saved games.

Bill



But de haz to zips dem first mon.

RE: Allied sub torp hit -> crash

Posted: Mon Oct 19, 2009 6:58 am
by EUBanana
Ah ha.

Ok then.


RE: Allied sub torp hit -> crash

Posted: Mon Oct 19, 2009 7:15 am
by Don Bowen

Ran the turn without issue. If you can tell me exactly which submarine makes the attack that causes the dump I will run that attack through the code in detail.

I don't think anyone else is reporting this though, so it might be something specific to your system.

RE: Allied sub torp hit -> crash

Posted: Mon Oct 19, 2009 8:15 am
by EUBanana
ORIGINAL: Don Bowen


Ran the turn without issue. If you can tell me exactly which submarine makes the attack that causes the dump I will run that attack through the code in detail.

I don't think anyone else is reporting this though, so it might be something specific to your system.

@work so from memory - it's the second naval action. AVP Bellatrix gets torpedoed, then some night bombing ,then a US submarine attacks DD Yugure I think it is south of Davao, crash.

RE: Allied sub torp hit -> crash

Posted: Mon Oct 19, 2009 11:03 am
by LoBaron
on second thought this could be a random event. thats the games just failing to react to a situation where an allied torpedo actually DOES explode... [8|]
 

RE: Allied sub torp hit -> crash

Posted: Mon Oct 19, 2009 4:12 pm
by EUBanana
Buh! It happened again, in the Guad scenario this time.

S-38 gets attacked by ASW at night.

Then in the morning S-38 attacks a Jap DD, torpedo hits, crash.


RE: Allied sub torp hit -> crash

Posted: Mon Oct 19, 2009 6:12 pm
by LoBaron
EUBanana have you tried switching everything like 64Bit colors or multi core support off or
didnt you use things like that?

RE: Allied sub torp hit -> crash

Posted: Mon Oct 19, 2009 6:29 pm
by EUBanana
ORIGINAL: LoBaron
EUBanana have you tried switching everything like 64Bit colors or multi core support off or
didnt you use things like that?

No - though this crash didn't happen before, it's a recent thing. Maybe the patch or something did it.

I'll have a go minus the multicore support which I am using.

RE: Allied sub torp hit -> crash

Posted: Tue Oct 20, 2009 7:00 am
by EUBanana
I noticed in the combat report the sub attack is there, but no torpedo hit.

Could this be some sort of sync issue?

RE: Allied sub torp hit -> crash

Posted: Tue Oct 20, 2009 4:01 pm
by Sonny II
ORIGINAL: EUBanana

I noticed in the combat report the sub attack is there, but no torpedo hit.

Could this be some sort of sync issue?


No, it is just a reporting issue - fixed in patch 02.