SH3 commander kills my campaigns... (NYGM 2.0)

Agdune · 07-27-06, 09:13 AM

Okay, here's the situation breifly. I've put GW away for a bit, since I hear that NYGM is harder/more realistic. I use generic mod enabler to remove GW and then put in NYGM 2.0. I run a single mission and think "wow! the destroyers actually ping me now!" (I'd been having a problem where destroyers absoloutley never used sonar, no idea why, but that's a different problem), and everything's great.

So I get out of SH3 and start up SH3 commander, to make a new career starting 1939, everything's quite normal and happily running along at this stage. I boot up the game, select the new career, do all the pre-mission setup and start the mission. The progress bar gets halfway and stops. 15 minutes later, it's still there, and i find that the computer's not responding.

I reset and start messing with the program directory, thinking that my careless mod enabling has caused some problems, and that I can fix things by juggling things around. No luck, a full day of messing around with files/mods gives no result, so I uninstall SH3 and remove all traces of sh3 related programs from the computer, for a fresh install. I install SH3, patch it, put in the generic mod enabler, NYGM 2.0 and Fubar's skin pack (what? I like the sexy, new looking U-boats, allright?! :p). I start a test campaign at every step, and they all work perfectly. Then I install SH3 commander (ver 2.6.0.120), make a new campaign and start. The loading bar gets halfway and stops, just like it did before.

"maybe it's because I'm starting a new campaign through SH3C" I think, and start SH3 through it's default exe file, then load the new campaign I tested before installing SH3C... same result. My only choice is to say that SH3C in combination with NYGM 2.0 is causing my campaigns to fail loading.

Can anyone explain why, or tell me how to fix this?

edit: I Did a google search to see if it was a semi-common problem, but didn't turn anything up. Sorry if this is one of those things that's fixed easily by a mod patch or something :p

07-27-06, 09:13 AM	#1
Agdune Swabbie Join Date: Jul 2005 Posts: 5 Downloads: 22 Uploads: 0	SH3 commander kills my campaigns... (NYGM 2.0) Okay, here's the situation breifly. I've put GW away for a bit, since I hear that NYGM is harder/more realistic. I use generic mod enabler to remove GW and then put in NYGM 2.0. I run a single mission and think "wow! the destroyers actually ping me now!" (I'd been having a problem where destroyers absoloutley never used sonar, no idea why, but that's a different problem), and everything's great. So I get out of SH3 and start up SH3 commander, to make a new career starting 1939, everything's quite normal and happily running along at this stage. I boot up the game, select the new career, do all the pre-mission setup and start the mission. The progress bar gets halfway and stops. 15 minutes later, it's still there, and i find that the computer's not responding. I reset and start messing with the program directory, thinking that my careless mod enabling has caused some problems, and that I can fix things by juggling things around. No luck, a full day of messing around with files/mods gives no result, so I uninstall SH3 and remove all traces of sh3 related programs from the computer, for a fresh install. I install SH3, patch it, put in the generic mod enabler, NYGM 2.0 and Fubar's skin pack (what? I like the sexy, new looking U-boats, allright?! :p). I start a test campaign at every step, and they all work perfectly. Then I install SH3 commander (ver 2.6.0.120), make a new campaign and start. The loading bar gets halfway and stops, just like it did before. "maybe it's because I'm starting a new campaign through SH3C" I think, and start SH3 through it's default exe file, then load the new campaign I tested before installing SH3C... same result. My only choice is to say that SH3C in combination with NYGM 2.0 is causing my campaigns to fail loading. Can anyone explain why, or tell me how to fix this? edit: I Did a google search to see if it was a semi-common problem, but didn't turn anything up. Sorry if this is one of those things that's fixed easily by a mod patch or something :p