This guide will show you how to easily fix the tick() issue when transitioning into update() in Teardown.
I was adding constrain functions in the “tick,” and that’s a problem because it messes up the physics based on how fast your computer draws frames (FPS). Silly mistake, right?
How to Fix
Here’s a simple guide to solve this issue with just one variable.
- In the Teardown modding API, it says that the “update” does 60 refreshes in a second, kind of like FPS.
- All you need to do is figure out what your FPS was during testing (same map, same code, and all that).
- Now, convert that FPS to the “update” by using this formula: fixRatio = PreviousFPS/60
That’s it! Easy fix to get your physics back on track.
That's everything we are sharing today for this Teardown guide. This guide was originally created and written by KevysNotHeavy. In case we fail to update this guide, you can find the latest update by following this link.