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 (إطارا في الثانية). Silly mistake, يمين?
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 “تحديث” يفعل 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
That’s it! Easy fix to get your physics back on track.
هذا كل ما نشاركه اليوم من أجل هذا Teardown مرشد. تم إنشاء هذا الدليل وكتابته في الأصل بواسطة KevysNotHeavy. في حالة فشلنا في تحديث هذا الدليل, يمكنك العثور على آخر تحديث باتباع هذا وصلة.