Pathfinder: Wrath Of The Righteous (1184370)

Compatibility Report

• Name of the game with compatibility issues: Pathfinder: Wrath Of The Righteous
• Steam AppID of the game: 1184370

System Information

• GPU: GeForce GTX 1070
• Driver/LLVM version: NVIDIA 470.63.01
• Kernel version: 5.10.61-1
• Proton version: Every version is affected (tried current, experimental, etc.)

Don't think that that any of these matter, though, as the bug(s) seem to affect everyone using Proton.
Have yet to meet anyone using Proton who can proceed past the Drezen battle.

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

There are basically two problems:
1. Using Proton normally (no WINED3D options, etc.), the game runs fine for the most part. However, sometimes when loading the next map (and for some maps, this is guaranteed to happen, e.g. Drezen battle map happens at 88%) the loading just freezes. The game will now continue to fully occupy one CPU/thread until manually closed.

This behavior can be worked around by doing the following:

• Launch the game with PROTON_USE_WINED3D=1 %command%
• You’ll now be able to get past the map that didn’t load before.
• The option seriously impacts performance and graphics quality, so leave the area you are in ASAP and go to some other map.
• Save & quit the game.
• Change the launch parameter to PROTON_USE_WINED3D=0 %command%.
• Launch the game again - you’ll now be able to play normally.

However, using the WINED3D mode, besides seriously impacting graphics and performance, leads to another bug:

2. (only when using WINED3D mode) In very large maps with lots of entities (again, e.g. Drezen), the game becomes fully unplayable (not even 1 fps, it will simply refuse to render anything anymore) and something causes the game to basically occupy all CPU cores at 100% making it very difficult to even shut it down manually.

If you happen to hit both bugs at once (guaranteed freeze for normal Proton usage + guaranteed unplayable with WINED3D), it will become impossible to proceed.

This seems to be the case for the Drezen battle.

Obviously, the first problem is the one that should actually be tackled as solving that makes the workaround leading to problem two not required any more.
Since it happens during loading, and since it ALWAYS happens at the same percentage, I can only suspect that it might be some kind of file that it tries to load on some maps, or that it tries to play some certain audio or video files, etc. which causes this.

Then again, the loading works just fine using PROTON_USE_WINED3D=1, which certainly doesn't change what files the game wants to load or play... who knows.

I'll try creating a proton log file from when this loading bug occurs and add that at a later point.

No source file, test, or code entry point is identified. Start by reproducing the Drezen loading freeze with the affected Proton versions and capture the Proton log the report mentions; done means the map loads normally without requiring PROTON_USE_WINED3D=1.