Problems with SH3 Commander? Check here first!

[JScones]

In an attempt to create a pseudo FAQ, I thought I'd start this topic for players to post any questions or problems that they may have with SH3 Commander (SH3Cmdr). Between myself, Beery and other experienced SH3 Commander users, most questions or problems can be quickly and easily resolved.

If you have a question or problem with SH3 Commander, check here first to see if an answer already exists. If one doesn't, please post your question here.

I tend not to read every topic posted to the forums, so by posting to this topic you will ensure that your problem is read by me, let alone Beery or other experienced users. And you may save yourself some time by finding that your question may already have been answered! ;)

[JScones]

OK, let me start...

Q: What is SH3 Commander?
A: Full readme can be found here (http://members.iinet.net.au/~jscones/software/SH3Cmdr%20Help.html).

Q: What is the latest release/version of SH3 Commander and where can I download it?
A: The latest release is 2.3. Whilst many sites host SH3 Commander, you can be assured of always getting the latest release by clicking on one of the links in the signature block below.

Q: I use Windows 98 or Windows ME, will SH3 Commander work for me?
A: No, SH3 Commander will only work on Windows XP or Windows 2000, the same operating systems as required by SH3. SH3 Commander uses core system functions which are not available on Windows 98 or Windows ME.

Q: What's the difference between SH3Cmdr2x.exe and SH3Cmdr2xLite.exe?
A: SH3Cmdr2x.exe includes all main files and mods. SH3Cmdr2xLite.exe includes all main files but excludes the Merchant Variety Pack (new ship skins). If you are currently running SH3 Commander release 2.2 or greater, you will already have the Merchant Variety Pack installed and thus can save download time by taking the Lite version. Alternatively, you can use the Lite version if you do not wish to install the Merchant Variety Pack. It's your choice.

Q: Do I have to install via JSGME?
A: No, SH3 Commander is a stand alone third party application. You install it as you would any other application, to a location of your choice.

Q: Do I have to have RUb, IUB or any particular mod installed?
A: No, SH3 Commander is not dependant on any existing mods.

Q: Where are my career history details stored? Will they be overwritten if I install a new version?
A: All career history details and game settings are stored in SH3Cmdr.ini. This file is never overwritten by upgrades.

Q: When I open SH3 Commander I get a screen full of "Error!" labels and/or error messages saying that SH3 Commander cannot write to, or access, certain game files. What's wrong?
A: This usually occurs if:
- you attempt to run SH3 Commander on an unsupported operating system (see above);
- you are not logged in under your Computer administrator account - ensure you have logged in as the Computer administrator (check under Control Panel|User Accounts);
- you have a firewall, antivirus or other system monitoring software that intercepts attempts to modify files - turn off all such applications and test again. If all is fine, switch each one back on individually, noting the application which is causing the conflict. You may be able to adjust settings to allow compatibility.
- in an attempt to create a shortcut to SH3 Commander on your desktop, you actually moved the SH3Cmdr.exe file - in this case you will receive at some point a "file not found" error message which will include your desktop folder location.
- the certain game files are read-only - ensure that no SH3 file has the read-only attribute set.

Q: I've modified some of my game files like Basic.cfg and en_menu.txt. Will SH3 Commander overwrite them with its own versions? Does it back up files first before modifying them?
A: SH3 Commander only modifies specific sections of files based on the SH3 Options that you select (only exception is the realistic U-boat availability dates which are not selectable. See further below for ways to adjust or remove these changes). If, for example, you choose a fatigue model, only the relevant fatigue values are written to Basic.cfg. All other values remain unchanged. Every file that SH3 Commander modifies is backed up first and can be restored by pressing the "Rollback SH3" button.

Q: When I press "Launch SH3!" SH3 Commander seems to hang or take a while to integrate the changes I want before loading SH3. Why is it so slow?
A: Slowness usually occurs if you have a firewall, antivirus or other system monitoring software that intercepts attempts to modify files - turn off all such applications and test again. If all is fine, switch each one back on individually, noting the application which is causing the conflict. You may be able to adjust settings to allow compatibility.

Q: I've just installed a new mod and since running SH3 Commander again my game is crashing/not working/acting strange. What's wrong?
A: In order to avoid any potential file integrity problems, ALWAYS perform a rollback in SH3 Commander BEFORE enabling or disabling any mods either via JSGME or manually - this includes uninstalling and installing Silent Hunter III. If you do not rollback before installing new mods, SH3 Commander may simply overwrite the updated files with the backup files it created the last time that you used SH3 Commander, thus potentially causing game instability.

Q: Since using SH3 Commander I can no longer hear speech or most sound effects. What sound files does SH3 Commander overwrite?
A: SH3 Commander does not overwrite any game sound files. This problem will occur if you set the "Character animations", "Sound effects" and/or "Particle rendering" Time Compression events to 1. Reset each event back to the default value and try again (a Rollback is not sufficient to reset these settings). If your problem persists, scrutinise any new mods that you have installed since you last had full sound.

Q: Can I run SH3 Commander with mid-patrol careers?
A: Yes, with SH3 Commander you no longer need to load SH3 directly. You can load SH3 via SH3 Commander on all new, existing, in base, or mid-patrol careers. SH3 Commander recognises the status of each career and disables or enables your realistic settings based on "where you are" at that point in time. You will not be retired nor will you lose crewmen if you start a mid-patrol career (assuming those two realistic options are set).

Q: Will changes I make via the Crew Manager be recognised within Silent Hunter III?
A:
- awarding *any* qualifications to officers impacts compartment efficiency as if they were awarded via Silent Hunter III;
- awarding the *first* qualification to a Chief Warrant Officer impacts compartment efficiency as if awarded via Silent Hunter III;
- awarding subsequent qualifications to a Chief Warrant Officer, whilst being recognised in Silent Hunter III, has no effect in Silent Hunter III;
- awarding a qualification to a Petty Officer impacts compartment efficiency as if awarded via Silent Hunter III;
- awarding a qualification to a seamen, whilst being recognised in Silent Hunter III, has no effect in Silent Hunter III;
- awarding any medal or badge has the same effect as if awarded via Silent Hunter III;
- promoting/demoting has the same effect as if awarded via Silent Hunter III (although there is no demotion via Silent Hunter III);

So, only qualifications awarded to seamen or extra qualifications awarded to Chief Warrant Officers are, despite being recognised in the game, not effective in the game.

Now, whilst these qualifications are not effective in Silent Hunter III, they are still handy "markers". Also, I know of some people who believe that despite not being recognised towards compartment efficiency, Silent Hunter III tends to align these qualified seamen to their respective compartments, but I haven't tested that myself.

Q: What is a 'Weddigen'?
A: Prior to 1 January 1940, the 1st Flotilla was known as U-Flotilla 'Weddigen', the 2nd Flotilla as U-Flotilla 'Saltzwedel' and the 7th Flotilla as U-Flotilla 'Wegener'. SH3 Commander includes a mod which ensures that these correct names are used prior to 1 January 1940.

Q: How do I get real ship names in my Patrol Logs?
A: Firstly select the "Use real ship names in patrol logs" option under SH3 Options|Career Options.

Then, when you next generate a Personnel File for a selected career, the stock SH3 ship names will be updated with real random ship names. After every patrol, generate a Personnel File again to update your latest patrol results and you'll always be up-to-date with real ship names. These ship names will display in both the SH3 Commander Personnel Files and SH3 itself.

Unfortunately, SH3 isn't flexible enough to record different ship names during a patrol, so the standard names will always be recorded.

Q: Where are my Personnel Files saved?
A: All Personnel Files are saved under your ..\SH3 Commander\Personnel Files\ folder, ready for easy moving or uploading to the internet. Re-generate whenever you want to update one for your selected career.

Q: I keep getting allocated the same patrol grid - what's up with SH3 Commander?
A: SH3 Commander does not interfere with the assigning of patrol grids, apart from giving players the ability to change an SH3 assigned grid. This problem seems exclusive to players that are running the milk cow mod, either as part of IUB, HT1.x or by itself.

Q: This realistic U-boat availability stuff sounds good, but I want my new U-boat now! What can I do?
A: U-boat availability in the stock SH3 applies equally to all Flotillas even though some Flotillas often received a U-boat type months after the type was available to other Flotillas. In addition, the stock SH3 really got it wrong with the 1st Flotilla!

SH3 Commander corrects these anomolies by providing availability dates that reflect the real dates experienced by each individual Flotilla, plus providing more accurate training times when updating across types. It means that you will generally have to wait longer for new boats, particularly if you are in the 1st Flotilla. It also means that the VIIC/42 no longer becomes available at all, as none were ever built!

So, want to revert back to the stock SH3 U-boat availability dates? Simply edit or delete 'U-boat availability.cfg', located in your SH3 Commander\Cfg folder. Follow the instructions outlined in the header of the file if you want to tailor the dates to your liking. You may find values in the file that appear strange (like the 1st Flotilla receiving VIIC's before VIIB's), but that's how it was in real life!

Q: I've just finished the first patrol in a new career. However, despite sinking ships, none show up in my game summary or Personnel File. Where's the tonnage for my sunken ships gone?
A: This is the biggest bug with the regular (unmodded) game. If you upgrade your U-boat equipment before going on your first patrol it will not record any tonnage for that patrol. To avoid this problem, do not upgrade equipment until *after* completing your first patrol.

[Maverick_[GER]]

Thanks for the great tool. I use SH3Cmdr since version 2.2 and I love it. :up:

With Commander release 2.3 I have a problem to start SH3. :(

If I press the "Lauch SH3!" button I get the error message "File access denied."! http://www.my-smileys.de/smileys2/shocked3_2.gif

http://mitglied.lycos.de/maverick_ger/PIC/SilentHunterIII/SH3_Commander.jpg

What do I make wrong? :hmm:

[JScones]

This will occur if a file SH3Cmdr is attempting to write to is marked as read-only. Rollback then check your "scene.dat" file (in the \data folder), the most likely culprit if everything worked fine under release 2.2.

[Maverick_[GER]]

This will occur if a file SH3Cmdr is attempting to write to is marked as read-only.
You were right. There "scene.dat" was read-only. :oops:
I have no idea why it was write protected. :hmm:
No matter, now everything is fine. Thanks for your help. :up:

[JScones]

Great. I've updated the FAQ with this problem and solution.

[Jagdtiger]

Hi,

please help me:

I've reinstalled my Win XP and then I've installed SH3 EMEA version with 1.4b patch. All sounds were ok. Next, I've installed RUB 1.45, sound still ok. Then I've installed SH3 Commander 2.3 (selfextracted version and 7zip version) and started game (by SH3 Cmdr). Arrrgh! I've lost many sounds (almost all sounds of my my crew and AA guns for example). In my opinion, SH3 simply doesn't play sound files. There was no problem with SH3 Cmdr 2.2

Thanks for help

[Beery]

Hi,

please help me:

I've reinstalled my Win XP and then I've installed SH3 EMEA version with 1.4b patch. All sounds were ok. Next, I've installed RUB 1.45, sound still ok. Then I've installed SH3 Commander 2.3 (selfextracted version and 7zip version) and started game (by SH3 Cmdr). Arrrgh! I've lost many sounds (almost all sounds of my my crew and AA guns for example). In my opinion, SH3 simply doesn't play sound files. There was no problem with SH3 Cmdr 2.2

Thanks for help

It has to be something else you did. SH3 Commander simply doesn't overwrite any sound files other than those found in the gramophone folder. RUb 1.45 does impact some of the sounds you're talking about (gunfire sounds etc.), so you might want to double check that RUb didn't overwrite those files.

[JScones]

Have you tinkered with the Time Compression settings via SH3Cmdr at all? If so, check out HEMISENT's posts here (http://www.subsim.com/phpBB/viewtopic.php?t=42005&postdays=0&postorder=asc&start=300).

Hmmm...I'll add this q&a to the FAQ anyway...

[Rubini]

JScones,
Beery,

I notice that when I reload a saved game in mid patrol I have a small error on the "News mod" in the load screen (this is ok when I load a new patrol in base). The small error is in the line when you should read the "monthly Uboat loses and tonnage". In the final of this line i see the name of my saved game and not the entire correct phrase!!???

Any advice here?

Rubini.

[joea]

I have been having crashes loading mid patrol saves every time and it's starting to annoy me. I have been racking my brain, one thing I think I have been doing differently is before I loaded SH3 from the game loading a mid patrol save while now I always load with SH3 Commander, and play single missions with it between loading the mid patorl saves. Probably wrong though.

[Beery]

JScones,
Beery,

I notice that when I reload a saved game in mid patrol I have a small error on the "News mod" in the load screen (this is ok when I load a new patrol in base). The small error is in the line when you should read the "monthly Uboat loses and tonnage". In the final of this line i see the name of my saved game and not the entire correct phrase!!???

Any advice here?

Rubini.

It's an occasional bug. It does no harm. I think it has to do with that part of the file being expanded to include a news report. The best thing to do is try to ignore it.

[Wijbrandus]

Apologies for asking a basic question, but I'm doing something wrong and I don't know what.

I've got SH3 with the latest patch, and I installed SHCommander 2.3. (Very nice, by the way.)

What I don't understand is how to install a mod. I tried to add in a few with JSGME, and that program says they went in, but they don't kick in when I start the game.

I did do a roll-back first, but I think I'm missing a step, or doing too much. Do I need to keep SHCommander open while I enable a mod? I get a message that no changes have been saved when I close it before enabling. When I leave SHCommander running, do a roll-back, and then activate the mod, still nothing in the game.

I guess I need a step by step. Where am I going wrong?

[Herr Karl]

Hmmm...not sure but did you create a Mod Folder in SHIII? That needs to be done first before using the mod enabler.

[JScones]

I did do a roll-back first, but I think I'm missing a step, or doing too much. Do I need to keep SHCommander open while I enable a mod? I get a message that no changes have been saved when I close it before enabling. When I leave SHCommander running, do a roll-back, and then activate the mod, still nothing in the game.

1. Open SH3 Commander and press "Rollback SH3" if enabled;
2. Exit SH3 Commander. Click "Yes" to the "Game files will not be updated..." message;
3. Install mod by following the great step-by-step guide here (http://forums.ubi.com/groupee/forums/a/tpc/f/857101043/m/3031058373).

That's it.

[Rubini]

Beery wrote
It's an occasional bug. It does no harm. I think it has to do with that part of the file being expanded to include a news report. The best thing to do is try to ignore it.

Ok. I can live with it! :up:

Rubini.

[GT182]

I've tried everything suggested here and SHIII will not load at all. All I get is the intros and when the game loads, as soon as the red bar stops "Error" messg shows. I even changed to SHIII Commander Lite, did the rollback and the readme thing and reboot pc. Nada, no SHIII.

[snowsub]

just a quick Q with regards to the random folder.

making a randon folder date of say: 19400626 on haveing files in them (say gramophone ones) will they be installed from every date from the 26-06-1940 until the next folder date (say 5-12-1940).

If that sounds right?

basically I'm asking is that if I greate folders for every month date
19390901
19391001
19391101
19391201
19400101
19400201
19400301
...
...
etc

when I load the game in 16-01-1940 i'll only get the files from the 19400101 folder and not all the ones before??, and when i get int0 february the files will be updated from the 19400201 folder??

That's the way I guess it'd work but just checking.

[JScones]

No, not quite right. Using your example, how it works is that every *unique* file in *all* folders previous to 16/1/40 will be copied into the game. Where files are duplicated (or more to the point, have the same names) across the date folders, only those files in the *last* date folder will be copied across.

This avoids duplication as you do not need to put every file into every date folder for it to be copied into the game - the files only need to be put into the *earliest* date folder and will always be copied into the game until replaced with files with the *same* name in a later date folder, which will from then take their place.

Example, with copied files in bold:

19390901 FILEA, FILEB
19391001 FILEC, FILED
19391101 FILEA, FILED
19391201 FILEB
19400101 FILEE, FILEA
CURRENT DATE 19400116
19400201 FILEA, FILEF
19400301 FILEB, FILEC

Each duplicate file could be an updated ship skin, or sound file (ie like Radio.wav).

[Highbury]

Hello, using the latest IuB and the latest SH3 Commander.

My question is, in the file U-boat numbers.cfg in the cfg folder found in the SH3 Commander directory, the values for the Type IIA are as follows:

[IIA]
ALL=1,2,3,4,5,6

This being historically accurate, is exactly how I want it. The problem is, I start a new career via SH3 Commander, load the game, select the Flotilla and year as set in SH3 Commander (1st and 1939 obviously since I am going for the IIA) and I still get boats numbered into the 20's. Why is this?

[Beery]

Hello, using the latest IuB and the latest SH3 Commander.

My question is, in the file U-boat numbers.cfg in the cfg folder found in the SH3 Commander directory, the values for the Type IIA are as follows:

[IIA]
ALL=1,2,3,4,5,6

This being historically accurate, is exactly how I want it...

But it's not historically accurate. The Type IIA was not used by any flotilla featured in the game. In fact, all Type IIAs were school boats, and if they saw combat at all they only saw combat as school boats. This type should be the Type IIB, which served extensively with 1st Flotilla, and which is what the latest version of RUb and SH3 Commander models, but there's no way (as far as I know) to change the actual U-boat type number in the game.

[trebby]

Hello JScones!

Still very happy with SH3 Commander, no complaints here!
The other day you mentioned working on a new version to be released (possibly) around Christmas.
I would like to ask you if it were possible to:

1.Keep the random career length as is
2. After retiring after some missions as dictated by SH3 Commander,
an option to re-activate the career a year or so later to simulate some BdU time as was done historically. Those commanders usually continued their career (Kentrat,Gysae,Lüth ect) in an IXD2. In middle 1942-1943.

That would be really great....

Cheers, trebby

[Highbury]

Hello, using the latest IuB and the latest SH3 Commander.

My question is, in the file U-boat numbers.cfg in the cfg folder found in the SH3 Commander directory, the values for the Type IIA are as follows:

[IIA]
ALL=1,2,3,4,5,6

This being historically accurate, is exactly how I want it...

But it's not historically accurate. The Type IIA was not used by any flotilla featured in the game. In fact, all Type IIAs were school boats, and if they saw combat at all they only saw combat as school boats. This type should be the Type IIB, which served extensively with 1st Flotilla, and which is what the latest version of RUb and SH3 Commander models, but there's no way (as far as I know) to change the actual U-boat type number in the game.

LOL I am NOT saying that the deployment of boats is accurate and my question was in no way about that. My post was about the DESIGNATION NUMBERS on the boats. Your quote of me left that part out. I stated that having the IIAs numbered 1 thru 6 was historically accurate, not the deployement of them in 1st. Flt. You do great work Beery and I have played enough WW2 games to expect the resident "Forum Historical Accuracy Police" but please understand the post first.

Anyways... my question is still unanswered. Why are boats of the IIA type numbered higher then 6 when the U-boat numbers.cfg supplied with SH3 Commander seems to show them as limited to 1 - 6 only? (I know that "but there's no way (as far as I know) to change the actual U-boat type number in the game" was in your post Beery, but then why would this file exist?)

[Beery]

Anyways... my question is still unanswered. Why are boats of the IIA type numbered higher then 6 when the U-boat numbers.cfg supplied with SH3 Commander seems to show them as limited to 1 - 6 only? (I know that "but there's no way (as far as I know) to change the actual U-boat type number in the game" was in your post Beery, but then why would this file exist?)

I think there's a miscommunication somewhere. I am understanding your post, but deployment does come into it, since the reason RUb and SH3 Commander doesn't model the Type IIA is because of deployment issues, and therefore it doesn't use Type IIA boats or numbers. My SH3 Commander U-boat numbers.cfg file has the following numbers for the Type IIA:

[IIA]
ALL=8,9,11,13,15,17,19,20,21,22,23,24,56,57,58,59, 60,61,62,63
902=8,9,11,13,15,17,19,20,21,22,23,24,56,57,58,59, 60,61,62,63

I'm not sure if that's what the current release has, but it will be in the final release and it's correct for the Type IIB as far as I know. We can only fix so many things at a time, and this may not have been fully implemented in earlier versions. I must admit I'm not as 'in-the-loop' as I used to be on these issues, so I can't give a more precise answer than that.

[kriller2]

I cant get SH-commander to work... It says something about "File acess denied" ? allthough I make the folder and files writeable the files suddenly is write protected when I run sh commander??

[JScones]

I cant get SH-commander to work... It says something about "File acess denied" ? allthough I make the folder and files writeable the files suddenly is write protected when I run sh commander??
Covered above in the FAQ - "Q: When I open SH3 Commander I get a screen full of "Error!" labels and/or error messages saying that SH3 Commander cannot write to, or access, certain game files. What's wrong?". Also, the first few responses in this thread cover this scenario.

[finchOU]

Started up my first career with SH3 Commander (lastest verison as of two weeks ago).....after the first patrol I docked at my starting point only to exit and have my tonnage taken away...so I researched for a bug and found that their is a bug with the above problem.....so I stopped docking and used the "Dock at" function (with in 25 km of base...hit exit patrol...yada yada)

So after my first career came to an end at 6 patrols I start a new one about the time my other one left off....I get back to base after the patrol and exit with in 25km....but ...no tonnage awarded???? me thinks something is a miss here???

Game bug or SH3 commander bug?....any specific actions Im missing for starting a new Career a la SH3 commander to cause this?

Specs:
Intel P4 2.8gh, 512 ram, GeForce 6600 GT (forceware 81.95)

MODS: RUB, SH3 commander....thats it so far.

[Beery]

...So after my first career came to an end at 6 patrols I start a new one about the time my other one left off....I get back to base after the patrol and exit with in 25km....but ...no tonnage awarded???? me thinks something is a miss here???

Game bug or SH3 commander bug?...

It's a game bug. If you want to avoid this bug, you have to avoid upgrading your U-boat's equipment before the first patrol.

[finchOU]

ah!!! ...Yahtzee!!!!...thanks man :up: ....I do remember up-grading something....hydrophone i think....lesson learned (hopefully)

[kriller2]

Covered above in the FAQ - "Q: When I open SH3 Commander I get a screen full of "Error!" labels and/or error messages saying that SH3 Commander cannot write to, or access, certain game files. What's wrong?". Also, the first few responses in this thread cover this scenario.

Yes I know but as I unprotect the files in sh3, the files suddenly protect itself, so I cant use the sh-comannder, quite anoying... Hope someone can help? because as it is now, I can't use this program which is a shame... :(

[JScones]

Covered above in the FAQ - "Q: When I open SH3 Commander I get a screen full of "Error!" labels and/or error messages saying that SH3 Commander cannot write to, or access, certain game files. What's wrong?". Also, the first few responses in this thread cover this scenario.

Yes I know but as I unprotect the files in sh3, the files suddenly protect itself, so I cant use the sh-comannder, quite anoying... Hope someone can help? because as it is now, I can't use this program which is a shame... :(
I'd be looking at your antivirus, firewall or any installed system monitoring software. If your SH3 files are somehow read-only (they shouldn't be by the way), and you remove the read-only attribute but it comes back on, that's something you or your system is doing. Curiously, are all SH3 files affected, or just some? Perhaps it's permissions related - I assume you are running WinXP and logged in under the Admin account?

[johnlax]

JS Can you help? I have win xp SH III patch 1.4b I was hoping to get a mod that allows for Milk Cow re-supply. I was told to secure Rubini's 1.47 Harbor traffic mod and this can be achieved. Then I was advised to install a mod enabler which I did (jsgme). I started running career patrols after I installed the above and did not notice any Milk Cows or extra Harbor traffic . Now I am being told that I need to install SH III Commander to make all the features of Rubini's mod work. Is this correct and if so what steps do I now do to get commander on my system. Do I need to deactivate Rubini's mod or can I install Commander as it is right now? Please help I feel like I am running in circles.

[JScones]

JS Can you help? I have win xp SH III patch 1.4b I was hoping to get a mod that allows for Milk Cow re-supply. I was told to secure Rubini's 1.47 Harbor traffic mod and this can be achieved. Then I was advised to install a mod enabler which I did (jsgme). I started running career patrols after I installed the above and did not notice any Milk Cows or extra Harbor traffic . Now I am being told that I need to install SH III Commander to make all the features of Rubini's mod work. Is this correct and if so what steps do I now do to get commander on my system. Do I need to deactivate Rubini's mod or can I install Commander as it is right now? Please help I feel like I am running in circles.
Getting HT to work is a question for the mod developer, Rubini, or experienced HT mod users. Whether HT needs SH3Cmdr and how they should work together is another question for Rubini or HT users. I'd be surprised though if this wasn't covered in the HT readme. You may have better luck posting this question to the HT1.47 thread (actually, a quick scan of that thread sees that this question has been answered). It's just that I've never used HT so don't know it that well.

Now, getting SH3Cmdr to work is simply a matter of downloading (from one of the links in my sig - the lite version differs only by excluding the random ship skins) and installing to a place of your choice - you don't need to uninstall any mods. After installing, read the SH3Cmdr Help.html file which provides more information (you can find it online here (http://members.iinet.net.au/~jscones/software/SH3Cmdr%20Help.html)). The first screen you will need to visit is "SH3 Options", which allows you to set career and gameplay preferences. FAQs can be found on page 1 of this topic.

[GT182]

If I may, SHII Commander 2.3 works very good with HT1.47. Makes the game even more real as campaign stats are saved for you and the crew.

Just make sure it's installed BEFORE you start a patrol (be in port is the only requirement while running a campaign) or it will corrupt the whole game and you'll have to do a complete reinstall. I found out the hard way by accident and lost 27 patrols. ;) No one's fault but mine.

[JScones]

If I may, SHII Commander 2.3 works very good with HT1.47. Makes the game even more real as campaign stats are saved for you and the crew.

Just make sure it's installed BEFORE you start a patrol (be in port is the only requirement while running a campaign) or it will corrupt the whole game and you'll have to do a complete reinstall. I found out the hard way by accident and lost 27 patrols. ;) No one's fault but mine.
Hehe...did you read my response in the UBI forum here (http://forums.ubi.com/groupee/forums/a/tpc/f/2881085392/m/3251036973)? ;)

[Skweetis]

Here's a weird one for you...

I was using SH3 Commander (full) just fine, no problems. No I have noticed that the Flotilla names are back to default. I.e. in SH3 Commander, the flotilla's are called 1st Flotilla, 2nd Flotilla, etc. where as it used to be Werdigen and so on.... the start locations are also different. IRolled back sh3C, unloaded RuB 1.45 with the JSGE (its the only mod I have) and completely uninstalled SH3C, and SHIII, deleted all the folders... and reinstalled from new, in this order: SH3, Patch 1.4b, RuB 1.45, SH3Cdr, launch SH3 start a carrer, start patrol, end patrol exit SH3, then launch SH3Cdr to create a new carreer and it STILL no longer shows the flotilla names.....

Very confusing... the only file I saved/restored from SH3Cdr is the Crew Fatigue Models (i added one of my own.)

What am I missing? and why did it change?

Thanks!

Jamie

[Marhkimov]

Possibly SH3Cmdr might not be working...

Are you sure you installed it correctly? Can you confirm that it is indeed working?


Other than that, I have no ideas.

[Skweetis]

It should be, because crew changes I have made in SH3Cdr are reflected in SH3, it just seems to be flotilla names (in the SH3Cdr pulldown, and SH3) and starting ports (I distinctly remember them being different with a different Captain for the same dates.

Kinda creepy.

Used the install sheild, so I cant see that being a problem.

[Skweetis]

NEVERMIND.... im an idiot! Can a moderator help me salvage my pride, and remove my and related posts in this thread!

[JScones]

THIS THREAD CAN BE UNSTICKIED - FAQ NOW FORM PART OF RELEASE 2.4 AND CAN ALSO BE FOUND HERE (http://members.iinet.net.au/~jscones/software/SH3Cmdr%20FAQ.html).

[jackcford]

Yeah! 2.4 is up and working, a big thank you.....

One problem that I cannot find an answer for in the FAQ or elsewhere is that it doesn't seem to like Improved U-Boatv102. SHIII starts from SHIIICmdr until Improved U-Boatv102 is activated then SHIII hangs at start up. I did the roll back and deactivated all mods first but still this problem?

Also I'm a little unclear about the extra skins (which are installed as per the instruction) does SHIIICmdr automatically select them according to date and is any other mod required to make them work?

Any ideas please

[U768]

Good work with this new version of SH3 to Command.
But unfortunately I have a problem with the creation of career!
By choosing the year, I acquire the following message of error:

Access violation at address 7C9231144 in moddule'ntdll.dll'. Write of adress 00403FE9

I did not find answer in FAQ.
Thank you for helping me.

[JScones]

You sure you're running Windows XP or 2000?

[U768]

Windows Xp pro Sp2 French version.

[JScones]

Interesting that you get a fatal OS error when simply reading a text file...

Does it make a difference if you have the "Correct U-boat availability dates" option selected (or whatever opposite to your current setting)?

Did you upgrade from SH3Cmdr 2.3? Or is this the first version of SH3Cmdr you have used?

Have you noticed any other anomolies, errors, missing details etc? Is it picking up existing careers? Are Personnel Files being successfully created etc etc?

Because you're getting a core OS error, I recommend as a start that you follow the "Q: When I open SH3 Commander I get a screen full of "Error!" labels and/or error messages saying that SH3 Commander cannot write to, or access, certain game files. What's wrong?" FAQ just to see whether it helps.

[U768]

On this machine SH3 Commander was not installed.
No problem in the installation.
I launch SH3 Commander ok
Randomize new commander ok
Then 1939 - 1943 ok
Then 1944 !!
"Access violation at address 7C9231144 in moddule'ntdll.dll'. Write of adress 00403FE9"
I remain hushed up program in air to work well.
Strange.

[JScones]

OK. I know what's happening, but I don't understand why your system is getting so upset.

Starting careers in 1944 and 1945 is only possible if you have the latest Flotilla mod or RUb (so I assume IUB) installed. This is mentioned in the readme.

If you don't have any of these mods installed, SH3Cmdr ordinarily doesn't care - details for the two years remain blank and are captured if you try to launch a career. For some reason though, your machine does care. I'll have a look at the code again and see what could be causing this - but the same code's been there since r2.0 and no-one else has raised this problem, nor have I seen it in testing.

Anyway, easiest fix is to d/l the Flotilla mod from here (http://www.beerymod.com/Flotilla1.44.7z). But read the readme first as it makes some other changes which you may not want! Or, simply avoid entering 1944/1945 years.

[U768]

It was definitely it!
I have just made a try with Flotilla 1.44, more problems.
This machine is installed for SH3 in Multi (for the Net) without any fair Mod a version 1.4b of SH3.
I thought that the file flotilla was included in SH3 Commander, I am sorry, I shall have of think there!
But really the message of error remains strange.
I thank you for your quick answer and I apologize to you for my pretty poor Englishman.

Still thank you for the very good program which you gave us.

[JScones]

I have just made a try with Flotilla 1.44, more problems.
I hope you mean *no* more problems <fingers crossed>?

[U768]

I hope you mean *no* more problems <fingers crossed>?
Yes, I confirm no problem
I wrote too quickly!
Thank you.

[vois2]

I use SH3 Commander v2.4 .

Before asking this question, I used the FAQ at the iinet.au site, as well as Googled +invalid +argument +to +date +code with a restriction of subsim.com domain. It seems this question was asked once before, but JScones reply to the problem was contained in a private message to the person experiencing the error.

When I load up SH3 Commander v2.4, in the 'Existing Careers' side panel, there are a number of careers that when clicking on them I receive only the "Invalid argument to date code" error. How does one remove these careers from that list? Thank you.

[JScones]

Can you pls email me the careers so that I can have a look? SH3Cmdr traps all known instances where SH3 writes '0' to date fields (the error message you have is where SH3Cmdr expects a valid date but is fed something else, usually just '0/0/0').

The fix is usually just to correct one date entry...but SH3Cmdr has learnt to work around this, hence why I am curious as to where it's now failing.

My email address is in 'SH3Cmdr Help.html' (near bottom).

[Sailor Steve]

I was going to post a complaint, in that the newest version changed all the dates and birthplaces in my 'Personnel Files' screens; but then I found out where I could manually change them to match my originals.

This is far and away the best mod out there-at least where living the career is concerned.

[JScones]

Hehe. Sounds like someone didn't back up SH3Cmdr.ini prior to removing the older version... ;)

[Sailor Steve]

By the way, Jaesen, did you ever get any of my emails? If not I can re-send. I've done a short version of the Generic ship list with all American references removed, and I added the C-and-T1 and 3 names to the original, plus fixing a few mistakes I found.

Oh, and I really love the new names lists; not to mention having the accurate numbers for the U-boats in specific flotillas. This thing just keeps getting better! :cool:

[JScones]

Sorry. Yes, I got them all (assuming there were three). They're on my "to implement" list. :yep:

[vois2]

JScones --
Disregarding my tiny problem mentioned above on this page, may I send to you a 3.1 MB file? It's a 7-zipped Career folder for Ulrich Schartow who is my current hero. His Career was created entirely in the context of Commander 2.4 but SH3 doesn't give him credit for the 23K of his first patrol. I can see the ships sunk listings in the log0.cfg file for him. But that data needs to be transferred to some other file as well, or Commander 2.4 needs to be viewing that data in a different way in order for it to pick up and include in history and credit for poor Ulrich. Anyway, I have Ulrich's 45MB Career file folder zipped to just 3.1 MB which I can send. Thank you.

[JScones]

JScones --
Disregarding my tiny problem mentioned above on this page, may I send to you a 3.1 MB file? It's a 7-zipped Career folder for Ulrich Schartow who is my current hero. His Career was created entirely in the context of Commander 2.4 but SH3 doesn't give him credit for the 23K of his first patrol. I can see the ships sunk listings in the log0.cfg file for him. But that data needs to be transferred to some other file as well, or Commander 2.4 needs to be viewing that data in a different way in order for it to pick up and include in history and credit for poor Ulrich. Anyway, I have Ulrich's 45MB Career file folder zipped to just 3.1 MB which I can send. Thank you.
Check the last FAQ - this is an SH3 bug that occurs if you upgrade anything before starting your first patrol.

[vois2]

Hmm ... well, I didn't upgrade anything at all, I kept my original provided 1500 points for prestige. I have yet to spend any prestige points to now, and have finished my 2nd patrol in full.

But I will check the FAQ especially as it may describe to me what to edit to make it show credit for that tonnage!

By the way, I did receive prestige for that patrol, and that prestige is now a part of the cumulative total. It's only the tonnage from it and ship sunk details which does not get reflected in the logs/career/records screens.

[JScones]

You can manually edit the following values in Careers.cfg:

TonnageSunk=0.000000
MerchantTotalTonnage=0.000000
WarshipsTotalTonnage=0.000000
ShipsSunkNb=0
MerchantTotalShipsSunk=0
WarshipsTotalShipsSunk=0
PatrolCraftSunk=0
CorvetteSunk=0
FrigateSunk=0
DestroyerEscortSunk=0
DestroyerSunk=0
MineSweeperSunk=0
LightCruiserSunk=0
HeavyCruiserSunk=0
EscortCarrierSunk=0
AircraftCarrierSunk=0
BattleCruiserSunk=0
BattleShipSunk=0
MineLayingShipSunk=0
AuxiliaryCruiserSunk=0
PlanesDownNb=0

and the following values in Patrols.cfg:

TonnageSunk=0.000000
MerchantTonnageSunk=0.000000
WarshipTonnageSunk=0.000000
ShipsSunkNb=0
WarShipsSunkNb=0
PatrolCraftSunkNb=0
CorvetteSunkNb=0
FrigateSunkNb=0
DestroyerEscortSunkNb=0
DestroyerSunkNb=0
MineSweeperSunkNb=0
LightCruiserSunkNb=0
HeavyCruiserSunkNb=0
EscortCarrierSunkNb=0
AircraftCarrierSunkNb=0
BattleCruiserSunkNb=0
BattleShipSunkNb=0
MineLayingShipSunkNb=0
AuxiliaryCruiserSunkNb=0
MerchantShipsSunkNb=0
SupplyShipNb=0
FuelTankerNb=0
CargoShipNb=0
TroopTransportNb=0
PlanesDownNb=0
FighterAircraftNb=0
BomberAircraftNb=0
DiveBomberAircraftNb=0
TorpedoBomberAircraftNb=0
ScoutAircraftNb=0
HelicopterNb=0

Not that it matters for the first patrol, but if it happens with any subsequent patrol, remember that Careers.cfg is *cumulative*.

[vois2]

THANKS A BUNCH!!!!!!!!

[PirateKaluen]

So i guess i forgot to pay alot of attention to the User guide that comes with she cmdr and i guess i get to pay the price.. so i installed some mods and enabled them (while in port dont worry) but forgot to rollback sh3 comander. now despite have the gwx cfg files AND having GWX of course, it appears i can only start a career at or after sept 39 and not august. and i cant start a career after 1943.. it all seems like the stock sh3 game!!! is there a way to fix these things or should i just say goodbye to my sh3 career and reninstall everything. please help me i should have known better than to not read the user guide carefully. :wah:

[shadow_wxh]

I need to know how to compare file offset value in Randomised events.cfg to AI_sensors.dat to make sure they are correctly matched.

[Malwulf]

Quick question regarding Commander:

When trying to launch a new career, the Flotilla selections are not displaying with the updated names, 'Weddigen' etc. Instead, they are just shown as Flotilla 1, 2, 3. Upon initial installation and some playtime, they were displaying properly. Then they suddenly changed. To my understanding, Commander should rename those Flotillas.

As a side note, this happened suddenly without any mod changes or updates.

Has anyone else experienced this? Any ideas?

[Jeff-Groves]

I need to know how to compare file offset value in Randomised events.cfg to AI_sensors.dat to make sure they are correctly matched.

You need a hex editor and know how to use it.
I suggest 010 by SweetScape. It costs a few bucks but well worth it if you work in hex as much as I do.
One CAN write a script that would read the files involved, verify the offsets, and then correct them as needed at the click of a button.

[shadow_wxh]

You need a hex editor and know how to use it.
I suggest 010 by SweetScape. It costs a few bucks but well worth it if you work in hex as much as I do.
One CAN write a script that would read the files involved, verify the offsets, and then correct them as needed at the click of a button.

Thank you ,will try that.I currently have S3ditor which only relcate the offset of the parameter group not individual entries.

[leinar_06]

hello, when I open my SH3 commander, then i press new career, I saw an error on flotilla,and no uboat type & number, when i launch it,it says "no uboat or flotilla selected please try again later" PLS HELP ME: k_confused:

[blackswan40]

Hi leinar 06 A Warm Wecome to Subsim sorry to hear your having trouble with the Commander mod now i need to ask you some questions hopefully this post may help you figure how to fix the problem.

1. when you first installed SH3 did you run a single mission when you do that it makes a SH3 Folder in your documents for all your SH3 Campaign Carrer saves.

https://www.subsim.com/radioroom/picture.php?albumid=1230&pictureid=11364

2. are you using the 4Gig patch for SH3/GWX SH3 is a old game and with the new super mods it needs more addressable memory.

download link

https://www.subsim.com/radioroom/downloads.php?do=file&id=2888

3. did you install the Commander Mod Config File and also if you have more than one SH3 install did you tell the Commander Mod the right location of the SH3/GWX install you want to use
make a folder on drive C:/Games and put your SH3 install there so its outside windows 10
security protection of Program Files x86.



4. are you using SH3 DVD version or Steam download

Commander Mod Config Download link from official GWX Grey Wolfs Site

http://www.thegreywolves.com/downloads/

https://www.subsim.com/radioroom/picture.php?albumid=1223&pictureid=11116


if you need any more just add to this post


the Pride Runs Deep at Subsim We Look After Our Own Salute Sir :Kaleun_Salute:

[Aktungbby]

leinar_06!:Kaleun_Salute:

[leinar_06]

Hi leinar 06 A Warm Wecome to Subsim sorry to hear your having trouble with the Commander mod now i need to ask you some questions hopefully this post may help you figure how to fix the problem.

1. when you first installed SH3 did you run a single mission when you do that it makes a SH3 Folder in your documents for all your SH3 Campaign Carrer saves.

https://www.subsim.com/radioroom/picture.php?albumid=1230&pictureid=11364

2. are you using the 4Gig patch for SH3/GWX SH3 is a old game and with the new super mods it needs more addressable memory.

download link

https://www.subsim.com/radioroom/downloads.php?do=file&id=2888

3. did you install the Commander Mod Config File and also if you have more than one SH3 install did you tell the Commander Mod the right location of the SH3/GWX install you want to use
make a folder on drive C:/Games and put your SH3 install there so its outside windows 10
security protection of Program Files x86.



4. are you using SH3 DVD version or Steam download

Commander Mod Config Download link from official GWX Grey Wolfs Site

http://www.thegreywolves.com/downloads/

https://www.subsim.com/radioroom/picture.php?albumid=1223&pictureid=11116


if you need any more just add to this post


the Pride Runs Deep at Subsim We Look After Our Own Salute Sir :Kaleun_Salute:

nvm i fix it already.
:Kaleun_Salute::Kaleun_Wink:

[credkd]

Hello, I hope this is still a thing,

Quickly to the question,

It seems that SH3 Commander overwrites the 'en_menu.txt' that exists in data\menu.

The issue is that H.sie's fixes which include a JSGME mod named 'Supplement to V16B1 (JSGME)' also edits the 'en_menu.txt' file.

In the Supplement mod, the en_menu.txt includes more radio messages and responses from BDU.

It also includes messages and notifications from officers in the U-Boat.

Because SH3 Cmdr and Supplement to V16B1 (JSGME) are conflicted in en_menu.txt file, I get empty responses and notifications from both BDU and officers, It only occurs with texts that the H.sie's mod adds or modifies.

For example:

Radio message:
From: BDU
To: U-48





BDU.

In short: Since both H.sie's mod and SH3 Commander modify en_menu.txt (I assume they also modify de_menu.txt), I don't get the messages and texts that the 'Supplement to V16B1 (JSGME)' mod provides.

But when I rollback and launch sh3.exe I don't get this problem, but I also can't get to enjoy SH3 Commander features such as realistic crew transfers and such.

I didn't notice any other compatibility issues.

Thanks.

Edit: Edited 'JGSME' to 'JSGME'.

[Anvar1061]

But when I rollback and launch sh3.exe I don't get this problem, but I also can't get to enjoy SH3 Commander features such as realistic crew transfers and such.
I didn't notice any other compatibility issues.

Modify your Static settings.cfg file by adding these lines
SH3 Commander\Cfg\Static settings.cfg
;------------------------------------
; Messages for h.sie sh3.exe patch
; -----------------------------------

[data\Menu\en_menu.txt]
STRINGS|4814=Fog disappeared.
STRINGS|4818=Fog sighted.

STRINGS|4815=Oxygen: %02.0f Percent.
STRINGS|4816=Oxygen back to normal: 21 Percent.
STRINGS|4817=Oxygen too low. Using oxygen supply.

STRINGS|4819=Reloading external torpedoes.
STRINGS|4820=External torpedoes reloaded.
STRINGS|4821=Bad weather. Cannot reload external torpedoes.
STRINGS|4822=Alaaaarm! We must wait %2.0f minutes to dive.
STRINGS|4823=We must wait %2.0f minutes to dive.
STRINGS|4824=We can dive now, Sir.

STRINGS|4825=;
STRINGS|4826=Reloading torpedoes.
STRINGS|4827=Sea state too harsh. We must dive deeper to reload torpedoes!

STRINGS|4830=Repairs and refuelling at U-Tanker finished. %1.0f Torpedoes loaded.
STRINGS|4831=Weather too bad. Docking not possible.
STRINGS|4832=Repeated docking not possible.
STRINGS|4833=Docking not possible for Uboat types II and XXI.


; BDU-Messages
;-------------
; General
STRINGS|4835=Only sink hostile ships, you amateur!
STRINGS|4836=Error in transmission, repeat last message!
STRINGS|4837=Start return to home base as directed!

; Congratulations for achievement of new tonnage-category
STRINGS|4838=Very good results! ; 20000- 40000t
STRINGS|4839=Congratulations! Excellent results! ; 40000- 60000t
STRINGS|4840=Germany salutes you and your crew! ; 60000- 80000t
STRINGS|4841=That is worth an award! ; 80000-100000t
STRINGS|4842=Congratulations - new wearer of the Knight’s Cross! ; > 100000t

; For sinking >15000t
STRINGS|4843=Great work! That will hurt the enemy!
STRINGS|4844=Bravo! Excellent shooting!

; For sinking >10000t
STRINGS|4845=Very good work! A decisive blow!
STRINGS|4846=Bravo! But next time get nearer to enemy destroyers!

; For sinking >2000t
STRINGS|4847=Nice work! Carry on!
STRINGS|4848=Good work! Continue search for single ships.
STRINGS|4849=Well done! Keep at it!
STRINGS|4850=Sinking registered. Report any survivors immediately!

; Occasional communications
STRINGS|4851=Message received, continue as ordered!
STRINGS|4852=Signal received.
STRINGS|4853=Short-signal received. Expect next status- and weather- news in 24h.
STRINGS|4854=Signal acknowledged, stay alert.
STRINGS|4855=Message acknowledged, we have high expectations!
STRINGS|4856=Message received. Beware of aircraft!
STRINGS|4857=Message acknowledged. All further transmissions on long-wave 20.4kHz.
STRINGS|4858=Signal acknowledged. Use short-wave until further notice.

; For motivation
STRINGS|4859=Be more aggressive! We need better results!
STRINGS|4860=Show more courage! Charge at the enemy!
STRINGS|4861=You can’t come home with fully-loaded torpedo-tubes!
STRINGS|4862=Attack! Shoot! Sink!


;-------------------------------
; Wolfpack Mod
;-------------------------------

; BDU orders to attack alone
STRINGS|4863=Full freedom of manoeuvre granted.
STRINGS|4864=Individual attack recommended.
STRINGS|4865=Attack at discretion.
STRINGS|4866=Attack on your own. Good luck.

; BDU responses on 1st contact report
STRINGS|4867=Good work! Maintain contact. Homing signals every hour.
STRINGS|4868=You are the contact holder. Transmit hourly. Other boats on way.
STRINGS|4869=Curb your impatience! Support is on way. Hourly transmissions needed.
STRINGS|4870=At last a convoy! Stick with it until pack arrives. Request hourly updates.

; BDU responses on 2nd and later contact reports
STRINGS|4871=Signal received. Continue hourly transmission.
STRINGS|4872=Signal acknowledged. Continue holding contact.
STRINGS|4873=Good work, hourly transmissions needed.
STRINGS|4874=Continue holding contact.
STRINGS|4875=Shadow the convoy, transmit hourly.
STRINGS|4876=Signal received. Hold contact. Good luck.
STRINGS|4877=Hold contact. Beware of escorts.
STRINGS|4878=Contact report received. Hourly transmissions needed.
STRINGS|4879=Pack is on the way. Homing signals every hour.
STRINGS|4880=Other boats are on the way, continue hourly transmission.

; Wolfpack in position. Attack will come soon.
STRINGS|4881=Pack has assembled. Expect joint attack tonight. Radio silence from now on.
STRINGS|4882=Pack reports contact. You are released for attack. Radio silence from now on.
STRINGS|4883=Other boats in interception position. Attack at will. Radio silence from now on.
STRINGS|4884=Boats in position. Commence operation tonight. Attack! Sink!

; Wolfpack has problems to reach operation area. BDU orders to attack alone.
STRINGS|4885=Pack is low on fuel. You are on your own - good luck!
STRINGS|4886=Pack reports local fog. You are cleared for solo attack.
STRINGS|4887=Weather expected to deteriorate. Attack at dusk.
STRINGS|4888=Pack unable to reach operation area. Attack alone!

; Wolfpack cannot reach operation area due to massive enemy activity.
STRINGS|4889=Enemy reinforcements will join convoy tomorrow. Don’t wait for others, attack tonight.
STRINGS|4890=Pack has disbanded. Attack at will.
STRINGS|4891=Pack reports strong enemy activity around convoy. Assume you must attack alone.
STRINGS|4892=Contact to pack lost. Attack alone!

; For Diesel Damages Mod
STRINGS|4893=If we don't cut power now, we're risking a breakdown!
STRINGS|4894=Yes, sir, everything we've got!


;------------------------------------
; Messages for h.sie sh3.exe patch
; -----------------------------------

[data\Menu\de_menu.txt]
; Fog warning
STRINGS|4814=Der Nebel lцst sich auf.
STRINGS|4818=Nebel zieht auf.

; Oxygen supply
STRINGS|4815=Luftsauerstoff: %02.0f Prozent.
STRINGS|4816=Luftsauerstoff wieder normal auf %02.0f Prozent.
STRINGS|4817=Luftsauerstoff zu gering! Verwende Sauerstoffvorrat.

; External torpedo reload
STRINGS|4819=Externe Torpedos werden umgeladen.
STRINGS|4820=Umladen externer Torpedos beendet.
STRINGS|4821=Schlechtes Wetter. Umladen externer Torpedos nicht mцglich.
STRINGS|4822=Alaaaarm! Wir kцnnen erst in %2.0f Minuten tauchen.
STRINGS|4823=Wir kцnnen erst in %2.0f Minuten tauchen.
STRINGS|4824=Wir kцnnen nun tauchen, Herr Kaleun.

; Internal torpedo reload
STRINGS|4825=;
STRINGS|4826=Torpedos werden nachgeladen.
STRINGS|4827=Starker Seegang. Wir mьssen tiefer gehen, um Torpedos nachzuladen!

; U-Tanker
STRINGS|4830=Reparaturen und Auftanken beendet. %1.0f Torpedos geladen.
STRINGS|4831=Wetter zu schlecht. Andocken nicht mцglich.
STRINGS|4832=Wiederholtes Andocken nicht mцglich.
STRINGS|4833=Andocken fьr Uboot Typen II und XXI nicht mцglich.


; BDU-Messages
;-------------
; allgemeines
STRINGS|4835=Nur feindliche Schiffe versenken, Sie Anfдnger!
STRINGS|4836=Ьbertragungsfehler! Wiederholen Sie Ihre letzte Meldung!
STRINGS|4837=Rьckmarsch antreten! Einlaufhafen wie befohlen!

; Gratulationen fьr das Erreichen einer neuen Tonnage Kategorie
STRINGS|4838=Sehr gute Ergebnisse! ; 20000 - 40000t
STRINGS|4839=Gratulation. Exzellente Resultate! ; 40000 - 60000t
STRINGS|4840=Deutschland ist stolz auf Sie und Ihre Besatzung! ; 60000 - 80000t
STRINGS|4841=Da ist wohl eine Auszeichnung fдllig! ; 80000 -100000t
STRINGS|4842=Gratulation dem neuen Ritterkreuztrдger! ; > 100000t

; Fьr das Versenken von >15000t
STRINGS|4843=Gratulation. Das wird den Gegner in die Knie zwingen.
STRINGS|4844=Bravo. Ein exzellenter Schuss.

; Fьr das Versenken von >10000t
STRINGS|4845=Sehr gute Arbeit! Ein entscheidender Schlag.
STRINGS|4846=Bravo. Nehmen Sie sich vor feindlichen Zerstцrern in acht.

; Fьr das Versenken von >2000t
STRINGS|4847=Saubere Arbeit. Machen Sie weiter so!
STRINGS|4848=Gute Arbeit! Halten Sie Ausschau nach Einzelfahrern.
STRINGS|4849=Gut gemacht! Dranbleiben!
STRINGS|4850=Die Versenkung wurde registriert. Ьberlebende sofort melden!

; Zufдllige Mitteilungen
STRINGS|4851=Meldung erhalten. Machen Sie weiter wie befohlen!
STRINGS|4852=Nachricht empfangen.
STRINGS|4853=Kurzsignal empfangen. Erwarte nдchste Status- und Wettermeldung in 24h.
STRINGS|4854=Meldung empfangen. Bleiben Sie wachsam.
STRINGS|4855=Nachricht erhalten. Nicht unterkriegen lassen!
STRINGS|4856=Meldung erhalten. Vorsicht vor feindlichen Flugzeugen!
STRINGS|4857=Meldung empfangen. Weiterer Funkverkehr ab sofort ьber Lдngstwelle 20,4kHz.
STRINGS|4858=Nachricht empfangen. Funkverkehr bis auf Weiteres ьber Kurzwelle.

; Motivation
STRINGS|4859=Seien Sie aggressiver! Wir brauchen mehr Erfolge!
STRINGS|4860=Seien Sie mutiger! Ran an den Feind!
STRINGS|4861=Kommen Sie ja nicht mit vollen Torpedorohren nach hause!
STRINGS|4862=Angriff! Ran! Versenken!


;-------------------------------
; Wolfpack Mod

; BDU gibt Angriff frei
STRINGS|4863=Nach eigenem Ermessen angreifen. Achten Sie auf Eskorten und halten Sie Funkstille!
STRINGS|4864=Angriff nach eigenem Ermessen freigegeben! Viel Erfolg!
STRINGS|4865=Angriff freigegeben. Erwarte Statusmeldung nach Angriff.
STRINGS|4866=Allein auf Verband operieren. Nicht zцgern, ran!

; Antwort des BDU auf erste Kontaktmeldung
STRINGS|4867=Gute Arbeit! Halten Sie Fьhlung und melden Sie jede Stunde Position, Geschwindigkeit und Kurs des Geleits. Keine Angriffsfreigabe!
STRINGS|4868=Fьhlung unbedingt halten und jede Stunde Fьhlungsmeldung senden! Nicht abdrдngen lassen. Kein Angriff, auЯer bei starker Luftsicherung!||An alle Boote im Umkreis: Auf gemeldeten Geleitzug operieren!
STRINGS|4869=Sie sind Fьhlungshalter. Fьhlungsmeldungen stьndlich senden! Bei Kontaktverlust unbedingt nachsetzen. Keine Angriffserlaubnis!||Alle Boote in Reichweite auf Geleit operieren.
STRINGS|4870=Gesichteten Geleitzug nicht angreifen, sondern Fьhlung halten! Erwarte stьndliche Fьhlungsmeldungen. Nicht abschьtteln lassen, und unter allen Umstдnden dranbleiben!

; Antwort des BDU auf weitere Kontaktmeldungen
STRINGS|4871=Weiter so. Bleiben Sie dran! Nдchste Fьhlungsmeldung in 1 Stunde.
STRINGS|4872=Meldung erhalten. Gute Arbeit. Dranbleiben. Nдchste Meldung in einer Stunde!
STRINGS|4873=Kontakt halten. Achten Sie auf Sicherungsschiffe. Nicht abdrдngen lassen.
STRINGS|4874=Nachricht empfangen. Weiter Kontakt halten.
STRINGS|4875=Weiter Fьhlung halten. Gute Arbeit.
STRINGS|4876=Dranbleiben, Mдnner! Weiterhin stьndliche Fьhlungsmeldungen senden.
STRINGS|4877=Meldung empfangen. Saubere Arbeit! Weiter wie befohlen.
STRINGS|4878=Nicht nachlassen. Weiter Fьhlung halten!
STRINGS|4879=Nachricht erhalten. Kontakt nicht abreiЯen lassen!
STRINGS|4880=Gut so. Weiter Fьhlung halten und stьndliche Meldungen senden.

; Wolfsrudel in Abfangposition. Angriff steht bevor.
STRINGS|4881=Wolfsrudel hat Operationsgebiet erreicht. Angriff freigegeben. Erwarte Statusmeldung nach Angriff!
STRINGS|4882=Geleitzug angreifen! Ran, Mдnner! Gute Arbeit, Fьhlungshalter. Ab sofort Funkstille!
STRINGS|4883=Rudel hat Abfangposition erreicht. Angriff ab sofort erlaubt. Von nun an Funkstille halten. Viel Glьck!
STRINGS|4884=Alle U-Boote in Position. Angriff freigegeben. Ab sofort absolute Funkstille.

; Wolfsrudel erreicht Abfangposition nicht. Angriff alleine durchfьhren
STRINGS|4885=Wolfsrudel kann Abfangposition nicht rechtzeitig erreichen. Greifen Sie nach eigenem Ermessen allein an.
STRINGS|4886=Andere U-Boote erreichen Geleitzug nicht rechtzeitig. Geleit selbstдndig angreifen. Viel Glьck!
STRINGS|4887=Andere Boote kommen nicht in Position. Angriff alleine durchfьhren. Achten Sie auf Sicherungsschiffe.
STRINGS|4888=Restliches Rudel findet Geleit nicht. Geleit nach eigenem Ermessen angreifen!

; Wolfsrudel erreicht Abfangposition nicht wegen starker Feindaktivitдt
STRINGS|4889=Auf Geleitzug operierende U-Boote melden sich nicht. Angriff alleine beginnen.
STRINGS|4890=Restliches Wolfsrudel meldet sich nicht mehr. Angriff nach eigenem Ermessen freigegeben.
STRINGS|4891=Kontakt zum Wolfsrudel verloren. Angriff alleine durchfьhren. Viel Erfolg!
STRINGS|4892=Wolfsrudel kann Operationsgebiet wegen starker Gegneraktivitдt nicht erreichen. Greifen Sie allein an! Viel Glьck.

; Fьr Diesel Damages Mod
STRINGS|4893=Wir mьssen die Diesel drosseln, sonst droht ein Totalausfall!
STRINGS|4894=Alles was drin ist...

[credkd]

Modify your Static settings.cfg file by adding these lines
SH3 Commander\Cfg\Static settings.cfg
;------------------------------------
; Messages for h.sie sh3.exe patch
; -----------------------------------

[data\Menu\en_menu.txt]
STRINGS|4814=Fog disappeared.
STRINGS|4818=Fog sighted.

STRINGS|4815=Oxygen: %02.0f Percent.
STRINGS|4816=Oxygen back to normal: 21 Percent.
STRINGS|4817=Oxygen too low. Using oxygen supply.

STRINGS|4819=Reloading external torpedoes.
STRINGS|4820=External torpedoes reloaded.
STRINGS|4821=Bad weather. Cannot reload external torpedoes.
STRINGS|4822=Alaaaarm! We must wait %2.0f minutes to dive.
STRINGS|4823=We must wait %2.0f minutes to dive.
STRINGS|4824=We can dive now, Sir.

STRINGS|4825=;
STRINGS|4826=Reloading torpedoes.
STRINGS|4827=Sea state too harsh. We must dive deeper to reload torpedoes!

STRINGS|4830=Repairs and refuelling at U-Tanker finished. %1.0f Torpedoes loaded.
STRINGS|4831=Weather too bad. Docking not possible.
STRINGS|4832=Repeated docking not possible.
STRINGS|4833=Docking not possible for Uboat types II and XXI.


; BDU-Messages
;-------------
; General
STRINGS|4835=Only sink hostile ships, you amateur!
STRINGS|4836=Error in transmission, repeat last message!
STRINGS|4837=Start return to home base as directed!

; Congratulations for achievement of new tonnage-category
STRINGS|4838=Very good results! ; 20000- 40000t
STRINGS|4839=Congratulations! Excellent results! ; 40000- 60000t
STRINGS|4840=Germany salutes you and your crew! ; 60000- 80000t
STRINGS|4841=That is worth an award! ; 80000-100000t
STRINGS|4842=Congratulations - new wearer of the Knight’s Cross! ; > 100000t

; For sinking >15000t
STRINGS|4843=Great work! That will hurt the enemy!
STRINGS|4844=Bravo! Excellent shooting!

; For sinking >10000t
STRINGS|4845=Very good work! A decisive blow!
STRINGS|4846=Bravo! But next time get nearer to enemy destroyers!

; For sinking >2000t
STRINGS|4847=Nice work! Carry on!
STRINGS|4848=Good work! Continue search for single ships.
STRINGS|4849=Well done! Keep at it!
STRINGS|4850=Sinking registered. Report any survivors immediately!

; Occasional communications
STRINGS|4851=Message received, continue as ordered!
STRINGS|4852=Signal received.
STRINGS|4853=Short-signal received. Expect next status- and weather- news in 24h.
STRINGS|4854=Signal acknowledged, stay alert.
STRINGS|4855=Message acknowledged, we have high expectations!
STRINGS|4856=Message received. Beware of aircraft!
STRINGS|4857=Message acknowledged. All further transmissions on long-wave 20.4kHz.
STRINGS|4858=Signal acknowledged. Use short-wave until further notice.

; For motivation
STRINGS|4859=Be more aggressive! We need better results!
STRINGS|4860=Show more courage! Charge at the enemy!
STRINGS|4861=You can’t come home with fully-loaded torpedo-tubes!
STRINGS|4862=Attack! Shoot! Sink!


;-------------------------------
; Wolfpack Mod
;-------------------------------

; BDU orders to attack alone
STRINGS|4863=Full freedom of manoeuvre granted.
STRINGS|4864=Individual attack recommended.
STRINGS|4865=Attack at discretion.
STRINGS|4866=Attack on your own. Good luck.

; BDU responses on 1st contact report
STRINGS|4867=Good work! Maintain contact. Homing signals every hour.
STRINGS|4868=You are the contact holder. Transmit hourly. Other boats on way.
STRINGS|4869=Curb your impatience! Support is on way. Hourly transmissions needed.
STRINGS|4870=At last a convoy! Stick with it until pack arrives. Request hourly updates.

; BDU responses on 2nd and later contact reports
STRINGS|4871=Signal received. Continue hourly transmission.
STRINGS|4872=Signal acknowledged. Continue holding contact.
STRINGS|4873=Good work, hourly transmissions needed.
STRINGS|4874=Continue holding contact.
STRINGS|4875=Shadow the convoy, transmit hourly.
STRINGS|4876=Signal received. Hold contact. Good luck.
STRINGS|4877=Hold contact. Beware of escorts.
STRINGS|4878=Contact report received. Hourly transmissions needed.
STRINGS|4879=Pack is on the way. Homing signals every hour.
STRINGS|4880=Other boats are on the way, continue hourly transmission.

; Wolfpack in position. Attack will come soon.
STRINGS|4881=Pack has assembled. Expect joint attack tonight. Radio silence from now on.
STRINGS|4882=Pack reports contact. You are released for attack. Radio silence from now on.
STRINGS|4883=Other boats in interception position. Attack at will. Radio silence from now on.
STRINGS|4884=Boats in position. Commence operation tonight. Attack! Sink!

; Wolfpack has problems to reach operation area. BDU orders to attack alone.
STRINGS|4885=Pack is low on fuel. You are on your own - good luck!
STRINGS|4886=Pack reports local fog. You are cleared for solo attack.
STRINGS|4887=Weather expected to deteriorate. Attack at dusk.
STRINGS|4888=Pack unable to reach operation area. Attack alone!

; Wolfpack cannot reach operation area due to massive enemy activity.
STRINGS|4889=Enemy reinforcements will join convoy tomorrow. Don’t wait for others, attack tonight.
STRINGS|4890=Pack has disbanded. Attack at will.
STRINGS|4891=Pack reports strong enemy activity around convoy. Assume you must attack alone.
STRINGS|4892=Contact to pack lost. Attack alone!

; For Diesel Damages Mod
STRINGS|4893=If we don't cut power now, we're risking a breakdown!
STRINGS|4894=Yes, sir, everything we've got!


;------------------------------------
; Messages for h.sie sh3.exe patch
; -----------------------------------

[data\Menu\de_menu.txt]
; Fog warning
STRINGS|4814=Der Nebel lцst sich auf.
STRINGS|4818=Nebel zieht auf.

; Oxygen supply
STRINGS|4815=Luftsauerstoff: %02.0f Prozent.
STRINGS|4816=Luftsauerstoff wieder normal auf %02.0f Prozent.
STRINGS|4817=Luftsauerstoff zu gering! Verwende Sauerstoffvorrat.

; External torpedo reload
STRINGS|4819=Externe Torpedos werden umgeladen.
STRINGS|4820=Umladen externer Torpedos beendet.
STRINGS|4821=Schlechtes Wetter. Umladen externer Torpedos nicht mцglich.
STRINGS|4822=Alaaaarm! Wir kцnnen erst in %2.0f Minuten tauchen.
STRINGS|4823=Wir kцnnen erst in %2.0f Minuten tauchen.
STRINGS|4824=Wir kцnnen nun tauchen, Herr Kaleun.

; Internal torpedo reload
STRINGS|4825=;
STRINGS|4826=Torpedos werden nachgeladen.
STRINGS|4827=Starker Seegang. Wir mьssen tiefer gehen, um Torpedos nachzuladen!

; U-Tanker
STRINGS|4830=Reparaturen und Auftanken beendet. %1.0f Torpedos geladen.
STRINGS|4831=Wetter zu schlecht. Andocken nicht mцglich.
STRINGS|4832=Wiederholtes Andocken nicht mцglich.
STRINGS|4833=Andocken fьr Uboot Typen II und XXI nicht mцglich.


; BDU-Messages
;-------------
; allgemeines
STRINGS|4835=Nur feindliche Schiffe versenken, Sie Anfдnger!
STRINGS|4836=Ьbertragungsfehler! Wiederholen Sie Ihre letzte Meldung!
STRINGS|4837=Rьckmarsch antreten! Einlaufhafen wie befohlen!

; Gratulationen fьr das Erreichen einer neuen Tonnage Kategorie
STRINGS|4838=Sehr gute Ergebnisse! ; 20000 - 40000t
STRINGS|4839=Gratulation. Exzellente Resultate! ; 40000 - 60000t
STRINGS|4840=Deutschland ist stolz auf Sie und Ihre Besatzung! ; 60000 - 80000t
STRINGS|4841=Da ist wohl eine Auszeichnung fдllig! ; 80000 -100000t
STRINGS|4842=Gratulation dem neuen Ritterkreuztrдger! ; > 100000t

; Fьr das Versenken von >15000t
STRINGS|4843=Gratulation. Das wird den Gegner in die Knie zwingen.
STRINGS|4844=Bravo. Ein exzellenter Schuss.

; Fьr das Versenken von >10000t
STRINGS|4845=Sehr gute Arbeit! Ein entscheidender Schlag.
STRINGS|4846=Bravo. Nehmen Sie sich vor feindlichen Zerstцrern in acht.

; Fьr das Versenken von >2000t
STRINGS|4847=Saubere Arbeit. Machen Sie weiter so!
STRINGS|4848=Gute Arbeit! Halten Sie Ausschau nach Einzelfahrern.
STRINGS|4849=Gut gemacht! Dranbleiben!
STRINGS|4850=Die Versenkung wurde registriert. Ьberlebende sofort melden!

; Zufдllige Mitteilungen
STRINGS|4851=Meldung erhalten. Machen Sie weiter wie befohlen!
STRINGS|4852=Nachricht empfangen.
STRINGS|4853=Kurzsignal empfangen. Erwarte nдchste Status- und Wettermeldung in 24h.
STRINGS|4854=Meldung empfangen. Bleiben Sie wachsam.
STRINGS|4855=Nachricht erhalten. Nicht unterkriegen lassen!
STRINGS|4856=Meldung erhalten. Vorsicht vor feindlichen Flugzeugen!
STRINGS|4857=Meldung empfangen. Weiterer Funkverkehr ab sofort ьber Lдngstwelle 20,4kHz.
STRINGS|4858=Nachricht empfangen. Funkverkehr bis auf Weiteres ьber Kurzwelle.

; Motivation
STRINGS|4859=Seien Sie aggressiver! Wir brauchen mehr Erfolge!
STRINGS|4860=Seien Sie mutiger! Ran an den Feind!
STRINGS|4861=Kommen Sie ja nicht mit vollen Torpedorohren nach hause!
STRINGS|4862=Angriff! Ran! Versenken!


;-------------------------------
; Wolfpack Mod

; BDU gibt Angriff frei
STRINGS|4863=Nach eigenem Ermessen angreifen. Achten Sie auf Eskorten und halten Sie Funkstille!
STRINGS|4864=Angriff nach eigenem Ermessen freigegeben! Viel Erfolg!
STRINGS|4865=Angriff freigegeben. Erwarte Statusmeldung nach Angriff.
STRINGS|4866=Allein auf Verband operieren. Nicht zцgern, ran!

; Antwort des BDU auf erste Kontaktmeldung
STRINGS|4867=Gute Arbeit! Halten Sie Fьhlung und melden Sie jede Stunde Position, Geschwindigkeit und Kurs des Geleits. Keine Angriffsfreigabe!
STRINGS|4868=Fьhlung unbedingt halten und jede Stunde Fьhlungsmeldung senden! Nicht abdrдngen lassen. Kein Angriff, auЯer bei starker Luftsicherung!||An alle Boote im Umkreis: Auf gemeldeten Geleitzug operieren!
STRINGS|4869=Sie sind Fьhlungshalter. Fьhlungsmeldungen stьndlich senden! Bei Kontaktverlust unbedingt nachsetzen. Keine Angriffserlaubnis!||Alle Boote in Reichweite auf Geleit operieren.
STRINGS|4870=Gesichteten Geleitzug nicht angreifen, sondern Fьhlung halten! Erwarte stьndliche Fьhlungsmeldungen. Nicht abschьtteln lassen, und unter allen Umstдnden dranbleiben!

; Antwort des BDU auf weitere Kontaktmeldungen
STRINGS|4871=Weiter so. Bleiben Sie dran! Nдchste Fьhlungsmeldung in 1 Stunde.
STRINGS|4872=Meldung erhalten. Gute Arbeit. Dranbleiben. Nдchste Meldung in einer Stunde!
STRINGS|4873=Kontakt halten. Achten Sie auf Sicherungsschiffe. Nicht abdrдngen lassen.
STRINGS|4874=Nachricht empfangen. Weiter Kontakt halten.
STRINGS|4875=Weiter Fьhlung halten. Gute Arbeit.
STRINGS|4876=Dranbleiben, Mдnner! Weiterhin stьndliche Fьhlungsmeldungen senden.
STRINGS|4877=Meldung empfangen. Saubere Arbeit! Weiter wie befohlen.
STRINGS|4878=Nicht nachlassen. Weiter Fьhlung halten!
STRINGS|4879=Nachricht erhalten. Kontakt nicht abreiЯen lassen!
STRINGS|4880=Gut so. Weiter Fьhlung halten und stьndliche Meldungen senden.

; Wolfsrudel in Abfangposition. Angriff steht bevor.
STRINGS|4881=Wolfsrudel hat Operationsgebiet erreicht. Angriff freigegeben. Erwarte Statusmeldung nach Angriff!
STRINGS|4882=Geleitzug angreifen! Ran, Mдnner! Gute Arbeit, Fьhlungshalter. Ab sofort Funkstille!
STRINGS|4883=Rudel hat Abfangposition erreicht. Angriff ab sofort erlaubt. Von nun an Funkstille halten. Viel Glьck!
STRINGS|4884=Alle U-Boote in Position. Angriff freigegeben. Ab sofort absolute Funkstille.

; Wolfsrudel erreicht Abfangposition nicht. Angriff alleine durchfьhren
STRINGS|4885=Wolfsrudel kann Abfangposition nicht rechtzeitig erreichen. Greifen Sie nach eigenem Ermessen allein an.
STRINGS|4886=Andere U-Boote erreichen Geleitzug nicht rechtzeitig. Geleit selbstдndig angreifen. Viel Glьck!
STRINGS|4887=Andere Boote kommen nicht in Position. Angriff alleine durchfьhren. Achten Sie auf Sicherungsschiffe.
STRINGS|4888=Restliches Rudel findet Geleit nicht. Geleit nach eigenem Ermessen angreifen!

; Wolfsrudel erreicht Abfangposition nicht wegen starker Feindaktivitдt
STRINGS|4889=Auf Geleitzug operierende U-Boote melden sich nicht. Angriff alleine beginnen.
STRINGS|4890=Restliches Wolfsrudel meldet sich nicht mehr. Angriff nach eigenem Ermessen freigegeben.
STRINGS|4891=Kontakt zum Wolfsrudel verloren. Angriff alleine durchfьhren. Viel Erfolg!
STRINGS|4892=Wolfsrudel kann Operationsgebiet wegen starker Gegneraktivitдt nicht erreichen. Greifen Sie allein an! Viel Glьck.

; Fьr Diesel Damages Mod
STRINGS|4893=Wir mьssen die Diesel drosseln, sonst droht ein Totalausfall!
STRINGS|4894=Alles was drin ist...


Thank you :Kaleun_Salute:.