Summary
In Fortnite Creative 1.0 the “First Person Camera” Device appears to have a bug when used in tandem with other cameras, that makes it impossible to make a custom fallback camera for items/actions it doesn’t support.
Please select what you are reporting on:
Creative
What Type of Bug are you experiencing?
Devices
Steps to Reproduce
1: Place a First Person Camera device and an Orbit Camera in the map
2: Set the Orbit Cameras offsets to be noticably different than the default camera, exact numbers shouldn’t matter but I have mine clipping inside the player character’s head.
3: Set the First Person Camera to priority 2, and the Orbit Camera to 1. Ensure both have “Add to players on start” enabled, and are enabled themselves.
4: Start the game with a gun that’s supported by the first-person camera and switch back and forth between the gun and your pickaxe.
Expected Result
It is expected that when the player switches to an item or does an action that the First Person Camera doesn’t support the game will fallback to the next highest priority camera, in this case the Orbit Camera.
Observed Result
Instead the Orbit Camera does not get used at any point while doing the test. This makes it impossible for the map maker to define a custom fallback camera for the fist person mode.
Platform(s)
Bug appears to not be platform specific. Occurs on my PC as well as my friend’s Xbox One, Xbox Series S, and PS5.
Video
Additional Notes
Even if this isn’t directly a bug, this is not desired behavior for me as a map maker, as I would like to be able to make a fallback camera for my first-person map so that players can’t peek around corners by emoting.
In the event that this likely undesired behavior needs to be kept possible to avoid breaking published maps, please add a toggle in the First Person Camera that changes it to what I believe to be the desired behavior.