Hi sublynx,

I had some problems with special characters in my Submarine Tracking Room app. So, it can well be that these are also problematic here. I'm working on a fix, but it might take some time. Until then I recommend avoiding special characters like ä, ü, ö,....

Regards, LGN1

Thanks LGN1! I'll have a go with the English alphabet.

Hi sublynx,

I have included a folder 'Test version' with a file 'SH3Log1.exe' in the original download. This test version should work with ä, ü, ö,...

Could you please download the mod again and test whether this version now works for you?

Cheers, LGN1

No luck.

Maybe there's something wrong in my career. I'm currently testing different weather mods in my career, and the first patrol in my career was just sailing out of Brest to the Bay of Biscay to see how the weather behaves and then sailing back and then reloading from a previous save.

When my current career ends (4 - 5 patrols, then SH3Commander probably sends the commander to a desk job), I'll try with a fresh career.

Hmmm...:hmmm:

Could you please start a new test campaign with a name containing, e.g., ä, finish a patrol (just leave port and return), and try it again? I would like to see whether it's related to the name.

Cheers, LGN1

PS: Do you see the name when pressing the 'Choose career...' button in the new version?

Works like a charm now :yeah:

It even confirmed a sinking I didn't report, as I didn't know the ship had sunk until I saved the game :D

I've said this before, but this thing is bringing a whole new dimension to the game. Do I stay periscope depth, do I keep contact with the convoy, do I do the proper reconnaissance I would need to do if I followed BdU's commands... :ping:

This mod makes what seems to be a small change in the game, but the impact on game dynamics (and "feel", whatever that is!:D) is huge. I use Hitman's GUI so I don't need to ID targets to feed a stadimeter - 25 m mast height and 140 m LOA is usually close enough. But now, I have to make an ID so that I can report accurate tonnage, which was what RL Kaleuns faced. And I have to try to get some indication whether the target actually sank. A great addition to the game. Thanks, LGN1!

Hi BigWalleye,

for a new version I tried your idea with the semicolons. However, I get an empty line in this case "NA: ".

Are you sure that it works in your case (with the navigator in place)?

Regards, LGN1

No, I found the same problem, and was unable to figure out how to get rid of the empty line. Usually, after a successful attack, a lot of messages scroll by pretty quickly and it was a while before I saw the empty NA: line. When I did, I played around trying to get rid of it, and eventually just reverted to your "Returning to course" message. By that time, I'd forgeoten about my earlier post. If I had remembered, I'd have posted a correction. I'm sorry if I wasted your time on a dead end. My bad!

Since there is usually a lot of message traffic, at least on my boat, immediately after an attack, I seldom see the "Returning to course" message either. I usually give a genuine Return to course order during the immediate post-attack activities anyway, so if I see the NA's response flash up, I'm never sure it wasn't legitimate. BTW, I use voice command, and my message block is on a slideout, so it usually is off-screen much of the time. That makes the NA's callout easier to miss.

If I have the time, I like to hang around until I am convinced that the target is actually sinking anyway. And when I don't have the time, that usually means I'm busy dealing with POed escorts and not reading mail! So I find your mod really effective. If I want, I can always beat the system somehow and find out how I did before making my report. But what would be the point? The dummy "Returning to course" hasn't proved to be a spoiler.

Thanks for testing this again, BigWalleye!

So it seems, although not perfect, the "Returning to course" is still the best way to hide the message :-? At least for players who use the command frequently (like I do).

Regards, LGN1

I have uploaded a new version 1.0 which fixes the problem with special letters like ä, ö, ü,... Only the exe/perl script has changed.

@Moderators: Could you please change the thread title to '[REL] SH3 Log Mod'. I think the mod has passed enough Beta tests. Thanks!

Regards, LGN1

After my last patrol I tried to report the sinkings and got this:

http://i.imgur.com/8klwO1D.jpg

Any idea what might help?

LGN1, regret being the bearer of bad news, but v1 apparently isn't working correctly for me, either.

I did a basic test when I got SH3 Log v1 just to see that it would load and cycle. OK.

After seeing sublynx's post, I created a career, ran a patrol, and tried to claim tonnage with SH3 Log. It cycled and found my test commander's folder. I entered 1 merchant and clicked "Create entries". Nothing happened. I tried 1 warship with the same result. No line of data entry boxes.

Just to make sure, I tried the same career with SH3 Log v0.5. It worked fine. (Although, I did enter a claim of 1 Bismarck-class battleship, 50,000 BRT, sunk at AO77 on 1 August 1939. BdU "reluctantly" confirmed my claim, but criticized my sloppy note-taking. Guess the desk-sailors had a few extra liters of Pils with lunch.:D Next patrol, I'm claiming the Ark Royal!)

Thanks for the feedback, BigWalleye and sublynx!

As a quick-fix I have removed the new version and uploaded the old one again.

I have to find out what is going on and then fix it.

@BigWalleye: What was your true tonnage when claiming the Bismarck?

Regards, LGN1

Hi,

I made some tests and found out that the problem only exists on one of my computers, but not on the other. The old version was compiled on one machine and the new one on a different machine with a different perl installation. On this machine the old perl script also does not work, but the old .exe does.

To cut a long story short, I will recompile the new exe on the other machine and this should do the trick.

Regards, LGN1

Zero. I just started a dummy career, docked immediately, then brought up SH3 Log. I figured it would reject whatever I entered, so I made up an absurd claim. If you mean claimed/credited, I'm not sure - I've since deleted it - but I believe it was 50000/50000. Obviously, they let us get away with one now and then. It happened in RL, too. Just happened when I claimed a whopper for my own amusement.:D

Ok, I have uploaded a freshly compiled version which, at least on my machine, works fine. It would be great if someone else could check it, too.

@BigWalleye: I checked the script again and your observation concerning the Bismarck should not happen. I also tested it myself and it was not accepted :hmmm: Did you maybe use a delimiter to separate the thousands, e.g., 55,000, like in your post above? That would explain it.

Regards, LGN1

I'll take a look.

I don't recall doing anything like that, but I sure wouldn't swear that I didn't.

But I didn't consider it a problem. I'm not in the habit of trying to falsify my patrol results. So I would have to have thought I had a sinking when I didn't, and then SH3 Log would have had to pick that particular report to accept the results without data in the log file. That's an unlikely pile-up of circumstances.

Seems to be working now! I'll report again, when I finish my current patrol.

Ran a test with Kaleun Forscher. Works fine, althought Norton AV doesn't like it! First test I tried, Norton just removed it! But I explained that SH3 Log was OK, so now Norton leaves it alone.

I'm 6 days out on my current patrol, so it will be a while before I have a chance to use it operationally.