null vehicle handling values leads to physics freeze

[CeebDev]

What happened?

OUTDATED See #3097 (comment)
Since at least b3258, going in certains slopes areas in a vehicle will cause physics state freeze.

The vehicle can't be unblocked, even if you fix it or going away with noclip

This is a video of what's happening

2025-01-25_03-27-27.mp4

Expected result

Vehicle should not lose physics

Reproduction steps

SetVehicleHandlingFloat(veh, "CHandlingData", "fTractionCurveMin", null);
SetVehicleHandlingFloat(veh, "CHandlingData", "fTractionCurveMax", null);
SetVehicleHandlingFloat(veh, "CHandlingData", "fLowSpeedTractionLossMult", null);

• Try to drift to activate vehicle physics

Importancy

Slight inconvenience

Area(s)

FiveM

Specific version(s)

tested on b3258 and b3407

Additional information

No response

[CeebDev]

After investigation, this was due to a change on our codebase.

For a unknown reason, some data for the handling change (offroad script) was received as null.

So this is another problem:

fTractionCurveMin / fTractionCurveMax / fLowSpeedTractionLossMult can be set to null without any errors.

Setting these values to null will result in what you see in the video when the physics need one of those.