Page MenuHomeFeedback Tracker

nearestObjects no longer finding certain terrain objects after last hotfix
Feedback, NormalPublic


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.


Operating System
Windows 10 x64
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 [].

Event Timeline

AgentRev created this task.Sep 9 2022, 6:53 AM
AgentRev edited Steps To Reproduce. (Show Details)

I was able to work around this bug by using nearestTerrainObjects [[10655.9,12201.3,1.49722], ["HIDE"], 5] instead.

I’m not sure the versions are correct, here is screenshot in 2.08

AgentRev added a comment.EditedSep 9 2022, 10:28 AM

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:

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.

Reproed, [] broken

rev 149916

possible hotfix. Dont use nearestObjects over long distances as objects might not exist that far

BIS_fnc_KK removed BIS_fnc_KK as the assignee of this task.Sep 9 2022, 12:28 PM
BIS_fnc_KK changed the task status from New to Feedback.