CoppeliaSim forums

Hello, yes, that is right. The sim.pauseSimulation API command actually only makes sense if there is some interaction with the user afterwards, otherwise there is no need/reason to pause a simulation: instead, simply do not step anymore and the result is the same. However, try to add function sysCal...

Hello,

it seems you are trying to use the old, deprecated remote API. Make sure to use the ZeroMQ remote APi, which is faster, more flexible, and simpler to use.

Cheers

Hello,

please do not use the legacy remote API anymore. Instead, use the ZeroMQ remote API, which is more flexible, complete, and faster.

To retrieve the handle of an object via the ZeroMQ remote API, do this:
Cheers

Hello, have a look at following functions for example: sim.createPrimitiveShape sim.createMeshShape sim.loadModel sim.setObjectInt32Param(shapeHandle, sim.shapeintparam_respondable, respondable) sim.setObjectInt32Param(shapeHandle, sim.shapeintparam_static, static) sim.setShapeMass sim.setShapeInert...

Hello,

the error very probably happens because the signal is not set (yet), and the call to sim.getFloatSignal returns nothing. So you can't assign nothing to a variable in MATLAB. Use a try-catch block to handle a possibly non-existing return value.

Cheers

See also the demo scene scenes/movingAlongAPath-lua.ttt

Cheers

Hello, yes, it is normal that the display is black, since you disabled rendering with: sim.setBoolParam(sim.boolparam_display_enabled, False) Disabling rendering will not disable vision sensors that will still be able to function normally. Instead of sim.getVisionSensorCharImage, use sim.getVisionSe...

Hello,

it seems that Windows is now handling console windows in a grouped fashion, and you cannot directly hide individual consoles anymore: those consoles will simply be minimized, not hidden. This now also happens with older CoppeliaSim releases (on Windows 11).

Cheers

Hello, this is an undocumented feature. Use following to get inspiration: --lua sim = require'sim' function sysCall_thread() while true do -- Read the keyboard messages (make sure the focus is on the main window, scene view): local msg, auxData = sim.getSimulatorMessage() if msg ~= -1 then if msg ==...

Hello,

thanks for the mention, yes, we are aware of that and it should be fixed for next release (in 2-4 weeks).

Cheers