From 157040f74340cba28c931ad04b19e705db77b25a Mon Sep 17 00:00:00 2001 From: Nimrod Gileadi Date: Wed, 7 Aug 2024 09:06:21 -0700 Subject: [PATCH] Refer to tex_data in docs instead of tex_rgb. PiperOrigin-RevId: 660412293 Change-Id: I164099ecc36833e20d5adc2c7345aff351fc4561 --- doc/programming/simulation.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/programming/simulation.rst b/doc/programming/simulation.rst index ca1d0b60..d892ea03 100644 --- a/doc/programming/simulation.rst +++ b/doc/programming/simulation.rst @@ -567,7 +567,7 @@ because that may result in incorrect sizes or indexing. This rule does not hold parameters such as inertias are expected to obey certain properties. On the other hand, some structural parameters such as object types may be possible to change, but that depends on whether any sizes or indexes depend on them. Arrays of type mjtByte can be changed safely, since they are binary indicators that enable and disable certain -features. The only exception here is ``mjModel.tex_rgb`` which is texture data represented as mjtByte. +features. The only exception here is ``mjModel.tex_data`` which is texture data represented as mjtByte. When changing mjModel fields that corresponds to resources uploaded to the GPU, the user must also call the corresponding upload function: ``mjr_uploadTexture``, ``mjr_uploadMesh``, ``mjr_uploadHField``. Otherwise the data used