Annoying crashes.

DaveU186 · 06-11-09, 04:55 PM

Alright geezers.

Basically noticed in my last two careers that trying to reload saves I quite often get a CTD. Now interestingly this begun after I installed SH3Commander 3.2. Save is always accessible but won't load. In Commander the patrol grid changes to NULL seemingly indicating a corrupt patrol file.

Running GWX 3.0 with Alternative Flotillas, Lite Harbour, VIIC41, Integrated Orders, and the XXI 1939 mod as well. As I said when I was running a previous version of SH3Com I had no problems.

I expect there's nothing I can do, but just wondered if anyone had similar experiences.

Letum · 06-11-09, 05:04 PM

Never save within 20km of a ship or land.
One save like this will mess up all the saves for that mission.

DaveU186 · 06-11-09, 05:08 PM

This is the thing though, I follow those rules so this is all the more baffling.

Hanomag · 06-11-09, 05:53 PM

For your reading enjoyment....

http://www.subsim.com/radioroom/show...ash+to+desktop

Nice thread on the CTD...

Murr44 · 06-11-09, 06:06 PM

Quote:

Originally Posted by Letum

Never save within 20km of a ship or land.
One save like this will mess up all the saves for that mission.

Actually it's 50km (or more to be "safer"). Do you have the updated GWX 3.0 files for SH 3 Cmdr installed? These were posted by Viking Granddad (sp?) a while ago (2-3 months).

FUBAR295 · 06-11-09, 08:56 PM

Another consideration is never remove or apply a new mod while on active Patrol. Always do this once you are back at base.

Good Hunting,
FUBAR295

Captain Nemo · 06-12-09, 01:13 AM

Quote:

Originally Posted by Letum

Never save within 20km of a ship or land.
One save like this will mess up all the saves for that mission.

The thing that makes the corrupt save game issue more interesting or annoying depending on how badly you are affected by it, is that it affects some more than others. In three years of playing SH3 I have had only one bad save game and I have saved in all kinds of situations breaking all the rules that have been given to avoid the corrupt save game problem. Maybe I've been lucky so far.

Nemo

Hanomag · 06-12-09, 10:28 AM

Quote:

Originally Posted by Captain Nemo

The thing that makes the corrupt save game issue more interesting or annoying depending on how badly you are affected by it, is that it affects some more than others. In three years of playing SH3 I have had only one bad save game and I have saved in all kinds of situations breaking all the rules that have been given to avoid the corrupt save game problem. Maybe I've been lucky so far.

Nemo

I also can save breaking all the rules, except in port.... that gets ridiculous!

But I also have had a few CTD's they seem to have subsided (knock wood). But I posted my thread mentioned above in the heyday of CTD's.
I usually can reload an earlier save.

I save once outside the "safe save" distance from port. Then once halfway to my patrol area. Then after I reach my patrol area. I always make a new save when plotting intercept or start an attack run. But save over those if successful. That usually covers me if the crash decides to take quantum leaps back through past saves.

But in the end, the CTD issue is just something else we have to live with. As if Hedgehogs werent enough. "Oh the pain..."

Murr44 · 06-12-09, 04:00 PM

The strangest ctd that I've had happened when I "changed a record" on the phonograph. We were going along at 128x & I was getting thoroughly sick of Charlie & His Orchestra; something about that guy's voice just bugs me sometimes, so I changed the record and SH3 "encountered a problem and needed to close".

I wasn't anywhere near land, ships or planes when it happened. This has never happened since (knock on wood).

Like Hanomag said, ctds are something that we all have to live with...

meduza · 06-12-09, 04:25 PM

I had a big crash a few days ago. Not just CTD, but BSOD. I was attack by aircraft and dived, switched to external camera to view the bombs falling (masochistic, I know

). When I switched to F7 screen, the game crashed big time. Unfortunately the BSOD didn't give any meaningful indication of the cause.

Hanomag · 06-12-09, 09:58 PM

Quote:

Originally Posted by meduza

I had a big crash a few days ago. Not just CTD, but BSOD. I was attack by aircraft and dived, switched to external camera to view the bombs falling (masochistic, I know

). When I switched to F7 screen, the game crashed big time. Unfortunately the BSOD didn't give any meaningful indication of the cause.

LOL ..does it ever?... bleh...

06-12-09, 10:25 PM

Just proves the Dev Team were Rushed to a 6 Month limit to Finish SH4
by the Ubisoft Corp,
They chose the Cheapest Country Dev Team To work with,
You decide,,,,,,,
1.5 came with no patches,
No chance to Switch,Upgrade,etc,etc,
Unless paid; The Dev Team would not finish the work.
Blame the Ubisoft Corporation,
SH4 was Rushed too fast too soon in the Making

06-11-09, 04:55 PM	#1
DaveU186 Torpedoman Join Date: Apr 2009 Posts: 112 Downloads: 14 Uploads: 0	Annoying crashes. Alright geezers. Basically noticed in my last two careers that trying to reload saves I quite often get a CTD. Now interestingly this begun after I installed SH3Commander 3.2. Save is always accessible but won't load. In Commander the patrol grid changes to NULL seemingly indicating a corrupt patrol file. Running GWX 3.0 with Alternative Flotillas, Lite Harbour, VIIC41, Integrated Orders, and the XXI 1939 mod as well. As I said when I was running a previous version of SH3Com I had no problems. I expect there's nothing I can do, but just wondered if anyone had similar experiences.

06-11-09, 05:04 PM	#2
Letum Navy Seal Join Date: Feb 2005 Location: York - UK Posts: 6,079 Downloads: 43 Uploads: 0	Never save within 20km of a ship or land. One save like this will mess up all the saves for that mission. __________________

06-11-09, 05:53 PM	#4
Hanomag Grey Wolf Join Date: Jul 2007 Location: LI NY Posts: 964 Downloads: 13 Uploads: 0	For your reading enjoyment.... http://www.subsim.com/radioroom/show...ash+to+desktop Nice thread on the CTD... __________________ "Only if I can save first..."

06-11-09, 08:56 PM	#6
FUBAR295 Krusty Krab Join Date: Mar 2002 Location: Decks awash in the North Atlantic Posts: 1,450 Downloads: 493 Uploads: 0	Another consideration is never remove or apply a new mod while on active Patrol. Always do this once you are back at base. Good Hunting, FUBAR295 __________________ Good judgment comes from experience. Unfortunately, the experience usually comes from bad judgment.

06-12-09, 04:25 PM	#10
meduza Ace of the Deep Join Date: Apr 2007 Location: on patrol Posts: 1,035 Downloads: 40 Uploads: 0	I had a big crash a few days ago. Not just CTD, but BSOD. I was attack by aircraft and dived, switched to external camera to view the bombs falling (masochistic, I know ). When I switched to F7 screen, the game crashed big time. Unfortunately the BSOD didn't give any meaningful indication of the cause. __________________

06-11-09, 05:08 PM	#3
DaveU186 Torpedoman Join Date: Apr 2009 Posts: 112 Downloads: 14 Uploads: 0	This is the thing though, I follow those rules so this is all the more baffling.

06-12-09, 04:00 PM	#9
Murr44 Grey Wolf Join Date: Mar 2008 Posts: 913 Downloads: 16 Uploads: 0	The strangest ctd that I've had happened when I "changed a record" on the phonograph. We were going along at 128x & I was getting thoroughly sick of Charlie & His Orchestra; something about that guy's voice just bugs me sometimes, so I changed the record and SH3 "encountered a problem and needed to close". I wasn't anywhere near land, ships or planes when it happened. This has never happened since (knock on wood). Like Hanomag said, ctds are something that we all have to live with...

06-12-09, 10:25 PM	#12
owner20071963 Stowaway Posts: n/a Downloads: Uploads:	Just proves the Dev Team were Rushed to a 6 Month limit to Finish SH4 by the Ubisoft Corp, They chose the Cheapest Country Dev Team To work with, You decide,,,,,,, 1.5 came with no patches, No chance to Switch,Upgrade,etc,etc, Unless paid; The Dev Team would not finish the work. Blame the Ubisoft Corporation, SH4 was Rushed too fast too soon in the Making