The game doesn't launch before the 20th it seems. How are you running it?

The game doesn't launch before the 20th it seems. How are you running it?

I have access to a press build. I don't know how it differs from the final retail version though, maybe the version accessible to all next week will work fine.

I haven't been able to reproduce that assert on basically the same setup. I did run into compiler segfaults inside the NV driver instead though. Reported that bug. I'm not sure I tested the same build as you though.

Can you try Proton Experimental at least? Maybe the issue has been fixed there.

Nope, same thing. Maybe there is something with the press build that Proton doesn't like, we'll know for sure in a few days, after all the demo was playable.

Even if the bug magically disappears on retail build, it's still valuable to fix the root bug in case it comes up again.

Would it be possible for you to create a proton log with:

• First mkdir /tmp/shaders
• VKD3D_DEBUG=info VKD3D_SHADER_DEBUG=info VKD3D_SHADER_DUMP_PATH=/tmp/shaders %command

then I should be able to tell if you're seeing different shader hashes than me.

Done. I got 14000+ files for a total of 650 MB 😅 Where do you want me to upload them ?

I don't really care where as long as it's not in public. You can email me a link. Email is in my profile.

Done.

https://github.com/HansKristian-Work/vkd3d-proton/pull/2474 should fix the bug. It's merged on master now.

That's amazing, thank you ! Anything I should do on my side to try and see if there is any improvement ?

https://github.com/HansKristian-Work/vkd3d-proton/actions/runs/15068985928 build should work.

So I replaced the 2x .dll in the vkd3d-proton lib & lib64 folders of Proton 9.0 (Beta), but unfortunately it didn't change much. The game starts, I get the black screen with the "loading" pic at the bottom right, and it crashes immediately.

Do you have a PROTON_LOG? It's probably the NV compiler bug now.

Sure, there you go.

steam-2104890.log

Please note that is not always the exact same behavior : sometimes it crashes with the "loading" pic on screen, sometimes without, and sometimes it freezes on a black screen and I have to Alt+F4 out of it. This is a log of a "loading pic + crash to desktop" situation.

You're still loading the wrong d3d12core dll here. Maybe just wait for bleeding edge to update with the new build.

Nevermind, I put the .dll in the wrong folder...

So now the game starts, I get the various logos and it will go up to the shader precomp phase, but I also get this error window pop-up.

That's probably the NV bug in question. I found a pyroveil hack for it, but that'll need to wait for retail build since the shader hashes seem to change.

Ok, to be continued next week then.

In any case, thank you very much for your help.

Added a pyroveil hack for now while we wait for driver to be fixed: https://github.com/HansKristian-Work/pyroveil/blob/master/hacks/roadcraft-nvidia-570-stable/pyroveil.json

Thanks, I'll try first the final version when it releases later today, in case it fixes the issue by magic, and orherwise I'll try the pyroveil hack. Will it work with 575 beta drivers ?

The pyroveil hack seems to be needed on 575 beta drivers too.

Now is retail version is out and still the same error

Did you try the pyroveil hack? There is no other fix for NV until they fix the driver.

The pyroveil hack does not seem to work for me at least. I get the above error regardless.

I have the same exact error as well.

GPU: GeForce RTX 3070 ti
Video driver version: 570.133.07
Kernel version: 6.11.0-26-generic

Did you try the pyroveil hack? There is no other fix for NV until they fix the driver.

Retail works correctly (5080, 570.144) with the hack. Thank you. 👍

Same shit here
OS: CachyOS
KERNEL: 6.14.7-5-cachyos
CPU: Intel Core i9-14900KF
GPU: NVIDIA GeForce RTX 4070 Ti SUPER
GPU DRIVER: NVIDIA 570.153.02
RAM: 64 GB

Did you try the pyroveil hack? There is no other fix for NV until they fix the driver.

Hack works fine for me. Drivers version 550.144.03 and Proton Experimental

Amazing, pyroveil hack works! For anyone having issues, these launch options worked for me:

PROTON_LOG=1 PYROVEIL=1 PYROVEIL_CONFIG=[path prefix on my local machine]/pyroveil/hacks/roadcraft-nvidia-570-stable/pyroveil.json %command%

Amazing, pyroveil hack works! For anyone having issues, these launch options worked for me:

PROTON_LOG=1 PYROVEIL=1 PYROVEIL_CONFIG=[path prefix on my local machine]/pyroveil/hacks/roadcraft-nvidia-570-stable/pyroveil.json %command%

dude, thank you. Got it working now too

EDIT2: These are cross-platform bugs. I resolved the flashing green artifact by changing DLSS from quality to balanced. I resolved the blurry textures by performing a complete reboot.

EDIT: This might just be a Roadcraft issue... I did play the demo and don't remember having this issue though.

This did get the game to launch for me! However, some textures are not loading properly, looks to be mostly the road textures and vehicle textures. Screenshots below. There is also a flashing green artifact in the top right that I couldn't capture in a screenshot. Let me know if I can include any other logs or information.

System info:

Operating System: Kubuntu 25.04
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.3
Kernel Version: 6.14.0-15-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700K
Memory: 94.1 GiB of RAM
Graphics Processor 1: NVIDIA GeForce RTX 3080 Ti
Graphics Processor 2: Intel® UHD Graphics 770
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B760M C
System Version: -CF

I confirm it works fine with the Pyroveil hack, thank you very much Hans-Kristian.

Pyroveil also works on NixOS. I built using a flake, and copied the result/share from nix build into ~/.local/share

can provide flake file if needed.

Amazing, pyroveil hack works! For anyone having issues, these launch options worked for me:

PROTON_LOG=1 PYROVEIL=1 PYROVEIL_CONFIG=[path prefix on my local machine]/pyroveil/hacks/roadcraft-nvidia-570-stable/pyroveil.json %command%

This worked for me, the error stopped, but now the game gets stuck "Precreating Shaders" on the bottom right before even loading into the main menu. Anyone else have this issue?

i have the same error as the Nvidia bois, but im on a intel arc A770
pops up around 7 of those errors while trying to load, but it just never finishes "Precreating Shaders"
trying the XE driver over the i915, il report back

ive now tried the XE driver no change still broken.
works on amd tho out of the box for me.

hack worked for me as well. Thanks so much!

OS: Debian 12
KERNEL: 6.1.0-35-amd64
CPU: AMD 5800X
GPU: NVIDIA GeForce RTX 3080
GPU DRIVER: NVIDIA 570.153.02
RAM: 64 GB

It works with pyroveil hack!

It finally worked. had to launch the game 4 times before it didn't crash due to a vulkan issue.

This is great, except proton_log grows at about 150MB/min, meaning that the game is slowed down by the raw data that has to be parsed, rendered and logged to file.

My log file is ~4~ ~6~ 10 GB so far, and I have not reached the main menu.

The workaround does not work if PROTON_LOG is off.

@HansKristian-Work is there any way to enable PYROVEIL without proton_log clogging up IO and CPU cycles?

This worked for me, the error stopped, but now the game gets stuck "Precreating Shaders" on the bottom right before even loading into the main menu. Anyone else have this issue?

This is where I'm at as well. proton log is stuck printing the following on repeat:

2158.845:0134:02a4:warn:seh:dwarf_virtual_unwind backtrace: 0x7ff21ec46850: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0x126850.
2158.845:0134:02a4:trace:unwind:execute_cfa_instructions 7ff21ec46845: DW_CFA_def_cfa %rsp, 8
2158.845:0134:02a4:trace:unwind:execute_cfa_instructions 7ff21ec46845: DW_CFA_offset %rip, -8
2158.845:0134:02a4:trace:unwind:dwarf_virtual_unwind fde 0x7ff21ed235e0 len 10 personality (nil) lsda (nil) code 7ff21ec46845-7ff21ec4685a
2158.845:0134:02a4:trace:unwind:execute_cfa_instructions 7ff21ec46845: DW_CFA_undefined %rip
2158.845:0134:02a4:trace:unwind:dwarf_virtual_unwind next function rip=00007ff21ec46850
2158.845:0134:02a4:trace:unwind:dwarf_virtual_unwind   rax=00007ff0c94de000 rbx=00000001000ff820 rcx=00007ff0c94de018 rdx=0000000000000000
2158.845:0134:02a4:trace:unwind:dwarf_virtual_unwind   rsi=00007ff0c94dde38 rdi=00007ff0c94d30c8 rbp=0000000000000000 rsp=00000001057b20e8
2158.845:0134:02a4:trace:unwind:dwarf_virtual_unwind    r8=0000000000000198  r9=fffffffffffffff8 r10=0000000000000003 r11=7d320baff4319a1c
2158.845:0134:02a4:trace:unwind:dwarf_virtual_unwind   r12=00000001048ff640 r13=000000000000000b r14=00007ff21ebb47d0 r15=00000001000ff980
2158.845:0134:02a4:trace:unwind:dwarf_virtual_unwind function 7ff21ec46850 base 0x7ff21ec46845 cie 0x7ff21ed0af20 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip

@HansKristian-Work is there any way to enable PYROVEIL without proton_log clogging up IO and CPU cycles?

Pretty sure you can just have the launch options for Pyroveil without the PROTON_LOG=1 launch option.

I've been playing with the PYROVEIL fix for around 10 hours and it works well. However sometimes, the audio cuts out.
systemctl --user status pipewire
returns a bunch of
May 21 20:17:41 mysystem pipewire[3499]: spa.audioconvert: 0x579b183e58f0: (0 suppressed) out of buffers on port 0 2.
Not sure if this is Proton-related? Only happens in Roadcraft so far.

@HansKristian-Work is there any way to enable PYROVEIL without proton_log clogging up IO and CPU cycles?

Pretty sure you can just have the launch options for Pyroveil without the PROTON_LOG=1 launch option.

Odd- The fix doesn't work for me w/o the log option present

I put pyroveil launch options but the game still say precreating caching shaders and it stuck

I put pyroveil launch options but the game still say precreating caching shaders and it stuck

Does your log file indicate pyroveil is working?

Unfortunately today's patch of the game broke the Pyroveil hack, and we're back to square one.

The hack was updated earlier today.

Damn man, you work FAST. I confirm the updated hack works with the 1.5 patch.

Play for at least 30 minutes

Can you idle on main menu screen to reproduce this, or do you have to do specific things in-game?

I didn't try to idle on the main menu, to be honest, and noticed it only while playing. I can try to leave the game on the main menu, I'll let you know what happens.

Ok so I confirm that the issue doesn't happen on the main menu, the GPU stays at 98% and the framerate is stable, even for an extended period of time. But when I started playing, in under half an hour I was back to ~60% GPU utilization and low framerate.

I'm having the same performance decrease over time issue. Maybe not quite the same gpu utilization decrease that @ZazaLeNounours is seeing, but its still there. Its late, I can figure out how to generate the full system report by this weekend at the latest.

GPU: Nvidia GeForce RTX 3080 10gb
Video driver version: 575.51.02
Kernel version: 6.14.7-arch2-1
Link to full system information report as Gist: Its late, I can figure out how to generate the full system report by this weekend at the latest.
Proton version: Experimental, I'll try with the 10.1 beta this weekend as well.

Please let me know what other info you want from me.

Those affected by reduced performance after a while, can you check if setting the game's launch parameter to the following prevents the issue from happening? LD_PRELOAD="" %command%

Should I add it before or after the Pyroveil parameter ?

@ZazaLeNounours order between PYROVEIL and LD_PRELOAD shouldn't matter, just make sure that %command% is placed last

Tried adding LD_PRELOAD="" before the whole Pyroveil line, it didn't change anything, I still ended up at ~60% GPU utilization.

LD_PRELOAD="" didn't change the performance decay at all. The only noticeable change is that it broke the steam overlay.

EDIT2: it stopped working again. Nothing changed on my end though.

EDIT: it works now! I found the fix in a Steam forum post (of all places...): lauch Roadcraft without the pyroveil launch arguments once (it will fail of course). Put the arguments back in. Lauch it again - it'll work. No idea why, I did not reinstall pyroveil in between, it was already up to date.

The game stopped working for me after the update even though I updated pyroveil before updating the game through Steam. The clickable error report is empty and the Steam log shows nothing unusual as far as I can tell. Pyroveil is working:

pyroveil: Found config in /home/pflavio/Games/Steam/pyroveil/hacks/roadcraft-nvidia-570-stable/pyroveil.json!
pyroveil: Adding match for OpString: 4935cbe43b8f9458.
pyroveil: Adding GLSL roundtrip via SPIRV-Cross for match.

Also, it does not shows the "assertion failed" screen this time, only the one below.

So I tried many times using different Proton versions (including GE) but I can#t get it to work. Here's the log if anyone would like to take a look.
steam-2104890.log

That's probably the NV bug in question. I found a pyroveil hack for it, but that'll need to wait for retail build since the shader hashes seem to change.

@HansKristian-Work How did you go about diagnosing the vkCreateGraphicsPipelines issue and also how it could be worked around with pyroveil in this instance? I'm hoping one of us can potentially keep this working to avoid burdening you in the future.

I was able to update the Pyroveil hack and it works for me on a 5070ti. PR is available here: https://github.com/HansKristian-Work/pyroveil/pull/16

Mine is crashing during gaming, not during logo or compiling shaders

@Anakins all issues for a given game go to the same thread.

I've tried to repro this issue on my 9060xt but the game hasn't crashed for me. You should upload the whole log, which will likely require compressing them first. Outside that, the issue might only happen in certain maps and/or at certain graphic configurations so try to provide as much information as you can about these.

@Anakins all issues for a given game go to the same thread.

I've tried to repro this issue on my 9060xt but the game hasn't crashed for me. You should upload the whole log, which will likely require compressing them first. Outside that, the issue might only happen in certain maps and/or at certain graphic configurations so try to provide as much information as you can about these.

Thanks.
I have uninstalled and installer again the game. And clean the folders in steam app. I have try 3 hours and for the moment, no issue. I will try again today and a lot this WE.

Hello, I play a lot this Week-End.
No crash !
Thanks

Glad to hear it

On Mon, Jul 28, 2025, 12:08 PM Anakins @.***> wrote:

Anakins left a comment (ValveSoftware/Proton#8694)
https://github.com/ValveSoftware/Proton/issues/8694#issuecomment-3127951377

Hello, I play a lot this Week-End.
No crash !
Thanks

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/8694#issuecomment-3127951377,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4ECSDGZ5IDQ7BVPGCMT3KZDGNAVCNFSM6AAAAAB5BTCTFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMRXHE2TCMZXG4
.
You are receiving this because you commented.Message ID:
@.***>

I'am disappointed.

After 2hours, it crashes...

https://limewire.com/d/1n2Cu#NpqIX9UAAm

This is a file with Proton logs en vdk dumps

7573.132:0160:016c:trace:seh:GetPerformanceInfo (0000000012E5FD50, 104)
7573.233:0160:016c:trace:seh:GetPerformanceInfo (0000000012E5FD50, 104)
7573.334:0160:016c:trace:seh:GetPerformanceInfo (0000000012E5FD50, 104)
7573.390:0160:01c4:warn:seh:dispatch_exception backtrace: --- Exception 0xc0000005.
7573.390:0160:01c4:trace:seh:dispatch_exception code=c0000005 (EXCEPTION_ACCESS_VIOLATION) flags=0 addr=0000000142848778
7573.390:0160:01c4:trace:seh:dispatch_exception info[0]=0000000000000001
7573.390:0160:01c4:trace:seh:dispatch_exception info[1]=0000000000000000
7573.390:0160:01c4:trace:seh:dispatch_exception rip=0000000142848778 rsp=000000002536db20 rbp=000000002536dbb9 eflags=00010206
7573.390:0160:01c4:trace:seh:dispatch_exception rax=0000000000000000 rbx=0000000000000000 rcx=0000000143b015b0 rdx=0000000000000080
7573.390:0160:01c4:trace:seh:dispatch_exception rsi=000000002536dba0 rdi=00000001458d7260 r8=0000000000151800 r9=000000003620f950
7573.390:0160:01c4:trace:seh:dispatch_exception r10=0000000000000008 r11=000000002536db18 r12=00000000ab001740 r13=0000000000000000
7573.390:0160:01c4:trace:seh:dispatch_exception r14=ffffffff9c5266e0 r15=0000000063ad9900 mxcsr=00001fbf
7573.390:0160:01c4:trace:seh:call_vectored_handlers calling handler at 0000000142849250 code=c0000005 flags=0
7573.390:0160:01c4:trace:seh:EnumProcessModulesEx (FFFFFFFFFFFFFFFF, 000000002536B100, 8192, 000000002536D130, 3)
7573.390:0160:01c4:trace:seh:EnumProcessModulesEx (FFFFFFFFFFFFFFFF, 000000002536B040, 8192, 000000002536D070, 3)
7573.438:0160:016c:trace:seh:GetPerformanceInfo (0000000012E5FD50, 104)

Are you monitoring the VRAM while you play ? I've noticed that the game is hungry for video memory, especially with the hi-res texture pack, it could be you just end up running out of it.

Hello, yes. it was the same without the 4k pack.
The VRAM usage is around 12 Gb only.

@Anakins in what map and with which graphics settings?

Hello,

Sandswept

Hello,

Yesterday after 30 minutes only, the game crashed as usual. Same graphic options.

Regards

https://limewire.com/d/aPgyT#K2h3H1QJUg

Sorry I haven't checked in a while, but last time I did I saw that the game
would show a crash dialog when closing the game on my desktop but only when
I'd reached in-game prior and quit from the game (vs using alt F4 or using
steam to close the game). However, that crash dialog doesn't appear if you
run the game with this as your launch parameter SteamDeck=1 %command%

While I wouldn't count on that preventing the game from crashing on your
end, I think it's worth trying to use it when you next play the game

On Thu, Aug 7, 2025, 1:30 AM Anakins @.***> wrote:

Anakins left a comment (ValveSoftware/Proton#8694)
https://github.com/ValveSoftware/Proton/issues/8694#issuecomment-3162545833

Hello,

Yesterday after 30 minutes only, the game crashed as usual. Sames graphics
option.

Regards

https://limewire.com/d/aPgyT#K2h3H1QJUg

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/8694#issuecomment-3162545833,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4ECVIHH2BDXUSUA6E633MLP7DAVCNFSM6AAAAAB5BTCTFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNRSGU2DKOBTGM
.
You are receiving this because you commented.Message ID:
@.***>

@Anakins the issue should be fixed if you use proton experimental bleeding edge https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge

Thansk a lot ! I'm in hollidays. I will try in 15 days !

Thansk a lot ! I'm in hollidays. I will try in 15 days !

Could you please update your post? Let us know if the game works now.

could this be map or object dependent? havent noticed shadows popping in and I can see some shrub shadows in the distance

What kind of visual settings did you use? because this issue appears only if you are using some settings and the issue is not map dependent and verify if you have a direct sun on some trees:

• Display Resolution: 960x600 (not native Steam Deck resolution!)
• Render Resolution: Native
• Resolution Upscaling: TAA
• Sharpness: set to 1
• FPS Limit: 30 FPS
• Anisotropic Texture Filtering: 4x
• Texture Resolution: Medium
• Shadows: Low (The engine render very well low shadows)
• Screen Space Ambient Occlusion: Default
• Screen Space Reflections: Default
• Effects: Low
• Details: Low
• Volumetric Clouds: Low
• Volumetric Fog: Low

With this settings I get great visuals on Steam Deck OLED.
Shadows set to "low" doesn't affects distance if you want to try.

Here is the real problem:
The "Details" set to "low" previously didn't affect distance rendering, but now you need "high or ultra" to avoid and also it destroy the performance.

I don't know if is Proton related or Devs related...:) but previously with settings above, the shadow distance render was perfect

ps: I get this issue on the first map too, I tried to start a new save and in the middle of the map where many palms cast shadows and their shadows disappears very close to the camera...but you need the direct sun moment....

Look this new video created in photo mode with a preset for to obtain direct lighting on the first map

https://github.com/user-attachments/assets/e4f4bff1-aa00-4f6d-baa1-8ffeba50eb92

Thanks for the general direction of a repro spot, I was able to find the same place as the video you last shared. While I see shadows popping in and out there, I'm also getting them on windows with similar settings to yours (only resolution related settings are changed).

https://github.com/user-attachments/assets/128bcb34-aa8d-45f8-9a20-fa1e091f3809

Fantastic! I also opened a ticket to Focus Entertainment (the publisher), on focus together via bug report and also on the discord channel.
I don't know if this issue come from Proton layer compatibility or from devs.
I'm sure companies likes to know if a game run well on Proton for the Steam Machine future compatibility not only for Steam deck.

@masterzone3d just to avoid any confusion, that video is on windows, it still has the shadows pop in

@masterzone3d just to avoid any confusion, that video is on windows, it still has the shadows pop in

Oh, ok. Interesting. Thanks for your clarification 🫡