No kills awarded using SH3 Commander?

[Draka]

I go even farther - I add a custom crew via SH3Cmdr. I have historical crew lists that I have added as choices under Commander, so that doesn't seem to break it. Once I have been out on a "shake-down" run for a day or so, then I add in equipment changes - which I roleplay as being ordered/installed as a result of the trial run!

So far this has worked up to mid-'42, so it should be stable for the entire war. (haven't lasted farther than that - was finally about to when my 'puter died - tend to fiddle with files etc more than play!)

[Cpt. Martin]

Thanks everybody, I just got home from work so I'm going to fire up a new career. I have "rollback automatically after exiting" checked this time and will not fiddle with my 1st patrol load-out. I had swapped some steam eels for 2 electrics and started my Career in October '39 during the failed cruise. This time I'll putz around for the shake-out patrol then return in time for ze Kampf to start.

I'll let you know if your suggestions have fixed things. This forum rocks btw; long time lurker, I've killed many hours just reading threads here

EDIT: I hear 2 conflicting pieces of advice should I have "rollback automatically after exiting" on or off?

[frau kaleun]

Originally Posted by Cpt. Martin

Thanks everybody, I just got home from work so I'm going to fire up a new career. I have "rollback automatically after exiting" checked this time and will not fiddle with my 1st patrol load-out. I had swapped some steam eels for 2 electrics and started my Career in October '39 during the failed cruise. This time I'll putz around for the shake-out patrol then return in time for ze Kampf to start.

I'll let you know if your suggestions have fixed things. This forum rocks btw; long time lurker, I've killed many hours just reading threads here

EDIT: I hear 2 conflicting pieces of advice should I have "rollback automatically after exiting" on or off?

I would definitely advise checking the box that activates the auto rollback of Commander. This undoes any changes Commander made to your game files during your last playing session, leaving them exactly the way they were before Commander touched them.

This is especially helpful because if you are going to enable/disable any mods manually or using JSGME in between patrols or careers, you would need to do a manual rollback of Commander beforehand... if you forgot to do that it could cause problems when you loaded the game again. If you let Commander roll itself back every time you leave the game, you don't have to worry about it.

[JScones]

Originally Posted by Cpt. Martin

Now I see this travesty: No ships sunk, no tonnage awarded listed in the after-action report. So I exit out of the game thinking maybe Cmdr needs to apply the values when I restart for patrol #2. I check "Review Patrol Logs" in Cmdr and "a ha!", there is my list of victims. I did notice that unique ship names are not displayed even though I checked that option (maybe b/c all kills were ~2000 tons, i.e. small vessels?) I fire up SH3/GWX from the Cmdr GUI and again I have zero kills in base before patrol #2. I checked the my C:\Users\myusername\Documents\SH3\data\cfg\Careers \Johannes Vogel\patrols_0.cfg and it does not show the kills either. That patrol was a wash

Essentially Cmdr is recording my talley but SH3/GWX is not registering the kills.

Ugh. I smell a reinstall of everything coming, what a PITA....

Any thoughts, ideas, suggestions would be much appreciated. Maybe I'm just noobing something simple eh? I installed Cmdr 3.2 then GWX3_SH3Cdr3.2Files_v1.2.exe as specified.

P.S. I read the included Cmdr .pdf, so I don't feel like I missed a procedural aspect.

EDIT: Rechecked my "patrol history" in-game and the list of kills is present. Also, my renown went from 30 pre-patrol to ~230 after even though renown gained shows "0" after patrol 1. Now I'm more baffled. Where's the disconnect?

This stock SH3 bug is explained in both the GWX manual (page 14) and the SH3Cmdr manual (page 30).

The bug will only appear if you make changes that alter the patrol start date. Adjusting crew, or using alternate crew config files, do not alter the patrol start date. Upgrading equipment (includes adding an emblem depending on mod installed) will alter the start date.

Obviously prevention is the best cure, but if you forget to follow the advice posted by others, then another way of "fixing" the problem is to save your game just prior to docking upon your return. If you then get hit with the bug, simply reload the save and dock again. This appears to rectify the problem.

[Sailor Steve]

Originally Posted by JScones

The bug will only appear if you make changes that alter the patrol start date. Adjusting crew, or using alternate crew config files, do not alter the patrol start date. Upgrading equipment (includes adding an emblem depending on mod installed) will alter the start date.

AHA!

Who knew? Well, obviously you did. All these years and it never ocurred to me that there might actually be a reason.

[frau kaleun]

Originally Posted by JScones

The bug will only appear if you make changes that alter the patrol start date.

I'm sure you've said this before, but I swear I'm going to remember it this time! It's the patrol date that borks things up. Good to know. Even better to remember knowing it.

[JScones]

Yes. The player just notices the missing renown. What they don't notice is that SH3 writes zeroes for the patrol start date and flotilla start date as well. It's this aspect that upsets SH3Cmdr (the telltale sign being the "Invalid date to encode" error).

It's a very easy bug to avoid, if one spends a few minutes reading the GWX and/or SH3Cmdr manuals, or follows the advice spouted on this forum ad nauseam.

[Jimbuna]

Originally Posted by JScones

It's a very easy bug to avoid, if one spends a few minutes reading the GWX and/or SH3Cmdr manuals, or follows the advice spouted on this forum ad nauseam.

Originally Posted by jimbuna

Best/safest practice is to add crewmen only.

[Cpt. Martin]

Verified the default start date fix worked. I feel Like I read that ages ago and forgot. I'm sure I did read it, here actually, and fudged it up anyway