Test unicode | Babylon.js Playground (babylonjs.com) In this example, the result of the mesh picking after deformation is still the same as before. How do I get the correct result for picking?

If you force the depth buffer to be 32 bits it’s a lot better (third parameter of enableDepthRenderer): Babylon.js Playground Babylon.js playground is a live editor for Babylon.js WebGL 3D scenes

Picking happens before the morphs are applied to the mesh so iirc it’s not possible to get the morph-deformed result, @Evgeni_Popov is that right? You could try GPU picking instead which would have the vertices already deformed, there’s a few topics on this forum about it if you search

It seems to be just as I guessed. I also read the article on GPU pickup schemes. However, since detailed coordinates and normal direction need to be obtained at that time, ray picking can be optimized using Octree. I gave up delving into GPU pickup schemes. Read this article： Using forceSharedVert…

Yes, you can calculate the normal from the depth buffer by reconstructing a position then doing the cross product between the x and y derivatives. See Improved normal reconstruction from depth – Wicked Engine Net for eg.

Test unicode | Babylon.js Playground (babylonjs.com) I created a case on playground to implement depth picking, but it seems to have precision problems, and there are abnormal normal lines after camera rotation and translation. I can’t find the cause of the problem. :smiling_face_with_tear:

GPU picking point and normal | Babylon.js Playground (babylonjs.com) I have fixed the error in normal calculation. It occurs because the screen coordinates are mirrored with the depth texture coordinates on the y axis. Now, the world coordinates and normal calculations are correct. But the accura…

[image] Streamer: This raises a new problem, when the boundary case occurs, the normal calculation will still be wrong. Do you have any suggestions? What do you mean by “boundary case”? Is it when the samples used to calculate the normal are not from the same object? If so, the link I gave a…

GPU picking point and normal | Babylon.js Playground (babylonjs.com) I tried using gbr.getGBuffer().textures[1] to get the normal, but the result is still wrong. It seems to have something to do with the attitude of the camera？

Using the geometry buffer renderer (gbr) was actually a bad idea… The morph target does not update normals, only positions, so the normals produced by the gbr are not correct (plus they are in view space, so you would have to multiply them by the inverse matrix of the view camera to get them in wor…

GPU picking point and normal | Babylon.js Playground (babylonjs.com) I followed the solution in the article to handle the boundary case, and now it works a lot better. It’s still not perfect. :weary:

How to obtain the correct picking result after morph application?

Questions

Evgeni_Popov May 17, 2023, 12:39pm 3

Indeed, see Using forceSharedVertices() to enable ray picking breaks my morph targets for eg.

Topic		Replies	Views
GPU picking point and normal example Demos and projects picking	31	3598	July 1, 2023
Using forceSharedVertices() to enable ray picking breaks my morph targets Questions morph , picking	3	749	December 24, 2022
GPU Picker: optional picked point and normal reconstruction Feature requests gpupicker	1	85	June 12, 2026
I used the depth map to pick up the coordinates, but it didn't work Questions depth	6	282	September 13, 2025
PickingInfo.getNormal() of a custom mesh Questions	1	335	April 4, 2023

How to obtain the correct picking result after morph application?

Related topics