This matters for builds dropped into compatibilitytools.d/. Steam uses
the internal tool name to detect it's Proton and alters some behavior
regarding how cloud saves work.
Not including Proton in the name may lead to confusing behavior
regarding saves where they are present on some builds but vanish on the
other, only to reappear when switching back.
NVIDIA-software may check the environment variable `NVIDIA_WINE_DLL_DIR`
for a path where DLLs provided by the NVIDIA Linux driver can be found.
This is done as a fallback for when the "DriverStore" cannot be detected
via the D3DDDI functions for querying an adapter-specific registry key.
Tested with an application that reads `NVIDIA_WINE_DLL_DIR` from the
environment and tries to load a known DLL from it. As expected manually
setting the environment variable to the on-disk location did not work,
as the path is not accurate within the pressure-vessel environment.
Link: https://github.com/ValveSoftware/Proton/pull/8087
Patch written by Emily <102429049+emily-is-my-username@users.noreply.github.com>
https://github.com/ValveSoftware/Proton/pull/8126
When using OpenComposite, both OpenVR and OpenXR functions may
call the same underlying OpenXR loader.
Because the OpenXR loader only supports a single active instance,
`initialize_vr_data` currently fails as an OpenXR instance
has already been initialized ath the time XR extensions are queried.
This commit fixes the problem by cleaning up the temporary
OpenVR context *before* initializing OpenXR instead of keeping it
open until the end of the call.
Fix for:
https://github.com/ValveSoftware/Proton/issues/7905
Signed-off-by: Paul Gofman <pgofman@codeweavers.com>
NVIDIA-software may check the environment variable `NVIDIA_WINE_DLL_DIR`
for a path where DLLs provided by the NVIDIA Linux driver can be found.
This needs to be set by `proton` script, as it is ran inside of the
pressure-vessel environment, so the paths returned will be valid within
the environment.
Tested with an application that reads `NVIDIA_WINE_DLL_DIR` from the
environment and tries to load a known DLL from it. As expected manually
setting the environment variable to the on-disk location did not work,
as the path is not accurate within the pressure-vessel environment.
https://github.com/ValveSoftware/Proton/pull/8087
