Feedback Public Beta BftB v4.4.264

[BigDuke66]

The problem I reported for v4.4.262 is still there:
To sum it up:
There is a delay between the former task of an order and the following defend task, a simple example is a defend order that has a move task which is followed by a defend task.
The move task is reported complete but the following defend task usually starts much much later, In my test scenario(Elsborn Ridge) sometimes 30-40 minutes but also up to around 90 minutes.
And that can happen in every order that has a defend task like secure/deny crossing, delay, withdraw, etc., I think even orders that are completed and where the units switch to defend because no other order is given show this behavior.

Anyone can test that himself, just try Elsborn Ridge and give one of the German bat a defend task nearby. You will see that it starts to move to position till move task is reported complete, still not all units are in position and the defend task for the closer and the move task for the units further away start with a big delay(as said 30 minutes up to 90 minutes).

Reminds of the attack problem that also add a delay in that shouldn't have been there because there was simply a gap between the task done and the start of the next task.

[navwarcol]

I think per the rules that all move orders become defend tasks upon the move's completion, negating the need for separate defend orders to follow. Or am I reading too much into your topic (this is also quite possible, sorry if so)

[navwarcol]

Disregard my above, I think I get what you are saying. I have seen this often and just assumed it is part of the orders delay. I can live with it, but if it is a bug, yes, it would be nice to fix!

[BigDuke66]

Order delay is just the delay between giving an order and the start of processing this order by the designated units.
Within the process of fulfilling this order there shouldn't be any delay, at least none that is so large and that can't be explained away with any real life behavior of combat units.

[wodin]

Isn't this time supposed to be your troops getting themselves into position etc etc..?

[jimcarravall]

ORIGINAL: BigDuke66

The problem I reported for v4.4.262 is still there:
To sum it up:
There is a delay between the former task of an order and the following defend task, a simple example is a defend order that has a move task which is followed by a defend task.
The move task is reported complete but the following defend task usually starts much much later, In my test scenario(Elsborn Ridge) sometimes 30-40 minutes but also up to around 90 minutes.
And that can happen in every order that has a defend task like secure/deny crossing, delay, withdraw, etc., I think even orders that are completed and where the units switch to defend because no other order is given show this behavior.

Anyone can test that himself, just try Elsborn Ridge and give one of the German bat a defend task nearby. You will see that it starts to move to position till move task is reported complete, still not all units are in position and the defend task for the closer and the move task for the units further away start with a big delay(as said 30 minutes up to 90 minutes).

Reminds of the attack problem that also add a delay in that shouldn't have been there because there was simply a gap between the task done and the start of the next task.

In order to defend, it takes time for the troops which are in a line formation following a move order, to get into their most effective defensive positions.

Yes, they can "defend" when they stop.

But, it takes time to disperse into effective defensive positions which take into account line of fire and cover to assure that the defense is effective.

You might check into the various defense formations (dug-in; entrenched; fortified).

Each has a time period before it becomes effective.

Likewise, from ending movement in a column with lead echelon of four soldiers facing a potential location of an attack to dispersing to a line formation where cross fires can defeat that attack more effectively by expanding the front to face that attack takes time, which varies depending on the type of terrain that has to be traversed by units and individuals to get into the appropriate defense formation.

http://www.ibiblio.org/hyperwar/USA/ref ... /FM7-5.pdf

http://www.ibiblio.org/hyperwar/USA/ref ... M17-10.PDF

http://www.ibiblio.org/hyperwar/USA/ref ... index.html

[BigDuke66]

@wodin
No this isn't time to get into position, because they simply don't get into position as even the most forward units still have to make there final move to get to their defensive position.
The really effects of taking time to form a defensive position are the various states of entrenchment(dug-in, entrenched, fortified) a unit can have if being long enough in a position.

@jimcarravallah
True and if we would speak about a reorg task that comes AFTER the units are in position I would find that perfectly plausible and highly realistic but we speak of units that simply stop doing what they should because the move task is reported as complete and the next task doesn't start before a considerably time went by, we simply have a gap in the orders that simply should follow one after another and not with a large pause in between.
As said neither the most forward nor the units still far back have reach their final positions so none should make anything at all except move on to the area where they should form a defense position.
As also said that is close to the thing we saw on attack moves some patches back, they simply stopped doing what they should be doing, and if it wasn't plausible at that time it isn't plausible now.
Especially as orders that don't involve a defend task don't have this delay.

[BigDuke66]

I have now compared the situation to an attack order and here we see that when the move task is reported as complete there is a minor delay of some minutes before another move task starts that is again followed by a reorg task on the final position for the attack.
Good here you can argue also that it looks strange to first have a move task that is superseded by another move task but in the end the overall movement, pace and start/finish of the attack looks quit plausible to me.

So and on an order that has a defend task the second move task doesn't start before much time went by, in my test 80 minutes and that simply can't be correct.

Just try it yourself, take Elsborn Ridge, use one of the German bat. and give it a defend order 2-3 kilometers ahead, check when they finally get into position, now start again and do the same again but this time give an attack order on the same position you used for the defend order, I bet the whole attack is solved long before the unit reach the defensive positions, at least now anyone should see that here something is deeply wrong.
Or is it normal to have an attack on an objective finished long before simply driving up, loading off and taking up defensive positions at the same objective?
Not on any planet I know...

[BigDuke66]

*cough cough*

[navwarcol]

I was going to bump this also BigDuke. But from another thread I read that Dave's daughter is in the hospital I believe, so I am sure this has been noticed. I was surprised it was not part of the patch that was released though.

[BigDuke66]

I thought the Dave's daughter was already on the road to recovery.
Of course if that is still on the table I don't mind that priorities are different, my were too.

[Arjuna]

No she is back in hospital again. On top of that I have been without internet for the last five days due to a failed set top box. Just got it fixed today.

[BigDuke66]

Sorry to hear that Dave, I hope she gets well again.

[dazkaz15]

When you give a defend order it seems to be split into two tasks now. This was introduced quite a while back, and as I usually keep my command capacity low I don’t notice it to much, and was not sure if it was by design or not.
In the scenario I have been playing, I have very long command delay now, as I am taking advantage of the no orders delay for the arriving para drops, and have a lot of units moving individually into positions.

So for a defend order now, I have a command delay of say 2 hours (I’m fine with that as I have overloaded the boss), then when the unit gets near the defend position it stops, and another full command delay is introduced for the final short leg (about 200 meters) of its defend task.

So for a defend task to complete I have a 4 hour command delay.
There is only one command delay for a move order, so I have been using this as a work around, by moving to the defend position then placing a defend order with facing etc on the counter, once it gets there, but it requires more, unnecessary, user interaction this way.

[Arjuna]

Am I right in assuming that you have given the Defend order ata distant location and that the force must do a Move to that location before defending. If so there should not be a significant delay transtioning between the end of the Move and the start of the Defend. Do you have a save taken just before the end of the Move?

[dazkaz15]

I can re-produce it very easily, as it happens on every defend order. The longer the command delay the longer the pause after the initial move.
I also think this has something to do with the unit not moving if given a short distance defend order.

It appears that if you place the defend order, within the radius of the counter, that it would have paused before processing its defend order after the move, then it will not move at all. Even after a command delay.

For moves shorter than about 300-500m its always best to use a move order to be 100% sure it will work.
If you give it a defend order within this distance, it usually does nothing.

Its very late here now, so I'll sort out a save for the tomorrow night.

[Arjuna]

If you issue a Defend order and the force is already deployed within the perimeter then there is a very good chance it will stay put and take advantage of its current deployed state. The probability is increased if the force is dug in or entrenched. The Ai will search through the force and separate out any units that meet these conditions. It will then issue them with a Defend inSitu order and issue a normal Defend to the rest of the force.

[BigDuke66]

Well I point to my starting post and my other postings in this theead and to the feedback of the former patch, it is this way at least since May and I don't think anything I saw is "normal" at all.
Simple and straight:
1. Defend order issued
2. Units move too position
3. Close to position move task is reported finished
4. They sit around and wait, wait, wait, wait...
5 A final move of the units into position

Test this simply by yourself:
Load Elsborn Ridge and give one of the German bat a defend task nearby. You will see that it starts to move to position till move task is reported complete, still not all units are in position and the defend task for the closer and the move task for the units further away start with a big delay(30 minutes up to 90 minutes).

[jimcarravall]

ORIGINAL: BigDuke66

Well I point to my starting post and my other postings in this theead and to the feedback of the former patch, it is this way at least since May and I don't think anything I saw is "normal" at all.
Simple and straight:
1. Defend order issued
2. Units move too position
3. Close to position move task is reported finished
4. They sit around and wait, wait, wait, wait...
5 A final move of the units into position

Test this simply by yourself:
Load Elsborn Ridge and give one of the German bat a defend task nearby. You will see that it starts to move to position till move task is reported complete, still not all units are in position and the defend task for the closer and the move task for the units further away start with a big delay(30 minutes up to 90 minutes).

Since player preferences affect how the game performs AI tasks, you'll get a more definitive answer to the problem if you send the autosave from the game between the time you issued the order and when the odd behavior was noted (if one or more exists, send the autosave closest to the time the odd behavior starts) or, as an alternative, run the scenario to some point after you issue the order and do your own save before the problem occurs.

[BigDuke66]

Well I send a bunch of saves to panthergames(contact@panthergames.com), I saved after every step:
1. After giving the order
2. After AI sets moves for order
3. After AI move task finished
4. After new task is set by AI
5. AI fully reached ordered position

After I first ordered the task a did not change anything except set speed to max, but also slower speeds didn't change anything.