SH3 Commander (current v2.7)

[JScones]

SH3 Commander Release 2.7 is now available!

"Main engine" changes:

• Now reminds player after exiting SH3 to rollback SH3 Commander
• Modelling the effects of malfunctions or malfunctions+sabotage are now Gameplay settings under SH3 Options
• Enhanced crew fatigue model functionality to include other related Basic.cfg file settings
• Now groups Personnel Files by save data folder name
• Added new ship classes and names to Ship names.cfg (credit to bigboywooly, Sailor Steve and AG124)
• Removed fatigue model - Grey Wolves 24 Hour
• Removed UpdtCars.exe (no longer required)
• Minor adjustments to main interface
• Minor adjustments to most Cfg files

Mod changes:

• Removed simulated fuel resupply strategy

Note that prior to installing this release you must *fully* uninstall your current release. Don't forget to rollback SH3 Commander first and back up any SH3 Commander files that you may have modified!

To download, click here or use SH3 Commander's "Update" feature.

After you have installed SH3 Commander you can reapply any add-ons such as the Combined Skin Pack (note that if you plan on using GWX, installing the Combined Skin Pack is not recommended).

Please note that malfunction and sabotage effects are now OFF by default - you must switch the effects on via SH3 Commander's "SH3 Options" screen.

As always, please post your questions/feedback/problems to this thread after reading the readme and FAQ (both files are installed into your SH3 Commander folder and can be accessed by clicking the ? button). Due to other priorities, threads started elsewhere with titles like "Problem" or "Why won't this work", may not receive my attention.

Feel free to post links to this thread in other SH3 related forums.

==IMPORTANT NOTE FOR NYGM USERS==

After installing SH3 Commander R2.7 you need to:

1. reinstall the updated SH3 Commander files provided with the NYGM download;

2. ensure that the "Model effects" option is set to "Malfunctions+Sabotage" within SH3 Commander's "SH3 Options" screen,

==IMPORTANT NOTE FOR GWX Beta USERS==

If you already have a copy of R2.7, please re-download as a few files have been updated. Don't forget to reinstall the updated GWX Cfg files!

[CCIP]

Surely you jest!

Great to see the Old Neccesary still being updated with all the latest. I assume it's already wired for GWX, too?

[JScones]

Originally Posted by CCIP

Surely you jest!

Great to see the Old Neccesary still being updated with all the latest. I assume it's already wired for GWX, too?

GWX users will need to download a small archive containing four files, but otherwise, yes, it's fully "GWX-ready".

[CCIP]

Okay, hopefully it will come with GWX. I'm mostly asking out of concern for the more casual users, after all the questions we get at WaW about the order-of-installations, I'm all too familiar with it.

Again, cheers on the great job done!

[Venatore]

Thanks JScones,

I've noticed you have also updated "MD5 Compare Version 0.9.0" on your site, I have found this to be a very valuable software product.

Once again thankyou for your hard work & contribution to this forum.

[JScones]

Originally Posted by Venatore

Thanks JScones,

I've noticed you have also updated "MD5 Compare Version 0.9.0" on your site, I have found this to be a very valuable software product.

Once again thankyou for your hard work & contribution to this forum.

Thanks. I originally developed a quick-and-dirty MD5 comparer for the purposes of GWX Beta testing. But when I looked around to see what already existed, I found that they were either command line based (and hence non-intuitive) or single file compare only (I'm talking the free and easily accessible ones here). So I re-wrote mine. It supports single file compare either by hash or by file, and by recognising standard MD5 files, supports multi file compare. It also creates standard MD5 files which are compatible with *any* MD5 application that reads standard MD5 files.

I've kept it at v0.9.0 because I haven't developed a help file yet and there are some fancy features I still want to add. But as it is, it's fully functional and should suit most users.

FYI MD5 hashes for GWX d/l files will be clearly listed for users to verify the integrity of their d/l *before* running the installer. An MD5 file will also be made available which can be opened in MD5Compare and which will do all the comparing automatically for you.

[JScones]

Originally Posted by CCIP

Okay, hopefully it will come with GWX. I'm mostly asking out of concern for the more casual users, after all the questions we get at WaW about the order-of-installations, I'm all too familiar with it.

Yep, I've explained to the Kpt the fun that he can expect on this one. And I'm sure that despite the instructions that appear in the GWX installer (in four languages), AND the instructions in the GWX manual AND the instructions in the updated file archive AND the expected explanations and reiterations here and elsewhere, people will still get it wrong.

Fortunately, at least, getting it wrong with GWX is not as critical as it is with NYGM.

But I would ask that players keep their GWX related questions for when GWX is released, as most of these questions will be answered then. If not, then players can ask on the appropriate GWX thread.

[/quote] GWX users will need to download a small archive containing four files, but otherwise, yes, it's fully "GWX-ready".[/quote]

What is this small archive?

Where do we find this dowload?

And at what point in SH3, 1.1patch, GWX, SH3 Commander install process do we install it?

Is it installed into Commander or into GWX?

Thanks.

[JScones]

What is this small archive?

Where do we find this dowload?

And at what point in SH3, 1.1patch, GWX, SH3 Commander install process do we install it?

Is it installed into Commander or into GWX?

Thanks.

How about waiting for GWX to be released first, where I am sure that all will be explained. No point having the GWX files before you have GWX now, is there???

[fredbass]

OK, maybe I missed this in the readme but does Commander 2.7 utilize the weather mod again?

[Capt. Shark Bait]

Originally Posted by JScones

GWX users will need to download a small archive containing four files, but otherwise, yes, it's fully "GWX-ready".

got it, but not yet installed. where might i find thse 4 files needed for GWX? thx

[darkfin]

I appreciate your program. I really can't imagine playing SH3 without it.

Again, thank you for your work.

Jim

[Boris]

Hey JScones, If you roll back SH3 Commander every time after using it, how does that maintain th effects of things such as the combined skin pack. The skin pack only installs at certain dates, and if you start a patrol not near that date, the skins won't install. Or am I wrong?

[JScones]

Originally Posted by Boris

Hey JScones, If you roll back SH3 Commander every time after using it, how does that maintain th effects of things such as the combined skin pack. The skin pack only installs at certain dates, and if you start a patrol not near that date, the skins won't install. Or am I wrong?

Let's say the next patrol start date is 15 Feb 1942. When SH3 is launched via SH3Cmdr, it will copy everything found in every Date folder between 1 Sep 1939 and 15 Feb 1942. Thus it takes a "building block" approach, with newer files overwriting older files.

This makes tasks like changing ship skins quite easy. For example, let's say you wanted to change NKGN skins based on date. You may want early-war skins between 1939 and 1940, grey skins between and 1941 and 1942 and camo skins thereafter.

You'd set up the following SH3Cmdr folder structure...

\SH3 Commander\Date\19390901\data\NKGN\NKGN_T*.tga <these are your early skins which will ALWAYS get copied into SH3>

\SH3 Commander\Date\19410101\data\NKGN\NKGN_T*.tga <these are your grey skins, which will be copied into SH3 if the next patrol start date is 1 Jan 1941 or after, thus overwriting the early skins>

\SH3 Commander\Date\19430101\data\NKGN\NKGN_T*.tga <these are your late war camo skins, which will be copied into SH3 if the next patrol start date is 1 Jan 1943 or after, thus overwriting the grey skins>.

So if you had 15 of each type of skin, the early skins would get copied first, but then overwritten by the 15 grey skins and so on. If you only had say 14 grey skins, then one early skin would always remain as it would never be overwritten (and you may want to deliberately do this).

You're not limited to total changeover at any given date either - you can stagger change, by perhaps introducing some grey skins earlier and some later than 1 Jan 1941. Then players would stumble across convoys with both early and grey skins. More mix and variety.

The other good use is for reflecting historically accurate warship schemes. For example, the Bismarck. You can model her sea trials scheme up to 6 Mar 1941, then her Operation Rheinubung scheme up to 18 May 1941 and her final scheme used when she sailed into the Atlantic.

Rolling back will return all skins to "stock", but when you next run SH3Cmdr, the appropriate skins will be copied in again dependant on the new next patrol start date.

Hope this is clear.

[Boris]

Originally Posted by JScones

Let's say the next patrol start date is 15 Feb 1942. When SH3 is launched via SH3Cmdr, it will copy everything found in every Date folder between 1 Sep 1939 and 15 Feb 1942. Thus it takes a "building block" approach, with newer files overwriting older files.

This makes tasks like changing ship skins quite easy. For example, let's say you wanted to change NKGN skins based on date. You may want early-war skins between 1939 and 1940, grey skins between and 1941 and 1942 and camo skins thereafter.

You'd set up the following SH3Cmdr folder structure...

\SH3 Commander\Date\19390901\data\NKGN\NKGN_T*.tga <these are your early skins which will ALWAYS get copied into SH3>

\SH3 Commander\Date\19410101\data\NKGN\NKGN_T*.tga <these are your grey skins, which will be copied into SH3 if the next patrol start date is 1 Jan 1941 or after, thus overwriting the early skins>

\SH3 Commander\Date\19430101\data\NKGN\NKGN_T*.tga <these are your late war camo skins, which will be copied into SH3 if the next patrol start date is 1 Jan 1943 or after, thus overwriting the grey skins>.

So if you had 15 of each type of skin, the early skins would get copied first, but then overwritten by the 15 grey skins and so on. If you only had say 14 grey skins, then one early skin would always remain as it would never be overwritten (and you may want to deliberately do this).

You're not limited to total changeover at any given date either - you can stagger change, by perhaps introducing some grey skins earlier and some later than 1 Jan 1941. Then players would stumble across convoys with both early and grey skins. More mix and variety.

The other good use is for reflecting historically accurate warship schemes. For example, the Bismarck. You can model her sea trials scheme up to 6 Mar 1941, then her Operation Rheinubung scheme up to 18 May 1941 and her final scheme used when she sailed into the Atlantic.

Rolling back will return all skins to "stock", but when you next run SH3Cmdr, the appropriate skins will be copied in again dependant on the new next patrol start date.

Hope this is clear.

Thanks Jaesen, that's what I wanted to hear! Makes my work alot easier for me...