You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
directly to the initial XML used for the initial instantiation (task.xml). In this test, I did not use any recompilation.
The mesh is loaded successfully (as part of the initial global_spec):
Question:
Is this a bug in how MuJoCo handles <default> definitions during recompilation? If not, what changes are necessary to ensure the expected behavior when using attachment and recompilation?
The text was updated successfully, but these errors were encountered:
Description:
I encountered inconsistent behavior when attaching a new mesh to the simulation
worldbody
and recompiling.Steps to Reproduce:
mjSpec
object (global_spec
) and compile it intomjModel
andmjData
.mjSpec
object (child_spec
).worldbody
fromchild_spec
toglobal_spec
and recompile.Code Example:
Temporary XML file: (parsed into
child_spec
)Expectation: (after recompilation)
Result: (after recompilation)
To verify that the mesh can be loaded successfully, I included the following lines:
directly to the initial XML used for the initial instantiation (
task.xml
). In this test, I did not use any recompilation.The mesh is loaded successfully (as part of the initial
global_spec
):Question:
Is this a bug in how MuJoCo handles
<default>
definitions during recompilation? If not, what changes are necessary to ensure the expected behavior when using attachment and recompilation?The text was updated successfully, but these errors were encountered: