Body SaveState question

[Ivan-le-sketch]

I'm considering using Jolt for a multiplayer game using some sort of rollback netcode approach and am looking for ways to reduce the amount of data to save/be sent over the wire.

Would it make sense to exclude Body MotionProperties force and torque from the recorded state and ensuring these are always zero before recording ? I'm not very experienced regarding how the engine works but I'm assuming force and torque are zero at the end of the simulation step.

[jrouwe]

They are zero after the step indeed, so if you always make a snapshot right after the step then you could leave them out. The rule for SaveState is that it should only save properties that are calculated by the engine and not properties that have been supplied by the user through the public API, so they should not have been added in the first place. However, I'm a bit worried that I'll break peoples code in subtle ways if I remove these.

[Ivan-le-sketch]

Fair enough. Would you consider adding a way to choose to either include or exclude them ?

[jrouwe]

I'd rather not as that makes things messy.