CoppeliaSim forums

Hello,

have a look at the demo scene scenes/movingAlongAPath.ttt. Note that old path types are not supported anymore.

Cheers

You will have to look at Mujoco's 3 friction values mujoco.friction and maybe also mujoco.solref and mujoco.solimp. You'll need to play with those values and find the combination that best handles your task.

Cheers

Hello,

you won't be able to achieve a perfect dynamics simulation: errors, even small ones, will gradually accumulate and become visible.
In addition, how well you will be able to simulate a specific aspect highly depends on the used physics engine (you haven't mentioned which one you are using ...

CoppeliaSim is not meant for speed. Its emphasis is functionality, flexibility and ease of use. For speed, you should look at using one of the physics engines naked.

Cheers

It really depends on your IDE you are using. The mentioned add-on is an example for Notepad++. For other IDEs you will have to look at a different way to generate relevant files.

Cheers

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