Open kisak-valve opened 4 years ago
poperigby
commented
4 years ago I'm getting a hard crash that seems to happen after 30 minutes or so. Here's the log file: https://send.firefox.com/download/945b855f1dd20e0d/#dP9yXbTc4PGFlF5mkZL1EQ
I have a RX 5700XT and am using ArchLinux with RADV.
kisak-valve
commented
4 years ago Hello @PopeRigby, 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.
As a side note, Proton logs are known to compress well, please consider throwing large logs into an archive.
poperigby
commented
4 years ago Here's the system information gist: https://gist.github.com/PopeRigby/263d2b99e3998f99fdf4e0d222845843
jjbarr
commented
4 years ago So does ACO work on Mesa 20.1 now? Last I heard ACO was not working.
silviucc
commented
4 years ago Is it still true that enabling the overlay causes performance issues?
My own experience shows the opposite: https://forums.developer.nvidia.com/t/low-performance-in-doom-eternal/116394/30?u=silviu_c
btegs
commented
4 years ago @kisak-valve - You made a comment in the other thread about removing libvulkan1 in Ubuntu, which is a BIG NO NO as it will nuke your system. Is there a better way in having the vulkan included with Steam runtime take priority over the system one?
``` teg@pop-os:~$ sudo apt remove libvulkan1 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: cabextract efibootmgr evolution-data-server-common filezilla-common firmware-manager-notify firmware-manager-shared fonts-wine fprintd fuseiso gir1.2-accountsservice-1.0 gir1.2-appindicator3-0.1 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdm-1.0 gir1.2-gnomebluetooth-1.0 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-upowerglib-1.0 gkbd-capplet glade2script gnome-session-common gnome-shell-extension-system76-power gstreamer1.0-pulseaudio gtk2-engines-murrine gvfs-libs i965-va-driver intel-media-va-driver libaacs0 libaom0 libasound2-dev libass9 libavcodec58 libavfilter7 libavformat58 libavresample4 libavutil56 libbdplus0 libblkid-dev libbluray2 libbs2b0 libcamel-1.2-62 libcapi20-3 libcapnp-0.7.0 libcdio-cdda2 libcdio-paranoia2 libcdio18 libchromaprint1 libcodec2-0.8.1 libcue2 libdazzle-1.0-0 libdbus-1-dev libdc1394-22 libdvdnav4 libdvdread4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libexiv2-14 libfftw3-double3 libfilezilla0 libfirmware-manager libflite1 libfontenc1 libfprint0 libgdm1 libgexiv2-2 libgif7 libgles1 libglib2.0-dev libglib2.0-dev-bin libgme0 libgnome-autoar-0-0 libgnomekbd-common libgnomekbd8 libgsf-1-114 libgsf-1-common libgsm1 libgsoap-2.8.75 libibus-1.0-dev libigdgmm11 libjavascriptcoregtk-4.0-18 libldb1 liblilv-0-0 libmikmod3 libmirclient-dev libmirclient9 libmircommon-dev libmircommon7 libmircookie-dev libmircookie2 libmircore-dev libmircore1 libmirprotobuf3 libmount-dev libmspack0 libmtp-common libmtp-runtime libmtp9 libmysofa0 libnfs12 libnorm1 libodbc1 libopenal1 libopengl-dev libopengl0 libopenjp2-7 libopenmpt0 libosmesa6 libpam-fprintd libpcre16-3 libpcre2-32-0 libpcre2-dev libpcre2-posix0 libpcre3-dev libpcre32-3 libpgm-5.2-0 libphonenumber7 libpop-theme-switcher libpop-upgrade-gtk libpostproc55 libprotobuf-dev libprotobuf-lite17 libpugixml1v5 libpulse-dev libqt5positioning5 libqt5qml5 libqt5sensors5 libqt5webchannel5 librubberband2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libs76-hidpi-widget libsdl-net1.2 libsdl-sound1.2 libsdl1.2debian libselinux1-dev libsepol1-dev libserd-0-0 libshine3 libsmbclient libsndio-dev libsord-0-0 libsratom-0-0 libssh-gcrypt-4 libswresample3 libswscale5 libtalloc2 libtevent0 libtracker-control-2.0-0 libtracker-miner-2.0-0 libudev-dev libva-drm2 libva-wayland2 libva-x11-2 libva2 libvidstab1.1 libvncserver1 libwayland-bin libwayland-dev libwbclient0 libwebpdemux2 libwoff1 libwxbase3.0-0v5 libx264-155 libx265-176 libxatracker2 libxcb-glx0 libxcb-res0 libxcb-xv0 libxcursor-dev libxfixes-dev libxfont2 libxi-dev libxinerama-dev libxkbcommon-dev libxkbfile1 libxklavier16 libxrandr-dev libxv-dev libxvidcore4 libxvmc1 libxxf86dga1 libxxf86vm-dev libzmq5 libzvbi-common libzvbi0 mesa-va-drivers nautilus-data pastebinit pop-fonts pop-gnome-shell-theme pop-gtk-theme pop-icon-theme pop-sound-theme pop-theme python3-pyxattr python3-talloc rtmpdump rygel samba-libs switcheroo-control syslinux-common system76-power tracker tracker-extract tracker-miner-fs va-driver-all virtualbox-dkms x11-apps x11-session-utils x11-xkb-utils x11proto-fixes-dev x11proto-randr-dev x11proto-xf86vidmode-dev x11proto-xinerama-dev xbitmaps xfonts-base xfonts-encodings xfonts-scalable xfonts-utils xinit xinput xserver-common xserver-xorg-legacy yelp-xsl youtube-dl zenity-common Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libqt5gui5-gles Suggested packages: qt5-image-formats-plugins qtwayland5 Recommended packages: libqt5svg5 The following packages will be REMOVED: boot-repair boot-sav boot-sav-extra chrome-gnome-shell com.github.tkashkin.gamehub dosbox evolution-data-server ffmpeg filezilla gdm3 ghostwriter gir1.2-mutter-5 gnome-calendar gnome-control-center gnome-getting-started-docs gnome-getting-started-docs-de gnome-getting-started-docs-es gnome-getting-started-docs-fr gnome-getting-started-docs-it gnome-getting-started-docs-ja gnome-getting-started-docs-pt gnome-getting-started-docs-ru gnome-getting-started-docs-zh-hk gnome-getting-started-docs-zh-tw gnome-mpv gnome-online-accounts gnome-session-bin gnome-shell gnome-shell-extension-alt-tab-raise-first-window gnome-shell-extension-always-show-workspaces gnome-shell-extension-desktop-icons gnome-shell-extension-do-not-disturb gnome-shell-extension-pop-battery-icon-fix gnome-shell-extension-pop-shop-details gnome-shell-extension-pop-suspend-button gnome-startup-applications gnome-user-docs gnome-user-docs-de gnome-user-docs-es gnome-user-docs-fr gnome-user-docs-it gnome-user-docs-ja gnome-user-docs-pt gnome-user-docs-ru gnome-user-docs-zh-hans gstreamer1.0-clutter-3.0 gstreamer1.0-gl gvfs gvfs-backends gvfs-daemons gvfs-fuse libavdevice58 libcheese-gtk25 libcheese8 libclutter-1.0-0 libclutter-gst-3.0-0 libclutter-gtk-1.0-0 libcogl-pango20 libcogl-path20 libcogl20 libedataserverui-1.2-2 libegl-dev libegl1-mesa-dev libfolks-eds25 libgl-dev libgl1 libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libgles-dev libgles2-mesa-dev libglu1-mesa libglu1-mesa-dev libglvnd-dev libglx-dev libglx-mesa0 libglx0 libgoa-backend-1.0-1 libgstreamer-gl1.0-0 libmpv1 libmutter-5-0 libqt5gui5 libqt5opengl5 libqt5printsupport5 libqt5quick5 libqt5svg5 libqt5webkit5 libqt5widgets5 libsdl2-dev libvdpau-va-gl1 libvkd3d1 libvulkan1 libwebkit2gtk-4.0-37 libwine libwxgtk3.0-0v5 libyelp0 mesa-vulkan-drivers mpv mutter nautilus phantomjs pop-default-settings pop-session qsynth ubuntu-docs virtualbox virtualbox-qt wine wine64 winetricks x11-utils xorg xserver-xephyr xserver-xorg xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-input-wacom xserver-xorg-video-all xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-nouveau xserver-xorg-video-qxl xserver-xorg-video-radeon xserver-xorg-video-vesa xserver-xorg-video-vmware xwayland yelp zenity The following NEW packages will be installed: libqt5gui5-gles 0 upgraded, 1 newly installed, 131 to remove and 0 not upgraded. ```
kisak-valve
commented
4 years ago @btegs, where was this comment made?
dpanter
commented
4 years ago a comment in the other thread about removing libvulkan1 in Ubuntu
@btegs, you should re-read that comment. Kisak didn't say remove, he said re-add.
btegs
commented
4 years ago a comment in the other thread about removing libvulkan1 in Ubuntu
@btegs, you should re-read that comment. Kisak didn't say remove, he said re-add.
I was referencing https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-613766116 where re-adding libvulkan1 on Ubuntu 19.10 via apt would just re-install v1.1.114.
So if you leave that as the main libvulkan1 at a system level and remove pinnedlibs* from the steam install, how does this automatically make your AMD drivers under MESA use the libvulkan from Steam and not your system?
kisak-valve
commented
4 years ago @btegs, removing the pinnedlibs* folders prompts Steam to regenerate those folders the next time Steam is started (this is literally what I said previously). The folder's contents is the result of comparing the system libraries to the Steam runtime variants and pinning the Steam runtime variant if it is newer than the host system.
Steam prioritizes libraries in the following order: Pinned libraries > Host system > Steam runtime > ld.so.conf
btegs
commented
4 years ago @btegs, removing the pinnedlibs* folders prompts Steam to regenerate those folders the next time Steam is started (this is literally what I said previously). The folder's contents is the result of comparing the system libraries to the Steam runtime variants and pinning the Steam runtime variant if it is newer than the host system.
Steam prioritizes libraries in the following order: Pinned libraries > Host system > Steam runtime > ld.so.conf
Deleted those folders and were recreated once starting Steam. I checked the directory and they were symlinking to a 1.2.135 version of Vulkan. cool.
Then I load up a random game with Proton 5.0-6 with the DXVK hud set to 1 under Ubuntu 19.10. It shows up as Mesa 20.0.99 (using the bleeding edge git version from https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers for my RX 580. Shows Vulkan 1.2.128 for my Vulkan version. I obviously cannot start DOOM Eternal either.
What is going on and what steps are missing?
NOTE: I found an Ubuntu repo at https://packages.lunarg.com/ which gives me an updated libvulkan1 and libvulkan1:i386 without affecting my current Mesa. 1.2.135 is installed, but whenever I try a game on Steam or using GameHub with a GOG game, it is still at 1.2.128. I have no clue where this version of Vulkan is coming from!
tyqualters
commented
4 years ago "Alt-Tab may break the game rendering."
Arch Linux with KDE Plasma, can confirm Alt-Tabbing broke game rendering, but it also resulted in unresponsiveness to the close procedure by right clicking the process in the task bar and clicking the "Close" button..
sudo kill -SIGHUP 31117 did close the game though
System Information: https://pastebin.com/1z80Y7WG
poperigby
commented
4 years ago My hard crash seems to be happening after about 20 minutes every time I start the game. Maybe I could time it to check.
Emanem
commented
4 years ago Adding bugs (perhaps obvious/already known):
DarkArc
commented
4 years ago This game is also seems to be affected by https://github.com/ValveSoftware/Proton/issues/2927
If you're having problems, and you have a Ryzen 3xxx processor, try the workaround there ^
kisak-valve
commented
4 years ago Doom Eternal Monitor/Resolution fail
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3797. @Kalevr1 posted on 2020-04-24T23:18:50:
After installing latest SteamPlay Proton 5.06 I got one perfect play session that lasted several hours. I took a break to eat and then came back to continue play. I have a 2 monitor setup. When I tried to launch the game a second time, it switched to a small window on the the secondary monitor. The lower monitor is my default screen and sits at eye level. I can see the upper left corner of the Doom Intro being rendered within the quarter-sized window on the secondary monitor. The game engine thinks it is rendering on the entire screen but I only see the portion that overlaps the window. I can see 2 buttons in the UI and I can interact with them. I Alt-F4 to exit.
Seems fixable if I can manually force the monitor and resolution for the app but I don't know if that would work. One workaround I have found is if I delete ../steamapps/compatdata/782330 the game does 'first run' again, which always runs perfectly.
I have included a screenshot of both monitors (1920x2160 pixels). Steam is fullscreen below on primary and you see the Doom Window above on the secondary.
@Kalevr1 commented on 2020-04-24T23:21:15:
This is my first post so I hope it is correct starting a new report rather than attaching to another. If not apologies.
iddm
commented
4 years ago I've been trying to use the 5.06 proton and 5.6 GE, the game very often crashes on both of these.
Here is the Proton GE 5.6 crash log Here is the Proton 5.06 crash log
iddm
commented
4 years ago I've been trying to use the 5.06 proton and 5.6 GE, the game very often crashes on both of these.
Here is the Proton GE 5.6 crash log Here is the Proton 5.06 crash log
Guess my problem is solved. I guess, this problem was caused by an AVX instability on my processor. I had overclocked my processor but hadn't checked the overclocking stability with AVX2. I had to add an AVX offset for my CPU in bios in order to pass the "Small FFTs" tests in Prime95 with AVX2 in Windows and confirm the same stability using the stress utility on my archlinux. Once I did that, I have never seen any crashes anymore. My first guess was about the RAM instability (I also overclocked it), but having turned XMP off and on, untightened timings and frequencies, I was able to confirm that it was not a ram issue.
BloodyIron
commented
4 years ago I'm effectively in the identical scenario, same versions, cannot figure out how to get DOOM Eternal not to crash on start. :(
Did you get this figured out @btegs ?
@btegs, removing the pinnedlibs* folders prompts Steam to regenerate those folders the next time Steam is started (this is literally what I said previously). The folder's contents is the result of comparing the system libraries to the Steam runtime variants and pinning the Steam runtime variant if it is newer than the host system. Steam prioritizes libraries in the following order: Pinned libraries > Host system > Steam runtime > ld.so.conf
Deleted those folders and were recreated once starting Steam. I checked the directory and they were symlinking to a 1.2.135 version of Vulkan. cool.
Then I load up a random game with Proton 5.0-6 with the DXVK hud set to 1 under Ubuntu 19.10. It shows up as Mesa 20.0.99 (using the bleeding edge git version from https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers for my RX 580. Shows Vulkan 1.2.128 for my Vulkan version. I obviously cannot start DOOM Eternal either.
What is going on and what steps are missing?
NOTE: I found an Ubuntu repo at https://packages.lunarg.com/ which gives me an updated libvulkan1 and libvulkan1:i386 without affecting my current Mesa. 1.2.135 is installed, but whenever I try a game on Steam or using GameHub with a GOG game, it is still at 1.2.128. I have no clue where this version of Vulkan is coming from!
Seltyk
commented
4 years ago On the old thread a few users reported that battlemode can't find games, and I have the same issue. Nobody on that thread either suggested a cause or reported a fix, so I'd like to bring back attention to that issue.
When trying to find a match in battlemode, on any of the three choices, I simply cannot find a game, ever. There is not crash or error, though admittedly I haven't checked any log files.
btegs
commented
4 years ago I'm effectively in the identical scenario, same versions, cannot figure out how to get DOOM Eternal not to crash on start. :(
Did you get this figured out @btegs ?
@btegs, removing the pinnedlibs* folders prompts Steam to regenerate those folders the next time Steam is started (this is literally what I said previously). The folder's contents is the result of comparing the system libraries to the Steam runtime variants and pinning the Steam runtime variant if it is newer than the host system. Steam prioritizes libraries in the following order: Pinned libraries > Host system > Steam runtime > ld.so.conf
Deleted those folders and were recreated once starting Steam. I checked the directory and they were symlinking to a 1.2.135 version of Vulkan. cool. Then I load up a random game with Proton 5.0-6 with the DXVK hud set to 1 under Ubuntu 19.10. It shows up as Mesa 20.0.99 (using the bleeding edge git version from https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers for my RX 580. Shows Vulkan 1.2.128 for my Vulkan version. I obviously cannot start DOOM Eternal either. What is going on and what steps are missing? NOTE: I found an Ubuntu repo at https://packages.lunarg.com/ which gives me an updated libvulkan1 and libvulkan1:i386 without affecting my current Mesa. 1.2.135 is installed, but whenever I try a game on Steam or using GameHub with a GOG game, it is still at 1.2.128. I have no clue where this version of Vulkan is coming from!
I upgraded to Ubuntu 20.04 with that Vulkan package from lunarg and I still am stuck with 1.2.128. I removed the pinned libs (Steam even warns me when its recreating it on launch) and cannot get that newer version to sync up.
@kisak-valve ignored my comment before, but I'm glad that there are other people having this issue.
luisalvarado
commented
4 years ago The following is Ubuntu 20.04, latest Nvidia drivers 440 with a GTX 1080. After the game is started, a small black screen shows on the second monitor and stays like that.
Sometimes it would show the actual menu instead of the black screen like this
But if I try to make the game go fullscreen by pressing ALT+ENTER, then all hell breaks loose
BloodyIron
commented
4 years ago Alright well DOOM Eternal is now launching for me. I'm unsure what has changed for me to do this. It might have been a recent MESA driver update that fixed it, unsure. Just blind tried it again, and I'm able to get in and play the game. If I observe further issues I'll report them.
Kalevr1
commented
4 years ago The following is Ubuntu 20.04, latest Nvidia drivers 440 with a GTX 1080. After the game is started, a small black screen shows on the second monitor and stays like that.
Sometimes it would show the actual menu instead of the black screen like this
But if I try to make the game go fullscreen by pressing ALT+ENTER, then all hell breaks loose
Did it happen on first-run as well or only subsequent launch attempts? If it's like my situation you can do a workaround by deleting the folder under compdata as I explained in my report, so that every run is a "first" run. I had to dual boot my way through this game unfortunately. It was either that or delete that folder with every launch of the game. Until they fix the multi-monitor launch bug, there is no other way that I can see.
mtb-xt
commented
4 years ago But if I try to make the game go fullscreen by pressing ALT+ENTER, then all hell breaks loose
@luisalvarado instead of pressing alt-enter, try going into settings, and changing 'windowed' mode to 'borderless windowed' first. If it works, change it to 'fullscreen' then. Or just play on borderless?
luisalvarado
commented
4 years ago But if I try to make the game go fullscreen by pressing ALT+ENTER, then all hell breaks loose
@luisalvarado instead of pressing alt-enter, try going into settings, and changing 'windowed' mode to 'borderless windowed' first. If it works, change it to 'fullscreen' then. Or just play on borderless?
Let me test. Thank you
vatula
commented
4 years ago I am on Fedora 32 Workstation with Steam flatpak. NVIDIA 1080 Ti. DOOM Eternal crashes at start. I have a tiny blank wine window for a few seconds. The window then closes and the game is not started. System info attached. I do have NVIDIA 440.82 drivers.
I use Proton 5.0.7
MagicRB
commented
4 years ago @vatula I'm out of the loop when it comes to doom eternal, but could you get the stdout of wine by running doom manually? I don't think we have enough info to help you.
jsfdez
commented
4 years ago I was having a massive FPS drop in later stages of the arenas when a lot of monsters and particles appeared on the screen. I tried r_antialiasing 0, and the experience is greatly improved. I think there's an issue with the temporal antialiasing and particles for some reason.
Now the game feels smooth even in big battles.
nathanjackson
commented
4 years ago @vatula I have a configuration almost exactly the same as yours (Fedora 32, GTX 1080 ti, latest released Proton). The only difference is that I don't use the Flatpak Steam. How averse would you be to trying the RPMFusion packge of Steam?
I used to use Flatpak (about a year ago or so), but I would sometimes have issues with games that I didn't have with the RPMFusion version.
DOOM Eternal runs really well for me.
vatula
commented
4 years ago @MagicRB @kisak-valve I'm attaching proton logs for the crash. It's hefty (3.7 GB), has some errors in it but because it's so large I couldn't figure out which one was critical. I have uploaded zipped log to mega.nz steam-782330.zip
vatula
commented
4 years ago @nathanjackson I confirm the game launches when Steam is installed from RPMFusion. @kisak-valve could that mean there's an issue with Steam flatpak?
kisak-valve
commented
4 years ago Hello @vatula, possibly. Since there's a difference in behavior between the host system and flatpak, it wouldn't hurt to politely mention your experience to the flathub-provided steam package maintainers over at https://github.com/flathub/com.valvesoftware.Steam/issues.
thebozzcl
commented
4 years ago I'm running into a weird issue after updating my OS. The intro video will freeze periodically, for almost exactly 5 seconds, then run for half a second or so, then freeze again and so on. The system is unresponsive during those freezes.
Specs:
The Proton logs show several lines that seem to repeat on each freeze:
10015.302:002d:002e:trace:seh:dwarf_virtual_unwind next function rip=0000000140325af5
10015.302:002d:002e:trace:seh:dwarf_virtual_unwind rax=00007fffffea8000 rbx=00000000075a1cb0 rcx=00000000008fd690 rdx=000000007b475166
10015.302:002d:002e:trace:seh:dwarf_virtual_unwind rsi=0000000000000005 rdi=0000000000000001 rbp=00000000008fee60 rsp=00000000008fed60
10015.302:002d:002e:trace:seh:dwarf_virtual_unwind r8=00000000008fe910 r9=000000007b4751a0 r10=000000007bd225a8 r11=0000000000000000
10015.302:002d:002e:trace:seh:dwarf_virtual_unwind r12=0000000000000001 r13=0000000000000001 r14=000000014293fd90 r15=ffffffffffffffff
10015.302:002d:002e:trace:seh:RtlRestoreContext returning to 7b475166 stack 8fe9d0
10015.432:002d:003e:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\dxvk_config.dll" at 0x69040000: native
10020.444:002d:002e:warn:debugstr:OutputDebugStringA "WARNING: PumpSessionAndNetworkPackets: Not called for 5.00 seconds\n"
10020.518:002d:002e:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b00fdce ip=7b00fdce tid=002e
10020.518:002d:002e:trace:seh:raise_exception info[0]=0000000000000044
10020.518:002d:002e:trace:seh:raise_exception info[1]=00000000008fef10
10020.518:002d:002e:trace:seh:raise_exception rax=00000000008fe930 rbx=00007fffffea8000 rcx=00000000008fe910 rdx=0000000000000000
10020.518:002d:002e:trace:seh:raise_exception rsi=00000000008fea10 rdi=00000000008fe940 rbp=00000000008fed50 rsp=00000000008fe8f0
10020.518:002d:002e:trace:seh:raise_exception r8=0000000000000002 r9=00000000008fea00 r10=000000007b47aa26 r11=0000000000000000
10020.518:002d:002e:trace:seh:raise_exception r12=0000000000000001 r13=0000000000000001 r14=000000014293fd90 r15=ffffffffffffffff
10020.518:002d:002e:trace:seh:call_vectored_handlers calling handler at 0x69060d70 code=40010006 flags=0
10020.518:002d:002e:trace:seh:call_vectored_handlers handler at 0x69060d70 returned 0
10020.518:002d:002e:trace:seh:call_vectored_handlers calling handler at 0x14094ae30 code=40010006 flags=0
10020.518:002d:002e:trace:seh:call_vectored_handlers handler at 0x14094ae30 returned 0
10020.518:002d:002e:trace:seh:RtlVirtualUnwind type 1 rip 7b00fdce rsp 8fe8f0
10020.518:002d:002e:trace:seh:dump_unwind_info **** func fd80-fe07
10020.518:002d:002e:trace:seh:dump_unwind_info unwind info at 0x7b08e344 flags 0 prolog 0x11 bytes function 0x7b00fd80-0x7b00fe07
10020.518:002d:002e:trace:seh:dump_unwind_info 0x11: subq $0xc8,%rsp
10020.518:002d:002e:trace:seh:dump_unwind_info 0xa: pushq %rsi
10020.518:002d:002e:trace:seh:dump_unwind_info 0x9: pushq %rdi
10020.518:002d:002e:trace:seh:dwarf_virtual_unwind function 7b439ca1 base 0x7b439a58 cie 0x7b490710 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %ripHere's a few more extracts around some of those freezes: https://gist.github.com/thebozzcl/d443097713938069abb233dabd4bba47
I'm still checking system logs to see if I find another pattern that could give me a clue.
aoswalt
commented
4 years ago When attempting to play Battlemode, I have not been able to connect to any games. I noticed some Bad Requests to AcceptGroupInvitation in the console, but I have been connected to Bethesda.net with no issue.
nathanjackson
commented
4 years ago When attempting to play Battlemode, I have not been able to connect to any games. I noticed some Bad Requests to AcceptGroupInvitation in the console, but I have been connected to Bethesda.net with no issue.
I am having the same problem, this used to work on a previous Proton version.
mtb-xt
commented
4 years ago When attempting to play Battlemode, I have not been able to connect to any games. I noticed some Bad Requests to AcceptGroupInvitation in the console, but I have been connected to Bethesda.net with no issue. I am having the same problem, this used to work on a previous Proton version.
@nathanjackson Really? What was the version? I was never able to play Battlemode in any Proton versions :/
nathanjackson
commented
4 years ago Battlemode worked for me when I had the following configuration:
However, I've recently upgraded to Fedora 32 and Battlemode stopped working, but a few variables changed:
As a test, I tried Proton 5.4-GE-3 on Fedora 32 and Battlemode still did not work. So I think something about the OS upgrade has resulted in Battlemode no longer working. Although I think Bethesda pushed an update to DOOM Eternal for the Battlemode changes, so maybe that had something to do with it? It's weird because I can connect without issue to Bethesda.
libcg
commented
4 years ago Looks like the latest DOOM update broke the game on Proton. It doesn't launch at all anymore.
serebit
commented
4 years ago Yep, not launching at all with the new update. I see the id software logo in my system tray for a brief moment, and then it's gone.
kisak-valve
commented
4 years ago Hello @libcg, looks like a WPF issue
trace:mscoree:mono_assembly_preload_hook_fn "PresentationFramework, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies.
mdtita
commented
4 years ago Stopped working after last update for me too, doesn't launch at all.
kisak-valve
commented
4 years ago Doom Eternal Patch 14 May broke the Game.
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3867. @TheReaperUK posted on 2020-05-14T17:37:02:
Game will no longer Load at all after a Patch today 14 May 2020, No errors are shown, click Play wait a few seconds and nothing Happens and Play button returns to normal.
? It does not work at all, I think it may be anti cheat denuvo problem
albertz
commented
4 years ago Since last update (I think today, May 14, 2020 -- where can I see the update history?), it also does not work at all anymore. As reported before, no errors are shown, click Play, the id Software icon appears for 1-2 seconds as a tray icon, and then disappears, and Steams say it has stopped (it also says that last play time was just right now, so it looks like it doesn't get that there was some error).
Before that (a few days ago, when I last played), it ran really flawlessly, as reported here.
spagootie
commented
4 years ago I installed dotnet48 into the game's prefix using protontricks, and now I get a denuvo popup when I start the game that says the game can't start.
libcg
commented
4 years ago Yeah, same with dotnet35sp1. It's likely that the WPF error is caused by the Denuvo popup itself.
ghost
commented
4 years ago @libcg I think you're right, given that this was logged before WPF was called on my end:
139193.878:00ec:00f0:trace:mscoree:_CorExeMain L"C:\\users\\steamuser\\
Temp\\denuvo-anti-cheat-crash-report.exe" "C:\\users\\steamuser\\Temp\\
denuvo-anti-cheat-crash-report.exe" "-error" "2" "-transaction"From https://slayersclub.bethesda.net/en/article/2zHgbzsIV8gTzFUZ75ADGx/update-1:
I might have to ask for a refund if there's no DRM-free executable available.
Edit: refund requested
Edit: aaaaand refund denied :(
serebit
commented
4 years ago Consider me absolutely livid. One of my favorite games on Steam worked just fine on Linux, and then id decides to add kernel-mode anticheat, seemingly to spite me in particular.
artemyto
commented
4 years ago From https://slayersclub.bethesda.net/en/article/2zHgbzsIV8gTzFUZ75ADGx/update-1:
Maybe one need uninstall the Denuvo Anti-Cheat to run the game?
Due to the early flood of feedback for Doom Eternal while the community figured out how to get this game to run, the discussion for this game has been reset. If you have an interest in the community efforts made to run this game, feel free to read #3654.
Known hard requirements:
Proton 5.0-6 or newer Mesa 20.0.3 / LLVM 9.0 (AMD only) (or equivilant AMDVLK / AMDGPU-PRO) (RADV/ACO needs 20.1+) nVidia 440.82 (nVidia only, mildly older drivers may work with degraded performance.) vulkan-icd-loader 1.2.135 (This is provided by the Steam runtime. Drivers can report support for an older vulkan spec and that is okay.)
Known Quirks:
As of this writing, Denuvo is having a hard time with something in Wine-Staging, and third party Proton builds based on that may hit a 24 hour lockout after 5 runs per day. ~Steam overlay degrades performance when visible.~
Improved Steam Overlay and FPS counter performance for games using Vulkan async compute (such as DOOM Eternal).in the 2020-04-16 Steam client beta update. Alt-Tab may break the game rendering.Tinkerer guides:
Please do not re-post tinker guides in this issue report. If you have one to share, please put it in a gist and request that the gist be shared in this section.