Proton
Proton copied to clipboard
ValveSoftware
Starfield (1716740)
Compatibility Report
- Name of the game with compatibility issues: Starfield
- Steam AppID of the game: 1716740
System Information
- GPU: rtx 4090
- Video driver version: 535.98
- Kernel version: 6.4.0-1-amd64
- Link to full system information report as Gist: will have to update later
- Proton version: 8.0-3 and experimental
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
The game starts up and seems okay but when starting a new game the game freezes during first load. Experimental freezes and 8.0 crashes.
Also if i add PROTON_USE_WINED3D=1 to launch options the game wont boot and gives an error about video card not meeting minimum spec.
I'm having a different problem. When I start the game, it'll reach the building shaders screen and make it partway through. At a decent way in, the game will crash to desktop and refuse to start until I delete the shader cache. Attached is the log. steam-1716740.log
I'm having a different problem. When I start the game, it'll reach the building shaders screen and make it partway through. At a decent way in, the game will crash to desktop and refuse to start until I delete the shader cache. Attached is the log.
I got past this by removing all my launch options and changing my proton version (which I assume clears the shader cache)
I'm also hitting this, logs appear to indicate an issue with a semaphore in vkd3d.
In particular I see this first
70498.977:0128:01dc:err:vkd3d-proton:vkd3d_view_map_create_view: Intense view map pressure! Got 1024 views in hash map 000000018dcd8dc8.
70498.977:0128:01dc:err:vkd3d-proton:vkd3d_view_map_create_view: Intense view map pressure! Got 1024 views in hash map 000000018dcd9048.
but then, e.g.
70503.294:0128:0224:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
70503.294:0128:0224:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
70503.294:0128:0224:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
70503.294:0128:0224:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
70503.294:0128:0224:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
(RTX 4090)
Replying to https://github.com/ValveSoftware/Proton/issues/7064#issuecomment-1701988449
Same hardware and same issue for me
I'm also hitting this, logs appear to indicate an issue with a semaphore in vkd3d.
How do you figure? Just curious. I haven't looked under the vkd3d hood yet.
also running into the same issue
manjaro 5.15.128-1 ryzen 9 3900x 3080ti (535.104.05)
Just adding that I too am facing
4320.209:0124:01e4:warn:vkd3d-proton:d3d12_device_QueryInterface: {0742a90b-c387-483f-b946-30a7e4e61458} not implemented, returning E_NOINTERFACE. 4324.573:0124:0208:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
Arch Linux 6.1.50-1-lts Ryzen 9 5950x 32 @4.1 RTX3080 12GB (535.104.05) 128GB RAM
Only Proton Experimental, Proton 8.0-3, and GE-Proton8-13 launch the game to main menu before crashing upon launching new game.
The vr -4's here appear to mean VK_ERROR_DEVICE_LOST is being returned from calls to vkQueueSubmit2 and vkWaitForFences, among others. I know nothing about Vulkan and D3D, but is the "view map pressure" causing the device to be lost somehow? As ExpandingMan mentioned, that's the last thing in the log before things start failing, although there's a delay of several seconds between the last "view map pressure" message and the first "vr -4".
@descawed https://github.com/HansKristian-Work/vkd3d-proton/blob/master/libs/vkd3d/resource.c#L1211 You're probably not far off, going by this comment
Someone on steam stated they got it to work with Proton Hotfix. Upon launching under Hotfix it yielded the same result with an error I'd not seen before. Unsure if it's relevant.
5366.455:0128:020c:err:vkd3d-proton:dxgi_vk_swap_chain_submit_blit: Failed to wait for fence, vr -4 5366.455:0128:020c:err:vkd3d-proton:dxgi_vk_swap_chain_present_signal_blit_semaphore: Failed to submit present discard, vr = -4. 5366.455:0128:020c:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
I'm having a different problem. When I start the game, it'll reach the building shaders screen and make it partway through. At a decent way in, the game will crash to desktop and refuse to start until I delete the shader cache. Attached is the log. steam-1716740.log
I got past this by removing all my launch options and changing my proton version (which I assume clears the shader cache)
Thanks. That worked. Now I just get stuck on a black screen when starting a new game. I can generate and attach logs if someone else hasn't already.
I'm also hitting this, logs appear to indicate an issue with a semaphore in vkd3d.
How do you figure? Just curious. I haven't looked under the vkd3d hood yet.
I eventually hit this log line
211167.632:0134:0218:err:vkd3d-proton:dxgi_vk_swap_chain_present_signal_blit_semaphore: Failed to submit present discard, vr = -4.
Is anyone on an AMD card and have it not working?
im on a radeon 6600 and game doesnt crash on launch or when starting a new game but at some point before i enter the tunnel. i also have shader pre caching off if that affects it since its related to shaders. am on experiemental
Is anyone on an AMD card and have it not working?
Yep, 5950X + 6950XT, hanging shortly after E for New Game. Same report as OP, tried on both 8.0.3 and experimental.
Getting basically the same as everyone else but I also tried loading up a cloud save generated on windows, that also crashes during the load screen. Looks like similar d3d12 errors but possibly some different trace dumps before the crash proton-experimental-x11-cloud-save.log proton-experimental-x11-new-game.log
managed to make it a bit farther than was able to before with experimental on the bleeding edge branch. on the loading screen when you first start the game i also saw a progress bar about something to do with shaders that i didnt see before so maybe they changed something to fix it, but am not far enough to say for certain that i just havent gotten lucky to make it this far yet so will continue playing to see
Looks like we segfault on the game side:
* thread #45, name = 'CreationRendere', stop reason = signal SIGSEGV: invalid address (fault address: 0x10)
* frame #0: 0x00000001caf0c506
frame #1: 0x0000000000090200
Have Ubuntu 22.04 and RTX 2060. Game freezes after clicking start new game and needs to be killed.
My investigations so far from reading proton logs and trying other DX12 games...
https://pastebin.com/rRJJF4bn - proton log starting the game with no command vars
When it initializes both main and chipset GPUs it finds both but for some reason decides to "DXGI: Hiding actual GPU" and after this it begins to spam dx12 function errors endlessly , ie
warn:vkd3d-proton:d3d12_device_QueryInterface: {0742a90b-c387-483f-b946-30a7e4e61458} not implemented, returning E_NOINTERFACE
So it seems to me, the nvidia GPU is considered invalid and hidden for some reason. Other DX12 games tested work fine (deep rock galactic) All drivers updated and latest. (proprietry nvidia 535.86) tried proton experimental, proton-ge 8.13
managed to make it a bit farther than was able to before with experimental on the bleeding edge branch. on the loading screen when you first start the game i also saw a progress bar about something to do with shaders that i didnt see before so maybe they changed something to fix it, but am not far enough to say for certain that i just havent gotten lucky to make it this far yet so will continue playing to see
@kimgconnor This didn't work for me. It still crashed just after starting a new game.
managed to make it a bit farther than was able to before with experimental on the bleeding edge branch. on the loading screen when you first start the game i also saw a progress bar about something to do with shaders that i didnt see before so maybe they changed something to fix it, but am not far enough to say for certain that i just havent gotten lucky to make it this far yet so will continue playing to see
@kimgconnor This didn't work for me. It still crashed just after starting a new game.
@benbot do you have shader precaching on? and did you see the progress bar related to shaders ingame while it was loading before the main menu?
@benbot do you have shader precaching on? and did you see the progress bar related to shaders ingame while it was loading before the main menu?
I"ve tried this with both shader pre-caching on and off but result is the same either way. Someone said they got it to work with Proton Hotfix but this has yielded the same results in my case.
@benbot do you have shader precaching on? and did you see the progress bar related to shaders ingame while it was loading before the main menu?
I"ve tried this with both shader pre-caching on and off but result is the same either way. Someone said they got it to work with Proton Hotfix but this has yielded the same results in my case.
@Alpha-Obeisance i unfortunately dont have the knowledge to help much more, but i can still be here incase a working version helps any. also do you have nvidia or amd gpu incase it happens to be seperate issues for them, cause if both me and the guy who had it working with hotfix are amd (which if you know if they are can you lmk) and if you are nvidia since benbot is also on nvidia it could be a sign of seperate issues (or i could just be wrong about all of this due to my lack of knowledge)?
Game is rock solid stable for me thus far. Fedora 38 + rawhide kernel (6.5) + mesa-git (23.3.0-devel) + Proton Experimental
Max settings at 1440P has yielded 70-130 FPS (no FSR) in my 1.5 hours of playtime. 5800X3D 7900XTX
Game is rock solid stable for me thus far. Fedora 38 + rawhide kernel (6.5) + mesa-git (23.3.0-devel) + Proton Experimental
Max settings at 1440P has yielded 70-130 FPS (no FSR) in my 1.5 hours of playtime. 5800X3D 7900XTX
So it seems it's something to do with nvidia and vkd3d?
Edit: guess not? Guess you have to be running the latest of everything to get it running properly
So it seems it's something to do with nvidia and vkd3d?
Edit: guess not? Guess you have to be running the latest of everything to get it running properly
that meaning you got it to work on nvidia? if so what things did you have to update?