This guide will show you how to easily fix the tick() issue when transitioning into update() in Teardown.
Issue Overview
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, 오른쪽?
수정 방법
Here’s a simple guide to solve this issue with just one variable.
- In the Teardown modding API, it says that the “업데이트” 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).
- 지금, convert that FPS to the “업데이트” by using this formula: fixRatio = PreviousFPS/60
그게 다야! Easy fix to get your physics back on track.
이것이 오늘 우리가 공유하는 모든 것입니다. 분해 가이드. 이 가이드는 원래 작성자가 작성하고 작성했습니다. KevysNotHeavy. 이 가이드를 업데이트하지 못한 경우, 다음을 수행하여 최신 업데이트를 찾을 수 있습니다. 링크.