Move BVH active visualization flag reset after early return check in MuJoCo collision driver.

This avoids unnecessarily resetting the bvh_active flags when the collision driver returns early due to disabled constraints, disabled contacts, or having fewer than two bodies/flexes.

PiperOrigin-RevId: 959531283
Change-Id: I85caf054b06e3be1018d710f9ab762627fc3356a
This commit is contained in:
Alessio Quaglino
2026-08-05 02:41:02 -07:00
committed by Copybara-Service
parent f9a00bd5b5
commit 1362a8bded
9 changed files with 20 additions and 13 deletions
+3
View File
@@ -47,6 +47,9 @@ Engine
of the effective-metric Cholesky factor, which no longer exists; ``mjData.efm_L`` now holds dense 3x3 blocks,
9 numbers per covered vertex. ``mjData.efm_active`` no longer takes the value 2: nothing selects a solve path on
preconditioner exactness, so it is now a plain 0/1 flag.
- Changed the default value of :ref:`bvactive<visual-global-bvactive>` from "true" to "false". This avoids
unnecessarily clearing bounding volume hierarchy visualization flags at every simulation step, which can be a
bottleneck for models with large meshes.
Models
^^^^^^