Decimating a mesh is completely a different procedure than generating a convex mesh (or convex decomposed mesh).
In the case of such a simple mesh, simply approximate it with 5 cuboids as previously stated. You can still keep the original mesh just for visuals (make sure that in that case it is not ...
Search found 6100 matches
- 20 Jun 2025, 13:44
- Forum: General questions
- Topic: Further property strings for MuJoCo
- Replies: 7
- Views: 1906
- 14 Jun 2025, 12:52
- Forum: Videos, scenes and models around CoppeliaSim
- Topic: Exoskeleton Robot Project
- Replies: 2
- Views: 674
Re: Exoskeleton Robot Project
The video is unfortunately private...
- 14 Jun 2025, 12:50
- Forum: General questions
- Topic: Further property strings for MuJoCo
- Replies: 7
- Views: 1906
Re: Further property strings for MuJoCo
Hello,
from the picture, I can't see what type of shape this bin is: scene files are always better than pictures, My guess it is simply a random mesh. If this is the case, then MuJoCo and some other engines might use a convex hull alternative instead. If you do not want this, then you need to ...
from the picture, I can't see what type of shape this bin is: scene files are always better than pictures, My guess it is simply a random mesh. If this is the case, then MuJoCo and some other engines might use a convex hull alternative instead. If you do not want this, then you need to ...
- 11 Jun 2025, 14:00
- Forum: General questions
- Topic: Further property strings for MuJoCo
- Replies: 7
- Views: 1906
Re: Further property strings for MuJoCo
It should work from a simulation script. From a customization script, you'll have to add this e.g. to the sysCall_actuation section, the very first time it is called.
Cheers
Cheers
- 11 Jun 2025, 10:53
- Forum: General questions
- Topic: Further property strings for MuJoCo
- Replies: 7
- Views: 1906
Re: Further property strings for MuJoCo
Hello,
fitaabb is a compiler attribute, not a shape/geom attribute. But following should work:
function sysCall_init()
simMujoco = require'simMujoco'
local info = {}
info.element='mujoco'
info.xml='<compiler fitaabb="true"/>'
simMujoco.addInjection(info)
end
Cheers
fitaabb is a compiler attribute, not a shape/geom attribute. But following should work:
function sysCall_init()
simMujoco = require'simMujoco'
local info = {}
info.element='mujoco'
info.xml='<compiler fitaabb="true"/>'
simMujoco.addInjection(info)
end
Cheers
- 09 Jun 2025, 15:21
- Forum: Bug reports
- Topic: increasing memory usage causes crash (newton physics-engine)
- Replies: 1
- Views: 742
Re: increasing memory usage causes crash (newton physics-engine)
Hello,
very probably the memory leak happens in the Newton library itself. We can't fix or improve that, as we do not upgrade physics engines when available (except for MuJoCo), as most engine upgrades will break compatibility (i.e. behavior change, wich we didn't observe with MuJoCo).
As of now ...
very probably the memory leak happens in the Newton library itself. We can't fix or improve that, as we do not upgrade physics engines when available (except for MuJoCo), as most engine upgrades will break compatibility (i.e. behavior change, wich we didn't observe with MuJoCo).
As of now ...
- 03 Jun 2025, 19:45
- Forum: Bug reports
- Topic: no opengl info in ubuntu22.04
- Replies: 1
- Views: 6719
Re: no opengl info in ubuntu22.04
Difficult to say... I hear that for the first time, so it must be something with your system/machine I guess. Asking Deepseek I got this answer, maybe you could try some of those:
This issue typically occurs when there's a mismatch between the Qt version's OpenGL requirements and the system's ...
This issue typically occurs when there's a mismatch between the Qt version's OpenGL requirements and the system's ...
- 02 Jun 2025, 11:45
- Forum: Bug reports
- Topic: error message despite using eigen plugin
- Replies: 1
- Views: 4978
Re: error message despite using eigen plugin
Hello,
this is normal: previously, we had similar Matrix and Vector classes implicitly loaded. Many scripts still use that, thus the warning.
The better approach would be to explicitly use the Matrix and Vector classes from the simEigen module, like you are doing.
Cheers
this is normal: previously, we had similar Matrix and Vector classes implicitly loaded. Many scripts still use that, thus the warning.
The better approach would be to explicitly use the Matrix and Vector classes from the simEigen module, like you are doing.
Cheers
- 01 Jun 2025, 13:22
- Forum: Bug reports
- Topic: urdf import plugIn
- Replies: 5
- Views: 10801
Re: urdf import plugIn
There is indeed a regression that we introduced in V4.10
You can find fixed simURDF plugins here (Win and Ubuntu only).
Cheers
You can find fixed simURDF plugins here (Win and Ubuntu only).
Cheers
- 28 May 2025, 12:42
- Forum: Bug reports
- Topic: urdf import plugIn
- Replies: 5
- Views: 10801
Re: urdf import plugIn
Can you share how you exactly import the URDF? Do you use a replacement string for "package"?
Cheers
Cheers