by SEPA.ggCAM cannot connect or the camera service stopped
Service recovery never automatically retries a mod installation. Keep the original logs/camera-service-*.txt failure log; startup failures may also create logs/desktop-startup-*.txt.
Check the game and folder
Start FH6 and select the installation containing ForzaHorizon6.exe. Park safely and use a normal driving camera.
Close competing camera tools
Close other CAM windows, RealCam, Estate Judge and any other tool controlling the camera.
Recover a stopped service
Use Restart camera service in the error banner. Recovery returns disconnected and released. Connect again, then start or capture/arm deliberately.
Restart an older bridge session
If FH6 already loaded a bridge from an older build, fully restart FH6 before testing the new app.
Flight will not arm or has locked
- Prepare the intended mode and capture a fresh origin. Release clears the old origin.
- Xbox RT throttle: release RT fully and center both sticks. Check live throttle is 0%.
- Xbox Mode 2: hold left stick fully DOWN and confirm 0% throttle. Keep it down while arming. Center is roughly 50%, so it cannot arm.
- Finish or cancel input detection and calibration. Save settings, release held buttons, then rearm.
- Return focus to CAM or FH6. Focus loss, stale input, controller disconnection and long stalls hold flight.
- Release Menu before pressing it again. Holding it through a reconnect does not rearm.
- If you reached the 300-unit boundary, release, relocate and capture a fresh origin.
The drone falls or throttle feels wrong
Zero throttle is not hover. FPV uses an Acro model with gravity and persistent attitude. Centered rotation sticks do not level the drone.
Sweep the control and compare raw input, mapped output and live throttle percentage. Check calibration and the Maximum speed ceiling. A low ceiling can make different amounts of thrust feel equally fast.
A mapped USB throttle axis owns throttle even when keyboard controls are enabled. Space cannot override it. Maximum speed 0 is Automatic with a 100 native-unit/second ceiling.
A USB radio is missing or Xbox mapping changed
A controller must expose a Windows joystick/gamepad device or XInput through its driver. Use a radio’s PC joystick mode. A USB cable alone does not make a proprietary DJI mode or a vendor-specific driver compatible.
Refresh the device list with control released. For Xbox, select the XInput entry over a duplicate generic entry. Windows uses player slots rather than physical serial numbers, so a pad appearing in a different slot can restore a different saved profile.
CAM does not block the same input from reaching FH6. Shared bindings can still move the car or activate game menus. Physical devices and driver combinations need individual testing.
File mods or the Stream Panel seem unchanged
- A file mod has no visible effect
- Fully restart FH6 after installing or restoring. Check the intended file variant; disk state is not proof of game-loaded state.
- A scan is incomplete
- Read the folder notices and scan a smaller, focused camera-mod collection.
- The Stream Panel is behind FH6
- Use borderless or windowed mode. A topmost desktop window cannot reliably cover exclusive fullscreen.
- The panel is hard to find
- Ctrl + Alt + S reveals it when the global shortcut has registered. Entering the panel keeps the camera session.
Make a report that can be reproduced
Include the app version, FH6 build, workspace and whether the problem happened in the open world or an Estate. Write the steps from a fresh connection and include the exact error message.
For an input issue, include the controller model, Windows connection mode, selected device/slot, layout and the observed raw/mapped output. For a camera jump, the desktop Live diagnostic log can record local camera, flight and input state; it is not a video recording.
Review local paths and other details before sharing a log manually. No diagnostic report is sent automatically by CAM. Use the SEPA.gg Discord for CAM support and include only the diagnostic details you intend to share.