Restructure numeric constants table in API docs
Break the monolithic numeric constants table into 6 sub-grouped tables: Version, Engine constants, Array sizes, Visualization, Rendering, UI constants. Fix stale values: mjMAXUITEXT (500->300), mjMAXUIMULTI (20->35), mjMAXUIEDIT (5->7), mjMAXUIRECT (15->25). Add missing constants: mjMAXLIGHT, mjMAXMATERIAL. Fix placeholder description for mjMAXFLEXNODES. PiperOrigin-RevId: 875010581 Change-Id: Id47846de4d98b62cb96087b72ecd28358d5db9c7
This commit is contained in:
committed by
Copybara-Service
parent
a83fa7299d
commit
40e0007849
@@ -724,7 +724,7 @@ Warnings are provided when memory requirements exceed existing allocations durin
|
||||
setting `m.opt.contact_sensor_maxmatch`. Alternatively, refactor the contact sensor matching criteria, for example if
|
||||
the 2 geoms of interest are known, specify ``geom1`` and ``geom2``.
|
||||
- ``height field collision overflow``: The number of potential contacts generated by a height field exceeds
|
||||
:ref:`mjMAXCONPAIR <glNumeric>` and some contacts are ignored. To resolve this warning, reduce the height field
|
||||
:ref:`mjMAXCONPAIR <glNumericEngine>` and some contacts are ignored. To resolve this warning, reduce the height field
|
||||
resolution or reduce the size of the geom interacting with the height field.
|
||||
|
||||
Compilation
|
||||
|
||||
Reference in New Issue
Block a user