Collide mask

General Discussion
1

hello,

CollisionNode.GroundCol.setFromCollideMask(1048575)

0000 0000 0000 1111 1111 1111 1111 1111 - default max value in object all

but:

CollisionNode.GroundCol.setFromCollideMask(1048576)

0000 0000 0001 0000 0000 0000 0000 0000 - It is the engine slowing

Those. maximum range - 1048575?

2

That happens to be the “into” bit that is set by default for visible geometry:

>>> GeomNode.getDefaultCollideMask()
 0000 0000 0001 0000 0000 0000 0000 0000

So when you enable that, you are telling Panda to collide with all visible geometry, which is very slow.

If you want to use bit 20 for your own nodes, then you have to set a different collide mask (eg. all-zero) to your geometry.

3

Like on what basis ?
In the file egg is no record of a collision :exclamation:
But begins to count the panda valid …

4

If you set that bit, Panda will convert the visible geometry into collision geometry on the fly (even if there is no collision information in the .egg file). This should be avoided because this is much slower than just specifying collision information in the .egg file.