Map issue...

[Laxplayer]

I am trying to move my troops from Kragen (54, 103) to Soerabaja (56, 104). There aren't any enemy troops in the hex between them (hex 55, 103), but I am getting the message "Unable to reach target, move not allowed." The problem exists when moving between Kragen (54, 103) and the hex between the two bases (55, 103). Even though the hex is connected by both a road and a rail, it's not letting me move. I've attached a pic to show the situation.

I was able to clear a lane to evac troops quickly from Tjilijap to Soerabaja by using my little armored scout units to recapture bases in Java to open that lane. Really sucks that all the work was for naught.

[Laxplayer]

also... it's not allowing movement from 54, 103 to 55, 103, or the opposite direction.

[GB68]

Hmmm... I'm guessing that the program is auto-selecting another route via the base at 54,104 which is Japanese occupied.

You might have to do it one hex at a time via hex 55,103 then Soerabaja. Try that and see what happens?

Edit: ignore , I've just seen your new post!

[BigJ62]

Post a save.

[Laxplayer]

last save...

[treespider]

Its a map data error I remember seeing it in my PBeM game but then forgot about it...the hexside is coded as prohibited terrain. Easily spotted when hotkey is used...

[Laxplayer]

So it's WAD? If so then something should be done about the rail and road that connects the two hexes. Is it easier just to open it up to movement?

[treespider]

ORIGINAL: Laxplayer

So it's WAD? If so then something should be done about the rail and road that connects the two hexes. Is it easier just to open it up to movement?

It's a map data "error"..."error" generally means it is not WAD. The hexside is not coded correctly...which means it is broke which means it is not WAD.

[Laxplayer]

Wasn't sure that "error" didn't simply mean that the map was drawn incorrectly and that you are not supposed to be able to travel across that hexside, therefore making it WAD, but poorly displayed [:)]

[wdolson]

I believe it's been fixed for patch 2.

Bill