It's an know problem, just cancel UE4 Prerequisites installer, you don't need it.

After cancelling the installer, the game starts but hangs right off the bat. It opens a full screen window that is black in the center and the rest of it is a capture of the desktop. It is uncloseable and eats a whole CPU core.

I've tried leaving it for over an hour to confirm it was really crashed. The only way to close it is with
killall TheTuringTest.exe

Without any option with Proton Beta the game run around 30fps (720p with all at Low without motion blur). (I need to cancel UE4 installer).

I confirm that the fix about user.reg fix the crackeling audio for me.
For the user.reg I add the following line in [Software\Wine\DllOverrides] category.

"xaudio2_7"="native,builtin"

Laptop information: https://gist.github.com/kadogo/a72b612e48ede28a5bd7495b268de99d

It's not specified but i have this card too.

0a:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz PRO [Radeon R5 M255]

The DXKV hud showed information about AMD so I think that it use my AMD card without that I specify DRI_PRIME=1 in the launch command. I'm not sure if it's normal.

Cheers.

Can confirm that the previous issues with the game have been resolved in a proton update. However, audio is still unusably broken, even with the registry edit mentioned above. Performance is excellent and may even be better than native windows.

For newcomers, you do have to cancel the prerequisite installer every time the game starts.

"xaudio2_7"="native,builtin" not helped on Ubuntu 18.04. Any other hints?

After quite a bit of tweaking I've found a few settings that make the game work fine on an external monitor, with pulseaudio and bumblebee:

I manually added "xaudio2_7"="native,builtin" to the end of the [Software\Wine\DllOverrides] section of Steam/steamapps/compatdata/499520/pfx/user.reg

Then, in Steam, I set the Launch Options to PULSE_LATENCY_MSEC=120 PROTON_USE_WINED3D11=1 primusrun %command%

Is all of this strictly necessary? No idea, but it works.

audio works fine for me after applying the "xaudio2_7"="native,buitlin" tweak, great performance also

Me helped only trick with below "Launch Options":

PULSE_LATENCY_MSEC=120 PROTON_USE_WINED3D11=1

Nothing less, nothing more. Proton 3-16-6-Beta. Messing with registry either manually or by "winecfg" always was causing that game either no started or started with cracking sound. Maybe because of Polish locales? I don't know, never mind...

I was playing with game soundtrack played by Spotify - shit - now I will have to start game from beginning, because there is more fun! Thanks guys!

With Proton 4.2-3 it works out of the box. Finished the game completely and didn't have had any issue at all.

Sysinfo: https://gist.github.com/NoXPhasma/f842039588ff89403b66abae978a4882

The only thing which does not work properly, is the UE4PrereqSetup_x64.exe at the launch of the game. It can't install properly but still tries to install each game launch, but it does not stop the game from running. More like an annoyance as an issue. Pretty easy to get around it by renaming the Redist folder in the game folder.

I tried the game with DX12 with Proton 4.11-8 (vkd3d) but it hangs right on launch. Music keeps playing but image stucks and game needs to be killed.

steam-499520.log
https://gist.github.com/NoXPhasma/9c4497ebcb8838352716c93460353eab

I tried to play it but the UE4 installer fails after clicking "Install" and presents a screen that reads "Invalid ACL". Also, when the game actually launches, it shows just random screens with random colors such as Pink, dark blue an so on. Sound is great though,

Game works for me using the default D3D11 renderer, although the UE4 installer runs every time, including the "Invalid ACL" message.

@caiodev which is your setup? It works fine for me on linux mint 19 (try also to close UE4 prerequisite setup without trying to install it).

Hey @jumpy88 , here it is.

OS: Ubuntu 20.04 LTS
Kernel: 5.6.15-050615
DE: MATE
CPU: Intel i5-3230M
GPU: Intel 3rd Gen Core
RAM: 8GB

@kisak-valve Got it. Yeah, i really have an oldie here. Bought this laptop in 2014 actually lol NIce man, thanks for this info.

The game fails to load the sector 31 (start of chapter 4) - for me it just crashes to desktop.
steam-499520.log

I'd provide a save file to get there easily but can't find where it's location is right now.

Edit: Found it in the install folder next to steam_autocloud.vdf
savedata.zip

I also can't load the sector 31 level

Also getting frequent crashes loading levels starting on Chapter 4 (sector 31). The crashes are gone when running with Proton 5.13-6, but are present on 6.3-8, 7.0-1, and Experimental.

Steam System Information: https://gist.github.com/rlac/25a859413c9f9b139539f5820cc281c3
Proton log, fresh prefix on 7.0-1: steam-499520.log

Steps to reproduce from main menu:

1. Chapter Select
2. Chapter Four
3. Sector 31
4. If load succeeds (it will work very infrequently) return to main menu and repeat above

All of Chapter Four has the issue, not just Sector 31, but that's the first time it occurs. It doesn't appear to occur outside of Chapter 4, including 5 onwards.

Game save data with up to Chapter 7/Sector 62 unlocked (game not yet complete): savedata.zip

I've found a minor issue with this game using the DX12 mode and Proton versions from 9.0-4 to Experimental 2026-01-16 (haven't tested previous versions): if you set the display mode to Borderless Fullscreen instead of Fullscreen and restart, the game hangs after the intro logo.

Proton logs: steam-499520-protonexp.tar.gz

Main error logs:

684.764:0134:01f8:warn:vkd3d-proton:vkd3d_allocate_device_memory: Memory allocation failed, falling back to system memory.
radv/amdgpu: Not enough memory for command submission.
685.780:0134:01b4:err:vkd3d-proton:dxgi_vk_swap_chain_submit_blit: Failed to submit swapchain blit, vr -4.
685.780:0134:01b4:err:vkd3d-proton:dxgi_vk_swap_chain_present_signal_blit_semaphore: Failed to submit present discard, vr = -4.

Specs:

• OS: Arch
• Kernel: 6.12.61
• GPU: RX 6700 XT (Mesa 25.2.7)
• CPU: Ryzen 7 5700G (8c/16t)
• DE: Plasma 6.5.3 (wayland and X11)

I can no longer reproduce the issue mentioned before after upgrading Mesa to 25.3.5 and Plasma to 6.5.5 (wayland/x11)