Known issues

Known issues

NVIDIA Reflex and GPU crashes

Workaround for affected NVIDIA players: keep NVIDIA Reflex and Reflex Boost disabled, then restart the game.

A player running the 0.1.4 development client on an NVIDIA GeForce RTX 4070 reported a crash shortly after joining and subsequently identified Reflex as the problematic setting. The supplied Unreal report confirms a GPU Crash under DirectX 12; the multiplayer anti-cheat did not terminate that session. The report does not contain enough GPU diagnostic data to prove the exact rendering/driver cause. This is a reported compatibility issue, not a claim that Reflex crashes every NVIDIA system or that disabling it fixes all GPU crashes.

Manual workaround (also usable with existing launchers)

1. Fully close the game before editing its settings.
2. Back up %LOCALAPPDATA%\G1R\Saved\Config\Windows\GameUserSettings.ini.
3. In the existing [/Script/G1R.GothicGameUserSettings] section, set the values below. Replace existing keys instead of adding conflicting duplicates; preserve all other settings.
4. Save the file, restart the game and retest the same server/location.

[/Script/G1R.GothicGameUserSettings]
FrameGenerationDLSS=0
UpscalingMethod=0
StreamlineReflexEnabled=False
StreamlineReflexBoostEnabled=False

DLSS caution: disabling DLSS upscaling/DLAA and DLSS Frame Generation is an additional precaution; their separate effect on this crash has not been tested. The default-off NVIDIA game settings are a compatibility policy, not proof that every GPU crash is fixed. UpscalingMethod=0 selects no upscaler in G1R. The launcher only changes this selection when DLSS is selected (or missing/invalid); existing FSR, XeSS and TSR choices and their quality settings remain unchanged. FSR Frame Generation is not modified.

Default launcher policy since 0.1.4 BUILD134

From BUILD134, NVIDIA Reflex, Reflex Boost, DLSS upscaling/DLAA and DLSS Frame Generation are disabled by default before launching the game. No manual toggle is needed. Settings shows NVIDIA GPU CRASH WORKAROUND (DEFAULT ON). Fully close the game before joining again so the launch policy can apply.

• The compatibility policy is ON by default (the NVIDIA game features are OFF). BUILD134 also migrates older saved launcher settings once, including BUILD132/133's default false. Later explicit opt-out choices saved under the new policy remain respected. BUILD132/133 used an opt-in policy; 0.1.3 lacks this switch.
• On each launch with the option enabled, the launcher disables the NVIDIA settings shown above, preserving an existing non-DLSS upscaler in the Gothic settings section. The launcher's pre-existing frame-pacing settings are unaffected by this addition.
• Before changing an existing settings file, it creates a sibling backup named GameUserSettings.ini.g1rmp-before-nvidia-<timestamp>-<pid>.bak. No new backup is made if the required values already match. A new installation without a settings file has no previous file to back up.
• If backup or application fails, the enabled workaround stops that launch rather than silently continuing without the requested settings. Read-only or redirected config paths are rejected.
• These are persistent game settings, shared with single-player. Switching the launcher option OFF stops enforcing them; it does not automatically re-enable Reflex or restore the entire INI. To undo, disable the option and change the desired graphics settings in the game. A full backup restore is possible with the game closed, but may revert other settings changed after the backup.
• The option uses the settings file, not unverified raw -FrameGenerationDLSS=0 arguments. No Lua API, game binary, anti-cheat policy or server change is involved.

If the crash continues, provide the launcher build, GPU/driver details, whether Reflex/Frame Generation were disabled, and the latest folder from %LOCALAPPDATA%\G1R\Saved\Crashes. A missing Saved\Logs folder does not invalidate an Unreal crash report.

Database disconnects

See Known issue: MySQL error 2006 (Server has gone away) and MySQL connection recovery for database recovery guidance.

See also Update 0.1.4.