Starting with build 149879, the nearestObjects command fails to return certain terrain objects that it used to be able to detect in the past. One notable example is ATMs.
Description
Description
Details
Details
- Severity
- Minor
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Category
- Scripting
Steps To Reproduce
In A3 build 149799, on Altis, the command nearestObjects [[10655.9,12201.3,1.49722], [], 5] used to return something like [1f8c0c62080# 1813630: atm_01_f.p3d]. In build 149879, it returns [].
Related Objects
Related Objects
Event Timeline
Comment Actions
I was able to work around this bug by using nearestTerrainObjects [[10655.9,12201.3,1.49722], ["HIDE"], 5] instead.
Comment Actions
I’m not sure the versions are correct, here is screenshot in 2.08 https://feedback.bistudio.com/T167429#2354350
Comment Actions
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
The problem first appeared in the 2.10 hotfix released earlier this week, so it is most likely a side effect of the T167313 bugfix.
Comment Actions
rev 149916
possible hotfix. Dont use nearestObjects over long distances as objects might not exist that far