Proton
Proton copied to clipboard
ValveSoftware
Stray (1332010)
Compatibility Report
- Name of the game with compatibility issues: Stray
- Steam AppID of the game: 1332010
System Information
- GPU: AMD RX 6700XT
- Driver/LLVM version: Mesa 22.1.3, amdgpu 22.10.2.50102-1408194
- Kernel version: 5.14.21
- Link to full system information report: sysinfo.txt
- Proton version: Proton Experimental (Also tried with stable 7.0-3 and recent Proton GE 7-24, no luck)
I confirm:
- [ x ] that I haven't found an existing compatibility report for this game.
- [ x ] that I have checked whether there are updates for my system available.
Symptoms
- Default proton version (and many others) exits without any messages
- When prefix is cleaned and changed to Proton Experimental user is presented with MessageBox dialog stating that MSVC++ libraries are missing -- but I find the latter hard to believe given the prefix has every single one under the sun seems to be provided by default.
Proton log: steam-1332010.log
Error dialog: "The following component(s) are required to run this program: Microsoft Visual C++ Runtime"
Reproduction
- Install the game and try to launch: Nothing happens with whichever the default proton version the Steam runtime decided and prematurely exits with no dialog.
- Clean the prefix and try forcing any other version of Proton, be it: stable 7.0-3, experimental or 3rd party none of them seem to work out of box
- Using Proton Experimental at least gives the dialog complaining about MSVC++ libs
- Tried forcing installation of vc2019 and mfc2015 via winetricks/protontricks but this didn't seem to work either
System Information
- GPU: RX 6400 / RX 470
- Driver/LLVM version: Mesa 22.1.4 - kisak-mesa PPA
- Kernel version: 5.15.0-41-generic (Ubuntu 22.04)
- Link to full system information report as Gist:
- Proton version: 7.0-3
it just work on my PC. (screenshot)
update (25 Jul 2022):
- [v] Enable Shader Pre-Caching
- [_] Allow background processing of Vulkan shaders
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json
Interesting, do happen to know which version of DXVK is being used?
from Proton 7.0-3 Changelog,
Update dxvk to v1.10.1-57-g279b4b7e.
Same issue across multiple Proton versions
GPU: RTX 3070 Driver/LLVM version: 510.73.05 Kernel version: 5.15.0-41-generic #44~20.04.1-Ubuntu SMP Proton version: Tried following Proton-6.21-GE-1 GE-Proton-7-10 Proton Experimental Proton 7.0-3
Brief update: Yesterday I had tried latest Proton GE 7-26 with the same dialog as before.
Today I've just now got online, and interestingly two new updates were queued. One for the game and the other for Steam Runtime, and these seem to have helped/solved the issue!
Steam re-ran the installation script with three actions and launched the game to the menu with no issues. One of the items was DirectX installation, so I can only assume some libraries were unintentionally missing in the prefix. I've not yet done a diff of the directories to know what else/why. Note: This is still with Proton GE 7-26, I've changed nothing else not even cleaning out the prefix directory.
Secondly the d3d11.log + dxgi.log (Which gets dumped in the games' installation area in steamapps) now populates with the expected feature checks as expected
There's still some log spam with trace unwinds but it at least functions and got to the main menu.
had same "fatal error" problem with both proton 7.0-3 and proton GE 7-26
got it to run by using wine3d11 with the launch option PROTON_USE_WINED3D11=1 %command%, but its not really playable - many objects are missing in-game, and black squares are often flashing
maybe this could be related to dxvk?
@penguinuwu That's odd, everything looks fine from the system information dump. It doesn't appear like the Vulkan ICD is missing, which is one issue I'd had before.
I would expect Mesa to be the appropriate choice for Intel Xe for OpenGL and the libvulkan_intel packages as you have installed are perfectly fine. Although I'm unsure how well supported the Xe family of parts are currently/what functional limitations there are in Linux.
Three basic things to check would be:
-
glxinfo -
vulkaninfoTest whether simple OpenGL/Vulkan apps perform as you expect with:glxgearsandvkmark?
The only other thing you can try, when you have multiple Vulkan providers that conflict, is to enforce the correct ICD gets used by adding:
... VK_ICD_FILENAMES="/path/to/vulkan.icd" ...
In this case: ... VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/intel_icd.x86_64.json" ...
Last resort is to refresh the prefix entirely:
- Move the game prefix directory to keep a backup (eg:
mv /home/$USER/.steam/steam/steamapps/compatdata/1332010 /home/$USER/.steam/steam/steamapps/compatdata/1332010.orig) - Remove the environment overrides
- To force the game to retry the installation, I found validating the game files and then try launching it to be best. (I believe, validating the game files restores the installation script when it detects the prefix is missing but this might only be coincidence)
Also if you have a failure log that's significantly different, go ahead and attach one in a reply.
On my end the game now runs fine with the update patches that came in, in fact very much identical performance to Windows! Only performance issues of not are large stutters happening when looking in certain directions, this is identical across Windows and Linux. e.g. It often happens when quickly looking directly downwards, I suspect a divide by zero issue using trigonometry functions as the camera angle tends towards zero on a relative axis.
Also getting a "fatal error!" popup before the game crashes on GE-Proton7-20, Proton Experimental, and Proton 7.0-3.
Gathered the following after verifying game files:
- Proton logs: steam-1332010.log
- Steam System Information excerpt (please let me know if I omitted anything relevant):
- Pop!_OS 22.04 LTS (64 bit)
- CPU Brand: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
- Steam Runtime Version: steam-runtime_0.20220315.0
- Driver: Intel Mesa Intel(R) Xe Graphics (TGL GT2)
- Driver Version: 4.6 (Compatibility Profile) Mesa 22.0.1
- OpenGL Version: 4.6
@jfshorter thanks for the suggestions, i've given those a try but had no luck
glxinfo, vulkaninfo, glxgears, and vkmark all ran without errors. i'm not sure what else to look for, here are the results in a gist
i tried enforcing the ICD files by running steam with the command VK_ICD_FILENAMES='...' steam and also setting the launch options to VK_ICD_FILENAMES='...' %command% but it would still not launch. i used the values:
-
VK_ICD_FILENAMES='/usr/share/vulkan/icd.d/intel_icd.i686.json:/usr/share/vulkan/icd.d/intel_icd.x86_64.json' -
VK_ICD_FILENAMES='/usr/share/vulkan/icd.d/intel_icd.x86_64.json -
VK_ICD_FILENAMES='/usr/share/vulkan/icd.d/intel_icd.i686.json'(this one resulted in the error "A D3D11-compatible GPU (Feature Level 11.0, Shader Model 5.0) is required to run the engine." instead of the "Fatal error!" - guess i'm not supposed to use the 32-bit version)
next i tried: delete prefix directory -> verify integrity of game files -> reset launch options -> launch game. the "performing first time setup" window popped up and installed some microsoft stuff, but it still ended in the "Fatal error!" window. it doesn't look too different, but i noticed a few warnings - maybe those might be significant? here is the logs gist (i tried this on proton GE 7-26, Experimental, 7.0-3 and got similar results)
i'm out of ideas to try, not sure what's going on; might just wait for mesa/dxvk/proton updates and try again later...
@junefish Ahh okay, I spotted something in that log which gives me an idea:
info: DXVK: Read 0 valid state cache entries info: DXVK: Using 5 compiler threads ../src/intel/isl/isl.c:2216: FINISHME: ../src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is disabled, but a workaround is available. 18777.100:0138:013c:trace:seh:dispatch_exception code=c0000005 flags=0 addr=000000014181FA8A ip=000000014181FA8A tid=013c 18777.100:0138:013c:trace:unwind:dispatch_exception info[0]=0000000000000000 18777.100:0138:013c:trace:unwind:dispatch_exception info[1]=0000000000000000 18777.100:0138:013c:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised
I have a feeling the game is trying to launch a non-existent Windows native shader compiler and failing when the game needs to rely on Steams' fossilise tool to have the shaders pre-prepared for your GPU for DXVK to pick up on run time.
This is a long shot, but try going through the menus: Steam -> Settings -> Shader Pre-Caching: Tick the "Enable Shader Pre-Caching" + "Allow background processing of Vulkan shaders enabled"
This will consume more CPU time when you download game updates but will launch games quicker, and ensures the Vulkan shader cache always matches the version of the game you have.
I've had so many other similarly weird problems with other games after updates without this turned on, that I'm surprised it is not a default-on setting for Linux. 3kliksphilip voice "Valve, please fix"
(Sorry if you and others already have this setting enabled already)
@penguinuwu Looking at those results from a driver provider perspective all look perfect, thanks for sharing. It seems like the Proton log matches junefish's so might be worth trying the above if you happen to run without shader pre-caching enabled
I hope this is the magic bullet for you guys, or at least it's just some other minor oversight that can be fixed if this does not work.
just got the game to work purfectly! all i did was downgrade to proton 6.3-8 💀 here is the proton log to compare
i noticed that the working log is lacking the warning:
warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised
maybe that's the problem in proton 7 and newer?
@jfshorter i have both settings ticked already, but i tried unticking both options and it just replaced the DXVK error with
warn: DXVK: No state cache file found
warn: DXVK: Creating new state cache file
seems like that's not the problem here
just FYI,
my configuration:
- [v] Enable Shader Pre-Caching
- [_] Allow background processing of Vulkan shaders
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json
I have a feeling the game is trying to launch a non-existent Windows native shader compiler and failing when the game needs to rely on Steams' fossilise tool to have the shaders pre-prepared for your GPU for DXVK to pick up on run time.
This is a long shot, but try going through the menus: Steam -> Settings -> Shader Pre-Caching: Tick the "Enable Shader Pre-Caching" + "Allow background processing of Vulkan shaders enabled"
This will consume more CPU time when you download game updates but will launch games quicker, and ensures the Vulkan shader cache always matches the version of the game you have.
@jfshorter I had "Enable shader pre-caching" checked already, but not "allow background processing of vulkan shaders". I checked the latter and it started processing a bunch of games, with the "pre-cached" number going up (it was at 0MB when I opened Settings). A bunch of games including Stray showed up in completed Downloads.
I then tried launching Stray again on 7.0-3 and it had a "processing vulkan shaders..." progress bar popup, but it still exited with "fatal error".
just got the game to work purfectly! all i did was downgrade to proton 6.3-8
@penguinuwu tried changing to proton 6.3-8 and still got fatal error unfortunately. steam-1332010.log
Tried adding @penguinuwu's launch option VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json (verified that both files are present w/same paths). Then I verified integrity of game files again, and tried to launch using Proton 6.3-8.
This time I got the error:
A D3D11-compatible GPU (Feature Level 11.0, Shader Model 5.0) is required to run the engine.
I'm not sure whether this means my GPU is actually not compatible, or if it's a settings issue. (I see that penguin got the same message earlier, with a slightly different launch option?)
@junefish Ahh right, looking at Intel's Tiger Lake Xe-LP GT2 it seems to claim DirectX 12.1 feature compatibility: Intel ARK - i5-1135G7 Specifications
[Note: This can be ambiguous where DirectX 12.0 is essentially the same as full featured DirectX 11, similar for many releases the x.0 is just "everything the previous version supported". Thanks for that misleading dual naming, Micro$oft.]
I can only assume either:
- The game doesn't recognise Xe-LP / have a known supported entry for settings (Testing for sanity on Windows might give a clue if that's an option?)
- DXVK failed to init and detect Xe-LP with Proton 6.3-8
Feel free to attach another log if you have one for that second failure, could be useful if someone has an idea. Sorry I haven't been much of a help haha!
just got the game to work purfectly! all i did was downgrade to proton 6.3-8 skull here is the proton log to compare
@penguinuwu Could you try dropping the dxvk files from 7.0-3 where it fails into 6.3-8 to try to confirm if this is a dxvk regression or not? To do this: cp -rf ~/.steam/steam/steamapps/common/Proton 7.0/dist/lib/wine/dxvk/* ~/.steam/steam/steamapps/common/Proton 6.3/dist/lib/wine/dxvk/. cp -rf ~/.steam/steam/steamapps/common/Proton 7.0/dist/lib64/wine/dxvk/* ~/.steam/steam/steamapps/common/Proton 6.3/dist/lib64/wine/dxvk/.
After you are done testing, you can "revert" the change by deleting the whole 6.3 "dist" folder - it will recreate itself.
@alasky17 the game worked just fine after the steps, seems like that's not the problem. i've pasted a log of my commands below
also think it's worth noting that i'm mainly testing on wayland (swaywm). i just tried running on x11 (kde) (because one of my mouse buttons wasn't working), then ran into the same "Fatal error!" issue with proton 6.3-8 and above. however, proton 5.13-6 ran just fine??? luckily the game works for me, but i have no clue what's going on...
$ # commands log
$ cd my-steam-root/steamapps/common/
$ cp -vrf 'Proton 7.0'/dist/lib/wine/dxvk/* 'Proton 6.3'/dist/lib/wine/dxvk/
'Proton 7.0/dist/lib/wine/dxvk/d3d10_1.dll' -> 'Proton 6.3/dist/lib/wine/dxvk/d3d10_1.dll'
removed 'Proton 6.3/dist/lib/wine/dxvk/d3d10_1.dll'
'Proton 7.0/dist/lib/wine/dxvk/d3d10core.dll' -> 'Proton 6.3/dist/lib/wine/dxvk/d3d10core.dll'
removed 'Proton 6.3/dist/lib/wine/dxvk/d3d10core.dll'
'Proton 7.0/dist/lib/wine/dxvk/d3d10.dll' -> 'Proton 6.3/dist/lib/wine/dxvk/d3d10.dll'
removed 'Proton 6.3/dist/lib/wine/dxvk/d3d10.dll'
'Proton 7.0/dist/lib/wine/dxvk/d3d11.dll' -> 'Proton 6.3/dist/lib/wine/dxvk/d3d11.dll'
removed 'Proton 6.3/dist/lib/wine/dxvk/d3d11.dll'
'Proton 7.0/dist/lib/wine/dxvk/d3d9.dll' -> 'Proton 6.3/dist/lib/wine/dxvk/d3d9.dll'
removed 'Proton 6.3/dist/lib/wine/dxvk/d3d9.dll'
'Proton 7.0/dist/lib/wine/dxvk/dxgi.dll' -> 'Proton 6.3/dist/lib/wine/dxvk/dxgi.dll'
removed 'Proton 6.3/dist/lib/wine/dxvk/dxgi.dll'
'Proton 7.0/dist/lib/wine/dxvk/openvr_api_dxvk.dll' -> 'Proton 6.3/dist/lib/wine/dxvk/openvr_api_dxvk.dll'
removed 'Proton 6.3/dist/lib/wine/dxvk/openvr_api_dxvk.dll'
'Proton 7.0/dist/lib/wine/dxvk/version' -> 'Proton 6.3/dist/lib/wine/dxvk/version'
removed 'Proton 6.3/dist/lib/wine/dxvk/version'
$ cp -vrf 'Proton 7.0'/dist/lib64/wine/dxvk/* 'Proton 6.3'/dist/lib64/wine/dxvk/
'Proton 7.0/dist/lib64/wine/dxvk/d3d10_1.dll' -> 'Proton 6.3/dist/lib64/wine/dxvk/d3d10_1.dll'
removed 'Proton 6.3/dist/lib64/wine/dxvk/d3d10_1.dll'
'Proton 7.0/dist/lib64/wine/dxvk/d3d10core.dll' -> 'Proton 6.3/dist/lib64/wine/dxvk/d3d10core.dll'
removed 'Proton 6.3/dist/lib64/wine/dxvk/d3d10core.dll'
'Proton 7.0/dist/lib64/wine/dxvk/d3d10.dll' -> 'Proton 6.3/dist/lib64/wine/dxvk/d3d10.dll'
removed 'Proton 6.3/dist/lib64/wine/dxvk/d3d10.dll'
'Proton 7.0/dist/lib64/wine/dxvk/d3d11.dll' -> 'Proton 6.3/dist/lib64/wine/dxvk/d3d11.dll'
removed 'Proton 6.3/dist/lib64/wine/dxvk/d3d11.dll'
'Proton 7.0/dist/lib64/wine/dxvk/d3d9.dll' -> 'Proton 6.3/dist/lib64/wine/dxvk/d3d9.dll'
removed 'Proton 6.3/dist/lib64/wine/dxvk/d3d9.dll'
'Proton 7.0/dist/lib64/wine/dxvk/dxgi.dll' -> 'Proton 6.3/dist/lib64/wine/dxvk/dxgi.dll'
removed 'Proton 6.3/dist/lib64/wine/dxvk/dxgi.dll'
'Proton 7.0/dist/lib64/wine/dxvk/openvr_api_dxvk.dll' -> 'Proton 6.3/dist/lib64/wine/dxvk/openvr_api_dxvk.dll'
removed 'Proton 6.3/dist/lib64/wine/dxvk/openvr_api_dxvk.dll'
'Proton 7.0/dist/lib64/wine/dxvk/version' -> 'Proton 6.3/dist/lib64/wine/dxvk/version'
removed 'Proton 6.3/dist/lib64/wine/dxvk/version'
GPU: Radeon RX 5500XT 8GB CPU: Ryzen 5 5600X Kernel: 5.18.14-zen1-1-zen (arch linux) Mesa: 22.1.3-1 Proton: 7.0-3 I have to report some things related to performance: if I don't use PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%, one core of my CPU in some parts of the map will be stuck at 100% usage and also the GPU performance of the game is way worse if compared to windows, even considering that on benchmarks my Linux OS outperforms Windows in GPU performance
I just discovered that using proton experimental (bleeding edge) fixes all the performance problems!
Replying to https://github.com/ValveSoftware/Proton/issues/6017#issuecomment-1194766734
Just to test I tried GE-Proton7-20 and a (newly updated) Experimental (steam-1332010.log) with the VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json launch option, and they also gave me the D3D11-compatible GPU required error, so it doesn't seem to be related to Proton version directly.
Also, realised I forgot to mention this before, but if I use PROTON_USE_WINED3D11=1 launch option the game does run, but basically nothing works except for the menus. If I start a game I hear the rain sounds and see a vaguely static image.
Hey, fellas. I thought this was known but doing a search for d3d12 in the thread, I'm not seeing it.
Stray runs vastly better on my Steam Deck when launching with the -d3d12 argument. I can get a (mostly) locked 60 fps at 80% res scale, low settings. That's compared to low-mid 40s on the default d3d11 backend. Go ahead and give it a try if you have a hankering for frames! 🐸
Haven't tested on my desktop, but I would assume the same principle applies there. Just keep in mind d3d12 is not officially supported by the game.
I was able to get it running (and working) by setting the launch options to:
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/intel_icd.i686.json:/usr/share/vulkan/icd.d/intel_icd.x86_64.json PROTON_USE_WINED3D11=1 %command%
I also have shader pre-caching enabled (and allow background processing); not sure if it's required though. Proton 7.0 and Experimental are super glitchy graphics-wise. 6.3 has some glitches too, but it's much better.
One thing I also tried that did not work was removing PROTON_USE_WINED3D11=1, and adding -d3d12 to the end. The game launched, and the menus worked, but none of the graphics displayed at all.
For reference, I have an Intel 12th-gen i7, with Xe graphics ("Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c)").
hey there! it works on my nvidia? but i dont know how to enable RTX effects? (is it has RayTrace reflections? on many screenshots from internet it has much better reflections, then mine, but i set all avaliable settings to maximum )
Stray Stuck In Launching
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7211. @AvocadoMoon posted on 2023-10-29T14:45:16:
Compatibility Report
- Name of the game with compatibility issues: Stray
- Steam AppID of the game: 1332010
System Information
- GPU: GTX 3060 Ti
- Video driver version: 4.6.0 NVIDIA 535.113.01
- Kernel version: 6.5.6-76060506-generic
- Link to full system information report as Gist:
- Proton version: 8.04
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
- [x] Attempt to create proton logs
Symptoms
When I launch the game stray, nothing happens and it stays saying that it's currently launching. I try to generate some logs from Proton, but I get nothing which makes this significantly more difficult to find out whats the issue.
Reproduction
I'm not fully sure how to, since all I do is attempt to play the game.
Hello @AvocadoMoon, the lack of a Proton log when you ask for it hints that something's gone wrong before Proton gets a chance to start the game.
The symptoms you've described reads like #6859. Please give that issue report a read and see if it's relevant.