Direct every scene.
Frame every moment.

Spectrem Director is an in-game filmmaking and scene-authoring suite for FiveM. It combines actor placement, saved characters, animations, synchronized scenes, cinematic cameras, object editing, replay tools, custom scene composition, and a multi-track Timeline in one consistent interface.

Recommended database permissions

During initial setup and version migrations, the configured database account should be allowed to run:

CREATEALTERSELECTINSERTUPDATEDELETE

Ped Studio: expand Ped, Inheritance, Face Features, Appearance, Clothes, Props or Tattoos in the left column. The adjacent rail controls camera views, rotation, temporary wardrobe visibility, Save and Cancel. Ped provides freemode presets, searchable models and a custom model field when model editing is allowed. Opening a section focuses its relevant camera view. Use clothing arrows or exact values to change variations.

Wardrobe visibility only hides clothing during inspection and never changes the saved outfit. Save and Cancel ask you to confirm before leaving. Saved peds retain the existing format for scenes and Timeline.

Spectrem Export is the optional Windows companion for direct MP4 output. Director works without it: ACTION continues to record for Rockstar Editor, while EXPORT requires the desktop application to be running on the same computer as FiveM/GTA.

The default output folder is %USERPROFILE%\Videos\Spectrem Export. If Windows rejects that location, the application uses %LOCALAPPDATA%\Spectrem Export\captures. For regular use, set the same long random token in the exporter's sharedToken and Director's Config.SpectremRecorder.Token, then restart both.

Minimum server.cfg example

set mysql_connection_string "mysql://USER:PASSWORD@127.0.0.1/DATABASE?charset=utf8mb4"
set sv_enableNetEventReassembly true

ensure oxmysql
ensure spectrem_director

Optional integration order

set sv_enableNetEventReassembly true

ensure oxmysql
ensure illenium-appearance   # Only if selected in edit.lua
ensure WC_EMOTES_V8          # Only if its bridge remains enabled
ensure spectrem_director

Expected production structure

General Director access and individual feature policies are separate. All configuration stays in the commented sections of config.lua.

Configuration example

Config.Access = {
    AdminOnly = true, -- false opens the menu, but feature policies still apply
    AcePermissions = { 'spectrem_director.use' },
}

Config.SceneAdmin = {
    Command = 'sceneadmin',
    CameraCommand = 'camera',
    Licenses = {
        -- 'license:0123456789abcdef0123456789abcdef01234567',
        -- Replace the example with your real player identifier.
    },
    AcePermission = '', -- Optional: 'spectrem_director.manage'
    AdminsHaveToolAccess = true,
    AuditLimit = 60,
    PublicAccess = { camera = true },
    Defaults = { camera = 'enabled', developer = 'admin' },
}

Grant general Director access to a trusted group in server.cfg:

add_ace group.admin spectrem_director.use allow

To authorize policy management through ACE, configure the optional AcePermission shown above and grant it explicitly:

add_ace group.superadmin spectrem_director.manage allow

Policy modes and AdminOnly

Changing AdminOnly to false opens the main menu to everyone; it does not disable feature policies or authorize everyone to manage them. Keep it true for the public-camera-only setup. The legacy Config.Access.Enabled = true also enables the general access restriction if that field is present.

A SceneAdmin manager is a player listed in Config.SceneAdmin.Licenses or granted the optional Config.SceneAdmin.AcePermission. Having spectrem_director.use alone grants general Director access, not management of policies or use of features in admin mode. AdminsHaveToolAccess = true gives managers general access automatically; if set to false, they also need general access to use restricted tools, but can still manage policies.

Set up and use Scene Admin

1. Edit the commented Scene Admin / Feature Policies section in the existing config.lua; there is no separate config_admin.lua.
2. Add full player identifiers, including license: or license2: and their 40-character hexadecimal hash, to Licenses. These are player identifiers, not the server's sv_licenseKey. Documentation examples are placeholders.
3. Optionally set AcePermission = 'spectrem_director.manage' and grant that exact ACE to the intended group. An empty string disables this alternative; license authorization continues to work.
4. Keep PublicAccess.camera = true and set the camera policy to enabled for public /camera. Setting it to admin or disabled removes public access. PublicAccess.camera = false makes enabled camera use require normal Director access.
5. Restart the running resource after editing configuration. For development, use restart spectrem_director_dev; for an installation named spectrem_director, use restart spectrem_director.
6. Run /sceneadmin, search or filter by category, change individual modes or apply one mode to the filtered results, then select Save changes. Discard changes cancels the current draft; Refresh reloads the current saved policy. Closing a draft with unsaved changes asks before discarding it. Ctrl+S saves and Esc closes the panel.

Command and CameraCommand are stored without a slash and default to sceneadmin and camera. Managers can also open Scene Admin using the shield button in Director. The panel provides English and Spanish text, counts per mode, pending-change indicators, and a history of who changed each feature, when, and its previous/new mode. AuditLimit defaults to 60 and is bounded to 10–100 entries.

Features covered

The panel has 33 feature controls:

Combat NPC actions are covered by peds; Ghost Replay uses vehicle_replay. Camera movement recording belongs to the camera workflow; capture/export has its separate policy. Public camera access does not grant the animation workspace, Timeline, Custom Scenes, or capture/export.

Persistence, live changes and recovery

Saved panel choices survive restarts in this resource's KVP storage. They are not written back into config.lua. Existing saved modes take precedence over Defaults, so changing AdminOnly or editing Defaults does not reset saved feature choices. On first use, omitted defaults become admin when general access is restricted, otherwise enabled. Use Restore configuration defaults in the panel to deliberately reapply the current defaults globally.

Saving applies policies to connected players. Revoked tools run their cleanup, and active composed previews/recordings may be stopped; saved projects remain. Existing availability limits supported by config.lua and edit.lua still apply: the panel cannot override a feature disabled there. The UI marks these configuration locks.

Concurrent edits use a revision check. If another manager saves first, your draft is retained but cannot overwrite the newer revision: refresh and reapply the changes. A failed save leaves the active policy unchanged. Invalid saved policy data locks features; an authorized manager can restore defaults from /sceneadmin.

Fixes and verification

The administration integration validates permissions in server handlers as well as client callbacks and commands. Nested camera, Timeline and Custom Scene actions check their required features. Server identity comes from identifiers/ACE, not a role submitted by the UI. The default access list uses the explicit spectrem_director.use ACE instead of the broad command fallback.

The public /camera flow opens Camera Controls directly and returns to gameplay on close, including for managers who entered through the command. F5, /director and /tutorial remain separate entry points. The camera's animation shortcut is hidden for public users. Denied or malformed scene-list responses are normalized to an empty array, fixing the Vue render error Cannot read properties of undefined (reading 'length') seen when access was rejected.

Test with both a manager and a regular player: verify public camera open/close, denied main-menu access with AdminOnly = true, each policy mode, saved settings after restart, and continued restrictions with AdminOnly = false. Automated permission, camera lifecycle, NUI and TypeScript checks passed for this implementation; a live FiveM session is still needed to verify native behavior on your server.

1. Start the server and confirm oxmysql connects first.
2. Confirm Director starts without a missing dependency, manifest, or NUI error.
3. Wait for the database-ready messages before testing saves.
4. Join with an authorized account and open Director using F5 or /director.
5. Use a configured manager account to open /sceneadmin, save a feature policy and verify that it survives a resource restart.
6. With AdminOnly = true, verify a regular player can use public /camera and return to gameplay on close, while F5, /director and /tutorial remain denied. Also verify that disabling the camera removes that access.
7. Open Cutscene Player using F6 or /cutscenes.
8. Run /tutorial, verify the spotlight and language selector, then finish the tour. Director should remain open.
9. Create, save, and reload one ped.
10. Tune a vehicle, save it under My Vehicles, and spawn it again to verify its mods and liveries.
11. Create, save, close, and reopen a small Custom Scene.
12. Create and save a small Timeline project, then preview it.
13. Preview and cancel a small Object Motion path; confirm the original prop transform is restored.
14. Draw and preview a two-point Actor Sequence route using the persistent Freecam.
15. Select a supported door, test both opening directions, then use Back to restore it.
16. Place one physical Stage Light and verify it in a short Rockstar Editor clip.
17. Test optional integrations only if they are enabled.

Healthy startup messages

[Spectrem Director] DB replay work unit: 256 KB
[Spectrem Director] Database table ready
[Spectrem Director] Custom scenes, Ghost Replays, and Ped Replays tables ready

All supported user options are kept together in the root config.lua. Keep comments and data structures intact, change only values, and preserve a copy outside the resource before updating.

Default entry points

Config.OpenKey = 'F5'
Config.Command = 'director'
Config.TutorialCommand = 'tutorial'
Config.Language = 'en'

Language startup behavior

Config.Language is the initial, global interface language. Supported codes are en (default), es, de, tr, fr, ar, vi, pl, and pt-br (Brazilian Portuguese). Director loads and caches this value once when the resource and NUI start, so opening the F5 menu does not translate the full interface again. Restart spectrem_director after changing the value.

edit.lua is the supported location for server-specific bridges and editable lifecycle hooks. Avoid changing core files when the integration can be expressed here.

Appearance provider

The default provider is native, which uses the built-in ped studio. External appearance systems are optional.

EDIT.ClothingSystem = "native"

If you select an external provider, start it before Director and verify the supplied model, appearance, save, and customization hooks with both freemode and non-freemode models.

External animation-menu bridge

The included bridge targets WC_EMOTES_V8 and is enabled in the shipped editable file. If that menu is not installed, disable the bridge:

EDIT.AnimationBridge.Enabled = false

Supporting a different emote menu means adapting the bridge functions inside edit.lua. If you are not comfortable editing them, ask us on Discord and we will help you set it up.

Weather bridge

Local cinematic overrides use GTA natives. Server-wide weather changes require the configured bridge and permission. Keep framework imports in a separate companion resource; do not add another framework's initialization file to Director's manifest.

Other optional resources

Optional content catalogs

Director discovers the following catalog files when the resource starts. Keep their filenames and paths exactly as shown:

1. Stop the server and back up the Director database tables.
2. Back up the current production resource.
3. Save your edited config.lua and edit.lua separately.
4. Extract the new release into a clean folder.
5. Compare the new config.lua with your backup and reapply custom values.
6. Keep the production folder name spectrem_director.
7. Start the server and allow automatic migrations to complete.
8. Repeat the first-start verification workflow.

Open the main interface with F5 or /director. The header provides language selection, saved-scene count, a ? Guided Tutorial button, and entry points to the major tools. New users can run /tutorial directly; Director opens automatically before the tour begins.

General behavior

• Esc or Backspace returns from the active editor or closes the current panel.
• During placement, Enter confirms and Backspace cancels.
• Text inputs protect keyboard editing, so Backspace deletes text instead of closing Object Spooner.
• Timeline preview uses Backspace to stop and return to the editor.

Director controls are context-sensitive and the active workspace always shows its own HUD. Inputs are ignored while typing unless the field explicitly supports a shortcut.

Shared authoring Freecam

Native gizmo

Run /tutorial from chat, or select the ? button in the Director header to start or restart the tour from step 1. The walkthrough contains 62 steps in nine chapters and uses a moving spotlight to identify the Director control or entry point being explained. Its 12-step Camera chapter covers capture/replacement, motion recording, timing, independent attachment/look targets, optical focus, look/zoom speed, drone banking, framing, output and saving.

New production workflows

Choose Chapters → Advanced Authoring for the replay, traffic, actor and text workflows. These explanations highlight their actual Custom Scene entry buttons; perform the described actions after the tour. The tour never launches a nested recorder, creates traffic or writes a saved scene.

• Scene placement: G ground snap in move, free-camera and aim modes; heading and actor/prop offsets stay intact. This is separate from Camera's G target lock.
• Environment and timing: save an environment snapshot, replace it explicitly after live changes, and distinguish clip start from source offset and recorded car delays.
• Vehicle Replay: driver/passenger seats, weapon-fire playback off by default, names as labels, server-confirmed saves and safe append to folders already referenced by scenes.
• Traffic Replay: generate stopped cars; use Advanced spawn codes or My Vehicles; replace/remove and ground-place cars; draw rounded routes and delays; record, save and reuse the actual motion.
• Actor Sequence: walking and weapon styles, waypoint overrides, smooth corners, exact event stops and Preview versus Scrub. Legacy routes retain their old mode until smoothing is enabled.
• Cinematic Text: bundled fonts, Fixed/Face camera, gizmo placement, occlusion and timing. Use direct EXPORT for text: Rockstar Editor cannot capture its DUI surface.

Language and direction

The selector inside the tutorial changes the explanation immediately between EN, ES, DE, TR, FR, AR, VI, PL, and PT-BR. English is the default. Arabic automatically applies right-to-left direction to both the tour and Director interface.

Buttons and keyboard navigation

Safe startup rules

The tutorial uses the same ACE authorization and integrity gate as Director. To protect unfinished work, it refuses to start during playback, recording, saving, loading, a modal or picker, entity placement, an active Camera, a specialized authoring tool, Object Spooner, an open Timeline, or the separate F6 Cutscene Player. An idle Custom Scene and the normal Director layout are snapshotted and restored automatically. Finish the blocked operation and run /tutorial again; the warning is shown in the configured language.

Scenes are ready-made synchronized arrangements with actors, animations, and optional objects. Search by name, filter by category, or star a scene for quick access in Scenes Fav.

Combine With props, With weapons and actor-count filters below search. Filters also apply to Favorites. Place with my character appears in the cast dialog only for scenes with exactly one actor: position the scene using your current appearance, then confirm to perform it with the actual player. Cancel returns without starting playback. Start on foot; Stop releases the player and restores temporary scene weapons and ammunition. Scenes with multiple actors keep their normal Place workflow, even if other actors are disabled.

Scene workflow

1. Select a scene card.
2. Review its actor and object count.
3. Enable or disable individual actors and objects.
4. Choose each actor from presets, a Saved Ped, or a custom model.
5. Assign a preset or custom weapon where applicable.
6. Choose loop behavior.
7. Select Preview to inspect the full scene around its first enabled actor.
8. Return with Esc, make any cast/object changes, then select Place, position the origin, and confirm.
9. During placement, press G to snap the whole scene origin to the surface below it. Works in move, free-camera and aim modes; it leaves aim mode to keep the snapped position. Heading and relative actor/prop offsets are preserved, and the scene's own props are ignored by the ground check. If no surface is detected, nothing moves. Fine-tune height with Q/E, then confirm with Enter. Also available when placing scene entries in Custom Scenes or Timeline.
10. Use the scene controls or parent Custom Scene/Timeline to stop playback.

My Peds stores reusable characters and manages NPCs spawned by Director.

Saved Ped actions

Spawn as NPCApply to playerMoveRenameCloneEdit OutfitDelete

Spawned NPC actions

Edit outfitAssign animationTake controlRemoveRemove lastClear all

When controlling a spawned NPC, walk, use clothing tools, and assign animations normally. Press F7 or choose Back to my ped to return. Director preserves the NPC's configured state and keeps it protected from ambient panic behavior.

The standard browser supports search, favorites, playback mode, placement type, actor models, weapons, partner actors, and prop variants.

Using Another Menu

1. Open Custom Anims.
2. Select Another Menu.
3. Choose and start the animation in the external menu.
4. Return to Director.
5. Select the ped that should receive the chosen animation.

If the bridge shows Offline, start the configured animation resource or disable the bridge in edit.lua. Stale selections and emotes that are no longer playing are ignored.

Chase

Chase builds a local cinematic pursuit whose target is always the current local player. Choose a configured vehicle or valid streamed/add-on spawn name, select the unit count allowed by the server (1–8 by default), choose Normal, Aggressive, or Ramming, then configure sirens, helicopter support, deployment distance, unit protection, and the optional on-foot response. Classic Chase remains the default until the operator explicitly enables Advanced Fleet.

Advanced Fleet (optional)

Config.PoliceChase.AdvancedFleet.Enabled makes the advanced controls available but does not replace the classic defaults. Turn on Advanced Fleet in the Chase panel only when the shot needs custom casting. Same setup for all applies one vehicle, crew and weapon template to every ground unit; Configure each unit configures every unit independently.

• Choose the default Chase vehicle, enter a valid streamed/add-on model, or select a tuned preset from My Vehicles. Saved paint, modifications, extras, lights, liveries and decals are retained.
• Chase reads the selected vehicle's exact seat capacity. Seat -1 is the mandatory driver; seats 0+ are passengers, and no invalid seat is offered.
• Assign the default Chase ped, a saved ped with its appearance, or a valid custom ped model to each seat.
• Choose the on-foot weapon used by that setup if the normal on-foot response conditions are met.

Workflow

1. Open Chase and choose the ground vehicle, units and driving style.
2. Optionally enable Advanced Fleet, sirens, helicopter support, protection and on-foot response.
3. Select Start Chase. The menu closes only after at least one valid pursuit unit starts.
4. Drive or move normally. Reopen F5 to make live changes.
5. Select End Chase when finished. A forced Director shutdown or resource stop also cleans up the pursuit.

Chase Replay

Chase Replay is a separate tab and replay library for the current active pursuit. One synchronized clock records the target vehicle, every active ground Chase unit, and the Chase helicopter when present, preserving the timing between all participants.

1. Stage and start a classic or Advanced Fleet Chase.
2. Open Chase Replay and select Record.
3. Perform the pursuit, then select Stop.
4. Name the take and select Save.
5. Use the dedicated library to Play, Stop, or Delete a take.

DefaultDeploymentDistance sets the initial distance behind the local player and is clamped by MinDeploymentDistance / MaxDeploymentDistance. Protection independently controls ground vehicles, drivers, the helicopter, and its pilot.

Density

Switch between Vanilla and Custom density, then adjust pedestrians, moving vehicles, parked vehicles, random vehicles, and scenario peds from 0–100%. Empty, Low, Medium, and Full presets apply immediately and locally.

Weather & Time

Use Server Sync when the configured bridge is available, or Local Only for cinematic overrides. Select weather, hour, minute, time speed, freeze, and blackout. Local mode also exposes rain level, wind speed, and artificial lights.

Clubs

Configure theme, atmosphere, podium, sound system, turntables, droplets, neons, bands, lasers, bar setup, resident DJ, dancers, and bartenders. Use Enter Club, Exit Club, and Reset. Club configuration is session-based in the current release.

Environment groups

During Environment placement, F5 shows or hides the live controls while keeping the free camera and preview active. Adjust NPCs, formation or animation, then press F5 to resume flying. Confirm placement when finished.

Timeline → Environments → New Environment and Custom Scene → Environment open the full Environment editor inside the project. Configure NPCs, formation and animation, place the group with the free camera, confirm, then choose Save and return. Timeline inserts the group at the playhead. Edit Environment reopens a clip or entry at its saved position while retaining its timing. Cancel discards the draft; saving clears its temporary preview NPCs. Project edits keep an independent copy and leave the standalone library unchanged.

Create reusable NPC environments in Single or Group mode. Choose generated NPCs or a Saved Peds folder, then set count, radius, spacing, extension, gender, formation, and animation.

Available formations include CircleSemi-circleLineGridScatter. Preview or regenerate before confirming placement. Active environments can change animation or be cleared.

Effects

The library's eye / Preview button opens the same orbital viewer as Scene Preview with the selected mode, scale, alpha and RGB. Adjust distance, height, orbit, angle, FOV and smoothing; Replay effect repeats bursts or restarts a loop. Fireworks use a wider, elevated frame. Back / ESC restores the catalog, search and scroll without adding a scene entry. Looping preview particles stop on close; already emitted one-shot particles fade naturally. Camera defaults use Config.ScenePreview and permissions use effects.

Search by effect name or particle asset, filter All, Fireworks, or Favorites, and choose Normal or Loop playback. Selecting an effect starts a live authoring particle: scale, alpha and RGB update in real time before placement. A fixed effect stores a world position; an attached effect follows a supported actor or replay ped through a placed local offset. Looping fireworks use a coordinated show-style behavior.

In Timeline, the effect starts when playback reaches the clip's exact start time. Use View at playhead to inspect it and Place Attachment when it must follow a subject. In Custom Scenes, edit/re-place the entry and use Test. Closing the editor stops the temporary authoring particle and restores the parent scene.

Object Spooner is a complete in-game entity editor for peds, props, and vehicles. Open it from the Director menu or with /spooner.

Spawn and selection

• Search models or browse Peds, Props, and Vehicles.
• Choose Place or Replace Selected.
• Vehicle placement can start with the engine enabled.
• Use Shift + LMB for multi-selection.

Selected Entity panel

Edit position XYZ, rotation XYZ, opacity, freeze, godmode, and health. Apply numeric changes, copy and paste transforms, or use undo and redo.

The camera can run independently or as the editor for a Camera entry opened from Custom Scenes or Timeline. Source-linked editing writes changes back to that source; standalone use does not create a clip automatically.

Adjust Drone banking

Enable Drone mode to reveal the Drone banking slider. Set the maximum tilt from 0° to 45°: 0° smoothly levels the horizon, 15° is the default, and 45° gives stronger banking. This changes tilt when turning, not flight speed or inertia. Fast mouse turns cannot request a tilt beyond the selected limit. The startup default is Config.CinematicCamera.Drone.Banking; live camera recordings store the resulting rotation.

Attach to one entity and look at another

Attachment controls position. Look target controls rotation. With three cars, attach to the middle car using LMB, turn toward the right car using Alt + RMB, then select it with RMB. To track a passing car from a fixed spot, detach and turn off Follow Player, Allow Player Movement and Auto Orbit; select only a look target.

• Click: RMB locks the aimed entity. Click it again, click empty space, or choose Release to stop tracking.
• Hold: RMB tracks the selected entity until mouse-up. Keyboard and panel selections remain locked until released.
• Free: RMB rotates manually. Alt + RMB provides manual rotation in the other modes; N toggles free look and releases tracking.
• B selects the next look target; V selects the previous one. Neither changes the attachment. Hide the panel with H to use these shortcuts.
• Target priority: Scene / Timeline first is the default. Scene / Timeline only excludes world entities. All nearby entities permits unrestricted picking. B/V uses stable entity identity order, not changing distance order.
• Picking a look target releases composition lock but retains the positional mount. Enabling composition lock again releases the independent look target.

Look speed, in the Look target section, sets live turning and tracking speed from 1–100% (default 50%). Lower values give slow pans; higher values aim quickly. It applies to RMB, B/V, panel targets and G. Very low values lag behind fast-moving subjects. Manual rotation smoothing, attachment movement and Drone banking remain unchanged. Authored keyframe playback is unaffected; Live Camera Record stores the resulting turn. Set the startup default with Config.CinematicCamera.LookSpeed.

Zoom speed, under Movement → Lens, controls live zoom from 1–200% (default 100%). Hide the panel with H, then hold Z to zoom in or C to zoom out. Lower values zoom slowly; 100% changes FOV by 25 degrees per second and 200% is twice as fast. This changes FOV, not position. Lens presets still apply directly, authored zoom playback is unchanged, and Live Camera Record captures the resulting FOV. Zoom keys do nothing while the panel is open or a sequence is playing/scrubbing. Startup default: Config.CinematicCamera.ZoomSpeed.

Choose lens focus separately

Enable Depth of field, then choose exactly one mode: Manual distance, Autofocus — screen centre, or Follow focus — look target. Follow focus prioritizes the look target, then the attachment or G/sequence target. Focus changes sharpness; it does not steer the camera. Autofocus smooths changes and briefly retains its last valid hit when the ray crosses a gap.

Scene look targets are saved per keyframe independently of the positional anchor and re-resolved if Timeline recreates their entities. A missing scene target waits; a deleted world target is released. Live Camera Record bakes gaze and focus, including B/V switches. World entity handles are not saved as portable references. Defaults and B/V bindings are configurable in Config.CinematicCamera.

Capture a keyframed sequence

1. Move and frame the camera.
2. Press L or click Capture.
3. Move to the next pose and capture again.
4. Edit keyframe time, FOV, easing, path, speed, and pacing.
5. Use Linear for direct motion or Spline for curved movement.
6. Preview with F7 and stop or rewind with F8.
7. Use Loop or Close Loop when the sequence must repeat.

Edit an exact Timeline keyframe

1. Select the Camera Sequence clip.
2. Choose Edit Camera.
3. Click the desired keyframe diamond to enter at its exact pose and time.
4. Adjust the camera.
5. Click Save frame or Replace to persist the change.

Live camera movement recording

Use Record to capture a live camera move. Replace starts a new take; Append adds another pass. Adaptive sampling and curve simplification keep the resulting path editable. Duplicate, Distribute, Level, and F9 help refine recorded keyframes.

What each Camera area does

Camera controls

Scene Preview is a lightweight inspection camera separate from Camera Director. It creates local preview actors and objects, follows the first enabled actor and preserves the scene selection dialog when you return.

1. Choose each actor model and enable only the actors/objects required.
2. Click Preview. Adjust distance, height, angle, orbit speed, smoothing and FOV in real time.
3. Play/pause the scene, then press Esc to return and correct the cast.
4. Click Place only when the preview is correct.

Replace a scene prop

1. Choose Replace beside the object.
2. Object Spooner opens in prop-selection mode; select the replacement model.
3. The Scene Object Editor plays the scene on its own timeline. Pause or scrub to freeze every actor at the most useful pose.
4. Choose Adjust prop, use the native gizmo to set its offset/rotation, and confirm.
5. Select Use replacement, or press Esc to cancel and return to object selection.

The replacement and its transform are stored with the placed scene. The source catalog definition is never changed.

Replace a scene vehicle

Adjust entire scene is available without /dev from the actor/replacement dialog and the vehicle/prop editor. It includes actors, vehicles, scene objects and actor-attached props. Select a target, pause or scrub to a useful frame, then use Adjust with gizmo or the fine-adjustment − / + buttons (0.01–0.50 m; 1°, 5° or 15°). Actors use scene axes; vehicles and props use local attachment axes. Actor yaw pivots around the visible ped.

Reset this element restores its loaded state. Apply alignment keeps corrections and replacements for this scene selection and placement; Cancel discards this editing session. Neither changes the catalog or global defaults. A fresh selection starts fresh, and the scene origin only moves the preview. Check several frames: spatial adjustment does not retarget animation, change model dimensions or add missing bones, and does not add separate animation time offsets. Segmented scenes are not supported in this editor.

Scenes with actual vehicle slots show a separate Scene Vehicles group. Choose Replace to browse the vehicle catalog or search by installed spawn code. In the Scene Vehicle Editor, pause or scrub the scene, use Adjust vehicle to align the model, then confirm Use replacement. Cancel preserves the previous choice; the reset button restores the scene default. Each slot is independent, even when original models repeat.

The visible replacement plays the original vehicle animation, including compatible doors, wheels and other animated bones, synchronized to the scene clock. Pausing, scrubbing, slow motion and loop changes preserve that synchronization; the attachment and gizmo still control placement. Choose similar dimensions and inspect actor contacts: missing bones are not created and actor animations are not resized to fit a different car. Scenes without vehicle slots do not show the vehicle section. Invalid model types are rejected. The existing segmented-scene editor restriction still applies.

Object Motion animates a prop independently from Camera Director. It can combine procedural layers with editable motion keyframes and can be saved into Object Spooner, Custom Scenes or Timeline.

Advanced: Physical levitation. Enable the switch in Object Motion, then set the zone center offset, radius, height, return strength, damping and maximum speed. Start Preview and choose Interact to move around and push the floating prop; H / ESC returns to the editor. The preview can display the cylindrical boundary. Saved entries retain all zone settings.

Physical mode enables collision and replaces scripted motion while active, preserving the stored keyframes. Forces return the object toward the center, with a boundary correction for extreme impacts. Bounds apply to the prop origin. Timeline scrubbing shows the initial hover pose; each playback simulates new interactions. Use models with dynamic physics. This follows Object Motion's local playback and does not create a shared multiplayer physics session.

Camera-style path recording

Object Motion opens with a persistent work freecam that stays active during editing and Preview. Hold right-click over the central viewport + WASD to move with the panels visible; release right-click to edit. Q/E changes height, the wheel changes speed, and Shift/Ctrl provide fast/precise movement. Move camera enables continuous navigation without hiding panels; H / ESC returns cursor control; Frame object centers the prop. Physical Interact, Object Spooner and Camera Sequence temporarily take over, then restore the work view.

Select Camera sequence. The prop uses a temporary camera-local mount while recording, but only the resulting world-space prop path is saved. Camera effects are not baked into Object Motion.

Actor Sequencer builds a portable performance through four guided steps: Route, Actor, Events and Review.

• Transit corners are rounded, with their radius limited by neighboring segments. A moving look-ahead target keeps native walking/running continuous instead of stopping and snapping heading at every point. Speed commands blend between segments; per-segment walking styles remain active.
• Points containing a pause or any event remain exact destinations with a small arrival tolerance. Events execute once on arrival. Compatible upper-body animations can continue during subsequent movement. Transit orientation follows the curve tangent; at stops, authored headings use a native turn task that a subsequent aiming/turn event can replace.
• The route preview, playback, Timeline inspection and source-offset starts share the same curve geometry. The UI duration estimator is tested against native geometry, but actual walking timing may vary with navigation, gait and obstacles.
• A blocked smooth route retries direct native navigation once, then stops at the waypoint timeout without dragging the ped through obstacles or firing unreached arrival events. Legacy behavior remains available by disabling Smooth path. Near-reversal and navigation-mode boundaries are not rounded.
• Save to Custom Scenes or Timeline to preserve the smooth mode and radius. No server.cfg change, extra resource or migration is needed.

• In Events, equip a weapon before Aim or Shoot. Select a scene actor/vehicle or capture a world point: move Freecam with RMB + WASD, point the center crosshair at a surface, release RMB, then press Use camera crosshair. Fine-tune X/Y/Z if needed.
• Weapon poses depend on the model and weapon; one-handed styles mainly suit pistols. Shoot uses real bullets in playback. Time inspection only shows the aiming pose.
• Animation events search compatible Custom Animations and normal animation favorites (up to 60 results). Paired/prop emotes are excluded. Manual dictionary/clip entry is still available. Choose Once, Loop, or Upper body + loop; disable Wait until event finishes to combine a compatible torso animation with movement.
• Styles and per-point/event overrides save with Custom Scenes and Timeline. Changes appear on the next preview, and reopening route placement preserves them. No rpemotes dependency is required.
• Only used walking clipsets are preloaded. Stop/reset restores changed channels to GTA defaults; unknown styles from another resource must be reapplied by that resource. Legacy sequences without style overrides remain unchanged.

1. Start drawing the route and click the starting point, then every destination in order.
2. Choose Walk or Run for the segment leading to each new destination.
3. Cast the current player, a stable actor reference or a Saved Ped offered by the parent editor.
4. Add optional waypoint events such as wait, turn, aim, shoot, scenario, animation, weapon changes or vehicle actions.
5. Scrub or preview the full performance. The persistent RMB + WASD Freecam remains available for inspection.
6. Save the sequence into its Custom Scene or Timeline parent.

Route capture controls

Door Director animates supported entity-backed map/MLO doors and doors registered in GTA's Door System.

1. Select or change a door. Object Spooner's read-only world selection Freecam opens.
2. Hold RMB with WASD, Q/E, Shift and Ctrl to frame it; release RMB and click the physical door once.
3. Choose Open, Close or Open & Close.
4. Choose Side 1 or Side 2 for the signed swing direction.
5. Select Soft, Normal or Fast, or enter the exact movement time.
6. Drag the Door Timeline playhead and markers to inspect or author exact open-ratio keyframes. Optional lock/unlock events use their own lane.
7. Preview, then add to the parent scene/Timeline.

The persistent editor Freecam remains available after selection. Back/Esc restores the original world state. Baked MLO geometry cannot be animated unless the addon exposes a selectable object or Door System registration; add unexposed addon door archetypes to Config.DoorDirector.RegisteredDoorModels.

Scene Tools organizes the current Custom Scene without modifying source assets.

• Create named collections and move entries between them.
• Select, show/hide and lock entries from one hierarchy.
• Attach an entity-backed child to an entity-backed parent using a bone and local offset/rotation.
• Open the clean viewport to inspect the result; Esc returns without discarding the draft.

Custom Scenes combines multiple Director systems into a named, reusable production. Saved scenes support lazy loading, rename, edit, and confirmed deletion.

Supported entries

CameraStage LightCinematic TextObject MotionActor SequenceDoor MotionAnimationSceneVehicle ReplayPed ReplayEffectCombat Ped

Build a scene

1. Create a new scene and give it a descriptive name.
2. Add entries in the order that is easiest to manage.
3. Set each entry's start delay: preset or custom.
4. Configure models, positions, replay takes, effects, props, and attachments.
5. Prop placement: Custom Scenes and Timeline share Props > Place & Add, with Place for existing attachments. Scene and solo-animation actors play in an isolated preview with an animation timeline. Play, pause or drag the time slider to choose a pose, then click Adjust prop. This freezes the animation and detaches the prop before opening the gizmo. Enter accepts the adjustment and returns to the timeline; Backspace cancels just that adjustment. Use placement returns to Props, then Save commits. Vehicle props retain the vehicle root or named bone and use the same gizmo, without ped-animation transport.
6. Edit the camera sequence from its entry.
7. Use Test to preview without starting the final action workflow.
8. Correct placement and timing, then save.
9. Use ACTION! for the configured countdown and full execution.

Playback choices

• Test / Stop Test: local editing preview.
• ACTION!: countdown followed by the complete scene.
• Attach: prepare static elements and attach the player to a selected entity before action.
• Nearby synchronization: share the scene with eligible nearby players.
• Stop & Save: stop the active production and retain authoring changes.

Stage Lighting

Add a Stage Light entry from Custom Scenes or Timeline. Every light now uses a physical streamed fixture with an embedded GTA spotlight, allowing the same light visible during authoring to persist in a Rockstar Editor recording. There is no separate native-only output.

• The authoring Freecam remains active while Stage Lighting is open. Hold RMB and use WASD, Q/E, Shift, and Ctrl to inspect the scene; release RMB to use the interface.
• Choose one of 15 verified physical fixtures: three white levels plus soft or bright red, magenta, green, yellow, blue, and cyan. Each choice applies the asset's exact embedded RGB value.
• Use Place near me or Aim at me for a quick start. For exact placement, click Edit fixture with gizmo, translate or rotate the light, then finish placement to resume its animation.
• Use Move camera for mouse navigation and Esc/RMB to return to controls, or Frame light to center the fixture. The Freecam stays active throughout editing.
• Attachment: choose a project subject or nearby ped, vehicle or prop, optionally enter a bone, then Attach. Keep position preserves the placement; the gizmo adjusts local offsets and rotation. Detach preserves the world placement. Project targets reconnect on playback; nearby world targets are temporary for the current entity/session.
• Aim can keep the beam pointed at a separate actor or vehicle. Missing attachment targets hide the light until they become available.
• Add movement, rotational sweeps, and sway. Pulse and flicker use recordable binary fixture visibility because the embedded brightness is fixed.
• Use Preview for live authoring. The original scene is unaffected when the editor closes.

Guided setup order

1. Light: name it, set duration and decide whether procedural motion loops.
2. Place: place near the player, use exact transform faders or open the native gizmo. Gizmo keys are W move, R rotate and Tab local/world.
3. Look: choose a verified color and, when needed, choose an actor/vehicle subject with Follow and/or Aim offsets.
4. Motion: start from Static, Float, Sweep, Pulse or Flicker; Advanced exposes each layer separately.
5. Preview: verify the correct scene time, daylight and beam direction. Finish the gizmo session before saving.
6. Save: add it to the parent. Esc/Backspace returns and restores temporary preview state.

Stage lights share the Custom Scene playback clock, including delays, pause/stop behavior, static scrubbing, nearby-scene playback, and loop or once duration. Models are preloaded before that clock starts, one managed fixture entity is used per active light, and the entity is removed when playback, preview, or the resource stops. The included fixtures are enabled for all 24 in-game hours.

The 15 included fixtures have photometrics compiled into each model: intensity 4, 20 m falloff, 5 degree inner cone, and 15 degree outer cone. Position, rotation, targeting, timing, movement, sweep, and on/off patterns are editable.

Cinematic Text

Text attachment: in Content, refresh the target list, choose a ped, vehicle or object and click Attach / apply anchor. Scene and Timeline subjects are listed first. Preview the target clip before opening this tool. Optionally enter a bone name (head, hand, door, wheel…) or a GTA ped bone ID. Empty means the entity origin.

Text starts above its anchor unless Keep current world position is selected. The gizmo adjusts a saved local offset. Face camera follows the target while facing the camera; Fixed optionally inherits its rotation. Finish the gizmo before changing the link. Detach preserves the current position. The saved link reconnects to registered scene/replay actors, vehicles, Object Motion, scene props and playback Environment NPCs. If the target or bone is absent, the text hides until it returns; keep the target clip active during the text.

Cinematic Text is a new guided world-space title system inspired by the strongest authoring ideas from Core Cinematics and Maker Pro, but integrated into Director's existing Custom Scene and Timeline clocks. Open it from Director, add it as a Custom Scene entry, or create/edit its Timeline clip.

The font picker previews 40 offline options: 5 base families and 35 bundled local families. It covers condensed title, elegant serif, modern sans, techno/display, handwritten, and monospaced styles without requiring an Internet connection. Latin and Latin Extended are available across the library, and many families also include Vietnamese glyphs. Arabic, emoji, and glyphs missing from the selected family use compatible system fallbacks, so coverage can vary between families and client installations.

1. Content: name the entry, write Unicode or multiline text, and start from Title, Subtitle, Neon, Warning, or a custom style.
2. Appearance: choose a bundled/system font, color, opacity, alignment, outline, glow, shadow, and world scale.
3. Movement & timing: enter the exact duration; select None, Fade + slide, Scale, Rise, Typewriter, or Wave and set independent entrance/exit times.
4. Orientation: use Face camera to face the current camera without interpreting the saved world heading as screen rotation, or Fixed to retain the authored world rotation. Switching to Fixed initially faces the camera, including elevation. Both modes preserve the same world dimensions and texture proportions. A fixed plane is readable from either side, but remains edge-on from its side and can be occluded by world geometry. Finish the gizmo before switching modes; changing facing preserves the preview time and texture.
5. Place: enable the gizmo to translate or rotate the invisible anchor. Hold RMB plus WASD/Q/E for the persistent Freecam, Shift for fast movement, or Ctrl for precision; release RMB to use the controls.
6. Preview and save: stop/restart the temporary preview without losing Freecam, then add or update it in the parent production.

Saved definitions live in the normal Custom Scene or Timeline JSON payload, so no SQL migration is required. Runtime instances are lazy and cleaned up on preview stop, parent playback stop, editor close, or resource shutdown.

While editing, keyboard and mouse retain UI focus even with a gamepad connected. Gameplay controls are blocked only in the editor; Freecam, placement and playback release that editing guard.

FREECAM in the top bar, or Move camera beside the inspector, inspects the scene without creating camera keyframes. Use WASD / Q / E to move, move the mouse freely to look, and use Shift / Alt for fast / slow movement. F5 or ESC returns to Timeline and holds the framing, including while editing effects. Use shot camera resumes authored camera scrubbing. Takes without camera clips keep this view; authored cameras take priority during output. Closing Timeline releases Freecam.

• Effects: click once or press + to insert and inspect an effect at the playhead. Search covers the complete loaded catalog. Move effect and Move camera sit beside its settings; placed, unattached effects expose live X/Y/Z coordinates.
• Animation placement: choose Ground or Fly above Place in the animation inspector. Ground follows the floor; Fly preserves the placed height. The choice is saved per clip and reused in placement, scrub, Test and output. Existing clips default to Ground.
• Layer order: new dedicated layers appear at the top. Duplicates appear directly below their original layer. Dropping onto a row inserts below that row. Shared controls reuse their existing track.
• Expandable groups: Vehicle Replay, Ped Replay, animations, effects and other types have parent rows. Click the arrow to collapse or expand their child tracks. The parent retains an occupancy overview; collapsing never disables playback. The project remembers the view. Use the group button beside TRACKS for a flat view, or workspace settings to collapse/expand all groups. New clips expand their group automatically.
• Layer ON/OFF: the eye button on each row uses the saved Mute state to exclude that layer from preview and output. It supports undo and is disabled during playback/capture.
• Reorder type groups: drag a parent header such as Speech or Animation above or below another type. The insertion line marks the destination; the entire group moves with its tracks and subgroups. Clip times stay unchanged. The order is saved and supports undo/redo; a normal click still expands or collapses.
• Named subgroups: click + beside Animation or another type to create Group 1, Group 2, etc. Rename in the group header. Drag a track label or clip onto the subgroup to assign it without changing its time, even if the group is empty or collapsed. Drop on the type header to ungroup. Compatible library items can be dropped directly into a subgroup; gear > Subgroup is also available. Collapse each independently. Removing a group keeps its tracks. Project saving and undo/redo retain the organization; duplicates inherit their source group. The old Collections block has been removed from the clip inspector.
• Select in view: activate the button and click an active Timeline actor, vehicle or owned prop. Unattached effects can be selected within 24 screen pixels of their emitter origin; select attached effects from their track. Map objects and inactive clips are excluded.

TEST, Play from, ACTION! and EXPORT hide the local player's ped during Timeline takes, including the recording countdown. Stop, cancellation, failed preparation and resource shutdown restore the previous visibility.

Timeline is a multi-track nonlinear editor. Projects can be created, saved, searched, loaded, renamed, duplicated, and deleted. Unsaved work remains a local draft until saved to the database.

Add and organize clips

• Drag an option onto Timeline or double-click it to add at the playhead.
• Tracks are created only when needed.
• Scene, Animation, Stage Light, Cinematic Text, Effect, Vehicle Replay, and Ped Replay clips receive independent tracks for clearer organization.
• Camera, Speech, and World & Time content share type-specific tracks.
• Drag track headers or use their arrows to reorder them.
• Mute tracks to exclude playback and lock them to prevent edits.
• Resize Timeline vertically using the top handle or the plus/minus controls.

Edit clips

Move, trim from either edge, split, copy, paste, duplicate, delete, or select multiple clips. Use Ctrl for individual multi-selection and Shift for a range. Right-click opens context actions.

Snapping and markers

Use the magnet button to toggle snapping. Grid choices include 0.05, 0.1, 0.25, 0.5, and 1 second. Hold Alt while dragging to bypass snapping. Press M to add a marker, drag it to move, and right-click it to remove.

Complete Scene and Animation blocks keep their natural duration and cannot be stretched. This prevents invalid partial playback. Source-aware camera/replay/authoring clips expose trimming or loop behavior only when their runtime supports it.

Playback modes

• TEST: preview from the beginning.
• Play from: preview from the current playhead.
• ACTION!: run the complete edit with a countdown.
• Attach: prepare attachment-based staging.
• Stop & Save: stop and preserve the current authoring state.

Timeline shortcuts

Ghost Replay

Records the controlled subject's movement for repeatable blocking. Press E to stop, name the take, save it, and add it to a larger production. Use shorter test takes while calibrating routes.

Ped Replay

Adaptive playback: the recorded route guides native movement while weapon changes, shots, rolls, cover, jumps and reloads can finish. Small differences are accepted and the route is recalculated after actions. Unavailable cover falls back to locomotion; only large, sustained drift outside protected actions triggers recovery. Live takes can vary with the environment, while scrubbing still inspects the recorded pose. Record a new take for combat-roll phases and confirmed shots; older takes cannot supply missing action data. Settings are in Config.PedReplay; PlaybackMode = "legacy" restores the previous controller.

Records only the active player, including appearance, movement, actions, combat state, and vehicles used by that player. Nearby NPCs are not scanned or captured. Press E to finish, then name and save. Before placement, configure the actor model and appearance; prop attachments and drift correction are supported.

Vehicle Replay / Vehicle Sessions

Keep recording in a used folder: saving another take is allowed even when a saved Custom Scene or Timeline references that folder. Save uploads only the new take; the server appends it to its committed data without replacing or reordering previous takes. You do not need to empty the scene or restart the game. Deleting or fully replacing referenced recordings remains protected.

If another save changed the folder during upload, the new take remains pending while the folder refreshes. Press Save again after the refresh message. Failed uploads do not replace saved takes. Do not close the game/resource while a take is unsaved. Deploy matching client, server and compiled UI files together; old servers are rejected before append data is uploaded. No SQL migration or server.cfg change is needed.

Large folder uploads: a disconnect naming spectrem:server:updateVehicleSessionChunk concerns network transfer, not a fixed 14-vehicle limit. Updates use 8 KiB latent chunks, with at most four in flight and a combined 256 KiB/s budget. The server acknowledges consecutive blocks before the database commit; progress keeps long uploads alive. Incomplete or stalled uploads are cancelled without committing partial recordings. The existing 32 MiB encoded-folder limit depends on recording duration and detail, not only vehicle count. No server.cfg changes or SQL reinstall are required. Update matching client and server resource files and restart when nobody is recording; older servers are rejected before bulk upload.

After stopping with E, name the take, click Save, and wait for confirmation before recording the next take in the same folder. Names are display labels; previous takes load by session ID. A new folder has no ghosts until its first take is saved. The next capture waits for all previous ghost vehicles to spawn. If startup fails, saved takes remain intact; the menu reports the failure and F8 logs beginning with [Spectrem][VehiclePreview] identify the loading or model error. No SQL migration is required.

Enter a vehicle first. Open or create a session, record one or more takes after the countdown, and press E to stop. Finalization briefly freezes the vehicle, removes invalid trailing samples, and restores the player and vehicle to the origin.

After recording, save, discard, record another take, test, delete, or select one or multiple takes for Custom Scenes or Timeline. Full paint, mods, extras, lights and liveries are captured with the take. Per-vehicle settings include driver appearance, siren, collision, motion, drift correction, engine, invincibility, visible damage, freeze behavior, and prop or ped attachments.

Select a Vehicle Replay clip in Timeline, or open its settings in Custom Scenes, to replace each recorded model with a preset from My Vehicles. The replacement is stored with the production, so editing the library later does not alter the scene.

Replay recorded weapon fire is off by default. Enable it in Vehicle Replay settings only when the take needs gunfire or a water cannon. Real weapon events are still captured; disabling playback does not erase them. Existing saved scenes and timeline clips keep their explicit setting: switch it off there too if it was saved enabled. Unarmed cars no longer treat the shared attack/gesture control as mounted-weapon fire or receive native firing tasks from replay. The global default is Config.GhostReplay.ReplayVehicleWeapons = false.

Driver-operated mounted-weapon fire is captured as compact timed events. When enabled, native playback supports GTA weaponized vehicles. Ballistic mode replays a captured weapon hash when the native firing command does not respond; resource-defined turrets, muzzle animations, or weapons that never expose a native hash require a custom bridge.

Traffic Replay: traffic for races and pursuits

1. Open/create a Vehicle Replay folder and choose Traffic Replay.
2. Add here places a zone at your player position. Use View scene / move and Open controls to move around and add more zones. The crosshair button moves a center to you; the trash button removes that zone.
3. Set radius (30–180 m), vehicle count, target speed (10–120 km/h) and behavior. Normal respects lights; Flow ignores lights while still using road routing and avoidance.
4. Generate / refresh places local cars and drivers stopped, with the handbrake on and no driving task. Placement checks road direction, lane count, median gap and obstacles. Check the actual count: occupied/unavailable points can reduce it. Regenerate after editing zone settings.
5. Use Vehicles in the scene to review the fleet. Click a car's name to mark it in the world, then use View scene / move to inspect it. Select a model from the pool, a customized car from My Vehicles, or an installed car model name, then Apply. Only that car is replaced; an invalid, oversized or blocked replacement keeps the original. The trash button removes only that generated car. Editing is locked while a replacement loads. Generate / refresh resets the fleet and these choices.
6. Optional: select Advanced · manual placement. Add cars by spawn code or from My Vehicles, without generating a zone. Typing k lists installed car codes starting with k; click a suggestion or press Enter for the first result. Full addon codes are also accepted. Suggestions use the cached catalog, with no request per keystroke. Saved cars retain their customization; presets are not modified.
7. Add vehicle places a stopped car 8 m in front of you; keep that spot clear. Position on ground opens a translucent vehicle preview using scene-placement controls, without gizmo axes. WASD moves the car, the mouse wheel rotates it, Shift/Ctrl select fast/precise movement, and Space switches to/from free camera (WASD + Q/E, mouse look). X toggles placement at the camera's aim point. Wheel contact keeps the car grounded and aligned to slopes; Q/E cannot lift the car in move mode. Enter confirms a clear, grounded position; an invalid position keeps the preview open. Backspace cancels and restores that car. Opacity, collision and camera/player controls are restored on exit; other cars remain stopped. Adjust speed and behavior independently per car.
8. The placement camera starts behind the car, like scene placement. Movement follows the view: D/A move car and camera right/left together, regardless of the car's heading. Wheel rotation stays in place. If the ground rejects a step, neither the car nor its following camera advances.
9. Align to traffic explicitly snaps one car to a clear nearby lane and its native heading. Failed alignment preserves its previous position. Automatic placement preserves the game's node direction, including one-way roads with reversed edge ordering, and rejects unrelated crossing/parallel-road geometry. Ground placement keeps the wheels supported but does not choose a lane or direction automatically: off-road or wrong-way cars may turn to join the road. Switching modes keeps the fleet; Generate / refresh replaces it. Generated and manual cars share the same total limit.
10. On any staged car, expand Vehicle trajectory and choose Draw route. The first point is anchored to the car. Use WASD + mouse for Freecam, Q/E up/down and Shift/Ctrl fast/precise. Left click adds road-surface points ahead of the vehicle. Backspace undoes a point (not the start), Enter saves, and Esc cancels without changing the previous route.
11. The blue line previews rounded corners. Corner smoothing (2–20 m; default 8) rounds more of each corner, limited by neighboring segments. Keep the line and car body inside the road. Speed reduces ahead of bends; the car stops at the endpoint. Start delay (0–30 s, shorter than the recording) coordinates individual departures on the shared clock. Match delays for parallel cars or stagger them for spaced arrivals.
12. Edit route reopens the points; Use automatic traffic removes the route. Replacing a car keeps its route. Confirming ground placement or successfully aligning the car clears it; cancellation or failure preserves it. Regenerating/closing clears the fleet and routes. Save the recorded take to retain the actual motion. Limits: 2–64 points including start, at least 3 m apart, within 600 m of the start and up to 1,500 m total. Avoid walls, steep height changes, reverse starts and extremely sharp turns.
13. Choose a duration and Record traffic. The initial stopped frame is captured before cars are released according to their delays. Cars without an authored route keep automatic road AI. Press E to stop early. Only this tool's generated/manually added vehicles are captured, on a shared clock. Record your race or chase separately.
14. Live traffic is removed on completion. Name and Save the take, then Configure & Place it in Custom Scenes or Timeline. NPC drivers are supplied by default and can be changed per seat.

Defaults: 4 zones, 16 vehicles total, 120 seconds, 24,000 samples total. Sampling adapts to the budget. Centers must be within 450 m of the player. Unattended staged fleets expire after 180 seconds. Cancel clears only this tool's vehicles; no world traffic or saved recordings are deleted. Zone presets are remembered on the local browser/client; saved takes retain the cars' captured appearance using the existing Vehicle Session database and acknowledged upload path.

Zones are spawn areas, not barriers. Cars without authored routes follow GTA's road network and may leave the radius. They are not repeatedly assigned random destinations across medians. Shortcuts, oncoming-lane avoidance and off-road avoidance are disabled. Authored routes use physical driving with moving look-ahead targets and anticipatory braking, not per-frame position/rotation writes. Neither mode guarantees collision-free driving: GTA AI can deviate or get stuck on narrow roads, custom maps or in congestion. Sustained route deviation over 12 m ends capture and retains the available take for review. Missing entities also stop capture early. Traffic never respawns or teleports during recording. Route drawing pauses preview expiry. Roadless areas and interiors may not support automatic placement. Traffic is local, not a synchronized multiplayer population; playback follows captured frames, including start delays, instead of making new AI decisions. Configure models, driver, availability, limits and estimated lane spacing (LaneWidth, default 3.25 m) in Config.TrafficReplay. No server.cfg changes, SQL migration or extra resource are required. Finish this capture before another Vehicle/Ped/Chase recording.

Chase Replay

Start a Chase first, then use its separate Chase Replay tab to record the target, all active ground units, and the helicopter on one synchronized clock. Stop and name the recording, save it, then use the dedicated library to play, stop, or delete the complete pursuit take. NPC exit and combat remain locked during capture and playback. Although the library is separate, storage uses the existing Vehicle Replay persistence and chunk transport; no SQL reinstall or migration is required.

Open with F6 or /cutscenes. Browse Rockstar cutscenes, search, use favorites, and configure playback before starting.

• Override cutscene actors with selected or Saved Ped models.
• Detect eligible nearby NPCs or entities where supported.
• Choose HUD, audio, fade, and spectator behavior.
• Use /spectator for the related spectator utility.
• Stop cleanly before launching another cutscene.

Mechanic

Run /mechanic while driving a vehicle. The panel discovers the slots actually supported by that GTA or addon model and exposes performance upgrades, all available body/interior mods, wheels, indexed and RGB paint, liveries, extras, tyre options, xenon, neons, plates and model-specific values with live preview.

Paint swatches stay fixed under the pointer, including the last metallic gold row. Hover to read the colour name and click to apply it to the chosen surface. You can also use Tab and Enter/Space; the focused swatch has an inset outline.

My Vehicles

1. Enter and customize the vehicle you want to preserve.
2. Open Director and select My Vehicles.
3. Name the preset and press Save.
4. Use the library to spawn, enter, apply, refresh, rename or delete it, or select it as a Vehicle Replay replacement.

Addon models are supported when their streaming resource is running. A preset keeps the model hash/name and the full supported customization schema.

PropPlace

Run /propplace <model> to attach a temporary prop to the current player. Choose a ped bone and step size, adjust exact XYZ offsets/rotation, then copy the generated Lua configuration. Reset zeroes the transform; closing deletes the temporary prop and restores the player.

Advanced staff diagnostics

These commands are for authorized development and troubleshooting, not the normal creator workflow. Run them on a development server and read their output in the F8 console.

Director automatically creates and migrates its storage. Permanent user-data tables include:

Temporary staging/support tables may also appear while safely updating large scene and vehicle-session data. Do not delete, truncate, or manually edit Director tables while the resource is running.

Operational guidance

• Back up the database before every resource update.
• Keep the database on fast local or low-latency storage.
• Monitor slow queries and storage growth.
• Do not raise replay or payload limits without profiling memory, network, and database I/O.
• Wait for active saves to finish before restarting the resource.

When requesting help, include the Director version, FiveM artifact, oxmysql version, database type/version, the first relevant server-console error, the first relevant F8 error, exact reproduction steps, and whether the issue persists with optional bridges disabled.