Skip to content
Discussion options

You must be logged in to vote

You are correct. ObjectIDPicker uses an RTT technique to find the object at the location under the mouse. The object IDs of each on-screen object get rendered to a temporary texture, which it then queries for an object ID.

If you want to query a larger area and get nearby object IDs you can modify/write code based on the picker to do this. But this technique will not support more than one object ID at a given pixel.

PlaceNode's render in screen space which is why a normal intersector doesn't work. It sounds like you may need to roll your own code to do it.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@user-1199
Comment options

Answer selected by user-1199
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants