Fix order of enable flag strings. Before this change, using the UI to toggle the "InvDiscrete" and "Sensornoise" flags would toggle the opposite flag.

PiperOrigin-RevId: 618658133
Change-Id: I35d4b9da2fdf68fed24efd518a30af60d3a806eb

doc/changelog.rst

@@ -59,6 +59,11 @@ Python bindings
 .. |ls_colab| image:: https://colab.research.google.com/assets/colab-badge.svg
               :target: https://colab.research.google.com/github/google-deepmind/mujoco/blob/main/python/least_squares.ipynb
 
+Simulate
+^^^^^^^^
+13. Fixed bug in order of enable flag strings. Before this change, using the simulate UI to toggle the
+    :ref:`invdiscrete<option-flag-invdiscrete>` or :ref:`sensornoise<option-flag-sensornoise>`
+    flags would actually toggle the other flag.
 
 Version 3.1.2 (February 05, 2024)
 -----------------------------------

src/engine/engine_support.c

@@ -66,8 +66,8 @@ const char* mjENABLESTRING[mjNENABLE] = {
   "Override",
   "Energy",
   "Fwdinv",
-  "Sensornoise",
   "InvDiscrete",
+  "Sensornoise",
   "MultiCCD",
   "Island"
 };