I have implemented a workaround to the affected script: https://github.com/A3Wasteland/ArmA3_Wasteland.Altis/commit/9cc182c6aff0dfa2f9f28925ce9d9ac9d2f60339
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Advanced Search
Sep 9 2022
The versions I indicated are correct; their bug report is what's incorrect. My ATM locator script they referenced uses allMissionObjects for editor ATMs, but nearestObjects for terrain ATMs. Here's the script with the workaround: https://github.com/A3Wasteland/ArmA3_Wasteland.Altis/commit/9cc182c6aff0dfa2f9f28925ce9d9ac9d2f60339
I was able to work around this bug by using nearestTerrainObjects [[10655.9,12201.3,1.49722], ["HIDE"], 5] instead.
Oct 25 2021
In T161546#2249658, @kju-PvPscene wrote:I guess Dedmen fears abuse by script kiddies?
That's highly unfortunate. This would have been way cleaner than the findDisplay 46 displayAddEventHandler ["KeyDown", {condition}] stuff that is required to override user input in vanilla missions.
Oct 22 2021
Nov 24 2020
6 and a half years later; better late than never!
Apr 4 2020
@BIS_fnc_KK wrote:try using getMissionPath