I think the main issue is the full stop between orders.  Staying at the same speed and heading until able to react to the next order would be a bit more believable, achieve more or less the same thing and hopefully be easier to implement.

There is nothing in your permissions that would prevent it.

I see a number of errors in the log, but not the one you are experiencing.

I'll dig around more.

Quote from: Iranon on August 08, 2018, 04:42:10 AM

IMO the biggest issue is what happens during delay... if orders change from "keep a distance of 200k" to "keep a distance of 300k", at no time should the task group sit idle and allow a slower enemy to close the range at will.

Agreed, a better behavior would be to continue with the previous order(s) until the delay has expired.

John

This I agree with... if there is an issue with order delay that should be fixed not the delay itself. There should never be a case where zero delay is a must to play the game.

In my opinion having some delay always being the case seem more interesting overall and also mean that crew grade and officers competence always will matter.

IMO the biggest issue is what happens during delay... if orders change from "keep a distance of 200k" to "keep a distance of 300k", at no time should the task group sit idle and allow a slower enemy to close the range at will.

Agreed, a better behavior would be to continue with the previous order(s) until the delay has expired.

John

IMO the biggest issue is what happens during delay... if orders change from "keep a distance of 200k" to "keep a distance of 300k", at no time should the task group sit idle and allow a slower enemy to close the range at will.