CAM by SEPA.gg 0.15.0 community preview — User guide CAM is a Windows desktop camera studio for Forza Horizon 6. Use Camera to adjust the driving view, Fly Free to compose a steady world shot, FPV Drone for Acro flight, and Mods to manage camera XML/INI files. No phone is required. This community preview supports the open world and Estates. Start with a short parked session to confirm your game build, camera view and controller mapping. Game updates and individual devices can affect compatibility. This guide describes the current interface, not a stable 1.0 release. START WITH A PARKED CAR 1. Close older CAM windows. Keep the supplied unpacked app folder together in a writable location. Launch CAM.exe; do not move the EXE away from its DLLs, resources and supporting files. 2. Use Game folder to select the folder containing ForzaHorizon6.exe. 3. Start FH6, park, and select a normal driving camera. Exit other camera tools before connecting. If an older CAM bridge was loaded, restart FH6 first. 4. Choose a workspace and follow the procedure below. Connect to FH6 creates the connection with camera control released; starting control is separate. 5. Keep Release within reach. Ctrl+Alt+Backspace releases globally when the shortcut is registered. The app warns if registration is unavailable. CAM does not suppress FH6's own keyboard or controller bindings. The same input can also drive the car or operate game menus. Use a parked car and separate or unbound driving controls while setting up and flying. CAMERA: FRAME THE DRIVING VIEW 1. Open Camera. Select Camera angles and choose a starting angle. Native framing is the zero-offset starting point. Chase, shoulder, quarter, rear, cockpit and hood choices are included; tune the fit for your car. 2. Read Suggested game camera under Fine tune > Framing. Select that camera yourself in FH6. This dropdown does not switch the game's camera. Changing it releases CAM's camera control so you can set the matching view. 3. Click Connect to FH6, then Start camera. Check the result in FH6. 4. In Framing, adjust Side, Height and Depth relative to the selected driving camera. Set Yaw, Pitch and Roll to change orientation. Blend time controls the transition: 0 is immediate; larger values ease into the new framing. 5. Open Lens. Follow game retains the game or installed mod's lens. Fixed lens sets a chosen field of view. Tight 35°, Balanced 60° and Wide 95° are quick starting points; Lens angle allows 25–130°. 6. Adjustments apply live while Camera is active. Use Release to return control to FH6. The connection can stay available for the next shot. The Composition preview is a 3D illustration, not a live FH6 feed. Orbit, Lens, Side view, Top view, drag-to-orbit and Reset 3D orbit change that illustration. The native lens is illustrated at 60°; this is not a reading of the game's FOV. Hide camera library gives the preview more room. Always judge the final frame in FH6. Position units are native game units, not calibrated metres. Save, compare and share a camera fine tune • Save fine tune stores position, orientation, lens, blend time and suggested game view. Enter a Preset name and save; find it under Saved fine tunes. • A duplicate name offers Keep both or Replace. Keep both adds a numbered copy. Replace preserves the previous file in history. • Camera angles change framing and blend time while retaining your current lens. Saved fine tunes recall their own lens and blend time. • Compare previous camera recalls the prior angle and lens. Load another angle first to make comparison available. It is a recall, not split-screen. • Export writes the current camera fine tune as a .live.json file at a location you choose. Show file reveals the completed export. • Import previews a compatible JSON preset. Review its name, game view and lens, then choose Add to library, Keep both or Replace. Importing adds it to Saved fine tunes without changing the active camera. Select it to use it. • Imported framing, FOV and blend time are retained. Older movement-effect fields are ignored; loading an older saved original does not rewrite it. FLY FREE: A STEADY WORLD CAMERA 1. Open Fly Free. If another flight mode is prepared, click Prepare Fly Free. Browsing the tab alone does not change the mode that currently owns control. Preparing a different mode releases control and clears the old origin. 2. In Current location, enter a useful estate or world-location label and click the location button to set it. This label is manual; CAM does not detect the Estate. Changing the label releases control. 3. Connect to FH6. Set a normal driving view where you want to begin, then click Capture origin. Wait for Origin captured. 4. Center movement and look controls, release any action buttons, then click Enable camera. A mapped Arm button can also enable a captured origin. 5. Hold the on-screen direction/height buttons, drag the aim pad, or use your configured keyboard/controller. Precise, Normal and Fast set the translation speed to 1, 10 and 45 native units per second. 6. In Motion, choose Level plane to move horizontally at the camera's heading, or Where you look to follow its orientation. Adjust Smoothing and Look rate. Motion changes save and lock flight; enable or unlock deliberately afterward. 7. In Position, enter exact X · Across, Y · Height and Z · Depth coordinates. Expand Orientation for Yaw, Pitch and Roll. Field of view is 25–110°. Top down points the camera down and levels its roll; it does not raise the camera. Aim at origin points toward the captured reference and resets roll. Move away from the origin before using it. Undo move recalls the previous stored framing change; it is not a recording or rewind of a flight path. Lock position holds the current frame. Unlock & rearm or Enable camera resumes only with neutral, fresh input. Release returns control to FH6 and clears the origin; capture again before the next flight. Camera and flight modes share a connection and cannot control the game camera simultaneously. The camera must stay within 300 native units of the captured origin on EACH axis. This is a bounded region, not a calibrated 300-metre travel radius. Reaching the boundary locks movement. There is no collision detection: the camera can pass through scenery. Distant scenery and scene transitions need in-game testing; move to a new starting point and recapture when necessary. Save and return to a view Use Save current view, enter a View name and Estate / location, then Save view. The view stores position, orientation and lens. Search collection finds names and locations; the collection groups entries by your location labels. Loading a view in the current labeled location with a captured origin recalls it if it is inside the allowed boundary. Otherwise CAM stages it and releases control: travel to that place yourself, capture a fresh origin nearby, then enable. A view outside the new origin's boundary is not applied. Loading a view does not teleport the car or load an Estate. Use the trash button to delete an unwanted entry. Keep copies of your data before deleting views. FPV DRONE: ACRO FLIGHT 1. Open FPV Drone and click Prepare FPV Drone when needed. Its tuning, device mappings and Flight starts are separate from Fly Free's saved profile. 2. Configure input before arming. For an Xbox pad, the recommended layout uses RT throttle. For a radio, map Pitch, Roll, Yaw and Throttle explicitly. 3. Preview Cinematic, Freestyle or Chase in Tuning. Selection only previews a tune; Apply flight tune saves it and locks flight. Cinematic is a useful gentle starting point. Existing settings are not silently replaced. 4. Connect, choose a clear normal driving view, then Capture launch point. 5. Set throttle to 0% and confirm the live throttle readout before Arm drone. Xbox FPV Mode 2: hold the left stick FULLY DOWN and keep it down while arming. A spring-centered stick gives about 50% throttle at center, not 0%. Xbox RT throttle: fully release RT and center both sticks; pulling the left stick down does not lower throttle in this layout. Center the other rotation axes, release action buttons, then click Arm drone or press the mapped Arm button. Raise throttle gradually after arming. Acro keeps its bank when the sticks center. Throttle supplies thrust along the drone's body-up direction; gravity, attitude, drag and momentum affect motion. Releasing throttle is zero thrust, not hover. Tilt against your travel to brake. There is no automatic level, collision avoidance or automatic car tracking. Tuning contains Center response, Rotation smoothing and Motor response. Expand Advanced flight for Pitch rate, Roll rate, Yaw rate, Maximum speed, Air resistance, Thrust, Gravity and Drag. The FEATURE REFERENCE lists all ranges, defaults and tune values. Manual physics changes save as Custom and lock flight. Restore previous tune restores the prior tuning in the current session; it is not a permanent tune-history library. Maximum speed 0 means Automatic with a 100 u/s ceiling. FPV does not inherit Fly Free's Precise/Normal/Fast speed. A low explicit ceiling can make different throttle positions reach the same speed. Throttle controls thrust; it does not set a target speed. Precision/Boost alter Acro rotation rates, not thrust or the speed ceiling. The console shows speed and, when mapped, USB throttle. Lens contains Field of view (25–110°) and Camera up-tilt (0–45°). Up-tilt helps you see ahead while pitching forward. Applying a tune changes its tilt and physics while preserving FOV and input mappings. Manual tilt saves as Custom and locks flight. A FOV-only edit applies after capture without resetting the drone's attitude or momentum. Use Save flight start to store a named position, orientation and lens. These entries appear under Flight starts and use the same location/capture boundary rules as Fly Free views. They are starting positions, not recorded flight paths. XBOX / XINPUT SETUP 1. Connect the pad to Windows; USB is a good first test. Release camera control before refreshing devices. Open Input setup > USB radio / gamepad. 2. Click Refresh controllers and select Xbox / XInput controller 1, 2, 3 or 4. Prefer this entry over a duplicate generic joystick listing so that the triggers stay independent. 3. A newly selected XInput slot gets its recommended layout. A slot with a saved mapping restores that mapping instead. Merely previewing a different layout does not apply it. Apply Xbox layout explicitly saves the shown layout and resets that slot's axis calibration, response and buttons; flight locks. 4. Capture an origin and review the live readings. For FPV RT throttle, fully release RT and center both sticks. For FPV Mode 2, hold the left stick FULLY DOWN; a spring-centered stick is about 50% throttle, not zero. Confirm live throttle reads 0% BEFORE clicking Arm drone, and keep the throttle control in that position while arming. Center the other axes. In Fly Free, center both sticks and release both triggers before enabling. Recommended FPV Drone layout: Left stick left/right Yaw Right stick up/down Pitch down/up Right stick right/left Bank right/left RT Analog throttle; released = zero LT Unassigned Fly Free layout: Left stick Forward/back and sideways Right stick Look left/right and up/down RT / LT Rise / descend Both triggers released No vertical command Equal trigger pressure Commands cancel each other Buttons in both recommended layouts: Menu Arm/resume a captured origin with neutral input X Lock B Release; capture again before starting LB / RB Precision / boost A, Y, View, LS, RS, D-pad Unassigned For optional FPV Mode 2, choose Left-stick throttle · FPV Mode 2 in Preview a layout, then Apply Xbox layout. Left-stick up/down becomes throttle and left/right remains yaw. Hold the left stick FULLY DOWN, confirm live throttle reads 0%, then click Arm drone while keeping it down. A spring-centered Xbox stick gives about 50% throttle at center, not 0%, so centering it prevents arming. Center yaw, pitch and roll; raise throttle gradually after arming. The right stick still controls pitch and bank. RT is the recommended pad layout: there, fully release RT to reach 0%; pulling the left stick down does not lower throttle. Profiles are stored per device and separately for the two flight modes. Xbox identity is a Windows XInput PLAYER SLOT, not a hardware serial number. The same slot restores the same profile; a different slot may need its own layout. Two physical pads assigned the same slot share that profile. Four XInput slots are supported. Radio profiles remain saved when switching to Xbox or keyboard. Keyboard/mouse preferences belong to the flight mode and carry across devices. Windows must expose the device through XInput for this layout. Xbox 360, One, Series and compatible pads may use that path; individual hardware, wireless connections and remappers still require testing. Reconnection never arms the camera automatically. Release Menu, center controls/lower throttle, then press Menu again deliberately. Holding Menu through an interruption cannot rearm. USB RADIO / OTHER GAMEPAD SETUP Put the controller/radio in its Windows PC joystick or gamepad USB mode. CAM can read Windows XInput, DirectInput devices and a WinMM fallback. A USB cable alone does not establish compatibility. Proprietary modes, including devices that do not expose a Windows input device, are not automatically supported. 1. Prepare the required flight mode, release control, refresh and select the Input device. Setup and calibration can be done without FH6 running. 2. Choose a flight channel. This only selects a channel for inspection; it does not start detection or change its direction. 3. Press Detect movement, then move only that control in the prompted direction and hold briefly. Detection waits up to 15 seconds. If several controls move, let them rest and try one again. Cancel or Escape stops listening. 4. Review the assigned axis and Invert direction. Raw input · before tuning is the hardware reading. Mapped output (Throttle output for throttle) includes calibration, deadzone, expo and inversion. Unsaved preview is not yet used for flight. Stale/disconnected readings show no valid mapped value. 5. You may choose an axis manually instead, or choose Not mapped to remove it. On XInput Fly Free, assigning a trigger to Up uses the paired RT/LT lift axis so released triggers give no vertical movement. 6. Use Lock & calibrate. Center an ordinary axis and Capture center, then sweep slowly through both endpoints and Finish sweep. For throttle, fully release the trigger or lower the stick, use Capture low, then sweep the full travel. 7. Fine-tune response offers Deadzone and Expo. Increase deadzone to ignore small unwanted input; higher expo softens the center. Invert direction reverses mapped output, so its preview changes even when the raw value does not. 8. Expand Controller buttons. For Arm, Precision, Boost, Pause, Lock or Emergency, choose a button manually or press its Detect button and then the hardware button. Use Not mapped to clear a binding. 9. Click Save mapping (or Save changes). Calibration, detection and inversion edits are drafts until saved. Review every channel before arming. 10. Finish/cancel setup, release ALL learned/action buttons, lower throttle and center the other controls. Capture if needed and explicitly arm/resume. The setup guard holds flight during learning and calibration. A button being learned cannot arm or release flight during setup. Detection does not auto-save or auto-arm. Focus loss, unplugging or device/mode changes cancel listening. Changing a channel keeps edits in the draft; save before switching devices. When a USB throttle axis is mapped, it owns FPV throttle. Space and on-screen full-throttle input do not override it. The console displays its live percent. Unplugging does not hand throttle to the keyboard; it locks flight. If keyboard control is disabled, map a throttle axis before trying to arm FPV Drone. KEYBOARD, MOUSE AND ON-SCREEN CONTROLS Defaults for Fly Free: W / S Forward / backward A / D Left / right E / Q Up / down Arrow keys Aim: left/right yaw, up/down pitch Z / C Roll left / right Defaults for FPV Drone: Up / Down Pitch up / down Left/Right Yaw left / right Z / C Roll left / right Space Full throttle while held, only with no mapped USB throttle axis W/A/S/D/E/Q are not FPV translation controls. Shared defaults: Ctrl Precision (15% movement/rate scale) Shift Boost (2× movement/rate scale) F9 Pause/hold flight F10 Lock flight F12 Emergency release while CAM/FH6 input is permitted After Pause or Lock, release the key, center controls/lower throttle, then explicitly enable/rearm. The global Ctrl+Alt+Backspace shortcut is separate from the remappable F12 input. Escape releases from the main CAM window; an open dialog closes instead. Escape cancels controller detection and may also release control; use its Cancel button to stop listening while held. In Input > Keyboard & mouse, Keyboard control starts on and Mouse aim starts off. Enable Mouse aim to hold right mouse and move the pointer to aim. The cursor stays free; it is not hidden, captured or warped. Mouse sensitivity is adjustable. These switches save and lock flight. To remap, expand Remap keyboard controls, focus a binding and press a key. Save keys applies the draft. Reset defaults fills the defaults into the draft; use Save keys to apply them. Typing or editing a control holds flight. Native input is permitted while CAM or FH6 has focus; switching to another app locks flight until you explicitly resume. The on-screen pads are hold-to-move controls, with an aim surface you can drag. They suit positioning and checking directions. They are not a latched throttle or a full simultaneous-stick substitute: releasing desktop input in Acro holds flight. Use a mapped controller for continuous analog flying. MODS: INSTALL OR RESTORE CAMERA FILES 1. Open Mods > Choose mods folder. Select a folder containing camera-mod ZIPs and/or extracted mod folders. CameraPhysics.xml and CameraSettings.ini are recognized together or individually; variants in a collection are listed. 2. Wait for the background scan. Camera controls remain usable while scanning. Search name or source and filter All files, ZIPs or Folders. Use Change folder for another source, or Rescan after adding files. 3. Open any folder notices. A large or unreadable collection may be incomplete; choose a smaller camera-mod folder when a scan limit is reported. 4. Click Review & install on the intended variant. Review camera files lists what will be installed. Check that the selected source is the one you want. 5. Click Install files. CAM releases camera control, backs up the exact current pair and installs the selected source bytes. An XML-only or INI-only mod keeps the other currently installed file. 6. FULLY RESTART FH6 to load the changed files, then reconnect. A return to a menu is not a full game restart. Check the camera behavior in FH6. Installed on disk means the files match the installed selection on disk. It does not prove the running game loaded them. Restart required is a reminder, not a live reload. Camera framing and FOV remain separate live controls. To undo a file install, choose Restore files, review Return to your latest backup, then Restore files. This restores the latest backed-up camera files; it does not promise a factory reset. Restart FH6 again. Saved fine tunes remain in your library. Keep the backups folder for recovery. STREAM PANEL AND APPEARANCE Stream panel opens a compact controller for Camera, Fly Free and FPV Drone without making a new connection. It starts pinned. Drag the header to position it; use Pin/Unpin panel and Return to studio. Camera can select a saved fine tune or camera angle; flight pages expose saved starts/views, capture, arm/enable, lock and Release. Configure detailed tuning in the full studio. Ctrl+Alt+S reveals CAM when registered; the panel shows if that shortcut is unavailable. Keep on top controls the full studio's pin. Use borderless or windowed FH6 for desktop overlays. An ordinary topmost window cannot reliably appear over exclusive fullscreen. Pinning does not change the game's mode. Light / Dark in the top bar changes and remembers the interface theme; Dark is the new-install default. The compact theme button uses the same preference. The question-mark Quick guide introduces the four workspaces. Keyboard focus and reduced-motion preference are supported. RECOVERY AND TROUBLESHOOTING Cannot connect: confirm Game folder, close competing camera tools, ensure FH6 is running in a normal driving camera, then reconnect. Restart FH6 if an older bridge was loaded. A game update may require compatibility work. Connected but no visible movement: control may be released, waiting for the game, or locked. Read the status, verify the suggested driving view, and start or capture/enable deliberately. App counters and diagrams are not proof of visible game output. Check the actual FH6 frame. Cannot arm: finish/cancel detection or calibration and release mapped buttons. For Xbox FPV Mode 2, hold the left stick FULLY DOWN and confirm live throttle reads 0% before clicking Arm drone; keep it down while arming. A centered spring stick is about 50% throttle, not zero, so it prevents arming. For the RT throttle layout, fully release RT and center both sticks; pulling the left stick down does not lower throttle. Center the other rotation axes. Ensure the selected device is connected and fresh, the app/game has focus, and an origin is captured. An empty USB mapping needs at least an axis/button; FPV with keyboard disabled needs mapped throttle. Flight suddenly holds: focus loss, stale input, a disconnected controller, editing, setup, boundary limits or a stalled sender can hold/release control. Fix the condition, return to neutral and explicitly resume. Long input stalls are not replayed as a large jump. Closing CAM releases control; the native sender lease expires after 500 ms without updates. Controller response is wrong: use Raw input and Mapped output to distinguish hardware readings from calibration/inversion. Finish a full endpoint sweep, save changes, and check the active device, mode and XInput slot. For throttle, verify a gradual percentage sweep and review Maximum speed before assuming the axis is digital. Camera service stopped: use Restart camera service in the error banner or Stream panel. Recovery returns disconnected and released. Connect again, then start or capture/arm deliberately. Failed mod installation is not automatically retried. The original failure is saved locally in logs/camera-service-*.txt; startup errors can be recorded in logs/desktop-startup-*.txt. When reporting a problem, include the CAM version, FH6 build, workspace, world/Estate context, steps, exact message, device/model/Windows mode and relevant local log. Review local paths in logs before sharing. No report is sent automatically. KEEP YOUR DATA Keep these folders alongside the app when moving or upgrading: live-presets Camera fine tunes and prior preset revisions flight-views Saved Fly Free views and FPV starts studio-data Flight profiles, per-device mappings and preferences backups Exact camera-file restore points logs Local diagnostics Back up the folders before an upgrade and close CAM before copying them. Existing mappings and saved data are preserved; migration keeps backup copies of older profile files. The supplied preview is an unpacked build. This guide does not announce a public download, installer or archive.