Document compiler/usethread fix.
PiperOrigin-RevId: 855735924 Change-Id: I5b638ccf2a74194b363cf7c6436f78c1c3d9b0e1
This commit is contained in:
committed by
Copybara-Service
parent
a49576e469
commit
7e21f18fd3
@@ -828,7 +828,7 @@ has any effect. The settings here are global and apply to the entire model.
|
||||
|
||||
:at:`usethread`: :at-val:`[false, true], "true"`
|
||||
If this attribute is "true", the model compiler will run in multi-threaded mode. Currently multi-threading is used
|
||||
for computing the length ranges of actuators and for parallel loading of meshes.
|
||||
for computing the length ranges of actuators and for parallel loading and processing of meshes.
|
||||
|
||||
.. _compiler-fusestatic:
|
||||
|
||||
|
||||
@@ -65,6 +65,9 @@ Documentation
|
||||
|
||||
Bug fixes
|
||||
^^^^^^^^^
|
||||
- Multi threaded mesh processing, enabled by the :ref:`usethread<compiler-usethread>` compiler flag (on by default), was
|
||||
in fact disabled by the flag. Fixing this bug speeds up compilation of mesh-heavy models by (up to) the number of
|
||||
available cores.
|
||||
- The ``vertid`` argument of :ref:`mju_rayFlex` and :ref:`mju_raySkin` was marked as nullable but was not; it is now
|
||||
nullable.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user