The complete INI reference.

When enabled, RE+ performs the capture instead of Rockstar's stock encoder. Other exporters such as EVE do not run at the same time because RE+ has already diverted the export operation.

Sliding plays the clip in controlled slow motion and preserves temporal history. Walking pauses and seeks to exact sample times. DepthOfField uses Walking timing while the capture add-on accumulates every output frame across a physical aperture.

A 24 fps render creates 24 finished frames for every second of timeline. It does not require the game itself to be running at 24 fps during capture.

More samples make accumulated motion blur smoother. They do not increase the amount of blur; RenderShutter controls that. Samples are the dominant render-time cost.

1.0 represents a 360-degree shutter. 0.5 represents 180 degrees. At 24 fps, 0.5 equals a 1/48-second exposure; 0.65 is approximately 1/37 second and therefore carries more blur.

This gives the game time to present a stable frame after a timeline jump. It is paid once per output frame and matters most when the sample count is low.

Each extra redraw is multiplied by RenderSamples, so raising it is expensive. Zero would capture the same image repeatedly instead of distinct times.

The accumulator works in linear light. This lift helps headlights, sun glints and reflections remain visibly bright along a motion trail instead of fading toward grey.

A larger aperture produces shallower focus and larger bokeh. The Export menu uses a narrower 0.005 to 5.0 adjustment range, while the source clamps manually entered INI values between 0.001 and 10.

The value represents rings across the aperture; total sampling and render time rise with it. The in-game Export menu exposes 1 to 60, while the INI loader accepts and clamps 1 to 100.

When enabled, RE+ casts a ray through the configured focus point and sends the measured depth to the capture add-on. It follows depth, not a named subject, so anything on the same focus plane is also sharp.

Zero is the left edge, one is the right edge and 0.5 is the centre of the frame. It only applies while RenderDofAutofocus is enabled.

Zero is the top edge, one is the bottom edge and 0.5 is the centre of the frame. It only applies while RenderDofAutofocus is enabled.

Zero writes PNG. One writes JPEG. This applies to frame sequences and to frames retained while Video mode is active.

This value has no effect while RenderJpeg is 0 and PNG output is active.

A wrong choice swaps red and blue in files while the live screen still looks normal. The correct forced value varies between some Legacy and FiveM configurations.

RE+ restores the interface after the render completes or is aborted.

Disabling it leaves the editor in playback instead. It does not affect image quality.

Empty uses the Captures folder beside the RE+ installation. An absolute path can move large sequences onto a faster or roomier drive.

Video streams frames to FFmpeg as they finish. Frames writes a sequence plus assemble.txt. The actual capture process is otherwise identical.

Normally frames are removed after FFmpeg consumes them. Enabling this leaves both the sequence and video, using considerably more storage.

Empty searches the bundled copy first, then beside the game executable, then the Windows PATH.

A valid named preset overrides both RenderVideoArgs and RenderVideoExt. Included names are h264, h265, nvenc_hevc, prores_hq and lossless.

The attached command creates a high-quality, compatible H.264 file. It is good for delivery, but ProRes or PNG is preferable for heavy grading and repeated editing.

The container must support the codec in RenderVideoArgs. A named preset supplies its own extension and overrides this value.

Video mode muxes the recording into the result. Frames mode leaves audio.wav and adds the matching assembly command to assemble.txt.

When enabled, the output clock follows the project's authored marker speeds. This keeps rendered duration and the normal-speed audio pass aligned on projects that use speed changes.

This is ignored while RenderAudio is enabled. A stock Rockstar export of the same project can serve as the source.

Zero restores stock behaviour and prevents the mod's hooks from being installed. Render.ini has its own separate renderer switch.

Instead of blending along stock straight segments, the camera follows a spline that passes through the authored marker positions.

Position and rotation can be controlled separately. Look-at markers are re-aimed after the positional spline rather than relying on this interpolation alone.

The zoom curve is monotone, which is designed to avoid unintended overshoot beyond the FOV values you placed.

The curve is evaluated in the parent entity's frame, allowing mounted shots to flow instead of using the stock attached blend.

Without re-aiming, a look-at direction calculated from the original stock position can miss the subject after the camera is moved onto the spline.

Zero uses the displayed frame's aspect ratio. A positive override is useful only when the intended composition has a different aspect.

With one, Linear markers remain stock and Smooth markers use RE+. With zero, the mod also curves Linear marker transitions.

Natural pacing follows the time-parameterised path directly, easing through tight bends and flowing faster through open sections.

This produces even, metered travel rather than letting every segment establish its own pace. It is used only when NaturalPacing is off.

This is the per-segment fallback used only when both NaturalPacing and SmoothSpeedProfile are disabled.

Uniform produces wider tangents, Centripetal shortens them around close points, and Chordal weights them most strongly by distance.

Simple mode exposes real-world-style degrees and hertz. Complex mode instead uses separate slow Sway and fast Jitter movement and rotation layers.

Each degree also creates approximately 0.05 metres of positional travel. The effect is inherited by markers that select Rockstar Editor+ shake.

0.20 Hz creates a slow wander, while 0.35 Hz completes its broad character more quickly. It is not an arbitrary speed multiplier.

Zero produces a more metronomic, consistent signal. Higher values introduce irregularity that can read more like an operator.

More octaves add progressively finer-scale motion to the procedural signal. This affects texture, not the main amplitude setting.

Changing the seed rerolls the motion character without changing its amplitude, frequency or axis weighting. The same seed reproduces the same result.

The base amplitude remains present. This value defines the extra amplitude applied at ShakeSpeedRef.

This adds frequency at the reference speed, independently of the intensity coupling.

The speed-driven amplitude and frequency additions scale toward their configured amount as the camera approaches this value.

This is useful for motion-rig behaviour. A true handheld operator would normally retain some movement even while standing still.

Ignored while ShakeSimpleMode is enabled. Sway supplies the broad, low-frequency movement layer.

Ignored in Simple mode. It works alongside SwayMove and SwayFrequency.

It has no visible effect while both Sway amplitudes are zero or while Simple mode is active.

Ignored in Simple mode. Keep it restrained because high-frequency translation can read as digital vibration.

Ignored in Simple mode. It works with JitterMove and JitterFrequency.

It has no effect while the Jitter amplitudes are zero or Simple mode remains enabled.

This multiplier changes only lateral translation. Zero locks that axis while leaving the other shake axes active.

This multiplier changes only forward translation. Zero locks that axis while leaving the other shake axes active.

This multiplier changes only vertical translation. Zero locks that axis while leaving the other shake axes active.

This multiplier changes only pitch rotation. Zero locks that axis while leaving the other shake axes active.

This multiplier changes only roll rotation. Zero locks that axis while leaving the other shake axes active.

This multiplier changes only yaw rotation. Zero locks that axis while leaving the other shake axes active.

The same stock limit drives the warning and fallback to the recorded camera, so lifting it frees all three behaviours.

This is an editor movement limit, not an image-quality control. StreamingFocusOnCamera is the separate setting that decides whether world detail follows the camera or player.

Stock GTA streams the world around the player. RE+ uses the same camera-frame mechanism as Rockstar's switch and debug cameras so detail follows the shot instead; turning it off lets the game restore player focus on the next frame.

This allows moves through windows, fences and tight spaces without the stock collision response silently bending the authored path.

The stock naming flow can refuse local names when its network profanity request times out. This removes that dependency.

RE+ removes both the disabled menu row and the underlying director lock that would otherwise force the recorded view.

The stock editor waits for the whole game's streamer to report zero outstanding requests for consecutive frames. Heavily modded installs may never reach that state, so RE+ bypasses that global gate while keeping the replay's own preload check.

The audio wait has its own budget after the streaming wait. Disabling only FastPrecacheAudio can therefore leave a long pause even when FastPrecache is enabled.

It is off by default so rendered frames retain the stock preload guarantee. Enabling it is mainly an A/B diagnostic option.

Zero restores the stock unbounded wait. Positive values below 100 are raised to 100 because a healthy request cannot usefully complete below that floor.

Zero restores stock timing. A lower positive ceiling trades a long freeze for an entity that may appear late or be absent briefly when its model cannot arrive in time.

The wider range reaches the engine's own FOV limits, enabling genuinely long lenses as well as extreme wide angles.

The editor readout is 45 divided by FOV, so 1 degree appears as 45× zoom. This is an extreme engine limit.

At 130 degrees the editor displays roughly 0.35×. Distortion becomes very strong near this engine limit.

The original .clip is not changed. The override is applied live and can be removed by switching this setting off.

720 is 12:00, 1065 is 17:45 and 1320 is 22:00. It is ignored when the time override is off.

The game weather system evaluates the selected type, including clouds, wind, precipitation and related effects.

0 Extra Sunny, 1 Clear, 2 Clouds, 3 Smog, 4 Foggy, 5 Overcast, 6 Rain, 7 Thunder, 8 Clearing, 9 Neutral, 10 Snow, 11 Blizzard, 12 Snowlight, 13 Xmas, 14 Halloween.

Minus one disables blending. Any weather index enables an engine-evaluated intermediate state controlled by WeatherBlend.

Zero is entirely WeatherType and one is entirely WeatherBlendTo. It is ignored when the second type is -1.

Minus one preserves recorded wetness. Zero forces dry surfaces. Higher values increase puddles and reflective wet-road response without requiring rain particles.

One lets the engine evaluate lighting from the override time and weather. Zero preserves the fully resolved timecycle recorded in the clip and makes the override settings inert.

Clip duration varies with scene density. The supplied 128-block setting reserves roughly 604 MB and measured about 1 minute 45 seconds in dense city traffic.

Useful when a per-marker override appears to defeat the global INI value. Leave disabled during ordinary work.

Use only while investigating a curve problem. It adds noise to the log without improving the shot.

It is a diagnostic multiplier and does not belong in the creative camera setup. The source clamps it between zero and 100.

This produces a very noisy log and should be enabled only for focused developer-level investigation.

This is written automatically by the in-game menu. It has no effect on the rendered cinematic look and normally should not be hand-edited.

This is written automatically by the in-game menu. It has no effect on the rendered cinematic look and normally should not be hand-edited.

This is written automatically by the in-game menu. It has no effect on the rendered cinematic look and normally should not be hand-edited.