[REDACTED] Unreal Engine 4 Crash Reporter
AppImage, UMU enabled, Proton-GE latest, Steam Deck
89 Replies
stormy-goldOP•5mo ago
Vcrun2022 is installed
extended-salmon•5mo ago
maybe the brackets might be causing an issue with the wineprefix path
try removing the brackets from the wineprefix path
stormy-goldOP•5mo ago
No go
stormy-goldOP•5mo ago
extended-salmon•5mo ago
odd it worked fine for me
wait did u enable the EOS overlay
vicious-gold•5mo ago
just curious, why are you using appimage on the steamdeck? flatpak is recommended there
stormy-goldOP•5mo ago
Primarily HDR support, works on the flatpak but requires extra steps
I don't think this game has HDR so I can swap and see if that works
No EOS overlay isn't installed, let's see
EOS overlay installed, same crash, trying Flatpak
stormy-goldOP•5mo ago
This is flatpak, no brackets, EOS overlay installed
extended-salmon•5mo ago
could you run it with WINEDEBUG=+fixme, DXVK_LOG_LEVEL=info and VKD3D_DEBUG=fixme
and send a new log
stormy-goldOP•5mo ago
Yep one sec
extended-salmon•5mo ago
it enables logging with proton
stormy-goldOP•5mo ago
Those are each separate environment variables?
extended-salmon•5mo ago
yes
stormy-goldOP•5mo ago
extended-salmon•5mo ago
oooh it needs d3dcompiler_43 and d3dcompiler_47 as well @arieljuod
stormy-goldOP•5mo ago
Where does it say that?
extended-salmon•5mo ago
it's trying to access some property from the shader using d3dcompiler
and wine doesn't implement it
so it crashes
vicious-gold•5mo ago
hmmm the game worked fine for me without d3dcompiler, but I haven't tried on my steamdeck yet, I only needed vcrun
extended-salmon•5mo ago
I already had d3dcompiler, so I didn't realize
but according to this log it's needed
vicious-gold•5mo ago
I had a new clean prefix, but I can check if I get d3dcompiler errors too, wouldn't hurt to fix those messages even if the game is working for some people
extended-salmon•5mo ago
btw could you try installing it using winetricks
man with the number of games that require vcrun2022 on epic I think we should just start installing it automatically
stormy-goldOP•5mo ago
Sifu requires it as well
extended-salmon•5mo ago
yeah I just saw
stormy-goldOP•5mo ago
It installs 47 but not 43
Oh
There we go, took a few tries for whatever reason
extended-salmon•5mo ago
yeah winetricks is a little bit slow u have to be patient with it
stormy-goldOP•5mo ago
Ah gotcha, patience is not my strong suit
vicious-gold•5mo ago
weird, I don't have those errors, no idea why, but we can add d3dcompiler_47, I don't think it can create any issue
stormy-goldOP•5mo ago
It's still crashing with all 3 installed
stormy-goldOP•5mo ago
extended-salmon•5mo ago
could you send another log
stormy-goldOP•5mo ago
Yep
stormy-goldOP•5mo ago
vicious-gold•5mo ago
I'll try later on my steamdeck too
stormy-goldOP•5mo ago
No hurry, we're in the middle of a holiday anyway, appreciate y'all taking the time
vicious-gold•5mo ago
sifu prompts to install it when the game runs, there's no need to use a known fix for it
I mean, it doesn't show an error and stops, it shows the option to install it
extended-salmon•5mo ago
oops i already merged it 💀
stormy-goldOP•5mo ago
Sorry about that, didn't know best practices
extended-salmon•5mo ago
i guess one less popup is better
vicious-gold•5mo ago
the thing is, I think that from the way things work, the popup happens first
and then after the legendary setup runs we apply known fixes
so the popup will still show, and it will try to install vcrun2022 after probably already installing it through the EU requirements proces
extended-salmon•5mo ago
oh it runs it without the silent mode ?
vicious-gold•5mo ago
the game shows a wizard to install the c++ runtime, no silent
I think that if we change known fixes to run before the legendary setup then we would avoid the extra popup, but the way it works not it won't prevent that
extended-salmon•5mo ago
ok i created a PR to revert it
vicious-gold•5mo ago
(I don't know why we do it in that order, I'd rather have vcrun2022 always added in all prefixes before running the legendary setup)
extended-salmon•5mo ago
when I made it I thought it would be stuff like directx because epic games launcher installs vcrun anyway
but sifu has a vcrun setup process for some reason
i wonder if this game takes a steam deck specific code path and that causes it to crash
too bad i don't have one lol
stormy-goldOP•5mo ago
Another report on the subreddit, https://old.reddit.com/r/HeroicGamesLauncher/comments/1hqagnt/redacted_steamdeck_crashing/ so maybe?
extended-salmon•5mo ago
ill keep the revert PR open for now, instead of merging it btw
because it might be a good idea to change the order
frozen-sapphire•5mo ago
We got the same crash report with Junk Store from users as well as myself. All I did to resolve this was to change my Proton version from GE-Proton9.20 to GE-Proton9.7 (it's one I have used with great success before). The game then booted without issue. I tested it again with GE-Proton9.20 and it crashed again.
The only thing that I installed was C++ runtime as well.
Thought this might be of some help to you guys as well.
extended-salmon•5mo ago
i was using proton-ge 9-21
maybe that's the issue then
i think OP was also using proton-ge 9-20
frozen-sapphire•5mo ago
Yeah that's the only thing I changed to get it to work. And I tested with my default Proton version to verify that was my issue.
stormy-goldOP•5mo ago
I tried a couple earlier, I wasn't very consistent in the logs I uploaded. I tried 16, 19, 20, and 22 I think
I just tried 7 though and no go
frozen-sapphire•5mo ago
Hmmm I did also have to verify with my Epic account.
stormy-goldOP•5mo ago
I don't think I'm getting that far, it crashes on the very first screen
vicious-gold•5mo ago
I used 9-20 and worked fine for me
frozen-sapphire•5mo ago
Hmmmm interesting I tried multiple times with 9-20 and it kept crashing. Then I changed my version and it worked. Changed back to 9-20 crashed again a few times. Back to 9-7 and it worked. Strange....
Could it be a corrupted prefix? We've had a few users with corrupted prefixes in the last few days with some of these games. Once they deleted their prefix they were good to go.
stormy-goldOP•5mo ago
I've been deleting my prefixes when switching proton versions just in case
I don't get the crash reporter on 7 though
Just a straight crash
stormy-goldOP•5mo ago
stormy-goldOP•5mo ago
I don't know if the vulkan errors mean anything but the Steam Deck OLED has been plagued with vulkan bugs on emulators
extended-salmon•5mo ago
the vulkan driver is fine
it works well with dxvk and vkd3d-proton
should work with emulators too
some of them might be programmed a bit ... poorly ofc
automatic-azure•5mo ago
stupid question, but did you disable the readonly file system at some point? I spent days trying to troubleshoot some weird stuff with a user only to find out that they disabled it numerous times and it clearly caused some shenanigans....
just spitballing here... I think you've got a toughy on your hands here...
stormy-goldOP•5mo ago
No this is actually a pretty vanilla install, I did a factory reset in december for fun
automatic-azure•5mo ago
Just thought I'd ask, at least this eliminates a TON of potential issues
stormy-goldOP•5mo ago
Yeah makes sense, thank you both for popping in and helping out:)
automatic-azure•5mo ago
no worries, we can't sit back watching others suffer....
I don't have the internet bandwidth to download it on heroic (or the mental bandwidth at the moment, I'm supposed to be taking a break). If I was chasing this bug on my side I would have it installed in both my solution and Heoric, then compare what's going on to see why it's working in one and not the other. I'm not expecting the users to do this, but maybe some of the more adventurous staff here might be willing to look into this.
extended-salmon•5mo ago
i found it kinda wierd that it worked for me and ariel tho
maybe it has something to do with the steam deck who knows
stormy-goldOP•5mo ago
Isn't ariel on one too?
Or did I misread oops
extended-salmon•5mo ago
i think he said he was gonna test it soon
ig meanwhile
i can try in heroic flatpak
vicious-gold•5mo ago
just tested on my steamdeck, I can reproduce the issue using proton-ge9-22, but worked just fine with wine-ge-latest
extended-salmon•5mo ago
hmm something is very wrong
i can't actually play the game
it's wierd
pressing the play button doesn't do anything
vicious-gold•5mo ago
so proton-ge9-22 fails both with and without UMU on my steamdeck
wine-ge-latest seems to work fine, so I'd suggest testing that if an older proton-ge doesn't work @emotion
stormy-goldOP•5mo ago
I tried wine-ge earlier, how long does the prefix creation/dependency install take? I don't know how long I left it for but I thought it froze and restarted the deck
extended-salmon•5mo ago
a few seconds
vicious-gold•5mo ago
yeah it was pretty quick for me
stormy-goldOP•5mo ago
Ooh so 5ish minutes isn't the norm
extended-salmon•5mo ago
yeah wine-ge works
odd
proton broke something ?
stormy-goldOP•5mo ago
The only bug I see is controller related, https://github.com/ValveSoftware/Proton/issues/8209, might just be unreported though yeah
And someone using vanilla proton with success? https://old.reddit.com/r/SteamDeck/comments/1hq5m4e/redacted_via_heroic_launcher_no_controls/
vicious-gold•5mo ago
I tested with proton-ge9-5 and it opens for a bit, then closes, no error screen
stormy-goldOP•5mo ago
Is there a good way of killing this without restarting?
extended-salmon•5mo ago
yeah press win+ctrl+esc
and click on the window
stormy-goldOP•5mo ago
That kills heroic but not the prefix creation window
vicious-gold•5mo ago
so confusing, proton-ge9-5 without umu closes itself after a few seconds, but proton-ge9-5 with umu seems to work fine
extended-salmon•5mo ago
which window did u click ?
lol
stormy-goldOP•5mo ago
I'm a little sleep deprived, I'm using steam link and that opened the system monitor on my laptop so I just manually clicked heroic hah. I see what it's supposed to do now, whoops
vicious-gold•5mo ago
you can open the system monitor app, look for any wine or wineserver process, and kill it with that
extended-salmon•5mo ago
ok it just randomly doesn't work it seems
prob something to do with me alt tabbing
vicious-gold•5mo ago
tested with proton-ge 8-9 and it worked fine, so seems to be something with proton-ge 9
stock proton 9.0 worked fine
extended-salmon•5mo ago
ok the inputs are just finnicky for me
it works after some fiddling
stormy-goldOP•5mo ago
Yeah wine-ge 26 works
Hooray, thank you:)
Proton-GE bug then?
extended-salmon•5mo ago
hmm how come it works for me then
wierd
vicious-gold•5mo ago
proton-ge worked for me too on my desktop computer
it failed only on my steamdeck
so it's a combination of things I guess