Pioneers of Pagonia v0.8.2 crashes on startup (might be vkd3d regression)

[Mershl]

yesterdays Pioneers of Pagonia update 0.8.2 introduced a crash on startup when using vkd3d main or Proton Experimental.
the crash is NOT reproducible on Proton Stable.

it looks like an exception in d3d12core.dll. @doitsujin might this be related to #2119? I can bisect tomorrow if necessary.

Log files

steam-2155180.log

[doitsujin]

Bisect would be useful, it's weekend anyway though so there won't be much going on here for now.

I don't really see why the app profile would break the game though unless they are deliberately trying to troll us.

Edit: Just tested since I still had it installed, game still runs fine here.

[Mershl]

It seems like switching from Beta branch to Stable branch of the game caused some files to corrupt.
Clean installing the game fixes the issue for Proton Stable and Experimental.

[depate]

Hello!

I'd like to report, that this issue—if it is the same—did not resolve for me with reinstallation of the game.
Neither Proton Experimental, Proton 9, 8, 7 (the steam default) nor Proton-GE can get past the loading screen. I recall it used to work with not using Proton Experimental after the patch and with any non-experimental with the patch.

Often the music starts, but latest at “loading island” will crash the game. But typically it crashes right away after a second or two. As far as I can see, there's no sensible error shown related to that issue in the log that's steam is outputting to the console.

This is independent of X.org or Wayland.

@Mershl would you reopen your issue, or should I open a new one and link this one?

[Mershl]

I grabbed a freshly installed notebook to test this issue further. Fedora 41, Flatpak Steam, Pioneers of Pagonia 0.8.2.

run	Proton	game launch parameter	result
# 1	Experimental	gamemoderun mangohud %command%	crashes at "Arriving on island"
# 2	Experimental	none	works and gets ingame
# 3	Experimental	gamemoderun mangohud %command%	crashes at "Arriving on island"
# 4	Experimental	none	works and gets ingame
# 5	Experimental	mangohud %command%	crashes at "Arriving on island"
# 6	Experimental	none	works and gets ingame

@depate can you confirm this on your machine?

[doitsujin]

#2157

No idea what's going on, I haven't experienced a single crash so far but that should fix it again at the cost of losing the MSAA option.

[Mershl]

I can reproduce the following sequence on a clean installation of Fedora 41, Gnome Wayland, Flatpak Steam, AMDGPU (mesa 24.2.4), Pioneers of Pagonia 0.8.2

run	Proton	game launch parameter	result
# 1	Experimental	mangohud %command%	crashes at "Arriving on island"
# 2	Experimental	none	works and gets ingame
# 3	Experimental	mangohud %command%	crashes at "Arriving on island"
# 4	Experimental	none	works and gets ingame
# 5	Proton 9.0-3	mangohud %command%	!!! works and gets ingame
# 6	Proton 9.0-3	none	works and gets ingame
# 7	Experimental	mangohud %command%	crashes at "Arriving on island"
# 8	Experimental	none	!!! crashes at "Arriving on island"
			rm -rf ~/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/compatdata/2155180
# 9	Experimental	mangohud %command%	crashes at "Arriving on island"
# 10	Experimental	none	works and gets ingame

[depate]

On my AMDGPU laptop, the game still runs fine with the same setup that you described. Mesa 24.2, with mangohud, proton experimental and 9.0-3 as well as latest Archlinux packages with steam-runtime.
I checked the MSAA setting, which presents itself there, but has no options to set other than off there.

But the game is crashing for me with my workstation AMD CPU + NVIDIA graphics (open kernel drivers v560) setup. I noticed, that I had the MSAA option at an earlier point in Pagonia, which could go up to x8 or x16 and worked fine. However, I saw it also running with the MSAA being grayed out entirely, before the startup broke.

I'm rather confused about the different parts playing a role here. The game itself, VKD3D, maybe the graphic card drivers.

Could you give me a hint, on how to receive such detailed debug log from your initial post, @Mershl ?
Possibly it provides some clues on what component exactly is at fault here.

According to the Arch Wiki running steam with DEBUGGER=GDB steam should be able to retrieve stack traces, however, even with the game crashing, I don't get any trace.