What's the point of tracking individual volleys from artillery if the FO can't adjust after the first?

[byzantine1990]

When an FO calls artillery onto a moving unit, the barrage will hit one or more hexes behind the target.

In real life, wouldn't the FO be able to adjust fire to where the enemy moved?

Is this feasible in game? The hex the unit is in lights up orange showing the FO wants to call fire and follows the enemy unit . The barrage just doesn't move after the first call for fire.

[IronMikeGolf]

Without a concrete example (meaning a gave save file), here's what I suspect is happening.

1. FSCC mission requests are generated by specific friendly units. This is in response to a battlefield trigger, like an ENY unit moving or shooting or a friendly unit moving and discovering ENY units. That unit, and that unit only, is the Observer for the mission.
2. That goes into a queue and time elapses until the request can be handled. Then is get assigned to a firing unit.
3. More time elapses until the mission is ready to fire at the firing unit.
4. At the time the fire mission is executed, a check is made whether the Observing unit still has LOS on the target unit. If not, then the fires got to the initially reported location.
5. Overall, this behavior matches how things work on the ground. We could put a check fire on the original mission when LOS is lost. But, overall, Players are helped by keeping the mission active. Many times, such a mission lies on an area of interest, like the ENY axis of attack or a defensive position.
6. When a mission is fired, you do not get feedback on the observation state. This is a source of friction and is by design. As Bn/Bde/Regt commander/staff, the immediate info is mission fired and BDA. Why a mission didn't get desired BDA is an after-action topic.
7. You have the knobs and levers to shape your indirect fires both in time and space. You can use the SOP setting for any indirect firing unit to restrict mission requests they will respond to. You can remove a firing unit from FSCC control for a period of time, too.
8. I suggest you look at your battlespace and think about the practicality of engaging fleeting target with indirect fire and either arrange your support relationships between potential observers and firing units to minimize mission time or cut those potential observers out of the fire support network.

[CapnDarwin]

To add to Jeff's points above, there is a chance of the fire mission tracking a spotted moving target. We would need a save file with details on what units are involved so William can review for any possible bug.

Thanks.

[byzantine1990]

Without a concrete example (meaning a gave save file), here's what I suspect is happening.

1. FSCC mission requests are generated by specific friendly units. This is in response to a battlefield trigger, like an ENY unit moving or shooting or a friendly unit moving and discovering ENY units. That unit, and that unit only, is the Observer for the mission.
2. That goes into a queue and time elapses until the request can be handled. Then is get assigned to a firing unit.
3. More time elapses until the mission is ready to fire at the firing unit.
4. At the time the fire mission is executed, a check is made whether the Observing unit still has LOS on the target unit. If not, then the fires got to the initially reported location.
5. Overall, this behavior matches how things work on the ground. We could put a check fire on the original mission when LOS is lost. But, overall, Players are helped by keeping the mission active. Many times, such a mission lies on an area of interest, like the ENY axis of attack or a defensive position.
6. When a mission is fired, you do not get feedback on the observation state. This is a source of friction and is by design. As Bn/Bde/Regt commander/staff, the immediate info is mission fired and BDA. Why a mission didn't get desired BDA is an after-action topic.
7. You have the knobs and levers to shape your indirect fires both in time and space. You can use the SOP setting for any indirect firing unit to restrict mission requests they will respond to. You can remove a firing unit from FSCC control for a period of time, too.
8. I suggest you look at your battlespace and think about the practicality of engaging fleeting target with indirect fire and either arrange your support relationships between potential observers and firing units to minimize mission time or cut those potential observers out of the fire support network.

Thank you for the in depth answer. So FO'S have the ability to adjust fire to targets that have moved? I have a save file where the FO has continuous visual on a moving target but the fire mission isn't adjust from initial targeted hex.

[WildCatNL]

Thank you for the in depth answer. So FO'S have the ability to adjust fire to targets that have moved? I have a save file where the FO has continuous visual on a moving target but the fire mission isn't adjust from initial targeted hex.

Your save file would be appreciated. The game should shift HE fires for spotted moving targets but doesn't do that well enough (being restricted to 1 hex from the original target location).

[byzantine1990]

Thank you for the in depth answer. So FO'S have the ability to adjust fire to targets that have moved? I have a save file where the FO has continuous visual on a moving target but the fire mission isn't adjust from initial targeted hex.

Your save file would be appreciated. The game should shift HE fires for spotted moving targets but doesn't do that well enough (being restricted to 1 hex from the original target location).

I tried attaching the save files but it gave me errors. Do I get a dropbox link instead?

[CapnDarwin]

Try placing them in a zip file.

[byzantine1990]

I attached the save files. It is the first turn of the scenario and all four batteries are assigned to the scout furthest east. He has good view of multiple tank units that are moving west. In my tests the tanks only get hit once or twice during multiple turns.