CoppeliaSim forums

Hello,

if you are using internal controllers for e.g. position or velocity control of a joint, you won't obtain meaningful forces/torques for that joint. Instead, you should use an inverse dynamics controller: have a look at the demo scene scenes/inverseDynamics.ttt

Cheers

Hello,

you can specify the location of your Python executable in CoppeliaSim's user settings file via the defaultPython item.

Cheers

Hello,

did you try to install (or not even install, just have it side-by-side) CoppeliaSim V4.10 (the latest) and see if there are problems? If yes, what problems did you notice?

Cheers

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 ...

The video is unfortunately private...

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 ...

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

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

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 ...

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 ...