Scenes

With Camera Plus you can have multiple profiles and a different set of cameras per profile, with Camera2 you instead have your pool of all cameras and can enable or disable them per scene. If you need more specific scenes for certain situations that dont fit a gameplay situation you can use Custom Scenes.

Currently, there are these scenes:

• Menu
• MultiplayerMenu
• Playing
• Playing360
• PlayingModmap
• PlayingMulti
• SpectatingMulti
• Replay
• FPFC

Scenes have a hierarchy / priority order to them, The more "Specific" a scene is the higher its priority is when deciding which scene should be used. These hierarchies are:

• Group 1

1. FPFC, If active

• Group 2 (If playing a song)

1. SpectatingMulti
2. Replay / PlayingMulti
3. PlayingModmap / Playing360
4. Playing

• Group 3

1. MultiplayerMenu
2. Menu

Examples:

• You dont have any cameras assigned to any scene => All cameras are active at all times

• You only have one camera which is assigned to the Menu scene, have FPFC active and are in the Multiplayer Menu => FPFC(empty) ▶️ MultiplayerMenu(empty) ▶️ Menu ends up used as it has a camera

• You have a camera assigned to FPFC, and another to Menu, are in a song but not in FPFC => FPFC(Has a camera, but is inactive) ▶️ Playing(empty) ▶️ Menu ends up used as it has a camera

• You are watching the replay of a Modmap and have cameras assigned to the Replay scene, as Replay has a higher priority than PlayingModmap, the Replay scene will be used

Custom Scenes

Custom scenes can be used to build "Special" views that dont fit a specific gameplay situation / which are used sparingly, like for example a fullscreen static thirdperson camera for lightshows to use in a break or something.

Custom Scenes can currently only be configured by editing the Scenes.json found in the Camera2 settings folder.

Keep in mind that, by default, Camera2 will still switch away from custom scenes if the game scene changes. If you want to change this behaviour so that Camera2 stays on custom scenes until you manually disable it, you need to change autoswitchFromCustom to false in the Scenes.json config.

Heres a little video walkthrough curtesy of Fefeland on custom scenes!

Examples

Heres a couple of examples for how the "customScenes" and "customSceneBindings" values need to look like inside the Scenes.json file

• You want a scene called "Fullscreen Firstperson only" which only contains one camera called "FirstPerson" and can be enabled by pressing F2:

• You want to add a second scene which contains a smaller first person camera and one positionable camera and have that bound to F3:

Custom scenes UI

If you have at least one custom scene defined when the game is started you will get this UI inside the game which allows you to switch to / from custom scenes without needing access to a keyboard: