Babylon.js: Strange behavior intersectsMesh()

[azchatlanin]

This is your example https://www.babylonjs-playground.com/#C72JLZ#1

Please go to string number 68. Open console and see! At first it will print as expected! but if you replace the parameter as indicated in the comments, you'll see that the first works - "after", and only once.

Just watch when and what parameters are output in the console! When changing from truth to false and vice versa.

The same strange behavior occurs in other balls, if you change this BABYLON.Mesh.CreateBox to this BABYLON.MeshBuilder.CreateBox

[deltakosh]

Hello actually I do not see the problem :(

It changes when interacting with the mesh:
https://www.babylonjs-playground.com/#C72JLZ#2

[deltakosh]

[azchatlanin]

It should not be!

[deltakosh]

It should :) the ball starts in a position where it is not in collision

[azchatlanin]

Change the position of the ball! And everything will remain the same!

[deltakosh]

Not sure to follow you. THe test is about checking if the ball intersects the plane. If you move it to a position where it does not intersect then the message will be written.
Perhaps the text should be changed to "no intersection" instead of "after"

[azchatlanin]

IN your opinion, the animation starts with the fact that the ball collided with the ground? Regardless of where the ball is, the first animation is such!

pos 1: Ball has not yet collided with the ground , but in the picture he has already faced
pos 2: The ball is approaching the earth!

[deltakosh]

https://www.babylonjs-playground.com/#C72JLZ#3

Ball starts at a position where there is no intersection with the plane:

So this is correct:

[azchatlanin]

https://www.babylonjs-playground.com/#C72JLZ#4

Look at this example. Do the ball has already collided with the earth? Of course not! but in the picture the first picture shows that the collision occurred!

[azchatlanin]

Your picture suggests that the ball in the first frame collided with the ground! But really it's not!

[deltakosh]

ok I see it now :) will fix it!
Thank you !

[azchatlanin]

change state issues - unable to reproduce

[deltakosh]

yes my lord!

[azchatlanin]

)))

[deltakosh]

So it is not a bug actually :)
https://www.babylonjs-playground.com/#C72JLZ#5

I fixed it by using registerAfterRender. The point is we need the meshes to update their bounding info which is done automatically during render

Other way to fix it:
https://www.babylonjs-playground.com/#C72JLZ#6

you manually update the matrices

[azchatlanin]

Yes!)) It is elementary)) registerAfterRender and registerBeforeRender! Please, sorry me! Thank you!

[deltakosh]

No problem :)