When setting the CameraType of the Camera to Custom, it resets the camera’s positioning. This is a problem as the game I am scripting for uses Scriptable camera position to lock the player’s camera when they are modifying the rotation/position of stuff using drag handles. Now every time they do this, the camera position will reset back to being behind them. I have tried to store the camera position in a variable and set it again after changing the CameraType to custom, but for some reason I am also complete unable to set the position of the player’s camera until they move it on their own. This happens every time it is set to Scriptable and back to Custom.
Expected behavior
I expect the camera position to stay in the spot it was in. This is how it has worked for years and it does not appear like there is a way for me to get around this issue.
Same issue here. In my game you often have to toggle lock-on off to stop yourself from doing the special attacks in a combo (think of DMC) but now your camera is jarringly set behind you.
Massive issue and hope staff gets on it quick. Running into the same issue with something I’m working on and it doesn’t seem there’s anything I can do to get around it.
Same issue here, the only way I was able to fix it was by saving the cframe and waiting a frame before resetting the camera to that position, but it doesn’t feel good in-game.
I am not sure if it changed at some point in the past few days. My solution has been to maintain the Custom camera type and just lock the camera by setting up a function in RunService:BindToRenderStep() to lock the camera in place. However, when I was testing other fixes, even just waiting a frame was not working out. In my testing, it did not matter how long I waited before setting the camera position after returning to CameraType.Custom. It depended on whether or not tthe player manually moved their camera or not yet. If the player did not move their camera yet, I would be entirely unable to set the position of it. So unfortunately, for now, RunService is my solution.
I have noticed this bug as well and it is very annoying. I think many games including my own were designed around the CFrame remaining unchanged after changing the camera from custom to scriptable and then back to custom. This did not happen before and it needs to be fixed.