Scene.pick results off on larger distances?

[Carharttguy]

Hello

I use the scene.pick function which is very nice. But I notice is it off on larger distances, is this because of JS number accuracy or is something wrong with the pick function?
I've made a small gif to show the problem. First close up, good, then a bit further, and you can see the chest is below the mouse pointer, like 20 px or so.

Thanks for insights

Mathias

 

[Temechon]

Hi,

Are you sure to set the 'camera' parameter in the pick function ? https://github.com/BabylonJS/Babylon.js/blob/master/src/babylon.scene.ts#L3578

 

[Carharttguy]

Hi Temechon, thanks for your reply.

No I didn't use the camera parameter. My old code was:

let pickresult = gEditor.getScene().pick(mouseX, mouseY);

New code:

let pickresult = gEditor.getScene().pick(mouseX, mouseY, null, true, gEditor.getCamera());

But the result is exactly the same, the code for setting the mesh position is simply:

gEditor.getAttachedMesh().position = pickresult.pickedPoint;

 

It's not a huge problem for me, I just find it odd.

[GameMonetize]

You have only one mesh? (Only the ground I mean?)

[Carharttguy]

Hi Deltakosh,

Yes, only the groundmesh and the chest mesh.

[GameMonetize]

Ok..can you repro in the Playground?

[Pryme8]

using scene.onPointerDown method does not seem to do it.
http://www.babylonjs-playground.com/#1D3XZJ#1
 

 

which is using the scene.pick function inherently I believe.