Mali old DXVK: a setting to keep Proton's own, and Proton's own back when the bridge is off

Setup has a "DXVK" row under the bridge's safe mode: automatic (the default, as before) or
Proton's own (SessionPrefs.bridgeProtonDxvk). With Proton's own, nothing is chosen and an earlier
automatic choice goes back to the Proton's copy.

Automatic choices also go back when the session is not a bridge session (the bridge turned off),
even when nothing is known of the Vulkan; a queued automatic swap is dropped with them, the
player's own queued swaps stay. Turning the bridge off, or choosing Proton's own, does it right
away in the background instead of at the next session. A failed detection in a bridge session
still keeps the last choice.
This commit is contained in:
ASEbrahim authored and maxjivi05 committed 2026-10-26 13:55:31 -04:00
1 parent 678e16af4d
commit 7aeb194d6e
10 files changed
+142 -9

No files matched your search

+5
View File
@@ -3233,5 +3233,10 @@
<string name="setup_bridge_safe_off">Safe mode: off</string>
<string name="setup_bridge_safe_on_detail">Most compatible. Recommended for a new device.</string>
<string name="setup_bridge_safe_off_detail">Faster where this GPU passed its checks.</string>
<string name="setup_bridge_dxvk">DXVK</string>
<string name="setup_bridge_dxvk_auto">DXVK: automatic</string>
<string name="setup_bridge_dxvk_proton">DXVK: Proton\'s own</string>
<string name="setup_bridge_dxvk_auto_detail">Uses an older DXVK where this GPU\'s Vulkan is too old for Proton\'s.</string>
<string name="setup_bridge_dxvk_proton_detail">Every Proton keeps its own DXVK, even where this GPU\'s Vulkan may be too old for it.</string>
<string name="setup_gpu_bridge_detail">%1$s is not an Adreno. The experimental Vulkan bridge is on: the session draws through the phone\'s own driver. Expect bugs; send the session logs.</string>
</resources>