instant movement

[berto]

Even with

[*]Instant Movement OFF
[*]Movement Fast Slide OFF

and without my

[*]"click[ing] the left mouse button while the unit is moving so that it will instantly complete the move" (Manual, p. 44)

This is with sprites on, chits off... [edit:] no, with chit displays too.

I sometimes -- but not always! -- see units move a few hexes, then instantly teleport to their destination hex. Possibly applies to Force March movement only.

Yes, occasionally I like to speed things up, click the mouse button to force instant tele-moves. But for immersion's sake, usually I like units to move at the slow, stately pace. But it doesn't appear to be WAD, is hit or miss.

This is with the current 1.03 beta, and with an otherwise unloaded system (no other processes stealing CPUs cycles away from the game).

[AlessandroD]

Berto take a look at this post, can be your case.
Quote from Ericbabe's post: "but this happens in cases where the movement rules allow a unit to move through certain hexes at which they may not stop"

[berto]

No, my cases -- there have been two separate episodes of this -- are different.

In both cases, it was ordinary cross-country movement behind the lines. No Map scrolling or movement of any kind.

In the first case, it was Early's brigade, Force Marching from its starting location to the stream just north of Fort Magruder. Surely in every intervening hex, the units might stop there. Why would it be that for any of those hexes in that situation, they are hexes "at which they may not stop"?

The other episode, on a different turn, was the Southern infantry battalion at Fort Magruder moving up the road towards Redoubt 10.

...

In testing this again just now, it's now worse, a new problem:

[*]I Force Marched two regiments of Early's brigade towards that stream. They moved WAD, no teleporting.
[*]For the third regiment, I clicked the mouse mid-move. WAD, it instantly teleported to its final destination, but with the adjoining cyan move hexes still active.
[*]The mouse was then effectively useless. I could move the mouse pointer around, but could not click on anything, no displays or other tooltips worked, etc.
[*]I hit the Esc key, the lingering cyan movement hexes disappeared.
[*]The mouse function is still broken: I can move it around (and can scroll the screen), but only that. It is otherwise useless. I can't click on new units, no tooltips appear, the jump map doesn't work -- nothing.

The game is now effectively frozen (except for the mouse cursor movement and map scrolling). All I can do now it seems is to restart it.

[berto]

My hunch is that the teleporting problem maybe only applies to the sprites display. I have not observed the problem with chit movement. Maybe, maybe not, my data points -- just two separates episodes of this -- are so few.

[ericbabe]

Please see this thread: tm.asp?m=3843096

There is one movement routine for both chits and sprites. It first attempts to calculate a continuous movement path; if it finds one, it follows that. If it fails to find one, it defaults to a teleport. There are many reasons why the algorithm may fail to find the continuous move path -- I would have to explain the entire algorithm to explain all these reasons. The basic flaw in the algorithm is that it uses the actual movement costs to plot unit moves, and these values don't always allow for continuous movement paths. To fix this I would have to write a new algorithm mirroring the movement cost algorithm but eliminate any of the rules that are causing the movement discontinuities. This is quite a bit of work, and since this issue is purely cosmetic it's always been low on my list of priorities.

[berto]

Yes, I had read the thread.

And understood, about the priorities.

Cheers.

[miller7219]

I'm having the same problem since installing 1.03beta. Never had any mouse issues before. The mouse just stops wanting to click on any other units. Screen scrolling works and all clicking works fine, program just won't let you click on another unit. I have no idea what I was doing when it started, but it's definitely happening since installation of 1.03beta.

Anyone else having the same issue with 1.03beta? Maybe someone can narrow down what they were doing when the lock starts.

[ericbabe]

ORIGINAL: miller7219
I'm having the same problem since installing 1.03beta. Never had any mouse issues before. The mouse just stops wanting to click on any other units. Screen scrolling works and all clicking works fine, program just won't let you click on another unit. I have no idea what I was doing when it started, but it's definitely happening since installation of 1.03beta.

Anyone else having the same issue with 1.03beta? Maybe someone can narrow down what they were doing when the lock starts.

Is this with the OOB window open or shut?

[miller7219]

I played for an hour and couldn't get the locked mouse thing to occur again. The OOB window was definitely closed. It was sudden and seemingly random when I got it last time. If I come across it again I'll post it.

I did run across another issue. While combat is running I clicked on the "Game" button and I got the windows 7 program stopped working option box to wait of force shut down. I was just clicking on stuff to see if I could cause a problem! I would expect one wouldn't normally be clicking on stuff while combat is running. [:)]

[ericbabe]

Clicking on the game button during combat is not on my gigantic list of things to test for Good catch. I made a note to look into fixing this for a future patch.

[Erik Rutins]

Hi Miller7219,

In general, if you click around while the AI turn is running and combat is executing, Windows may get confused and think the game is not responding. If you just wait, the game will respond and that should clear up.

Regards,

- Erik