@axis-dominion yep.
@simon33 I know. I wasn’t able to get it to hang in the same version in a game created just the day before the one that is hanging. So yes, there is something else causing the hang.
Alright, I did some more methodical testing of my problematic file, narrowed it down to a battle calc of a sub vs fig
Happens with more units involved too, but I was able to strip it down/narrow it to that.
I suspect it’s a resources issue. Happens more when you have more battle calculator windows open.
@simon33 said in League General Discussion Thread:
I suspect it’s a resources issue. Happens more when you have more battle calculator windows open.
No I have to quit tripleA each time it happens. Have to open a new one to test it, and so I have one simple battle calc open. Pretty sure it’s not a resources issue. Happens on both my windows and Mac. And my windows is a new monster 32GB ram gaming laptop, you know, the heavy monsters that are so noisy lol
Is it possible that it occurs when the two players are using different versions of the engine?
I’m running 2.2.20868, java 11.06
@LennardF what version are you using (no problem)?
@dawgoneit what version are you using (problem)?
@freh said in League General Discussion Thread:
Is it possible that it occurs when the two players are using different versions of the engine?
I’m running 2.2.20868, java 11.06@LennardF what version are you using (no problem)?
@dawgoneit what version are you using (problem)?
Don’t think so. Ksmckay and I are using the same version.
@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!
@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.
