MLCP solver blows up for smaller timestep?

[maletinkert9n]

Strangely, the MLCP solver blows up as I decrease the (fixed) simulation timestep from 10 us down to 1 (some instability) and 0.1 us (totally blows up). Is this an intrinsic property of the MLCP algorithm or is it just because timesteps this small get into rounding off errors?

Strangely, the simulation works just fine for the largest timestep of 10 us.

[Basroil]

Strangely, the MLCP solver blows up as I decrease the (fixed) simulation timestep from 10 us down to 1 (some instability) and 0.1 us (totally blows up). Is this an intrinsic property of the MLCP algorithm or is it just because timesteps this small get into rounding off errors?

Strangely, the simulation works just fine for the largest timestep of 10 us.

For timesteps that small you'll likely need double precision, and even then it might not be perfectly stable. Considering the default step is ~16ms, 1us is quite a bit outside the intended step size

[Erwin Coumans]

There is no 'MLCPSolver' that you can execute, it is just an interface. Please provide the actual MLCPSolver that you use,
such as btDantzigLCP, btLemkeSolver,btSolveProjectedGaussSeidel or btPATHSolver.

It is very common to run the regular btSequentialImpulseConstraintSolver at 1000Hz or 3000Hz, using double precision. I haven't done much testing running the other solvers at small time steps.
Thanks,
Erwin