Page 1 of 1

1463 Strike Mission Possible Bug: Undesired Orbit/Hold at waypoint

Posted: Tue Oct 01, 2024 10:46 am
by boogabooga
In the attached scenario, I do not understand why the flight is orbiting waypoint 4. WP 4 should be locked in speed, not time- and no hold has been specified for that WP. This is a fixed takeoff time mission, not a fixed ToT mission.

Re: 1463 Strike Mission Possible Bug: Undesired Orbit/Hold at waypoint

Posted: Tue Oct 01, 2024 11:44 am
by blu3s
We're aware of the units circling WPs, mainly this is due to not being in the correct altitude and until the AC reachs the correct altitude it will circle the WP.

Also can be related to waiting for ToT strikes.

Re: 1463 Strike Mission Possible Bug: Undesired Orbit/Hold at waypoint

Posted: Tue Oct 08, 2024 12:30 pm
by boogabooga
The flight reaches its assigned altitude just fine well before reaching Waypoint 4.
blu3s wrote: Tue Oct 01, 2024 11:44 am Also can be related to waiting for ToT strikes.
This was not a ToT strike. It was a fixed takeoff time strike. Waypoints 4-6 are locked in speed, not time.

The hold just seems unnecessary.

Are the fixed takeoff time strikes still trying to adhere to ToT?

Re: 1463 Strike Mission Possible Bug: Undesired Orbit/Hold at waypoint

Posted: Wed Oct 09, 2024 3:40 pm
by Kushan04
boogabooga wrote: Tue Oct 08, 2024 12:30 pm The flight reaches its assigned altitude just fine well before reaching Waypoint 4.
blu3s wrote: Tue Oct 01, 2024 11:44 am Also can be related to waiting for ToT strikes.
This was not a ToT strike. It was a fixed takeoff time strike. Waypoints 4-6 are locked in speed, not time.

The hold just seems unnecessary.

Are the fixed takeoff time strikes still trying to adhere to ToT?
If you use Take Off Time, it's going to generate a Time on Target. Just like if you use ToT, it generates a Take Off Time. The AI is going to try an adhere to ToT regardless of how it was generated.

Re: 1463 Strike Mission Possible Bug: Undesired Orbit/Hold at waypoint

Posted: Thu Oct 10, 2024 12:54 am
by boogabooga
Kushan04 wrote: Wed Oct 09, 2024 3:40 pm
If you use Take Off Time, it's going to generate a Time on Target. Just like if you use ToT, it generates a Take Off Time. The AI is going to try an adhere to ToT regardless of how it was generated.
Could you please explain the purpose of the little red and green lock symbols in the flight planner then?

If I unlock the time for the target WP (and all the ingress WPs, too) and lock the speed, I would expect the AI to just follow the waypoints at the locked speed and ignore the time.

And if I were to do a ToT attack, I would expect the AI to adhere to the ToT as much as possible by varying speed and not by loitering around a waypoint.

And if loitering were necessary and could be anticipated, I would expect it to appear in the appropriate column of the flight planner.

But having my flight loiter in enemy territory- without any warning that they were even going to do that- is basically a terrible idea most of the time. In most cases, I'd rather have had them just arrive at target a few minutes early.

Re: 1463 Strike Mission Possible Bug: Undesired Orbit/Hold at waypoint

Posted: Tue Oct 22, 2024 7:53 am
by DWReese
Fighter/Bombers trying to be "stealthy" are anything but if they perform unnecessary circles around a WP.

The plane is unnecessarily exposing every angle of its shape to the enemy and risks detection with every movement and turn.