Jump to content

f-18hornet

ED Team
  • Posts

    2223
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by f-18hornet

  1. Hi @Northstar98, here is a mission where SEAD task for AI is not removed and AIs attack SON-9. The issues was if mission designer want AI attack rotating radar when it track AI - mission designer should not remove all target filters, but allow AI to search and select targets by standart enroute task SEAD - initial track removes all positive target filters (by removing SEAD enroute task) and try to make AI one-time task - attack radar that is impossible. AI_F-4E_AGM-45A_Mk50_SON-9_FireWhenTracked.miz null
  2. Hi @Convoy, at the end of that track, no UH-1H crashed or was damaged. Do you have any other track, please?
  3. Hi @Convoy, can you please provide a track?
  4. Hi @AG-51_Razor, this is not a bug. "Uncontrolled" state means that AI doesn't controll aircraft, no FM, collision, behaviour etc calculation executed for "uncontrolled" aircraft. Although previously it was possible to push a task like "Follow" for "uncontrolled" unit that lead to unexpected behaviour or even crash, so now pushed or setted tasks for "uncontrolled" aircraft ignored - this is necessary for stability and performance increasing. Second point is the route of "unconrolled" heli consists of only one waypoint - this means that after take off AI start executing it's mission - and as mission have only one WP - it is completed same time(when no more WP fly to left in the mission - mission is complete). So it is better to make more WPs for second heli and place "Follow" task there. It is clear that second heli can start at random moment and fixed WP can be far away of the ships formation, so another way to solve this task is to add start condition for "Follow" task - for example set flag when heli takes off and climb to some altitude.
  5. Thank you, reported.
  6. Hi @Eole, can you please attach a mission you are editing? I am not able to replicate any issue.
  7. Thank you, reported.
  8. Thank you, reported.
  9. Thank you, reported.
  10. Hi @Frenchy74, can you please provide a track? I am not able to replicate any issue.
  11. Thank you, reported for internal analysis.
  12. Thank you, reported.
  13. Thank you, reported for analysis.
  14. Thank you, reported for internal analysis.
  15. Thank you, reported for analysis.
  16. Thank you, reported.
  17. Thank you, reported for internal analysis.
×
×
  • Create New...