FSB relocation bug?

[willgamer]

The option to move the AGC FSB comes up, but Vyazma it not one of the several choices.

I suspect it's because of the destroyed bridge at Smolensk, since the trucks are coming up the road to Vyazma with no problems.

However the bridge is not on the route to Vyazma, so shouldn't relocation be allowed?

[willgamer]

The problem is getting worse. [:(]

Now, with the message to move the AGN FSB, Luga is not included.

Also, the bridge in AGC is repaired, but Vyazma still is not included on the AGC list.

Both of these locations are shown as valid on the map.

Do you need a save game file?

[Vic]

Hi will,

Cameron will get to you soon.

Best wishes,
Vic

[willgamer]

Now the problem also show up in AGS where the current FBS is Voronezh and I want to shorten it by moving it back to Kursk.

Kursk is in black on the map; it is not on the relocation list.

Perhaps is the issue that at this point in the game, late Oct., there are simply to many black cites on the map to list?

[:(]

[lancer]

Hi willgamer,

The bridge at Smolensk wouldn't affect the FSB to Vyazma but enemy action is the most likely culprit.

Looking at your screenshot in the area around Smolensk the enemy controlled area is right next to the rail line. For a location to be a viable option it must be able to trace a rail route back to it's main depot (Warsaw in this case).

If, during the enemy turn, they interdicted the rail route either physically, or by exerting a Zone of Control, at any point then the connection test would fail for that location. The sequence of internal events is such that even though no interdiction is showing at present it still could have happened during the enemy turn. The history review is the only way to check this.

This would have to be the odds on favourite for the first instance above given the proximity of the enemy to the rail line.

There isn't enough info for me to see what happened with Luga but the last instance, Kursk, is probably due to the abundance of possible FSB locations currently available. Whenever this happens the list of available locations is sorted and only the top four are shown, weighted towards those closer to those sites further into Russia.

If where you want to go isn't one of the four available options you'll have to leapfrog there using an interim location.

Cheers,
Cameron

[willgamer]

It seems the routine to identify the FSBs deepest into Russia is suspect.

Here's screenies of the problem on each of the 3 fronts on the same turn.

In every case there are better choices, indicated by black cities in the help map, than the ones shown on the relocation offer.

[willgamer]

AGN map.

[willgamer]

AGC Reloc.

[willgamer]

AGC map.

[willgamer]

AGS reloc.

[willgamer]

AGS map.

[lancer]

Hi willgamer,

In both AGN & AGS you've captured the objectives and there is a dearth of future FSB locations beyond these. You've reached the end of the road.

In AGC you're being offered 3 FSB locations near Moscow.

Cheers,
Cameron

[willgamer]

Honestly, I know the game is over... the reason you have the sceenies above is that's all I have left from a completed game. I still believe there is a problem. [:o]

I'm testifying to you that the lack of correct choices existed every single turn after the problem appeared. [:(]

AGN- Luga should be offered.

AGC- Vyazma was NEVER offered; not once!

AGS- Kursk, a former FSB, was never re-offered.

I suggest finding a way to scroll the offer list to include all valid choices.

[lancer]

Hi willgamer,

Looking at your screenshots you're correct about Luga and Vyazma. Kursk is hard to tell.

Did you change Beta versions during the game?

Did the problem start before or after you'd captured an objective?

Cheers,
Cameron

[willgamer]

ORIGINAL: lancer

Hi willgamer,

Looking at your screenshots you're correct about Luga and Vyazma. Kursk is hard to tell.

Did you change Beta versions during the game?

Did the problem start before or after you'd captured an objective?

Cheers,
Cameron

Yes, this game was played starting with the first 1.02 and continued under each update since. So it was played, in part, with each of the 1.02 versions.

The problems started before any of the 3 objective cities were captured.

[lancer]

Hi willgamer,

I'd say the most likely cause is the succession of Beta updates. Lots of small, funny things like this have been occurring.

Not a given, though.

We'll keep an eye on it.

Cheers,
Cameron

[Philippeatbay]

And I couldn't help noticing the color of converted (?) rail lines. Is the color change on coversion to German gauge broken again ?