Page 1 of 1

Possible Bug in RR around Riga

Posted: Mon Mar 02, 2020 5:46 pm
by kennonlightfoot
This may be a restriction but I think in may be a bug in RailRoad movement.
See attached jpeg which shows RR movement when different units are selected.
The left image shows RR movement for Sov. Cav Dorps in Daugava. It can move throughout the Riga area.
The right image shows RR movement for the Sov 17th Mech which is adjacent to Riga.
This occurs regardless of weather since earlier this area was clear and still had problem.

The restriction seems to be any unit in the area around Riga marked by the the Red dots can't use RR to move anywhere.
Units outside of this area can freely move into the Riga area using RR movement.

Germany and Russia are not at war.

In April 42 Germany declared war on Russia.
At that time the restriction disappeared and all Russian units in or out of Riga area could use RR there.


Image

RE: Possible Bug in RR around Riga

Posted: Mon Mar 02, 2020 5:48 pm
by AlvaroSousa
Thanks. I think I might know what this is. Odd bug very rare.

RE: Possible Bug in RR around Riga

Posted: Mon Mar 02, 2020 7:35 pm
by AlvaroSousa
Which version? My beta version it works fine.

RE: Possible Bug in RR around Riga

Posted: Tue Mar 03, 2020 2:25 pm
by kennonlightfoot
This is the 5 version. I haven't put on any beta updates since I am not sure how it would affect my on going games.

The situation is rather unique. The game was against the AI Axis and they didn't declare war on Russia in 41 but rather went into Spain for an extended stay. When I started moving back into the front lines in preparation for Russia having to declare war on Germany in 42 is when I saw the problem. When the AI finally declared war just before I planned to, the problem was immediate corrected and RR movement out of the area worked.

I don't know whether the problem occurs before 1942 since I only moved some road bump troops into that area in preparation for a '41 attack that never occurred.

RE: Possible Bug in RR around Riga

Posted: Tue Mar 03, 2020 3:04 pm
by AlvaroSousa
Then v6 is the fix. I remember this problem before and I was like "didn't I fix this?!?!"