Matrix Games Forums

I recently got serious in starting my first mission, Operation E, as the allies vs the axis (AI). While fiddling around with the setup, I noticed that the WDF forward HQ would not be moved off Sidi Barani: I could drag it, but it snapped back when I let go, as if the unit was Fixed. But it didn't have a red F marker.

At first I regarded this as a small bug and went on my way.

Much later, as I was getting near the end of my setup, I decided I wanted to spread out my recon platoons (under the 7th Division) to watch for any deep flanking loops around my south by the Italians, so I put a spare recon platoon up near Sidi Barani as an early warning post. That was in the red-group zone, and no problem.

A little later I decided I didn't want it there, but farther south for earlier warning. But when I tried dragging it south... it acted like the unit was now Fixed. I could drag it, but it would snap back to its position when I let go the mouse.

That was seriously weird, but I forged ahead, choosing another scout to be placed there. Ummmm, nope, it was now acting Fixed, too.

Was the target hex outside the red zone? It didn't seem to be, but maybe I was missing somehow. I tried moving one of them to an alternate position well within the red-group zone. Same result.

Long story slightly shorter: ALL MY UNITS NOW ACT LIKE THEY ARE FIXED! Previously I could move them around as much as I pleased; they would be marked with the little yellow triangle indicating they had been moved, but otherwise no problem. After I tried to move that one recon platoon away from near (not in, but 3 or 4 hexes away from) Sidi Barani, all my units suddenly became fixed. No red F, but that's how they act.

I haven't started the mission yet (to see if the units stay "fixed" in effect); in fact I quit and didn't save, so I don't have a save of it either. But I thought I should report it.

That's strange. The only thing I can thing of is: was "Show Units At Destination" turned off (i.e. shows units at their start position, not their destination)?
(I'm in work so can't check if that's grayed out during Setup).
If it happens again, can you save a game, and reload it and check if the units are at their new positions (the positions you to which you moved them (and form which they snapped back))?

I'll have a look to see if it's possible that the "Show Units At Destination" can get inadvertantly turned off.

Thanks,
Brian

I confirmed that the "d" hotkey (which I might have easily tapped, trying to WADS the map focus around!) does function in "setup phase", and it does lead to the effect I mentioned: on one toggle everything works normally; on the other toggle the unit simply rubberbands back like it's fixed. It does NOT actually move the piece in that case, it simply rubberbands back, presumably because there's no "plot" (also thus no yellow move arrow) in the setup phase.

D should be disabled for setup phase, if possible, to prevent this happening.

I have also sort-of figured out what's happening, or not happening rather, to the WFG forward HQ in Sidi Barani. It has a light blue group triangle, not a red one, so even though it does not read as "fixed" (red nor green), it cannot be repositioned anywhere else in the red-group zone. It _can_ be placed back westward anywhere in the light blue zone! -- and then re-placed in Sidi Barani, which reads as a light-blue zone (although it looks more grey, thanks to the colors overlapping and clashing.) Once the mission starts then the HQ is free to move however it wants.

ORIGINAL: JasonPratt

I confirmed that the "d" hotkey (which I might have easily tapped, trying to WADS the map focus around!) does function in "setup phase", and it does lead to the effect I mentioned: on one toggle everything works normally; on the other toggle the unit simply rubberbands back like it's fixed. It does NOT actually move the piece in that case, it simply rubberbands back, presumably because there's no "plot" (also thus no yellow move arrow) in the setup phase.

D should be disabled for setup phase, if possible, to prevent this happening.

Great! Will fix in the next patch! [;)]