Known issues - Revision history

QCherry: 0.1.4 BUILD134: Reflex and DLSS disabled by default, including existing installations

2026-09-21T20:54:12Z

0.1.4 BUILD134: Reflex and DLSS disabled by default, including existing installations

← Older revision		Revision as of 20:54, 21 September 2026
Line 15:		Line 15:
	[/Script/G1R.GothicGameUserSettings]		[/Script/G1R.GothicGameUserSettings]
	FrameGenerationDLSS=0		FrameGenerationDLSS=0
			UpscalingMethod=0
	StreamlineReflexEnabled=False		StreamlineReflexEnabled=False
	StreamlineReflexBoostEnabled=False		StreamlineReflexBoostEnabled=False
	</syntaxhighlight>		</syntaxhighlight>

	'''DLSS caution:''' disabling DLSS Frame Generation is an additional precaution; ~~its~~ separate effect on this crash has '''not been tested'''. ~~If problems continue, disabling ordinary DLSS upscaling in the~~ game~~'s graphics~~ settings ~~is another '''untested troubleshooting step'''~~, not ~~a verified fix~~. ~~DLSS upscaling and DLSS Frame Generation are different features~~. The ~~three settings above do '''not''' disable ordinary~~ DLSS ~~upscaling~~ or FSR Frame Generation.		'''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.

	=== ~~Launcher option~~ since 0.1.4 ===		=== Default launcher policy since 0.1.4 BUILD134 ===
	In the ~~public 0~~.1.~~4 launcher (BUILD133 or newer), open '''~~Settings~~''', switch~~ '''NVIDIA GPU CRASH WORKAROUND (~~OPTIONAL~~)''' ~~to '''ON''', click '''SAVE SETTINGS''', then join a server with~~ the game ~~closed~~.		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 ~~option~~ is '''~~OFF~~ by default'''. ~~Older launchers~~, including ~~public~~ 0.1.3~~, do not provide~~ this switch~~. The option is included in public 0.1.4~~.		* 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 ~~sets only~~ the ~~three~~ NVIDIA ~~keys~~ shown above in the Gothic settings section. The launcher's pre-existing frame-pacing settings are unaffected by this addition.		* 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 <code>GameUserSettings.ini.g1rmp-before-nvidia-<timestamp>-<pid>.bak</code>. No new backup is made if the ~~three~~ values already match. A new installation without a settings file has no previous file to back up.		* Before changing an existing settings file, it creates a sibling backup named <code>GameUserSettings.ini.g1rmp-before-nvidia-<timestamp>-<pid>.bak</code>. 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.		* 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.		* 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.

QCherry: Release 0.1.4 BUILD133 / Protocol 36 and document authenticated event origin

2026-09-21T20:37:13Z

Release 0.1.4 BUILD133 / Protocol 36 and document authenticated event origin

← Older revision		Revision as of 20:37, 21 September 2026
Line 21:		Line 21:
	'''DLSS caution:''' disabling DLSS Frame Generation is an additional precaution; its separate effect on this crash has '''not been tested'''. If problems continue, disabling ordinary DLSS upscaling in the game's graphics settings is another '''untested troubleshooting step''', not a verified fix. DLSS upscaling and DLSS Frame Generation are different features. The three settings above do '''not''' disable ordinary DLSS upscaling or FSR Frame Generation.		'''DLSS caution:''' disabling DLSS Frame Generation is an additional precaution; its separate effect on this crash has '''not been tested'''. If problems continue, disabling ordinary DLSS upscaling in the game's graphics settings is another '''untested troubleshooting step''', not a verified fix. DLSS upscaling and DLSS Frame Generation are different features. The three settings above do '''not''' disable ordinary DLSS upscaling or FSR Frame Generation.

	=== Launcher option since 0.1.4 ~~BUILD132 (development)~~ ===		=== Launcher option since 0.1.4 ===
	In the ~~BUILD132~~ or newer ~~development launcher~~, open '''Settings''', switch '''NVIDIA GPU CRASH WORKAROUND (OPTIONAL)''' to '''ON''', click '''SAVE SETTINGS''', then join a server with the game closed.		In the public 0.1.4 launcher (BUILD133 or newer), open '''Settings''', switch '''NVIDIA GPU CRASH WORKAROUND (OPTIONAL)''' to '''ON''', click '''SAVE SETTINGS''', then join a server with the game closed.

	* The option is '''OFF by default'''. Older launchers, including public 0.1.3, do not provide this switch. ~~This documentation~~ is ~~not a~~ public ~~updater rollout~~.		* The option is '''OFF by default'''. Older launchers, including public 0.1.3, do not provide this switch. The option is included in public 0.1.4.
	* On each launch with the option enabled, the launcher sets only the three NVIDIA keys shown above in the Gothic settings section. The launcher's pre-existing frame-pacing settings are unaffected by this addition.		* On each launch with the option enabled, the launcher sets only the three NVIDIA keys shown above 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 <code>GameUserSettings.ini.g1rmp-before-nvidia-<timestamp>-<pid>.bak</code>. No new backup is made if the three values already match. A new installation without a settings file has no previous file to back up.		* Before changing an existing settings file, it creates a sibling backup named <code>GameUserSettings.ini.g1rmp-before-nvidia-<timestamp>-<pid>.bak</code>. No new backup is made if the three values already match. A new installation without a settings file has no previous file to back up.

QCherry: Document reported NVIDIA Reflex GPU crash and optional BUILD132 workaround

2026-09-21T20:04:50Z

Document reported NVIDIA Reflex GPU crash and optional BUILD132 workaround

New page

= 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) ===
# Fully close the game before editing its settings.
# Back up <code>%LOCALAPPDATA%\G1R\Saved\Config\Windows\GameUserSettings.ini</code>.
# In the existing <code>[/Script/G1R.GothicGameUserSettings]</code> section, set the values below. Replace existing keys instead of adding conflicting duplicates; preserve all other settings.
# Save the file, restart the game and retest the same server/location.

<syntaxhighlight lang="ini">
[/Script/G1R.GothicGameUserSettings]
FrameGenerationDLSS=0
StreamlineReflexEnabled=False
StreamlineReflexBoostEnabled=False
</syntaxhighlight>

'''DLSS caution:''' disabling DLSS Frame Generation is an additional precaution; its separate effect on this crash has '''not been tested'''. If problems continue, disabling ordinary DLSS upscaling in the game's graphics settings is another '''untested troubleshooting step''', not a verified fix. DLSS upscaling and DLSS Frame Generation are different features. The three settings above do '''not''' disable ordinary DLSS upscaling or FSR Frame Generation.

=== Launcher option since 0.1.4 BUILD132 (development) ===
In the BUILD132 or newer development launcher, open '''Settings''', switch '''NVIDIA GPU CRASH WORKAROUND (OPTIONAL)''' to '''ON''', click '''SAVE SETTINGS''', then join a server with the game closed.

* The option is '''OFF by default'''. Older launchers, including public 0.1.3, do not provide this switch. This documentation is not a public updater rollout.
* On each launch with the option enabled, the launcher sets only the three NVIDIA keys shown above 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 <code>GameUserSettings.ini.g1rmp-before-nvidia-<timestamp>-<pid>.bak</code>. No new backup is made if the three 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 <code>-FrameGenerationDLSS=0</code> 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 <code>%LOCALAPPDATA%\G1R\Saved\Crashes</code>. A missing <code>Saved\Logs</code> 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]].