How to Organize Game Photo Mode Controls: A Basic Capture Path and Advanced Settings
For developers designing a game photo mode, put the controls needed to frame, review, and save a shot on the first screen. Group optional effects and fine adjustments in clearly labeled sections players can open when they want them. This keeps the everyday capture path short without removing the creative depth that experienced players may seek.
Start with the task a player came to do
A player who opens photo mode usually needs to get oriented, compose an image, and capture it. A useful first screen should make those actions discoverable before asking the player to learn camera terminology. Consider a compact set of controls: move and rotate the camera, reset the view, hide the interface, and take or save a screenshot. Add a small number of immediately legible choices—such as a grid overlay or a simple look preset—if they fit the game’s visual goals.
This proposed grouping follows patterns in shipped modes, rather than a universal standard. Dovetail’s current Train Sim World support guide separates movement, reset, grid, interface visibility, and screenshot actions from camera settings, image adjustments, and scene settings. Remedy’s announcement for Control described two tabs: camera options on one and filters or character visibility on the other. These examples show how distinct tasks can be separated, while leaving the precise grouping to each game. (Dovetail Games, “How do I use Photo Mode?”; Remedy Entertainment, “Control Gets Photo Mode Tomorrow, New Info on Expeditions Update”)
Treat capture as a complete path, not a scattered collection of buttons. The player should be able to enter the mode, frame the subject, hide overlays to inspect the composition, capture, and understand what happened next. If capture and saving are distinct steps in your game, label them distinctly. Give confirmation when an action succeeds, and make the route back to adjustment or exit easy to find.
Sort options by the decision they help players make
Avoid grouping every control under a broad label such as “Settings.” Instead, organize options around the questions they answer. A practical structure might include:
These are example categories, not a required taxonomy. Use the labels that match the game’s controls and the player’s mental model. Avoid placing a control in “Advanced” merely because its name sounds technical: a frequently used character-visibility toggle may belong on the main capture screen, while a less common effect may fit in an image-look section.
A useful test is whether two controls change the same kind of decision. Field of view and focus distance affect how the subject is framed or rendered; weather and character visibility alter the scene; color grading changes its visual treatment. Grouping by purpose helps players predict where an option lives. Add a short description where the label alone may not explain the visible result.
Reveal advanced controls progressively
Progressive disclosure means showing the controls needed for a straightforward shot first, while providing an explicit route to additional controls. It should not mean silently removing capabilities or making advanced features hard to find. Use visible section names, tabs, or expandable groups, and make the expanded state apparent. Preserve the player’s place when they open a section and return to the preview.
There is a useful precedent in Bend Studio’s description of Days Gone: the mode included lens and character controls, presets and frames, and an Advanced Mode with 55 settings across bloom and color-grading panels. The studio also described presets as a starting point for learning the advanced controls. That is one developer’s design, published in 2019; it does not establish that every photo mode needs dozens of controls. It does suggest a useful option for a complex toolset: let a player start from a known look, then expose the individual adjustments when they choose to refine it. (Bend Studio, “Everything you need to know about Days Gone’s feature-heavy Photo Mode”)
Make the cost of exploring clear. A player should know how to close a panel, return to the scene, reset a change, and tell whether a control is a toggle, slider, or selectable preset. Keep changes reversible where possible, and avoid making a player lose a carefully framed view just because they opened an adjustment group. If a feature changes more than the image—for example, if it changes the scene state—explain that before the player applies it.
Design a worked example around one shot
Imagine a hypothetical photo mode for a game with a character, a detailed environment, and optional color effects. A new player opens the mode to capture a character near a landmark. On the first screen, they can move and rotate the camera, reset it, show a composition grid, hide the interface, and capture. They choose a built-in look from a small preset selector. The shot is complete without visiting an advanced panel.
A player who wants a more deliberate portrait can open Camera to adjust field of view and focus, then Image look to tune exposure or color. If the game supports it, Scene and subject might offer character visibility or time-of-day options. A separate Advanced adjustments section could contain the additional grading parameters that only some players want to tune. This is an illustrative layout, not a claim about an existing game or a proven performance result.
Notice the decision sequence: composition first, treatment second, detailed tuning last. That ordering is an editorial design recommendation derived from the different functions represented in the cited photo-mode examples. It gives players an understandable route through the controls without asserting that every player will follow it or prefer the same workflow.
Make every layer usable with different inputs
A basic/advanced split can still fail if a control is hard to discover, navigate, or understand. Keep input prompts visible and appropriate to the active device. Ensure keyboard, controller, and any supported alternative input methods can reach the same essential actions. Avoid relying on color, position, or an unlabeled icon to communicate what a control does.
Accessibility applies to advanced panels too. Microsoft’s Xbox guidance says on-screen menu labels, control types, values, and interaction prompts should be available to screen narration, and describes announcing slider values as they change. Apply that principle to photo-mode controls: a narrated setting should identify its name, role, current value or state, and how to interact with it. A collapsed group should communicate that it can be opened; moving between layers should leave focus in a predictable place. (Microsoft Game Dev, “Xbox Accessibility Guideline 106: Screen narration”)
Do not make the preview the only source of meaning. A slider called “focal point” may need a brief explanation of what moves into focus; a toggle should announce whether it is on or off. For controls with a visible effect, a before-and-after preview can help, but it should not replace the text label, value, or an accessible interaction description. Ensure interface hiding does not strand the player without a known way to restore the controls.
Check whether the hierarchy works in practice
Evaluate the menu with a few concrete tasks rather than asking only whether players like the number of options. For example, ask a tester to take a simple screenshot, hide the interface and restore it, find a focus control, apply a preset, and undo a change. Observe where they look, whether they mistake a panel for a control, and whether they can explain what a setting will change before applying it.
Use the results to adjust labels, grouping, and the initial screen. If several testers search for a common control, consider surfacing it or making its category clearer. If an advanced control is rarely used in a particular build, that alone does not prove it should be removed; check whether its purpose is understandable and whether the intended audience needs it. This is a practical evaluation method, not a guarantee of usability outcomes.
Finally, test the capture and exit path after opening and closing advanced panels. Confirm that the framing is preserved as intended, the player can recover from unwanted changes, and the capture action gives clear feedback. Photo-mode behavior varies by game and may change between versions, so verify control mappings, save behavior, and any platform-specific capture flow against the build you ship.
Closing recommendation
Design the photo mode around a fast, complete capture path, then reveal deeper creative controls in purposeful, navigable layers. Put composition and capture actions where they are easy to find; group optional settings by the decisions they support; and explain each control in a form that can be read, navigated, and reversed. Use presets and advanced sections when they fit the game’s range of needs, then validate the hierarchy with real capture tasks on the supported inputs.