this is what happens without PROTON_USE_WINED3D

log: https://gist.github.com/Francesco149/6ad5433daee895ec6a281729808a8dce

Ah that makes sense! I wonder how much of these NUMA-APIs are stubbed and/or faked.

From the code link I posted above:

        ULONG highestNodeNumber;
        if (!GetNumaHighestNodeNumber(&highestNodeNumber))
        {
            throw scheduler_resource_allocation_error(HRESULT_FROM_WIN32(GetLastError()));
        }

        m_numaCount = highestNodeNumber + 1;
        m_numaInformation = _concrt_new NumaInformation[m_numaCount];

        ...snip...

        DWORD numaNodeNumber = pCurNode->GetNumaNode();
        m_numaInformation[numaNodeNumber].m_nodeMask.Set(nodeId); // this (probably) crashes

Again, I am not 100% about the disassembly but it seems this could be it.

Other users seem to be able to play this game just fine on Linux through Proton, so I wonder why my machine behaves differently here - if the code is stubbed it shouldn't really be a difference right?

Whitelist Request

System Information

• GPU: RX 480
• Driver/LLVM version: Mesa 19.3.1/9.0.0 (ACO enabled)
• Distro version: Arch Linux
• Link to full system information report as Gist: My Steam info
• Proton version: 4.11-11

I confirm:

• [x] that pressing the Play button in the Steam client is sufficient.
• [ ] that runtime config options are necessary to run the game.
• [x] that no workarounds other than PROTON_* env variables are necessary.

Issues

• [x] I haven't experienced any issues.
• [x] There are no issues left open for this game.
• [ ] Although I consider the gaming experience equal to Windows there are remaining issues:

Notes

12+ hours of play, game runs flawlessly. I have also ran this game on Intel Core2 Quad + GTX 670 with nvidia binary blob under Void Linux and the experience there is equally good!

@kbeckmann, can you check if adding taskset -c 0-15 %command% to the game's launch options works around the issue you encountered?

Wow this actually works, well sort of. Had to change to taskset -c 0-7 %command%. Simple solution to a weird issue for sure. Thanks again for helping out, @kisak-valve.

I get black screen no matter I put thetaskset -c 0-7 %command% or with 0.15, the game simply shows blackscreen after the XD logo. I'm puting the log down here
steam-774171.log

Game won't launch on Arch Linux from Steam. Tried all Proton version, including proton-ge-custom.
Using wine-ge-custom it displays a black screen.
I managed to make it run on Garuda Linux from Steam but now it won't launch at all.

Also, how do you use this:
PROTON_USE_WINED3D=1 %command%
Do I just put in the launch options?

System Information

• GPU: RX 6600
• Video driver version: Mesa 25.0.7 / LLVM 20.1.2
• Kernel version: 6.80-90-generic
• Link to full system information report as Gist
• Proton version: 10.0-3

I confirm:

• [x] that I have checked whether there are updates for my system available.

Symptoms

The game hitches heavily on the start screen and immediately afterwards in the main menu. Its visuals freeze as the music keeps playing, and occasionally they unhitch briefly before freezing up again, and they do this several times before finally accepting any user input.
Oddly enough, this issue gets way worse when I attempt to log this through Proton. The start screen hitches and never recovers, the mouse cursor remains the desktop cursor instead of the in-game cursor, and I ultimately have to force-quit the application through Steam. The resulting 1.5GB log compresses so poorly that I ultimately had to upload it to a third-party file host: https://files.catbox.moe/k1jhqe.gz . I do, however, have Unity player logs of the phenomenon with and without Proton logs activated.
Player_with_proton_log.log
Player_without_proton_log.log

Reproduction

Run the game with and without Proton logging enabled.