Directre — Camera Director Tool for Star Citizen

• Windows, with PowerShell 5.1 or newer available on the system — used internally by the app for its startup self-check, you never interact with it directly.
• Star Citizen, with its standard Advanced Camera Controls keybinds available (the default F4-held bindings — Directre drives the game through these, it does not inject a virtual joystick).
• opentrack, only if you want head-tracking cards or presets to actually move your in-game view.
• No other active head-tracking source (Tobii, TrackIR, etc.) running at the same time as Directre's synthetic tracker, unless you intend for Directre to take over that session.

What's included in the download: CameraDirector.exe (the app — this is what you run), Launch Directre.cmd (the recommended way to start it: runs a quick startup self-check, then opens the app), CameraDirector.ps1 (the app's source, kept alongside for transparency and used by the self-check — not meant to be run directly), Diagnostics.ps1, Reset Settings.cmd, an example flow, bundled visual theme assets, and the package license notice. The changelog is published separately next to the download.

Directre ships as a compiled Windows app (CameraDirector.exe). Getting it running takes less than a minute, with no installer, no admin rights, and no separate runtime to set up.

1. Extract the release ZIP into its own folder — any location, nothing needs installing or registering.
2. Double-click Launch Directre.exe.
3. On the very first launch, the Setup Wizard appears.

First-run Setup Wizard

A 3-step wizard, also reachable later from the toolbar's SETTINGS button, pre-filled with your current settings so you can revisit it any time.

• Step 1 — Output: informational only. Directre always drives Star Citizen through its standard keyboard/mouse Advanced Camera keybinds.
• Step 2 — Layout: keyboard layout (QWERTZ for Central-European keyboards, QWERTY otherwise — this sets the default Orbit key: QWERTZ uses Y, QWERTY uses Z), target process (default StarCitizen), and whether to only output when the target game is in the foreground (recommended on).
• Step 3 — Safety: Stop on physical mouse movement (on by default), Stop on mouse buttons or wheel (on by default), Stop on any keyboard input (off by default). Escape always cancels playback, and Ctrl + Shift + F12 is always the emergency stop, regardless of these checkboxes.

Start delay, the gap between actions, and screenshot timing are not set here — they live on the START card inside a flow. On finishing the wizard, or after changing layout/output, you're asked whether to reset your key mappings to the matching default preset — say yes unless you've hand-tuned CONTROLS and want to keep those changes.

Directre does not use a virtual joystick for camera motion. It sends the same keyboard and mouse inputs Star Citizen already expects for Advanced Camera Controls. These are the defaults for a fresh install — every mapping is fully editable afterward in CONTROLS (output type, positive/negative keys, modifier, sensitivity, pulse rate, and an Invert checkbox, one row per camera function).

Key	Function
F4 + Arrow keys	Dolly forward / back / right / left
F4 + Page Up / Page Down	Crane up / down
F4 + Mouse wheel	Zoom
Hold Y (QWERTZ) or Z (QWERTY) + move mouse	Orbit
F4 + Numpad −	Increase focal length / FOV
F4 + Numpad +	Decrease focal length / FOV
F4 + Home	Increase depth of field
F4 + End	Decrease depth of field

If your Star Citizen profile uses custom bindings, open CONTROLS in Directre and adjust the mappings there.

A flow is a chain of cards starting from START. Movement cards — Dolly, Crane, Zoom, Focal Length, Depth of Field, Orbit, and Head Track — each run sequentially or in parallel, with a custom Manual Vector Curve Editor available for hand-shaped easing on any of them. A Live Control Panel also lets you press-and-hold jog every camera function directly, independent of whatever flow you're building.

Orbit Calibration measures your camera's real degrees-per-second from a timed lap, since Star Citizen doesn't expose that distance/angle itself — once calibrated, an Orbit card can target an exact angle instead of a rough duration. The Matrix Wizard builds on that calibration to generate a full photogrammetry-style multi-angle screenshot grid automatically, previewed live on an interactive 3D sphere before you commit.

One-click Presets cover common shots: Vertigo / Dolly Zoom, Push In Reveal, Pull Back Reveal, Orbit Hero Shot, Parallax Slide, Crane Up, Drop Down, Dutch Tilt, Scanner Sweep, Focus Rack, Breathing Shot, Fly-By, and Impact Zoom.

opentrack is only needed if you want Directre to drive synthetic head tracking.

1. Install opentrack.
2. Start opentrack as administrator — this was more stable in testing with Star Citizen.
3. Set Input to UDP over network.
4. Open the input settings with the hammer icon.
5. Set the UDP port to 5555.
6. Keep the axis order as: yaw output → yaw input, pitch output → pitch input, roll output → roll input.
7. Leave additional axis offsets at 0.
8. Set Output to freetrack 2.0 Enhanced.
9. Open the output settings with the hammer icon.
10. Use one of these interface modes: Use TrackIR, disable freetrack, Use freetrack, disable TrackIR, or both protocols if your opentrack build offers it.
11. If Star Citizen appears confused, enable only the protocol you selected as the source in game.
12. Click Start in opentrack.

When Directre sends head-tracking data, opentrack should show values in both raw tracker data and game data.

Directre — Head Track panel

1. Open HEAD TRACK in Directre.
2. Enable Send synthetic head tracking during playback.
3. Host: 127.0.0.1
4. Port: 5555
5. UDP format: opentrack Generic UDP (default, 6× double XYZ/yaw/pitch/roll) or FreePIE UDP (3× float, yaw/pitch/roll only)
6. Maximum generated pose: Yaw 360, Pitch 90, Roll 360
7. Save.

Use SEND ROLL TEST or SEND 5S ROLL in Directre to confirm the pipeline before trusting it in a real flow. On startup, Directre also asks whether synthetic tracking should be enabled for this session — choose Yes to continuously send tracking data to opentrack, or No to leave synthetic tracking off so a real tracker is not disturbed.

Star Citizen — in-game settings

1. Start Star Citizen.
2. Open the options menu.
3. Open Comms, FOIP, VR & Head Tracking.
4. Enable head tracking.
5. Select TrackIR if opentrack outputs through TrackIR.
6. Disable Tobii if Tobii is not the intended source.
7. Make sure the in-game head-tracking toggle is active.

If opentrack shows values but Star Citizen does not react, the issue is usually the selected in-game tracking source, a disabled in-game toggle, or mismatched administrator rights between Star Citizen and opentrack.

1. Start opentrack as administrator.
2. Select UDP over network input and freetrack 2.0 Enhanced output.
3. Click Start in opentrack.
4. Start Directre.
5. Enable synthetic tracking for the session.
6. Confirm the left tracker panel shows TRACKING ON.
7. Set Roll to about 20.
8. opentrack should show roll values.
9. Press ZERO.
10. opentrack should return to zero.

If this works, HeadTrack cards and head-tracking presets are ready to test.

• Settings, key mappings, and orbit calibrations live in %APPDATA%\TaaviSpectre\CameraDirector\ (settings.json, orbit_calibrations.json).
• Logs are written to %APPDATA%\TaaviSpectre\CameraDirector\logs\, one file per day — check here first when troubleshooting; screenshot attempts, head-track sends, playback start/stop, and any errors are all recorded.
• Your saved camera flows (.tscd files) live wherever you choose with SAVE/OPEN — they are not tied to the settings folder above.

If the app gets into a confusing state, Reset Settings.cmd deletes all saved settings, key mappings, orbit calibrations, and logs with no further confirmation, letting you redo the Setup Wizard from scratch. Your saved .tscd project files elsewhere are untouched.

opentrack shows no values

• Confirm opentrack is started.
• Confirm input is UDP over network.
• Confirm the UDP port is 5555.
• Enable TRACKING ON in Directre.
• Press RESYNC in Directre.
• Start opentrack as administrator.
• Make sure no other app is using the same UDP port.

The first action works, but the next one doesn't

• Press RESYNC in Directre.
• Stop and restart opentrack's tracking.
• Toggle TRACKING OFF then back ON.
• Keep synthetic tracking enabled during a flow so Directre sends a continuous stream rather than one-off packets.

opentrack shows values, but Star Citizen does not react

• Enable head tracking in Star Citizen.
• Select TrackIR if opentrack outputs TrackIR.
• Disable Tobii if it is not used.
• Try the other TrackIR/FreeTrack protocol in opentrack.
• Run Star Citizen and opentrack with matching privileges.

Dolly, Crane, FOV, or DOF do not react

• Check the Star Citizen keybinds.
• Open CONTROLS in Directre and compare mappings to your game profile.
• Make sure Star Citizen is in the foreground during playback.
• Increase the start delay in the START card.

Playback stops immediately

• Physical mouse movement can stop playback if that safety option is enabled.
• For testing, temporarily disable Stop on physical mouse movement.
• Confirm the target game is in the foreground.