FiveM Guides/RE+ Handbook/Troubleshooting

Guide 07

Start with the symptom. Then read the log.

Do not change ten values at once. Prove the capture path with a short project, isolate the failing layer and keep the final log lines when something actually stops.

Verified against sourceRE+ troubleshooting notes by CoreFX/crxhvrd

Find the failing layer first

Choose the symptom you can actually see. The result gives you one controlled test and tells you how to interpret it before you touch another setting.

GUIDED CHECK

What do you see?

All known symptoms

01Export produces Rockstar's normal watermarked video+

Likely reason: RE+ did not get a working capture add-on and stepped aside.

  1. Confirm ReShade is the build with full add-on support
  2. Use the modified IgcsConnector.addon64 supplied with RE+
  3. Read the requirement line on the Export screen
02Export looks frozen+

Likely reason: It may be processing hundreds of real frames for each second of output, or it may genuinely be stuck.

  1. Open RockstarEditorPlus.log and look for progress written around every 15 seconds
  2. Test a two-second project at RenderSamples=3
  3. If the log stops completely, keep its final lines for diagnosis
03Red and blue are swapped in saved files+

Likely reason: The capture bridge interpreted the back-buffer channel order incorrectly.

  1. Set RenderChannelOrder=1 and test
  2. If still wrong, use RenderChannelOrder=2
  3. Judge the file, not the live screen
04The camera curve does nothing+

Likely reason: The marker may not be eligible for RE+ spline takeover.

  1. Set the marker blend to Smooth when OnlySmoothBlend=1
  2. Confirm SplinePosition or the relevant channel is enabled
  3. Remember Alpha is ignored while NaturalPacing=1
05Shake settings do nothing+

Likely reason: The marker is using stock shake, a per-marker override, or paused clip time.

  1. Set the marker's Shake row to Rockstar Editor+
  2. Look for a number instead of Default in the marker menu
  3. Play or scrub before judging shake
06Time changes but the sky still looks wrong+

Likely reason: The clip's recorded lighting keyframe is still being applied.

  1. Set LiveTimecycle=1 for a fresh exterior relight
  2. Enable the relevant time or weather override
  3. For interiors, restore LiveTimecycle=0 instead of forcing a mismatched sky
07Frames exist but there is no video+

Likely reason: RenderMode is Frames or FFmpeg was not found or rejected the arguments.

  1. Check RenderMode
  2. Confirm the bundled ffmpeg.exe is present
  3. Make sure codec arguments and RenderVideoExt use a compatible container
08Distant camera shows poor LOD+

Likely reason: Detail may still follow the player, the camera may have moved faster than the world can stream, or this feature's pattern may not match the running game build.

  1. Set StreamingFocusOnCamera=1 or Detail Follows to Camera
  2. Pause after a long city move so map and collision can arrive
  3. Read the startup log to confirm the streaming-focus feature resolved on this build
09Depth-of-field render takes far longer than expected+

Likely reason: Every output frame is a complete aperture pass, and RenderDofQuality increases the aperture sample count.

  1. Test only two seconds first
  2. Return RenderDofQuality to 12
  3. Check progress in RockstarEditorPlus.log before treating tens of seconds per frame as a freeze
10Depth-of-field focus lands on the wrong subject+

Likely reason: Autofocus measures world depth through one screen point; it does not recognise or track a named subject.

  1. Move RenderDofFocusX and RenderDofFocusY onto the exact surface that must be sharp
  2. Keep RenderDofAutofocus=1 for moving subjects
  3. Inspect frame zero separately because the current source records a known first-frame focus discrepancy

What a controlled test looks like

RenderCaptureMode=Sliding
RenderFps=24
RenderSamples=3
RenderShutter=0.5
RenderAudio=0
RenderMode=Frames
RenderJpeg=0

Use a two-second clip with one camera and no complex time changes. If this succeeds, restore one production feature at a time instead of rebuilding the whole configuration blindly.

The log tells you which layer failed

Log stateMeaning
No log fileThe ASI did not load at all
Stops during initializationThe final line normally names the missing pattern or requirement
Progress keeps updatingThe render is slow, not frozen
FFmpeg error after framesThe capture worked; output encoding failed
Stock encoder runsRE+ renderer is off or the capture bridge is unavailable

Match the guide to the installed build

This release of the guide follows the 92-key configuration at source commit d6c0a318. An older INI can omit newer keys and still load because the ASI falls back to defaults, but an older ASI cannot gain a feature merely because its key was copied into the file.

Check the binary before copying newer keys.

The opening lines of RockstarEditorPlus.log identify the loaded build and show which patterns resolved. That evidence is more useful than the age of the INI comments.