How to Fix Teardown FPS Related Tick() Issues When Transitioning to Update()

Fixing issues with physics when switching from tick to update.

The Issue

Hi. So I was just making a mod and was putting constrain functions in tick (it breaks your physics based on FPS DONT BE DUMB LIKE ME)

So, I figured I’d write a small guide to easily fix this issue with a single variable

If you check the teardown modding api it states that update does 60 refreshes in a second (similar to fps)

So all you need to do is take what the fps was during your testing (same map same code etc etc)

and then convert it to update by doing this

fixRatio = PreviousFPS/60