LinesMesh - Picking - Picked point is returned as null

In our application, we use LinesMesh. On picking of line, PickingInfo.pickedPoint is returning null since 5.0.0.alpha.64. It used to return position value until 5.0.0.alpha.63

In the console output of sample app here, PickingInfo.pickedPoint is returned as null. Also, the faceId returned is -1
In the above app, if I use 5.0.0.alpha.63, pickedPoint is returning values.

Is there any new / additional property that needs to be set for getting pickedPoint (from alpha 64) for line mesh picking? or Am I missing anything?!

Strangely, Identical code in the playground sample here is returning values for PickingInfo.pickedPoint.

cc @sebavan who worked on it recently

1 Like

Cab you try with the latest beta (beta 5?)

I see the same problem in 5.0.0-beta.5 also. The sample app that’s shared uses beta 5 only.

It has been fixed right after the beta.5 Babylon.js Playground it will be in the next one

1 Like

Thanks. I’ll check it when next version is updated to npm.

Further, I just noticed in the Playground sample you have shared above, Scene.pick is picking a mesh that’s made not pickable (isPickable= false).
Whereas Scene.multiPick is picking the mesh as intended.
In console, Mesh id is printed. For both Scene.pick & Scene.multiPick ids should have been the same.

Actually what happens here is you are using a custom predicate scene.pointerMovePredicate = () => { return true; } bypassing checks for enable/disable picking and such so you always test all of them.

Then in the result of this one, you are calling multipick without predicate so the default applies and returns only the pickable one.

PointerMove does not pick except if explicitely required by action manager, or enablePointerMoveEvents, or scene.constantlyUpdateMeshUnderPointer


ok. So now I understand, Playground works with Nightly builds. Hope I’m right.

I got confused as the playground currently shows version as 5.0.0-beta.5 and I expected it could be matching with the build last released in NPM. Seems it’s not.

Yup playground is on nightly builds :slight_smile: the version will be updated on the next npm push

1 Like