Defense Grid directx11 issue
Issue transferred from https://github.com/ValveSoftware/Proton/issues/6147.
@pdanoe posted on 2022-09-11T16:51:56:
Not sure what is asked for here. The problem has remained even when I downgraded the xubuntu from 20 to 18. So much I can say.
For about the last 2 years, I have been unable to make proton install directx11 when initialising the game after install. Until 2 years ago, I was able to make proton install directx11 by downloading the game, changing to a higer proton version, run the game (for which the proton version was too high, but it managed to discover that it should install directx11), change to lower proton version e.g. 3:7-8. run the game again, and there it would install the needed directx11.
When there is no directx11, the game will simply show a white screen.
Hope this is information enough for now.
Defense grid is an older game by now, but would be nice to see it work again
Hello @pdanoe, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.
Thanks, looking at your system information, you have an Ivy Bridge generation Intel GPU. The video drivers for this generation of GPU provides an incomplete implementation of Vulkan, and rendering artifacts and crashes are expected with this hardware. Unfortunately, that makes your system unsupported by Proton in general.
Separately, the Snap environment which Steam is running inside isn't providing a 32 bit Vulkan render path. Report that issue to the maintainers of the snap package.
Looking at the Proton log, all that tells us is that Proton from about 3 years ago isn't particularly good at compiling HLSL shaders with err:d3dcompiler:compile_shader HLSL shader parsing failed. standing out the most in the log. my understanding is that Proton doesn't support downgrading from a newer version, so it has to reset the wineprefix for sanity.
Thanks kisak-valve for your effort.
I get it from your response that I could try to buy a computer with a little bit newer GPU. I am currently looking at a gen 7 (kaby lake).
I am not exactly sure how to do the reporting you request me to do. So until I maybe understand the issue, I may leave it undone.
regards, Peter
Kaby Lake is generation 7.5. This is a little bit older than Broadwell (generation 8), which is the oldest Intel GPU chipset that has a spec-compliant Vulkan implementation.
Sorry, I have no insight into the feedback options available to Snap users.
Defense Grid: The Awakening (18500)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/8544.
@JustinWayland posted on 2025-03-20T21:06:29:
Game crashes 5-10 seconds after opening.
Just open the game.
PROTON_USE_WINED3D=1 allows the game to get to the main menu but causes severe graphical artifacts in gameplay.
This suggests that the problem lies in DXVK.
@JustinWayland Could you try deleting your prefix (located by default at ~/.steam/steam/steamapps/compatdata/18500) to see if that helps anything? It seems like you might have gotten a funky install somehow and missed the DirectX redist install which should happen automatically for that game.
Where are the Proton prefixes on Linux again?
On Tue, Mar 25, 2025 at 10:46 PM alasky17 @.***> wrote:
@JustinWayland https://github.com/JustinWayland Could you try deleting
your prefix to see if that helps anything? It seems like you might have
gotten a funky install somehow and missed the DirectX redist install which
should happen automatically for that game.—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/669#issuecomment-2753101147,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4H5HUVITRSWCCD4EWGBLT2WIIIZAVCNFSM6AAAAABZOQ7BACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJTGEYDCMJUG4
.
You are receiving this because you were mentioned.Message ID:
@.***>
[image: alasky17]alasky17 left a comment (ValveSoftware/Proton#669)
https://github.com/ValveSoftware/Proton/issues/669#issuecomment-2753101147@JustinWayland https://github.com/JustinWayland Could you try deleting
your prefix to see if that helps anything? It seems like you might have
gotten a funky install somehow and missed the DirectX redist install which
should happen automatically for that game.—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/669#issuecomment-2753101147,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4H5HUVITRSWCCD4EWGBLT2WIIIZAVCNFSM6AAAAABZOQ7BACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJTGEYDCMJUG4
.
You are receiving this because you were mentioned.Message ID:
@.***>
@JustinWayland I edited my original comment when I realized I forgot to mention it - the default location is ~/.steam/steam/steamapps/compatdata/18500 for this game.
Deleting the prefix does not seem to have worked. It generated a log that according to diff is distinct from the last run, so I'm attaching it to this comment.
I would send you the compatdata folder directly, but it's 250MB in size.
Update: adding d3dcompiler_47 via Protontricks fixed the crash, and now everything works. The compatdata needs to be updated.
Actually, scratch that last one, now the in-game voice lines don't seem to work. The first one seems to get said, and then the rest are never said.
This can be most clearly seen in the last level of the campaign, where it can be compared to this video on an older version of Proton.
PROTON_USE_WINED3D=1```x1 2025-03PROTON_LOG=1x1 2022-09
Smooth as silk, with no flaws.
https://gist.github.com/nstgc/02457d7920931a3f8d69cc7b9fa41a2c
this was tested both with and without a controller.