Describe the Bug
When creating an new world, and adding the default C or MATLAB controller using the Wizard "New Robot Controller", timestep (=64) don't match with the new created world (=32).
A better way to do is like in others default controller (C++, Python, Java) to use getBasicTimeStep .
I've no way to test for MATLAB a modification, so I let someone take it in charge.
Steps to Reproduce
Create a new world
See that basicTimeStep is 32
Create a new Matlab controller
See on line 13 TIME_STEP = 64;
Create a new C controller
See on line 18 #define TIME_STEP 64
Expected behavior
Default timestep should match. Use of getBasicTimeStep should be nice.
System
Operating System: Debian 11
Webots from master c3c2f47a39f0ac4eeffb27f4074c164421f49e3e
Describe the Bug When creating an new world, and adding the default C or MATLAB controller using the Wizard "New Robot Controller", timestep (=64) don't match with the new created world (=32). A better way to do is like in others default controller (C++, Python, Java) to use
getBasicTimeStep
. I've no way to test for MATLAB a modification, so I let someone take it in charge.Steps to Reproduce
TIME_STEP = 64;
#define TIME_STEP 64
Expected behavior Default timestep should match. Use of
getBasicTimeStep
should be nice.System