SH3 Commander Problem now??

So I dont see the Rollback button anywhere in SH3 commander. the only reason Im concerned with using it is because I installed GWX and my sky was always black like clouds looked like black storm clouds and according to Jimbuna this was because I didnt roll back SH3 commander before installing mods (even though I had roll back after every time I exit Sh3) so any ideas guys? and Ive noticed i have "start my patrols at sea" and some other options enabled that dont seem like they want to work?? I may try to uninstall SH3 Commander then reinstall it

[FIREWALL]

Your last sentence is, my answer.

[Gerald]

Wow what a nice response,

[Herr-Berbunch]

With the latest Commander you can set somewhere to auto-rollback, iirc, but a reinstall is a good start

[K-61]

The rollback selection box should display when you click on the options button, under general settings.

[JScones]

No rollback button means there's no files to rollback (I'll assume you know what button to look for as it's explained in the User Guide).

Many years ago it was a standard response to state that not rolling back SH3Cmdr would cause black skies. And certainly, it was true...

...but it wasn't the only reason. It was a possible reason and definitely the best first thing to check.

But it became a minor reason a few years ago. Unfortunately though, some people haven't updated their knowledge and still respond as if everyone's using SH3Cmdr R2.x.

To that end I don't understand how uninstalling SH3Cmdr will fix your problem. The problem is with your game, not SH3Cmdr. Uninstalling SH3Cmdr will only remove the SH3Cmdr installation. Your game will be untouched (even if the cause was a failed rollback - all you'd be doing is removing the "good" backed up game files that SH3Cmdr creates and thus requiring a full game reinstallation anyway).

I'm too lazy to search the forum for you, but I know alternative solutions have been posted. I will start with the obvious fundamental questions though - are you running Vista or Win7 and if so where have you installed SH3 and SH3Cmdr?

Going straight for the reinstall or hard drive reformat (another oddly recommended course of action for these things) without understanding the cause of the problem is akin to cracking a walnut with a jackhammer, or in some cases cracking a walnut with a feather (because it doesn't help). However, if you don't want to wait, then you might as well just uninstall SH3Cmdr and SH3 completely (this means manually deleting the residual files AND the VirtualStore files if you use Vista/Win7 and have installed to Program Files) and start again.

I thought it was a glitch with commander seeing as how I had autorollback on it but I figured out. its in the GWX mod somewhere. after i took SH3 C. 3.2 and uniinstalled I tried again with my mods enabled, same result, then I disabled them all and walla No black skies. so I am going to enable them one by one and find the oen thaat is causing problems (its the GWX mods you can enable with GWX 3.0) thank you for the good explanation though

PS: Many have told me to NOT install SH3 C or JSGME or GWX or SH3 itself to the Programfiles(x86) folder or Programfiles but straight to the C drive can you ask me why this is?? I am running Win7 btw

Originally Posted by JScones

No rollback button means there's no files to rollback (I'll assume you know what button to look for as it's explained in the User Guide).

Many years ago it was a standard response to state that not rolling back SH3Cmdr would cause black skies. And certainly, it was true...

...but it wasn't the only reason. It was a possible reason and definitely the best first thing to check.

But it became a minor reason a few years ago. Unfortunately though, some people haven't updated their knowledge and still respond as if everyone's using SH3Cmdr R2.x.

To that end I don't understand how uninstalling SH3Cmdr will fix your problem. The problem is with your game, not SH3Cmdr. Uninstalling SH3Cmdr will only remove the SH3Cmdr installation. Your game will be untouched (even if the cause was a failed rollback - all you'd be doing is removing the "good" backed up game files that SH3Cmdr creates and thus requiring a full game reinstallation anyway).

I'm too lazy to search the forum for you, but I know alternative solutions have been posted. I will start with the obvious fundamental questions though - are you running Vista or Win7 and if so where have you installed SH3 and SH3Cmdr?

Going straight for the reinstall or hard drive reformat (another oddly recommended course of action for these things) without understanding the cause of the problem is akin to cracking a walnut with a jackhammer, or in some cases cracking a walnut with a feather (because it doesn't help). However, if you don't want to wait, then you might as well just uninstall SH3Cmdr and SH3 completely (this means manually deleting the residual files AND the VirtualStore files if you use Vista/Win7 and have installed to Program Files) and start again.

[JScones]

Originally Posted by USNSRCaseySmith

PS: Many have told me to NOT install SH3 C or JSGME or GWX or SH3 itself to the Programfiles(x86) folder or Programfiles but straight to the C drive can you ask me why this is?? I am running Win7 btw

Sure, why is this?



Seriously, it's to do with the security infrastructure introduced in Vista and continued in Win7. It's called User Account Control. More detail here... http://en.wikipedia.org/wiki/User_Account_Control

One of the UAC triggers are changes to system-wide settings or to files in %SystemRoot% or %ProgramFiles%. Ordinarily, apps programmed to standards wouldn't modify files in Program Files, instead saving changes/settings to the appropriate Application Data folder. But moddable games don't work this way; the intent is to replace core game files with other modded game files. UAC doesn't like this and will either a) fail to action the request (increasing the potential for CTDs) or b) save the file to a VirtualStore folder. This very quickly causes confusion for users. The newer versions of JSGME avoid this problem somewhat, in that they "work" with UAC, however, that won't mitigate problems caused by modding files directly, installing patchs, using SH3Cmdr and so on, which all do the same thing and modify core game files.

Fortunately, you can avoid this mess by simply installing outside of Program Files, as UAC doesn't care what you write to somewhere like "C:\Games".

okay when I uninstall SH3 Cmnder, SH3, and GWX. do I have to manually go in and delete any files like you said there would be?? and what not?? cuz If it stops the chance of CTD I may as well uninstall and all that jaz

[JScones]

Yes and no.

If you intend installing to "C:\Games", then what is left behind after uninstalling from Program Files won't matter. However, for completeness and good housekeeping, you should delete the "Program Files (x86)\Ubisoft\SilentHunterIII" (assuming that is where you installed it) folder as well as the "C:\Users\username\AppData\Local\VirtualStore\Prog ram Files (x86)\Ubisoft\SilentHunterIII" folder (IIRC it's a hidden folder).

Repeat for "Program Files (x86)\SH3 Commander".

Install SH3, JSGME and SH3Cmdr to "C:\Games" and I'm betting you won't have any black sky issues any more.