Hello, I posted about this on Valve's Proton github page and they told me to mention this up here too, for some reason Raiden III Digital Edition crashes when trying to get in game with DXVK. Tested it out on Steam Deck and my Windows 11 laptop and the same issue seems to happen between both devices.
If you use Windows, please check the following page: https://github.com/doitsujin/dxvk/wiki/Windows
Raiden III: Digital Edition
I've been trying to get an Apitrace on windows and I can consistently get it to crash with the d3d9.dll from the 1.10.3 download, but when I try using the Apitrace version of the dll, it doesn't crash. Don't know if i'm doing something wrong or not.
For instructions on how to use apitrace, see: https://github.com/doitsujin/dxvk/wiki/Using-Apitrace
I've been trying to get an Apitrace on windows and I can consistently get it to crash with the d3d9.dll from the 1.10.3 download, but when I try using the Apitrace version of the dll, it doesn't crash. Don't know if i'm doing something wrong or not.
That is fine an expected. Apitrace doesn't go trough dxvk on windows by default. It's used to capture all api calls of the game, in this case native directx, and then the devs can replay it themselves with or without dxvk to see if anything stick out. So if you are able to make a trace to after the point where it usually crashes that would be great.
Alright then, made a trace log accordingly. It usually crashes as soon as you try to start a new game from what i've noticed. ProtonDB reports seem to vary on what was the last version that worked, some say it was 4.11-13 on Deck, others say it's 4.26 or 4.29. I can also say that it works fine when using wined3d too.
You mean it usually crashes before it gets to the part in the screenshot below right?
Yep, on my end it starts the screen transition (Futuristic gate closes on screen, covering it up for a little bit), then halfway I hear the sound stutter and stop, then it just silently exits on Deck and Windows.
Can confirm the crash in the actual game with ~~wined3d~~ (nvm, it works), dxvk and dxvk on windows. Mostly tested with dxvk on windows and i found that it's been crashing like that ever since d9vk 0.13 which is also the first version that could really display anything with the game. 0.12 doesn't crash but instead there are no visuals and the whole screen is just one big color like white, orange or green depending on scene. But i can hear from the music i get past the crash when i press start new game.
Haven't found any config options that change the outcome.
Surprised it's still crashing with wined3d, unless it's something with proton or Linux, since I was able to get the game working with it on deck.
Oh really? 🤔 I will have to try messing around with that again then
Edit: oh right you wrote that
All I know is with the Steam version on deck, I ran it with the latest Experimental build of Proton, set it to use "PROTON_USE_WINED3D=1 %command%" and somehow it got past the screen transition when starting a new game without issue, so I dunno if it's on protons end or wined3ds end.
Only thing keeping me from testing further is that... I'm not really that good at shmups.
Oh yea. It does work with wined3d :sweat_smile: Dunno why i thought it didn't. My bad :grin:
Made a couple of traces myself. One with dxvk so it crashes while tracing and one with wined3d where it doesn't so they can be compared.
https://mega.nz/file/doJgyDiC#c1tsSpOnraq5oMM65NYHGJPNRTvqryYlKUvPHitub9g
I can't reproduce the crash with the apitrace and I don't have the game.
Was it with the latest devbuild of dxvk? Dunno why it wouldn't be crashing on your end, but only crashing on my and Blistos devices
No i can only reproduce the crash in the actual game. The trace is fine for me too
Oooohhhhhh, yeah I wonder what dxvk is doing then that the apitrace isn't picking up?
