Move vehicle forward when it is completely stopped

[Matic]

Hello,

when my CustomMultBodyVehicle stops, I cannot move it forward again with function: CustomMultBodyVehicleApplyTorque. When it stops, it is completely dead. How can I move forward CustomMultiBodyVehicle from 0 speed? Is this a bug in Newton?

I am using this function to apply tourque JOINTLIBRARY_API void CustomMultiBodyVehicleApplyTorque (NewtonUserJoint *car, int tireIndex, dFloat torque);

[Sweenie]

It's probably going to sleep because it haven't moved for some time.
Applying torque should wake a body up, but since the torque applied to the tires are applied inside the contraint this won't
happen since the constraint stops working when the body falls asleep.

Try the following function on the chassi body to prevent it from going to sleep.

NewtonBodySetAutoSleep (const NewtonBody* body, int state);
state = 1 means it will go to sleep when no movement is detected.
state = 0 means it will always be simulated.

or just apply a small impulse to it.

[Matic]

Thanks I will try that.I have another question. I am using CustomMultiBodyVehicle on iPad and it is using almost 100% percent of CPU. When I comment it out CPU usage falls down to 3% (all other physics objects and collision detection are still in the scene).

Code: Select all

struct iNewtonUserJoint* vehicle = [world CreateCustomMultiBodyVehicle:&chassisMatrix.m_front.m_x :&chassisMatrix.m_up.m_x :vehicleBody];

Then I addTires and use TireTransformCallBack to draw them.

Any ideas? Is there problem with CustomMultiBodyVehicle perhaps?

[JernejL]

The multibody vehicle might be too much cpu intensive for ipad to handle. Try the raycast vehicle instead?

[Matic]

Hi,

thanks for answer. RayCastVehicle isn't available in Newton 2.33 . Any other options?

[banjkeee]

Any other options?

Use 2.20