Obstacle courses are what I make for the longest time. Unfortunately, since 2016 (1 DECADE AGO!) a peculiar issue appeared with the Studio camera scripts being tied to the render thread, with the client having none of those issues. Suppose we move our camera by 10 degrees in any direction at 60 FPS. If your framerate drops to 15, the camera will move by 40 DEGREES INSTEAD, which is a really painful issue.
Expected behavior
Camera scripts tie to a separate thread instead of the render thread. Genius solution: track the camera rotation externally with a vector that gets set to the camera’s current look vector every render, and update the value separately from the render thread. Then, update the camera rotation on the render thread using said values.
A private message is associated with this bug report