I also have a Xin7 64-bit box. The tests in the next section are with it, also confirmed to be running 4.4.260.
I loaded up a new Hoffen, didn't let the clock start, grabbed the 12cm Hvy Mtr Pl 12 Coy and plotted a fire mission.
The duration that comes up is 2 days 5 hours and 59 minutes.
If I then start the clock, let the fire mission begin, cancel it (with the clock running) and then plot a new mission (with the same unit)on another target, I see an initial duration of 2 days, 5 hours and 49 minutes.
I can repeat this ad infinitum.
I can't try with other units at the beginning because they have no ammo.
If I switch to the St. Vith demo scenario, open it, grab the 66 Ar Bn and plot a fire mission with the clock stopped, I see a duration of 3 days 23 hours 59 minutes.
If I cancel this mission with the clock now running, and plot a new fire mission I see a duration of: 3 days 23 hours and 48 minutes.
I then go back to my WinXP box and run the same St.Vith test with the following:
I see exactly the same initial results. When I plot a new fire mission with the clock ticking, it is 3 days, 23 hours and 51 minutes.
Again, I can repeat this ad infinitum.
On the WinXP box I open Joe's Bridge. Clock stopped. plot a mission with the ABTY 153 Gds Arty and I see a duration of 1 day 23 hours and 59 minutes.
cancel, plot a new mission with the clock running and see a duration of 1 day, 23 hours and 51 minutes.
So I see a consistent behaviour the is repeatable, that demonstrates a slight difference in results if the clock is running.
I am out of time right now - but I will come back latter to see if you want me to run another test.
All are on realist delay. all other settings are default. No other orders are initiated by me in any of the tests.
Both boxes are confirmed as running the latest beta.
"Popular Opinion? What I suggest you do with 'Popular Opinion' is biologically impossible and morally questionable." -
"One ping to find them all,
One ping to link them;
One ping to promote them all,
and in the darkness sink them"