@freh said in League General Discussion Thread:
@axis-dominion ok. Yeah, it would make sense that it’s something related to the file itself and it really only impacts subs. Somehow, the sub rules got corrupted or changed in some way.
I wish I knew enough about the coding in triplea to investigate the problem!
yah sub rules issue, an infinite loop somewhere…
We have had the issue in our Tournament game with @trulpen. Subs not diving and BB firing back once hit by sub (UK1 SZ110), Lone cruiser firing back after being hit by sub (UK2 SZ126) and Italian NO denied for a UK sub in the Med with no Stealth anymore (Italy 3).
https://www.axisandallies.org/forums/topic/35768/tt-majikandrew-x-vs-pejones-a-56-oob/52
when I hover over the sub in the file that hangs, I get this: 
but for the files that don’t hang, it shows the correct stats: 
So I figure something in the gamefile is preventing the sub from having/using all of its characteristics. It can’t be in the game engine, right? Then it would be the same for all files played.
if you look at this post G1 file, the sub stats are correct: https://www.axisandallies.org/forums/assets/uploads/files/1600887502234-triplea_35795_1ger.tsvg
but then in this post R1 file, the sub stats are now wrong: https://www.axisandallies.org/forums/assets/uploads/files/1600889975703-triplea_35795_1rus.tsvg
So something happened to change the sub stats during the end of G1. Interestingly, if I run through the file myself, the sub stats don’t change.
I recently ran into the same issue with the BC. As @axis-dominion mentioned it, it will hang and you have to restart triple a…
Feedback from the developers is that this is possible if you save the game with an earlier build. Some may say that they had it occur in other ways. Can you reproduce that?
@simon33 Confirmed!
I started a game with 2.2.20868, saved it, and then loaded the file with 2.1.20365 and reproduced the problem. Same thing happened with:
2.2.20868 > 2.0.20234,
2.2.20790 > 2.1.20365, and
2.2.20790 > 2.0.20234.
But it did not happen with
2.2.20868 > 2.2.20790, or
2.1.20365 > 2.0.20234.
So it seems that the update from 2.1.20365 to 2.2.20790 is key. My guess is that, if everyone is using 2.2.x, or 2.1.x or earlier, the problem doesn’t occur. But if there is a mix of 2.2.x & 2.1.x or earlier, the problem surfaces.
Bottom line, everyone should update to the latest version.
Thanks for your help with this!
what is the latest/recommended version?
@oysteilo It’s 2.2.20868
@axis-dominion So it seems the problems are in games when one player is using 2.1.x or earlier, and another player is using 2.2.x. If all players are using 2.2.x, or are all using 2.1.x, I can’t replicate the problem.
NOTE: edited to correct me entering the wrong version numbers.
@freh said in Submarine-related Issues with TripleA:
@axis-dominion So it seems the problems are in games when one player is using 2.2.20365 or earlier, and another player is using 2.2.20790 or later. If all players are using the most up to date version, the problem doesn’t occur. To me, that’s the solution.
Nope. Ksmckay and I were using the same latest version and ran into it big time.
@simon33 So it seems others are able to reproduce it even if both players are using 20868.
I know it’s not in 2.1.20625, as that’s the version we’re using in our team tournament game and it’s never come up.
@axis-dominion s***, I just released I screwed up the numbering…
So I can only see the following as latest versions:
2.2.20868 - Released Aug 22, 2020
2.2.20790 - Released Aug 12, 2020
2.1.20365 - Released July 1, 2020
2.0.20234 - Released June 24, 2020
So to clarify, I was able to replicate the issue by using a 2.2.x version with a 2.1.x or earlier.
So if you are saying that you have seen the problem occur when multiple people are using 2.2.x only (and no one in the game uses 2.1.x or earlier), then I have no idea what’s going on.
@axis-dominion said in Submarine-related Issues with TripleA:
@freh said in Submarine-related Issues with TripleA:
@axis-dominion So it seems the problems are in games when one player is using 2.2.20365 or earlier, and another player is using 2.2.20790 or later. If all players are using the most up to date version, the problem doesn’t occur. To me, that’s the solution.
Nope. Ksmckay and I were using the same latest version and ran into it big time.
Can you reproduce that?
