acemod / ACE3

Open-source realism mod for Arma 3
https://ace3.acemod.org
Other
994 stars 736 forks source link

ace_fastroping Causing Strange Helicopter Landing Behavior #4746

Closed E-Ledere closed 1 year ago

E-Ledere commented 7 years ago

Arma 3 Version: 1.66 (stable) CBA Version: 3.1.2 (stable) ACE3 Version: 3.8.2 (stable)

Mods:

Description:

Steps to reproduce:

  1. Place down player, helicopter, and landing pad.
  2. Give helicopter waypoint to land.
  3. If positioned correctly (and this happens in a surprisingly wide variety of locations, even locations completely devoid of obstacles for hundreds of meters, ie. airfields) the helicopter will display the behavior above.
  4. Remove ace_fastroping.pbo, reload the mission, and see the above behavior not replicated.

Due to this bug being slightly location dependent, I highly recommend using the test mission I created to replicate these results:

Test_Mission.Altis.zip

Where did the issue occur?

Placed Modules: None

RPT log file: Arma3_2016-12-04_09-21-25.txt

XDfort commented 7 years ago

Arma 3 Version: 1.7.0 CBA Version: 3.3.1 ACE3 Version: 3.9.2

Hello, I have to add that using the ALIVE addon, it happens exactly the same, the pilot descends but within a few meters of taking the LZ abort and retakes height.

I think the problem is the object that is created by adding FRIES to helicopters like the UH-80 GhostHawk. When the AI detects the object aborts the LZ to avoid colliding with it. Using the Zeus and eliminating that object the helicopter landed without problems, but eliminates the option to do fastrope.

Sorry for the grammatical errors, but I had to use Google Translator.

Thank you.

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

jonpas commented 5 years ago

Doesn't sound like anything we can do really, without affecting other AI behaviour or introducing issues for AI mods.

Mike-MF commented 1 year ago

Closing due to age, inactivity or already solved. May be re-opened if the issue is still present, even better just open a new up-to-date Issue.