Switched to mesa-git on my 7900XTX system and the game started working. Can't test (yet) whether that also fixes it on the 6600XT system

mesa-git did not fix it for my 6600XT system

Hah, good thing I now included the device name in mangohud and noticed in another game on Proton, that it was using the iGPU from my 4750G. Ran NFS Unbound with VKD3D_FILTER_DEVICE_NAME="6600" and now it works too.

I thought using DRI_PRIME was enough, but apparently that's not the case.

I have not been able to play this game for the past month due to EA app crashing while trying to start the game. Link to thread

bought the game yesterday, impossible to start it after a few restarts because denuvo can't get the license

I want to point out that when the drm doesn't block me the game works flawlessly, both with xbox controller and keyboard.

gpu: amd 7900xtx
cpu: amd 7800x3d
proton experimental
vulkan radv
linux 6.7 zen
archlinux

edit: i had bought the digital game through a key officially sold by amazon, i forced through amazon to issue a refund, since I don't want to have to deal with a drm that blocks users who legally buy the game

It seems that EA App on each full restart thinks it is a different computer or something and the game server no longer gives new licenses for several hours.

I wrote to support, sent EA App logs regarding the license issue but nothing to do

Replying to https://github.com/ValveSoftware/Proton/issues/6502#issuecomment-1985717193

Reply for clarification I got more fps than windows: 70 to 100 like a month ago

This issue was introducing via an update to the game.

Replying to [#6502 (comment)](https://github.com/ValveSoftware/Proton/issues/6502#issuecomment-1985717193)

Reply for clarification I got more fps than windows: 70 to 100 like a month ago

This issue was introducing via an update to the game.

try sudo sysctl kernel.split_lock_mitigate=0

Replying to [#6502 (comment)](https://github.com/ValveSoftware/Proton/issues/6502#issuecomment-1985717193)

Reply for clarification I got more fps than windows: 70 to 100 like a month ago

This issue was introducing via an update to the game.

try sudo sysctl kernel.split_lock_mitigate=0

Yep that fixed it

Back to 70 to 98 fps

Compatibility Report

Name of the game with compatibility issues: Need for Speed Unbound
AppID of the game: 1846380

System Information

• GPU: Nvidia RTX 3060 Max-Q
• Driver/LLVM version: 545.29.06
• Kernel version: 6.7.9-arch1-1
• Link to full system information report as Gist
• Proton version: Proton 8.0-5

I confirm:

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

Proton log without traces : https://gist.github.com/AzhamProdLive/a2ff5142182265c1fd095916983e4442
Proton log with traces : https://gist.github.com/AzhamProdLive/385b6a18a5f00f9cc5ed4d9b8c588a5c

Symptoms

The EA App opens, saying "Preparing Game", then the game open in a black screen, then crashes without showing the game. The Proton logs keep saying "wine client error:920: write: Bad file descriptor" in every Proton Versions I've tried (From Proton 5 up to Proton 9, and also trying Proton Experimental)

Reproduction

• Start the game with Proton 8.0-5
• Wait a bit for the game to open
• Game opens
• Crashes right after that, I can't see any gameplay nor any startup screen

Replying to https://github.com/ValveSoftware/Proton/issues/6502#issuecomment-2002400200

I wasn't effected by this yesterday, but I'm today :(

Hey @kisak-valve, thanks for moving my ticket to the right place. Please do keep in mind that this problem affects all games which have the EA Launcher copy protection in place. (like #7543) So this isn't a game specific issue per se, more of a global issue with the copy protection.

EA app won't launch at first, but I removed wine prefix(for the correspond game) and switch to proton beta 9.0 it worked(after few restarts)

I was having the same issues with not having NSF Unbound launch for Pop-OS. I did exactly this and it launched first go. I do have it using Proton 9.2 however.

Hah, good thing I now included the device name in mangohud and noticed in another game on Proton, that it was using the iGPU from my 4750G. Ran NFS Unbound with VKD3D_FILTER_DEVICE_NAME="6600" and now it works too.

I was having the same issues with not having NSF Unbound launch for Pop-OS. I did exactly this and it launched first go. I do have it using Proton 9.2 however.

Hah, good thing I now included the device name in mangohud and noticed in another game on Proton, that it was using the iGPU from my 4750G. Ran NFS Unbound with VKD3D_FILTER_DEVICE_NAME="6600" and now it works too.

I tried doing that too, and the game opened, however, it crashed before reaching the first screen (where it says "Press Enter to start")
There's my proton log, with all the stuff inside instead of Splitting the Trace and Traceless one :
steam-1846380.log

Whenever I go into Lakeshore Online in game and select a hot pursuit playlist, the car selection menu does not work if I am selected as a cop for that round. After the timer runs out to select a car, I am kicked from the match.

Error message I get after the timer runs out

If I try visiting the cop garage to look at what cop cars I have available, the game will lock me out of the menu controls although I can still pan and zoom around the previous racer vehicle I had selected. The only way for me to exit the cop garage menu in this state is to restart the game. Both of these bugs occur on 9.0-3 and Proton Experimental.

Here are the logs generated for both when I try to enter the cop garage and when I enter a hot pursuit race and the game selects me as a cop.
steam-1846380-cop-garage.log
steam-1846380-hot-pursuit.log

My system information as a gist

@sapientsand it appears that you have amdvlk installed, I couldn't reproduce the issue with mesa, so I recommend uninstalling amdvlk and then report back whether the issue persists.

@sapientsand it appears that you have amdvlk installed, I couldn't reproduce the issue with mesa, so I recommend uninstalling amdvlk and then report back whether the issue persists.

@simifor Oddly enough I did have the lib32-amdvlk package installed for some reason although uninstalling it, updating, then restarting my system did nothing, presumably because I had the environment variable AMD_VULKAN_ICD=RADV set. I still can't properly load any menu that has one of the lakeshore online police cars in it. The one time I was auto-selected as a racer for the first round, I did not see any rendering issues with the players' police cars. What hardware are you using to run the game?

I've just fixed this issue on Arch Linux, see: Arch Linux Forums > Multimedia and Games > "[SOLVED]Intel ARC A770 Steam DirectX Crash with DXGI_ERROR_DEVICE_HUNG"

The solution (using the April versions of Proton Experimental) was to set these environment variables in Game Properties > Launch Options MESA_VK_DEVICE_SELECT=[YOUR GPU PCI_VENDOR_ID]:[YOUR GPU PCI_DEVICE_ID] VK_DRIVER_FILES=/usr/share/vulkan/icd.d/[YOUR GPU's Vulkan 32-bit ICD FILE].json:/usr/share/vulkan/icd.d/[YOUR GPU's Vulkan 64-bit ICD FILE].json.

Then wait for it to compile the Vulkan shaders (should be a noticeable multi-core load), and it should start and work for the most part.

When launching the game EA App opens up and freezes immadiately

Playing on Lenovo Ideapad Gaming 3 laptop

Replying to https://github.com/ValveSoftware/Proton/issues/6502#issuecomment-2980733041

In the MangoHud overlay in the screenshot, it says it's running OpenGL with llvmpipe, a mesa software translation driver, it also doesn't show any GPU in the MangoHud overlay either.
I'm not sure what Linux distro you're using, but my first instinct is the GPU drivers are not installed and configured yet.

NFS Unbound uses DirectX 12, so Proton needs VKD3D to translate DX12 to Vulkan. I'm not sure if Vulkan is installed on that system.

Try the Mesa environment options from my linked forum answer and MANGOHUD_CONFIG=full, after confirming the GPU driver and Vulkan setup.

I've just started experiencing an Error with Proton 10.0 Experimental, Hotfix (also have the same error with Proton-GE 10.0-15,14,13,12) - these were all working fine two / three weeks ago, when I last launched the game. If i specify Proton 9.04 then the game launches fine. The older Proton 10.0-2 Beta seems to still work.

My setup has an Intel Arc A770m GPU, an Intel Nuc 12 enthusiast.

I'm getting a Wine C++ error, winevulkan/loader_thunks.c, assertion failed!

About two / three weeks ago, Proton Experimental and GE Proton 10.0-15 were working. On a side note, I also note that in Need for Speed Heat (different game), the headlights on the car has a weird green colour with the latest Proton Experimental, GE Proton 10.15 doesn't have this issue

Manufacturer: Intel Corporation
Model: NUC12SNKi72
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: 12th Gen Intel(R) Core(TM) i7-12700H
CPU Family: 0x6
CPU Model: 0x9a
CPU Stepping: 0x3
CPU Type: 0x0
Speed: 4600 MHz
20 logical processors
14 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
BMI1: Supported
BMI2: Supported
F16C: Supported
FMA: Supported
Operating System Version:
"Bazzite" (64 bit)
Kernel Name: Linux
Kernel Version: 6.16.4-107.bazzite.fc42.x86_64
X Server Vendor: The X.Org Foundation
X Server Release: 12401008
X Window Manager: KWin
Steam Runtime Version: steam-runtime_1.0.20250616.139563
Client Information:
Version: 1757650573
Browser GPU Acceleration Status: Enabled
Browser Canvas: Enabled
Browser Canvas out-of-process rasterization: Enabled
Browser Direct Rendering Display Compositor: Disabled
Browser Compositing: Enabled
Browser Multiple Raster Threads: Enabled
Browser OpenGL: Enabled
Browser Rasterization: Enabled
Browser Raw Draw: Disabled
Browser Skia Graphite: Disabled
Browser Video Decode: Enabled
Browser Video Encode: Disabled
Browser Vulkan: Disabled
Browser WebGL: Enabled
Browser WebGL2: Enabled
Browser WebGPU: Disabled
Browser WebNN: Disabled
Video Card:
Driver: Intel Mesa Intel(R) Arc(tm) A770M Graphics (DG2)
Driver Version: 4.6 (Compatibility Profile) Mesa 25.2.1
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x8086
DeviceID: 0x5690
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 2
Primary Display Resolution: 2327 x 1309
Desktop Resolution: 2327 x 1309
Primary Display Size: 24.45" x 13.43" (27.87" diag), 62.1cm x 34.1cm (70.8cm diag)
Primary VRAM: 16288 MB
Sound card:
Audio device: Realtek ALC274
Memory:
RAM: 31650 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_AU.UTF-8
Total Hard Disk Space Available: 854994 MB
Largest Free Hard Disk Block: 55878 MB
Storage:
Number of SSDs: 2
SSD sizes: 1024G,0B
Number of HDDs: 0
Number of removable drives: 0

Hello @pboard, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

I'll upload the values. The PROTON_LOG=1 goes into an infinite loop logging this over and over again - I have to stop the Game in steam, as the log file just grows infinitely - I stopped it at 7.3Gb..... I'll post the Gist of the Steam runtime Diagnostics.

949.614:0778:0e14:warn:seh:dwarf_virtual_unwind backtrace: 0x7fcc6ebea32c: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0xf532c.
949.614:0778:0e14:trace:unwind:execute_cfa_instructions 7fcc6ebea325: DW_CFA_def_cfa %rsp, 8
949.614:0778:0e14:trace:unwind:execute_cfa_instructions 7fcc6ebea325: DW_CFA_offset %rip, -8
949.614:0778:0e14:trace:unwind:dwarf_virtual_unwind fde 0x7fcc6eccd908 len 10 personality (nil) lsda (nil) code 7fcc6ebea325-7fcc6ebea336
949.614:0778:0e14:trace:unwind:execute_cfa_instructions 7fcc6ebea325: DW_CFA_undefined %rip
949.614:0778:0e14:trace:unwind:dwarf_virtual_unwind next function rip=00007fcc6ebea32c
949.614:0778:0e14:trace:unwind:dwarf_virtual_unwind rax=0000000000000000 rbx=00007fcc6eb66c70 rcx=0000000000000000 rdx=00007fcc1c0805c0
949.614:0778:0e14:trace:unwind:dwarf_virtual_unwind rsi=00000001027fe6e0 rdi=00007fcc1e6b09b0 rbp=0000000000000000 rsp=0000000102829a48
949.614:0778:0e14:trace:unwind:dwarf_virtual_unwind r8=00007fcc1c0805e0 r9=0000000000000000 r10=0000000000000040 r11=0000000000000000
949.614:0778:0e14:trace:unwind:dwarf_virtual_unwind r12=00000001027ff6c0 r13=00000001012fe6b0 r14=0000000000000016 r15=00000001012fe7b7
949.614:0778:0e14:trace:unwind:dwarf_virtual_unwind function 7fcc6ebea32c base 0x7fcc6ebea325 cie 0x7fcc6ecb8940 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip

Replying to https://github.com/ValveSoftware/Proton/issues/6502#issuecomment-3315986864

@kisak-valve - I've cut the log at 10mb, as its a repeated infinite output all the way to 7.3Gb where I stopped it. I've attached the Steam Runtime Diagnostics as a gist as well

steam-15212631221658976256-trimmed.zip

Gist Link
https://gist.github.com/pboard/30a66800936b648f743ff5047bff39c3

warn:seh:handle_syscall_fault backtrace: --- Exception 0xc0000005 at 0x7fcc5e0d754a: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libVkLayer_MESA_anti_lag.so + 0x254a. looks worthwhile to ponder. Can you try setting the game's launch options to DISABLE_LAYER_MESA_ANTI_LAG=1 %command%? If that helps, then report your findings to the mesa devs.

That worked. With the games launch options set to DISABLE_LAYER_MESA_ANTI_LAG=1 the game launched without the Wine C++ crash.

I have posted the issue to https://gitlab.freedesktop.org/mesa/mesa/-/issues/13941 - hopefully that's the correct location for this.

I've also posted about it in the Bazzite OS issues forum - https://github.com/ublue-os/bazzite/issues/3252 - just in case others have this same issue with other games

Tag it under the vendor-specific GPU driver on the Free desktop Mesa GitLab.

Check for similar issues first, in case it has been already reported there.

Tag it under the vendor-specific GPU driver on the Free desktop Mesa GitLab.

Check for similar issues first, in case it has been already reported there.

Looks like the Mesa Developers have seen others reporting it, and are looking at changing default behaviour to having it off until it's stable.

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/37509

Replying to https://github.com/ValveSoftware/Proton/issues/6502#issuecomment-3464153712

Tried GE10-24

same error as the rest here's the log

steam-1846380.log

@CosmicFusion the game is working normally on my end, tried my amd desktop and nvidia laptop each with proton 9/10/experimental. Can you delete the prefix folder, then switch to proton experimental, run the game and grab its log?

@CosmicFusion the game is working normally on my end, tried my amd desktop and nvidia laptop each with proton 9/10/experimental. Can you delete the prefix folder, then switch to proton experimental, run the game and grab its log?

I tried deleting the prefix and nothing worked.

I don't think it's a Linux/Proton Problem

I just installed windows and it's crashing in the absolute exact same manner in windows 11

Edit: A corrupt save file is being synced maybe, but is it loaded that early in?

Replying to https://github.com/ValveSoftware/Proton/issues/6502#issuecomment-3476646179

I tried deleting save game and using offline mode in win11

No luck same crash

Hey!

Has anyone managed to get Need For Speed Unbound with the Logitech G29 working? I can start the game normally but the G29 is not detected in NFS Unbound. It shows as an Xbox Controller. I have it in PS3 Mode and configured it with Oversteer but it just does not get detected. I tried both Proton Experimental and Proton-GE-28. I also tried disabling Steam Input.

Do you have any clue why?