Currently, this issue causes the camera to lock to the Scriptable CameraType. Changing the enum manually to something else, or even with the command bar, doesn’t seem to do anything.
Open up a place, any place should do.
Save the place as a file.
Close the place.
Open the place file.
The camera will now be Scriptable instead of the enum it was originally set to. Considering I can’t change the enum, it seems the only way for developers to get around this right now is to delete the camera.
Do you have any building plugins active that set the camera to scriptable? Building tools do this, and if they don’t also set the the CurrentCamera.Archivable to false, it will save the cameraType out to the file if you save while the plugin is active. The fact that you can’t edit it manually or from the command bar suggests that a script is repeatedly setting it.
Well that was it. Plugins hadn’t crossed my mind for this issue, but after turning all of them off and testing the ones which I felt may have caused this, it turns out this old plugin is the source of my issue.
Thank you for the help, and sorry that this was posted without a little more work in looking into what caused this.
No worries, glad I could help. It can be less than obvious what plugins are doing, especially ones that set up key bindings or don’t clean up after themselves correctly, so turning them all off and restarting is like booting in Safe Mode if you use a lot of plugins
