Agreed :up:

Redoing the logs shouldn't be too difficult since we already have stored copies of most of the essential data. I assume we could copy and past the coordinates information, making minor adjustments for any refits (although there shouldn't have been any at that stage of the war).

I have been trying to formulate a simple but effective way to determine commander skill level (for the sake of simplicity, I think we should ignore crew ability). The ideal method would be to calculate veterancy level based on tonnage sunk by date, thereby simulating the commander "learning" the business of U-boat warfare by experience. However, this method seems completely impractical since it would require recalculating tonnage at the beginning of every patrol. I don't think we should impose these burdensome requirements on our volunteers. Calculating veterancy based on commander's awards is also not an ideal solution: the requirements to receive a Knight's Cross declined steadily as Allied ASW increased in lethality, so that they were occasionally being awarded after sinking just one or two merchants by 1944.

In view of these obstacles, I think the best solution would be to have a one-time calculation of veterancy based on the total tonnage sunk by the commander over the course of his career. We would not be able to simulate "learning," but I think this method would greatly reduce the difficulty of determining skill level. For example, any commander that sank 75,000 GRT or more could be considered a "veteran," even from the beginning of the war. This would be about 64 commanders, according to a quick check of uboat.net.

Before assigning specific numbers, though, it would be important to know to what extent veterancy affects AI ability. Has this been tested?

Okay, I hope to release the next version of the generator within the next 24 hours.

Talking about veterancy levels, if I have got you, you are proposing not to take commander's ranks in any account. What if we assigned each rank a number of points, and then we averaged them with the tonnage sunk for determining U-oat's veterancy? :hmmm:

:up:

I was thinking that rank might be more of a reflection of bureaucracy than skill, but you are probably right that it is a useful variable. Since it is already included in the generator, we might as well make use of it. Of the two variables, I think tonnage sunk should be given a little bit more weight than rank. What do you think?

Agreed :up:

Now we need to:

- assign each rank a number of points comparable to tonnage sunk
- ask our volunteers if they think it practical to calculate the partial sum of tonnage sunk by any commander until the current patrol (otherwise, only total tonnages at the end of their respective careers will be taken into account)
- determine tonnage sunk + commander rank ranges corresponding to each veterancy level.

Can you please take care of the above tasks? :D

Sure thing. :up:

Even though it would only require very simple arithmetic, I am hesitant to ask people to recalculate tonnage sunk before each patrol, since it would add another barrier that might drive away volunteers. But what do you guys—Targor, Sartoris, Dogfish, Volodya, and anybody else interested in helping—think about this? Is it too demanding to calculate add up tonnage before each patrol? How about only using the commander's career tonnage?

Also, does anyone know how the veterancy levels affect AI ability? For example, if the AI becomes basically worthless at novice level, then it might be better to exclude the novice setting. Similarly, if the veteran level turns AI u-boats into the equivalent of Virginia-class attack subs, then we would make it very rare.

Maybe we can device a set of single missions to test how veterancy levels affect AI U-boats :hmmm:

Okay, I will run some tests. I won't be able to get to it until tomorrow since i have to prepare for a seminar tomorrow. I don't think it should take too long to get a since of the AI settings though.

I don't think it would be too much of a bother.

I have nothing against a bit of math.

:up:

Thanks for your responses. I think we can plan on calculating tonnage before each patrol. This should provide the most realistic portrayal of veterancy levels :up:

I'm just about to start testing AI U-boats to see how skill level affects their ability. After that, I'll post some preliminary suggestions for setting veterancy levels.

yep :up:

:sunny:

U-boat coordinates/logs generator v2 todo list
 

• Making lat/long input cells to accept coordinates divided by a comma (e.g. 53.31N, 08.12E) - done :up:
• Adding two new current activity tags which you can select: "Heading to refitting area" and "Refitting aborted" - done :up:
• Adding three new message flags which can be generated: "Proceeding to refitting area", "Successfully refitted" and "Refitting aborted" - done :up:
• Adding information on fuel left / total patrol distance to the logs generated - currently working on it :ping:
• Updating fuel / torpedoes aboard, after each successful refitting.
• Making U-boat veterancy to be calculated on the base of tonnage sunk by her commander.
• Adding an alternative lat/long input for German bases (no coordinates input required).

Have I forgot anything important?

I think that's everything :up:

I have done about 25 tests of the U-boat AI, and the results have been exciting—AI U-boats are quite capable, even if they are not very subtle. All of the tests have been at the "elite" setting so far, since I am trying to decide the fairest setup for more comprehensive tests. I think I have found the right setup and will begin testing other veterancy levels this afternoon.

I also have nothing to really add, gap. I think it's good!

@keysersoze:
Keep me in the loop on the results. It's pretty obvious, I guess, why I'm interested :)