SUBSIM Radio Room Forums - View Single Post - HELP! SH3-GWX3 Saves CTD.

BigWalleye · 07-15-13, 07:21 AM

I believe the problem is with the added ships. Full title of the mod: GWX 3 Wilhemshafen,St Naz,Schluese and xtra ships V7. It seems some of those extra ships cause the game engine to get indigestion. My problem with corrupted saves always occurred on a patrol after I had sunk at least one ship. Prior to sinking a ship, I could zip all over the freakin' ocean and save, then reload successfully. Once I sank a ship, the probability was high that any save, at any point, would CTD on reload. It didn't seem to matter how far away from land or enemy ships I got, or how long (game or R/T) I waited before saving. And it didn't seem to matter whether the ship I sank was from the stock GWX-modded game or an added one. (Sometimes it was a tramp steamer with the vanilla SH3 skin.)

I know that the guys who did the GWX 3 Wilhemshafen,St Naz,Schluese and xtra ships mod are experienced modders who do good work and test their work before releasing it. (I think Wreford-Brown and BigBoyWooly both had a hand in V7. Hope I didn't overlook anyone.) And I also recognize that V7 has been out for over a year, and I am sure there are others who are using the mod without problems. I don't mean to cast aspersions on anybody's work. Modding takes lots of hard work, creativity, and patience, and it's all made available gratis. I have nothing but respect for anyone who gives a mod to the community.

What I know is that my configuration had a problem with this particular mod, specifically with V7. I don't know whether it is because of a hardware limitation on my rig, or an interaction with another mod, or whatever. I still have no absolute proof that the change has solved my problem. (That involves the old "trying to prove a negative" conundrum.) At the moment, I am grateful to Fitzcarraldo, who at the very least saved me a lot of time by focusing me on a particular issue that he had experienced. I am relieved to be able to get back to playing the game, rather than spending all my gaming time troubleshooting. And, since V6 of the mod appears to work fine for me, I have no motivation to find and fix the issue I have with V7. Maybe I will tackle that chore at some future time.

Perhaps we should bring this to the attention of the mod developers. I am reluctant to call out: "Yer mod's busted!" especially when the problem may be with my configuration. So I prefer to leave it with the statement that I seem to have had a problem with V7 on my rig, and that someone else who is having a similar problem might benefit from my experience (and that of others.)

07-15-13, 07:21 AM	#12
BigWalleye Sea Lord Join Date: Jul 2012 Location: On the Eye-lond, mon! Posts: 1,987 Downloads: 465 Uploads: 0	I believe the problem is with the added ships. Full title of the mod: GWX 3 Wilhemshafen,St Naz,Schluese and xtra ships V7. It seems some of those extra ships cause the game engine to get indigestion. My problem with corrupted saves always occurred on a patrol after I had sunk at least one ship. Prior to sinking a ship, I could zip all over the freakin' ocean and save, then reload successfully. Once I sank a ship, the probability was high that any save, at any point, would CTD on reload. It didn't seem to matter how far away from land or enemy ships I got, or how long (game or R/T) I waited before saving. And it didn't seem to matter whether the ship I sank was from the stock GWX-modded game or an added one. (Sometimes it was a tramp steamer with the vanilla SH3 skin.) I know that the guys who did the GWX 3 Wilhemshafen,St Naz,Schluese and xtra ships mod are experienced modders who do good work and test their work before releasing it. (I think Wreford-Brown and BigBoyWooly both had a hand in V7. Hope I didn't overlook anyone.) And I also recognize that V7 has been out for over a year, and I am sure there are others who are using the mod without problems. I don't mean to cast aspersions on anybody's work. Modding takes lots of hard work, creativity, and patience, and it's all made available gratis. I have nothing but respect for anyone who gives a mod to the community. What I know is that my configuration had a problem with this particular mod, specifically with V7. I don't know whether it is because of a hardware limitation on my rig, or an interaction with another mod, or whatever. I still have no absolute proof that the change has solved my problem. (That involves the old "trying to prove a negative" conundrum.) At the moment, I am grateful to Fitzcarraldo, who at the very least saved me a lot of time by focusing me on a particular issue that he had experienced. I am relieved to be able to get back to playing the game, rather than spending all my gaming time troubleshooting. And, since V6 of the mod appears to work fine for me, I have no motivation to find and fix the issue I have with V7. Maybe I will tackle that chore at some future time. Perhaps we should bring this to the attention of the mod developers. I am reluctant to call out: "Yer mod's busted!" especially when the problem may be with my configuration. So I prefer to leave it with the statement that I seem to have had a problem with V7 on my rig, and that someone else who is having a similar problem might benefit from my experience (and that of others.)