Matrix Games Forums

A few times, and not every time, a stack of my units will go through a sea area that has an enemy unit. I control-click on the sea area as I intend to pass through it. What has happened is that even if there is no interception attempted, my fleet does not appear to be able to go into the next sea area but must pick a sea area, even though there are both sufficient range and movement to go further. This is not due to presence of the enemy, as there is only usually an enemy submarine in the area (this seems to be related as the bug seems to crop up in this case). This has happened more than once and is causing problems in my current game because TRS, for example, are unable to bring transported units where I wish them to be for disembarking.

Am I doing something wrong with my naval moves that this is occurring? Is ctr-click the wrong use of keys when the intent is to travel through a sea area?

I am not certain I still have a save of this but will check if this is a unique problem.

I think this happened to me once, but after sometime trying back and forth I could make it so I thought it was my fault.

CTRL leftclick is the right way to do it.

Is the optional rule In the presence of the enemy used?

That reduces movement of naval units in some cases.

It is, but the only enemy unit is a sub. And even so, a 4-4 TRS should be able to go more than one sea zone, especially uninterrupted.

I think, this is a bug in 4.2.3.2, which has been reported several times. It seems, in 4.4.1 this is working again.

Angeldust2 wrote: Tue Feb 22, 2022 2:19 pm I think, this is a bug in 4.2.3.2, which has been reported several times. It seems, in 4.4.1 this is working again.

It seems so

https://www.matrixgames.com/forums/view ... 1&t=380065

I am using 3.0.20 ... and the bug is there... although it is not gamestopping.

craigbear wrote: Sat Feb 26, 2022 2:16 am I am using 3.0.20 ... and the bug is there... although it is not gamestopping.

Have you tried 3.2.0? I believe the bug is not there. FYI. Could you post your game file and details on what your doing? I (too) would like to confirm that it's not there 3.2.0.

rkr1958 wrote: Sat Feb 26, 2022 8:11 pm

craigbear wrote: Sat Feb 26, 2022 2:16 am I am using 3.0.20 ... and the bug is there... although it is not gamestopping.

Have you tried 3.2.0? I believe the bug is not there. FYI. Could you post your game file and details on what your doing? I (too) would like to confirm that it's not there 3.2.0.

But if we need to go back all the way down we'll end in 1.0

Do not have the file any longer. I will post when it crops up again.