Drive World leverages Roblox’s CameraInput player script API for our in-car camera. As of 1pm PST today, Roblox enabled a flag inside of CameraInput player scripts that is causing an error with our code.
Here is our stack trace
And the line of code inside of CameraInput causing the issues. Appears to be related to a flag that was enabled.
Feel free to reach out to me if you need our code that is using CameraInput.
Hello, I’ve rolled back the flag. Can you please share how you are using the playerscripts CameraInput API?
I believe you’re calling the internal CameraInput.getRotation method outside of PlayerScripts. These methods were not intended to be officially supported APIs and are not guaranteed to remain unchanged. Can you either remove the reference to the method in your game or fork PlayerScripts and force the flag to false to guarantee the method won’t change in your game?
While I can do that for Drive World, I don’t think it’s fair to expect any other developer to know what API in player scripts are intended to public use and which aren’t. Outside of the player scripts is a wild west hell hole where you are responsible for handling all inputs on every single device.
I’ve used this method in multiple projects to support custom freecam and to implement cross-platform support for panning + zooming.
Edit: The issue appears to be the usage of dT variable, which my call did not pass. I’ll fix this on our end but Roblox will need to wait until our changes are fully rolled out to game clients since we are not interested in shutting down for a Roblox-induced issue.
Yep, we’ve identified PlayerScript APIs as a confusing part of development at Roblox. We’re in the process of updating how we serve PlayerScripts to games and how you can custom their behavior without sacrificing future updates.
For now, any changes you make to camera and controls outside of those within StarterPlayer should fork the PlayerScripts as they were not originally intended to be read or used externally.
Thank you. I’ve found CameraInput to be one of the most useful player scripts and would love the cross-platform functionality it provides to be an officially supported API in the future.
In the past, forking PlayerScripts was a no-no since you would have always wanted the most up to date controls and bug fixes. Will fork them for the time being to ensure we don’t run into other live issues.
