Thanks for the quick reply @Evgeni_Popov and for the updated docs!
I’m wondering how to get around this without reimplementing a chunk of the picking logic in userland. From this reply:
I understand that it would be a major rework to differentiate between thin instances in the action manager code. Is that right?
I’m thinking a leaner way would be to use debounce logic. I see that both pointer over and point out events are emitted in alternance. When the mouse stops on the mesh, the last event is a pointer over, and when the mouse starts moving again the first one is a pointer out event. I could set a debounce type of logic to ignore pointer out/over events if they are emitted too close to each other. This is relatively straight forward to do in userland (I think) so I would be happy with the solution.
2 questions though:
- do you think i’m missing something?
- would there be any interest in integrating that to the BJS code to solve for thin instance pointer over event?
Thanks again