Hi,

I have a RX590 and Heat closes after approx. 5 seconds with a black window.

System Information

GPU: RX 590
Driver/LLVM version: Mesa 20.2.0
Kernel Version: 5.6.0-18.1-liquorix-amd64
Proton version: Proton-5.8-GE-2-MF (with Proton 5.0.8 Heat doesn't even launch).

Full System Report: mlr_htpc_hardware.txt

steam-1222680.log

Hey guys, the game seems to be running fine (I have an Nvidia GTX 1080), the issue I found is that the game doesn't recognize my Logitech G27 racing wheel as such but as Xbox Controller making the game unplayable with it.
Could someone confirm that issue please?

Btw. Im also had issues with 5.0.9, but manually deleting the wine prefix, recreating it by starting the game and manually installing Origin in the prefix fixed all issues for me.

Hi,
Due to the fact, that Heat closes after 5 seconds with a black window, I am sorry that I can neither confirm nor deny your issue.

However, I can test your theory with manually deleting the prefix and recreating it. How exactly did you proceed? I installed Heat via Steam and started it by pressing the PLAY button. Should I just delete the wine prefix for this steam app and than press again START?

Hi,
Due to the fact, that Heat closes after 5 seconds with a black window, I am sorry that I can neither confirm nor deny your issue.

However, I can test your theory with manually deleting the prefix and recreating it. How exactly did you proceed? I installed Heat via Steam and started it by pressing the PLAY button. Should I just delete the wine prefix for this steam app and than press again START?

I deleted the wine prefix and let steam recreate it by pressing play, however, I don't know if deleting the wine prefix is even necessary,
Afterwards, I downloaded the origin installer, opened the terminal, selected the game's wine prefix as used prefix and let origin install itself. Afterwards, I was able to start the game without problems.
It should be mentioned though that the game never crashed for me so it's actually very unlikely that this will fix your problem.
In general I'm using a custom proton version, but that variant has issues with racing wheels as it seems. But you may try it.

Okay, I think this will not solve my problem really. I have the same custom Proton version running (Proton-5.8-GE-2-MF) as you I think?

Hi,

I have a RX590 and Heat closes after approx. 5 seconds with a black window.

System Information

GPU: RX 590
Driver/LLVM version: Mesa 20.2.0
Kernel Version: 5.6.0-18.1-liquorix-amd64
Proton version: Proton-5.8-GE-2-MF (with Proton 5.0.8 Heat doesn't even launch).

Full System Report: mlr_htpc_hardware.txt

steam-1222680.log

At least 1 other person trying with an AMD card :)
Works for me in 5.0.9 (Maybe you should remove the prefix 1222680 folder and start again)
Launch options: PROTON_NO_ESYNC=1

But still severe stuttering even on low settings for me in the menu's and in game. In protondb I only see Nvidia cards with good results. Unplayable as it is now.

Yes, it seems that so far everybody plays the game with an NVIDIA card and (therefore?) it works.

However, I tried your approach and deleted the wine prefix created by Steam in my home folder and switched to Proton 5.0.9 with the "PROTON_NO_ESYNC=1" Launch Option. The issue remains the same. Heat opens with a black window and crashes/closes after ca. 5 seconds.

Doing the same approach with Proton-5.8-GE-2-MF results in the exactly same behavior (Origin opens, Heat starts with black window & crashes after 5 seconds).

Furthermore, doing the same again with Proton-5.9-GE-2-MF: neither the game nor Origin launches.

Nevertheless, the game always creates CrashDumps in the "My Documents" folder inside the wine prefix. Maybe someone can help us with analyzing them or finding out why the game crashes?

Btw, in the next few days I will try to launch the game on a completely different computer (AMD FX-8350 with GTX 960 and proprietary NVIDIA driver). I know this setup is not very powerful and meets around the minimum requirements, but just for testing purposes it should be enough.

As soon as I have new insights, I will post them here and on ProtonDB.

Hey guys, the game seems to be running fine (I have an Nvidia GTX 1080), the issue I found is that the game doesn't recognize my Logitech G27 racing wheel as such but as Xbox Controller making the game unplayable with it.
Could someone confirm that issue please?

Btw. Im also had issues with 5.0.9, but manually deleting the wine prefix, recreating it by starting the game and manually installing Origin in the prefix fixed all issues for me.

Hi, I have exactly the same issue but with my G29. The controls are completely broken, as is the camera.

or me in 5.0.9 (Maybe you should remove the prefix 1222680 folder and start again)
Launch options: PROTON_NO_ESYNC=1

But still severe stuttering even on low settings for me in the menu's and in game. In protondb I only see Nvidia cards with good results. Unplayable as it is now.

I did a couple things and it became better, not perfect but a lot smoother

Not sure if this helped, found it somewhere (not sure where anymore) but I created a user.cfg in the installation directory: steam/steamapps/common/Need\ for\ Speed\ Heat/user.cfg

Thread.ProcessorCount 6
Thread.MaxProcessorCount 6
Thread.MinFreeProcessorCount 0
Thread.JobThreadPriority 0
GstRender.Thread.MaxProcessorCount 6

Also thanks to a Titanfall article on https://www.gamingonlinux.com/

chmod -R 555 your/path/to/steam/steamapps/compatdata/1222680/pfx/drive_c/users/steamuser/Application\ Data/Origin

To make the origin directory read only.

Update

Btw, in the next few days I will try to launch the game on a completely different computer (AMD FX-8350 with GTX 960 and proprietary NVIDIA driver). I know this setup is not very powerful and meets around the minimum requirements, but just for testing purposes it should be enough.

As soon as I have new insights, I will post them here and on ProtonDB.

As promised, I did setup a testing environment with an FX-8350 and a GTX960 using stock Ubuntu 20.04 LTS and NVIDIA 440 driver. I am using stock Proton 5.0.9. The game launches perfectly. Performance without the ESYNC launch option was okay, with the PROTON_NO_ESYNC=1 option the game performed nearly the same, maybe little bit better.

Not sure if this helped, found it somewhere (not sure where anymore) but I created a user.cfg in the installation directory: steam/steamapps/common/Need\ for\ Speed\ Heat/user.cfg

With the adapted user.cfg modification for my platform, the game performed better, almost fluent.
The chmod trick on the Origin folder helped a lot. The game now runs fluidly on the aging FX platform.

But still severe stuttering even on low settings for me in the menu's and in game. In protondb I only see Nvidia cards with good results. Unplayable as it is now.

I run it on Ultra with the GTX960 but on a lower resolution due to my display. So I think it definitely has to do with using AMD cards. No stuttering there.

Conclusion

The game runs perfectly with an NVIDIA card and the proprietary NVIDIA driver on Proton 5.0.9 with the user.cfg, chmod and esync fix. It seems, that the game won't start with an AMD card or the free Mesa driver (speculation). I am happy to provide a crash dump or other log file for anybody who has a better understand of those files than me. Maybe someone can help us AMD people out there?

Next

However, I will try the proprietary driver next (amdgpu-pro) to see, if the "black window" crash is still present with this driver.

Furthermore, I will try without the XBOX 360 wireless dongle. As soon as I have new insights, I will update this topic.

I have a RX 5700 XT with mesa-git and ACO enabled (ENV var) and with the fixes from above, it's quite smooth.

Hello @mlrsrt8, when you tested your RX 590, were you using RADV/LLVM or RADV/ACO? RADV/ACO was enabled by default very recently in mesa git master and it would be interesting to know if the game behaves the same with it.

I was using RADV/LLVM. Did not switch to ACO, but wanted to. Should I switch back to oibaf ppa with recent Mesa and enable ACO?

Unfortunately I have to wait 24hrs now, because Origin let me not start Heat on my RX590 machine due to hardware changes...what a absolute junk this mechanism is.

It looks to be better in the menu's with the latest version from Glorious eggrol. If only.. the window would stay at the top and not disappear to the background.. This also happens with default proton but after a number of tries with alt tab or logout / login it will stay on the foreground eventually.. Does anyone has a solution for this?

For me, using the GE proton, origin starts and the game starts, but it keeps minimizing itself when selected. I believe it's the origin overlay, but origin launched via proton doesn't allow you to disable it (says launched in restricted mode, and to restart origin, but can't do that via proton).
Is there a config file somewhere I can just change that in via CLI? or a way to start origin in regular mode?

For me, using the GE proton, origin starts and the game starts, but it keeps minimizing itself when selected. I believe it's the origin overlay, but origin launched via proton doesn't allow you to disable it (says launched in restricted mode, and to restart origin, but can't do that via proton).
Is there a config file somewhere I can just change that in via CLI? or a way to start origin in regular mode?

Yes, it actually could be related to the Origin launcher. On my FX/NVIDA test system, Heat minimizes as soon as the Origina Overlay gets displayed. Howevery, you actually can disable it through a XML file:

/home/YOUR_USER/.steam/steam/steamapps/common/Need for Speed Heat/__Installer, open installerdata.xml and set enableOriginInGameAPI="0".

Please report back if this solved the problem for you. Please keep in mind, that a game files validation through Steam (or maybe a new update of Heat through Steam) will revert you changes back to stock.

Unfortunately no, same behavior after changing that, and origin still reports it on. I feel there must be some config file for origin itself, outside of the game directory, but I don't really know windows filesystem structure so not sure where to look

Unfortunately no, same behavior after changing that, and origin still reports it on. I feel there must be some config file for origin itself, outside of the game directory, but I don't really know windows filesystem structure so not sure where to look

You can find the various Origin config files here: https://www.pcgamingwiki.com/wiki/Store:Origin#Configuration_file.28s.29_location

However, I didn't really found something useful except in the already mentioned location. Maybe you have more luck?

For me, using the GE proton, origin starts and the game starts, but it keeps minimizing itself when selected. I believe it's the origin overlay, but origin launched via proton doesn't allow you to disable it (says launched in restricted mode, and to restart origin, but can't do that via proton).
Is there a config file somewhere I can just change that in via CLI? or a way to start origin in regular mode?

You could start Origin without starting the game from steam with this command:
WINEPREFIX=/home/YOUR_USER/.steam/steam/steamapps/compdata/1222680/pfx wine /home/YOUR_USER/.steam/steam/steamapps/compdata/1222680/pfx/drive_c/Program Files (x86)/Origin/Origin.exe

Change the location of the steamapps to your situation.

This way, you can disable origin overlay and all notifications. If you can't because of the restricted mode (though not enabled), enable it, then disable it and you're good to go.

The games runs great with ACO compiler enabled (AMD) but has some stuttering problem that also occurs in Windows (in my Windows installation atleast). Has some artifact on water and reflection.

With Nvidia, the games runs with no issues so far.

The game is minimizing automatically and cannot go to the game screen/full screen when using custom Proton version (Proton GE).

Unfortunately no, same behavior after changing that, and origin still reports it on. I feel there must be some config file for origin itself, outside of the game directory, but I don't really know windows filesystem structure so not sure where to look

@mlrsrt8 using Proton GE for now is making the game minimizing itself and cannot go to foreground, use 5.0-9

@mlrsrt8 using Proton GE for now is making the game minimizing itself and cannot go to foreground, use 5.0-9

Thanks! I already tried using 5.0-9 but unfortunately, Heat closes still after a few seconds with just a black window. I have absolutely no idea, why the game crashes at my system. First I thought it was because of the RX590, but in the meanwhile people with RX580 report that the game works. I have absolutely no idea, why it always crashes. Is there anybody who can analyze the crash dumps?

Using 5.0-9 for NFS Heat does nothing on my system. Not even Origin launches. I've tried deleting the 1222680 folder for a clean prefix too.
RX5700.

Using 5.0-9 for NFS Heat does nothing on my system. Not even Origin launches. I've tried deleting the 1222680 folder for a clean prefix too.
RX5700.

Interesting! Origin installs without a problem and runs perfectly. What distribution are you using?

Using 5.0-9 for NFS Heat does nothing on my system. Not even Origin launches. I've tried deleting the 1222680 folder for a clean prefix too.
RX5700.

Interesting! Origin installs without a problem and runs perfectly. What distribution are you using?

Manjaro Gnome. I've also tried PROTON_NO_FSYNC=1 and PROTON_NO_ESYNC=1 with no luck whatsoever.

Using 5.0-9 for NFS Heat does nothing on my system. Not even Origin launches. I've tried deleting the 1222680 folder for a clean prefix too.

RX5700.

Interesting! Origin installs without a problem and runs perfectly. What distribution are you using?

Manjaro Gnome. I've also tried PROTON_NO_FSYNC=1 and PROTON_NO_ESYNC=1 with no luck whatsoever.

Do you use some tools when launching the game, like mangohud, or some other stuff ?

Do you use some tools when launching the game, like mangohud, or some other stuff ?

ENABLE_VKBASALT=1 RADV_PERFTEST=aco DXVK_HUD=fps gamemoderun %command%
Those are my launch options, I've never had any issues with them before. I'll clean the prefix and try with clean launch options.

Edit: No difference with clean prefix and clean launch options.

Do you use some tools when launching the game, like mangohud, or some other stuff ?

ENABLE_VKBASALT=1 RADV_PERFTEST=aco DXVK_HUD=fps gamemoderun %command%

Those are my launch options, I've never had any issues with them before. I'll clean the prefix and try with clean launch options.

I don’t know for gamemode, but with mangohud, origin doesn’t start either on my computer. Try removing gamemoderun from your launch options.

Do you use some tools when launching the game, like mangohud, or some other stuff ?

ENABLE_VKBASALT=1 RADV_PERFTEST=aco DXVK_HUD=fps gamemoderun %command%
Those are my launch options, I've never had any issues with them before. I'll clean the prefix and try with clean launch options.

I don’t know for gamemode, but with mangohud, origin doesn’t start either on my computer. Try removing gamemoderun from your launch options.

I tried without gamemoderun and nothing changed. One thing I noticed with proton 5.0-9 is that it creates an empty prefix folder whereas Proton-GE creates a proper one. I'm also not able to generate a steam_log with 5.0-9 so I'm not sure how to give valuable info.

Do you still experiment issues with RADV?

Hi,
yes I have still troubles getting NFS Heat to work. It does not matter which Proton version I am using, Heat opens with a black window and closes after a few seconds (when the Intro screen should be displayed). I tried Heat on another machine of mine with NVIDIA GTX 960 and the proprietary driver, and on this machine Heat works.

On what AMD GPU did you try?

Sapphire Nitro+ RX 590 8G

The game doesn't start at all with Proton 5.13.4 and Proton Experimental, it seems stuck somewhere. @kisak-valve

I'm having issues getting the game to launch, too. When running with Proton-6.0-GE-1, Origin seems to install without issue, but logging in just results in hanging at the "Connecting to Origin" screen. Log available here.

I was running with PROTON_NO_ESYNC=1 PROTON_LOG=1 %command%

System Specs:
OS/Kernel: Arch Linux / 5.10.9-arch1-1
Mesa version: Mesa 20.3.3
CPU: Intel i7-7700
GPU: Radeon RX Vega 64 (amdgpu driver)

Happy to provide more info as necessary.

Does anyone here have a solution for missing voice audio? I'm not hearing characters in cutscenes, in background while playing, at all.

System Specs:
OS/Kernel: KDE Neon (Derivative) / 5.10.0-15.1-liquorix
CPU: Ryzen 5 3600
GPU: NVIDIA GTX 1060

Hi @kisak-valve,

The RADV / Mesa labels can be removed. We retested the game on both Polaris (RX 590 Sapphire Nitro+) and Navi with Proton 5.13-6 and Mesa-Git. No launch failures were observed and no graphicals issues specific to AMD were present.

The only way to reproduce a launch failure similar to described above (black window and CTD after a few seconds) is if WineD3D is used instead of DXVK. All other failures mentioned appear to be related to Origin which has broken multiple times in the past few months, but as of 16/03/2021 Proton 5.13-6 and Experimental have no known issues with it.

Thanks for retesting, you grabbed the system information before Steam could finish gathering the extended diagnostics information. Can you go back to that, wait until the system information window in Steam doesn't end with The runtime information tool is preparing a report, please wait... and update your gist?

sorry for that, should now be corrected.

I deleted the 1222680 folder and launched the game again. Did naturally the first time setup with installing Origin and than automatically launching the game afterwards. The problem still persists. The game starts in a black window crashes back to Desktop after around 5 - 10 seconds. I attach a fresh log file.

steam-1222680.log

for me (on both current Proton, Experimental and GE), it randomly freezes up ingame (so i have to kill it), with the following 2 lines being printed to the log in an endless loop in random order (presumably by 2 threads?) when it does that (but not before):

39299.443:0054:0064:fixme:nsi:ipv6_forward_enumerate_all not implemented
39304.318:07e4:07e8:fixme:win:GetAltTabInfoW (0000000000000000, 0xffffffff, 000000000011EC88, 0000000000000000, 0x00000000)

seems to take longer with the threads/cpus set in user.cfg but still happens often enough sadly

Worked before on intel/nVidia, but currently unplayable running at 10-25 FPS and running slower than normal. NFS16 and Payback both run flawlessly.

Tried older Proton versions down to 5.13 and also the current latest GE 7-35

Here's my pc config: https://gist.github.com/7HEPOW/aa9ecdb115fba04963a4e6a74943a215
Here's a Proton Experimental log: steam-1222680.log.zip

Edit: Just finished testing all other EA titles using Origin I own to exclude the possibility it's Origin's fault. Only Heat has this problem.

Black window and game doesn't load. Similar behaviour to Titanfall2 so suspect it's Origin-related. Tried regular Proton, Proton Experimental and a selection of Proton-GE releases. Sometimes the game launches minimised too - attempting to maximise causes a brief burst of audio then the game minimises itself again.
Log with Proton Experimental: steam-1222680.log

After clicking maximise 20-30 times the game "clicks" and grabs the display. There's got to be a better way.

I recently bought the game a week ago and can't even play it at all. Origin launches and a few other origin boxes. After that it just goes back to steam. Tired every proton and various launch commands and still nothing

Hello @septemba, looking at your system information, it looks like you're missing the 32 bit userspace libraries for the NVIDIA proprietary driver. Please double check that you have the lib32-nvidia-utils system package installed.

Worked, thanks

Game not working anymore for me, i click on "play" and it does nothing, i'm using Arch (EndeavourOS).
My PC info: https://gist.github.com/KibaGasteiz/f90ab0f1bd5509e4139fa99b79c1c067
The log:
steam-1222680.log

Game not working anymore for me, i click on "play" and it does nothing, i'm using Arch (EndeavourOS). My PC info: https://gist.github.com/KibaGasteiz/f90ab0f1bd5509e4139fa99b79c1c067 The log: steam-1222680.log

I'm also having the same issue launching Assassin's Creed Odyssey, but other titles using Proton are working.

Battlefield 1 was also not launching, so i assume it has something to do with Origin and Ubisoft Connect, but i opted out from Steam beta and now the 3 games are launching correctly. Something with the Steam client beta is not okay.

EA APP needs these 2 d3dcompiler_47 d3dcompiler_43
or you will get a blank blue screen, A finally dropped Origin client

It's still opening Origin for me, EA App appeared for some seconds in the first launch but changed to origin and now it uses origin as always.

u need to delete the prefix in compatdata

well, this sucks. I cant get it to run on Ubuntu.
SYS INFO:
Ubuntu 22.04.1 LTS x86_64
Ryzen 7 2700x
RTX 2060
16 GB DDR4

Replying to https://github.com/ValveSoftware/Proton/issues/3955#issuecomment-647711660

This helped a lot for me. I went from about 0.3 FPS to a kind of playable amount of FPS

I was just playing NFS: Heat yesterday on my Steam Deck with Proton Experimental since it was the only Proton version that worked for the new EA app. But after today's Proton Experimental update the game is no longer launching on the Deck - I only get the blank blue screen of the EA app for a few seconds before I'm thrown back to my Steam library.

I was just playing NFS: Heat yesterday on my Steam Deck with Proton Experimental since it was the only Proton version that worked for the new EA app. But after today's Proton Experimental update the game is no longer launching on the Deck - I only get the blank blue screen of the EA app for a few seconds before I'm thrown back to my Steam library.

I can confirm this is happening with Proton Experimental on my PC with ArchLinux too, tested NFS Heat and Battlefield 1.

@Zackyist @KibaGasteiz I cannot reproduce what you are seeing right now. I have a couple of requests:

1. Could you try again today? I've seen several problems on the EA Launcher side, and maybe you got unlucky and they already fixed something. If you are still seeing the failure:

2. Could you try deleting the prefix?
   @Zackyist There is a "safe" way to do this on the deck -- 1) Click on the gear icon to the right of "Play" 2) Go to "Developer" menu 3) Click on "Delete Proton Files"
   @KibaGasteiz The default location on desktop is ~/.steam/steam/steamapps/compatdata/1222680 for NFS Heat.

2. Could you try deleting the prefix?
   @Zackyist There is a "safe" way to do this on the deck -- 1) Click on the gear icon to the right of "Play" 2) Go to "Developer" menu 3) Click on "Delete Proton Files"
   @KibaGasteiz The default location on desktop is ~/.steam/steam/steamapps/compatdata/1222680 for NFS Heat.

This worked, thanks!
For both, NFS Heat and BF1.

Replying to https://github.com/ValveSoftware/Proton/issues/3955#issuecomment-1305857837

Even after the latest game updates it didn't work with Proton Experimental, but after deleting the prefix the game finally launched once it was done with the fairly long EA App install again. Thanks!

Unfortunately, none of the above worked for me, I even reinstalled the game and Proton Experimental (+ deleted the prefix), to no avail.

Unfortunately, none of the above worked for me, I even reinstalled the game and Proton Experimental (+ deleted the prefix), to no avail.

Try to launch the game again and again, seems like sometimes it just fails and you may had bad luck.

Replying to https://github.com/ValveSoftware/Proton/issues/3955#issuecomment-1312632203

Tried around 10 times, tried reinstalling the game, switching proton versions, deleting prefix, nothing works, EA app is stuck with blank screen with "BETA" on top.

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

Tried around 10 times, tried reinstalling the game, switching proton versions, deleting prefix, nothing works, EA app is stuck with blank screen with "BETA" on top.

That's strange, you should share your PC info and maybe the proton log because i can't reproduce the issue anymore on Archlinux.

Replying to https://github.com/ValveSoftware/Proton/issues/3955#issuecomment-1312722937

Not him but I'm also unable to install the EA app even with the latest proton experimental version on arch linux. Running the game with an i5 10400 and 6700xt. Not sure if this is related to this bug or if I'm having a different problem as I was having issues getting the game to launch pre-EA app migration.

Here's my proton log output in case you're curious.

Replying to https://github.com/ValveSoftware/Proton/issues/3955#issuecomment-1312722937

Arch Linux, Linux 6.0.8 on 13th gen i5 + GTX 1080 ti. How can I capture a verbose proton log?

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

Arch Linux, Linux 6.0.8 on 13th gen i5 + GTX 1080 ti. How can I capture a verbose proton log?

Right click on the game on Steam, Properties, and use this launch parameter: PROTON_LOG=1 %command%

Launch the game and the proton log should appear in /home/USERNAME/

Alright, here's my log:
steam-1222680.log.zip

Hi there,
The game won't start at all. I've read somewhere that EA is dropping the Origin Login completely and replacing it with something they use. Maybe that can give a hint.
Also on my System (Linux Mint) the Game won't start. No login window whatsoever.
I've taken the Liberty to provide you with my system information and a log file.
log-system-info.zip

update: I deleted the Proton files at "~/.steam/steam/steamapps/compatdata/1222680" as recommended by @KibaGasteiz and now it runs. Sorry for the comment. Feel free to delete it if you think it is obsolete.

Still totally broken. Would like to hear if anyone has had better luck, runs on the Steam Deck but on desktop with Nvidia it's a mess and fails to load the game at all. Often fails to even create a window correctly.
Cannot even upload a log as I have a 40MB file after compressing the log, raw sizes of logs are ~1GB by the time the EA launch is gone and the game tries (and fails) to create a window.

Replying to https://github.com/ValveSoftware/Proton/issues/3955#issue-634869412

https://www.phoronix.com/news/Linux-Splitlock-Hurts-Gaming

this solves the bad performance. Have fun

Game shows as running but game window doesn't show up

Compatibility Report

• Name of the game with compatibility issues: NFS Heat
• Steam AppID of the game: 1222680

System Information

• GPU: GeForce RTX™ 3060 Laptop
• Driver/LLVM version: nvidia 530.41.03-250 (DKMS)
• Kernel version: 6.4.12-arch1-1
• Proton version: Proton 8.0-3

I confirm:

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

Symptoms

I start the game, game shows as running on Steam, but the game window never shows up

I'm linking my proton log, hoping it can help
steam-1222680.log

its been a while since this issue appeared with the steering problem, i have no issues playing dirt, assetto corsa, beamng or wrc but heat for some reason doesnt pick up the wheel, why is that? thanks!

Hey guys, this game needs some serious work from Valve, as it has quite a couple of issues, this bug report is open from 2020 which is not very reassuring tho.

My issues are:

1 - Stuttering, every 5 to 10 seconds the game seems to drop one frame, no matter what quality I set.

2 - After around 40 minutes to 1 hour of playing, the game loses alot of fps

3 - Rendering issues - There are some rendering issuers in the main menu on the car as you can see from this short clip I recorded, as there are some pixelated boxes appearing on the right of the car

https://github.com/user-attachments/assets/e0fa328a-3c7c-4ba2-ac13-1198111404ce

4 - also basically everytime I open steam, I have to do an update to the game and alot of time it makes me recompile the shader cache

5 - sometime the audio of the game doesen't get picked up automatically and I have to alt tab and reselect the window of the game to get audio back

I hope valve can fix those issues

Replying to https://github.com/ValveSoftware/Proton/issues/3955#issuecomment-2571757377

1. Doesn't mean an issue has been opened since 2020 doesn't mean it's bad, they keep these issues open so if someone has a new issue they put it in here, this is the same for all issues opened on here

2. The stuttering and fps loss issue is probably because of the steam client bug, use this launch command and see if it fixes your problem

LD_PRELOAD="" %command%

1. you haven't mentioned your hardware

2. Steam has a thing called downloading shader cache, you can turn this off in steams download settings

3. what proton version are you using and what distro are you using?

I myself have played this game without any issues on controller for 15 hours total on my amd hardware on arch, KDE plasma wayland

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

Yeah I know about the stuttering issue, I already use the launch option.

Also I've tested with both proton 9.04 and experimental, and I'm on NVIDIA 4060 proprietary drivers + KDE Plasma Wayland

I am experiencing many of those issues too.

Hello all,

I am having similar issues too, AMD 7900 GRE, Need for Speed Heat runs but takes a very long time to start, and when it does the performance in cutscenes is pretty much 0.5FPS. And when I load into the game its about 15FPS, the game does not utilize my system resources either, I have tried GE, experimental, hotfix, and some other Proton versions to no avail, and tried some launch options. If anyone would like more info let me know, and if anyone can help that would be very appreciated.

Thanks,

@JustPurpleN the game is working fine on my end with a 6600, so I imagine this is a setup issue. Please upload the proton log, run the game with the following launch parameter: PROTON_LOG=1 %command% which will then create a text file in your home folder called steam-1222680.log upload it here, you can just close the game after reaching the main menu.

I had the stuttering issue in NFS heat on my Bazitte OS setup, with an Intel Arc a770m setup with an Intel Nuc 12 enthusiast mini pc setup. Bazitte Os currently has Kernel 6.15 that supports NTSync scheduling.

I am running the game via the Decky Loader plugin, Non Steam Launchers, under the EA app.

However, with the latest GE Proton 10-10 supporting the NTSync kernel mode scheduling, i enabled that runtime and the ntsync launch parameter, and the stuttering issue went away, it's smooth now just like in Windows. PROTON_USE_NTSYNC=1 was the parameter.

I also enabled that on other Nfs games, such as Nfs Payback which had the stuttering issue and it fixed it as well. I also added it to my Steam Forza Horizon 4, switching to Ge Proton 10-10 and had an improvement in my minimum and maximum frames per second by a few fps, not that it was stuttering before, but it just seems to get a few extra fps. For Forza i switched compatibility to Ge Proton 10-10 and used PROTON_USE_NTSYNC=1 %command% as the launch parameters.

Anyway, hope that helps someone

Hi guys, I get an error by DirectX telling me to install video card drivers. The drivers are installed though and other games work, too. I am using an nVidia GTX 670, quite old, I understand, but should be still working as it is slightly faster than the GTX 760 which is listed as the minimal requirement.

Here is the message I am getting:

Failed to initialize display adapter. Please ensure your video card is compatible and the drivers for it installed. Usually this is a result of missing vendor specific drivers.

I use Proton 10.0-2 (beta) without any further tweaks.

@simifor yoo I thought I responded to this sorry! I was able to fix the issue, I had to disable Split Lock Mitigate and my problems were fixed. And as a permanent solution I gave Gamemoderun elevated permissions where it disables Split Lock Mitigate as part of the program. So I am able to just gamemoderun %command% in Steam launch options and I have no stutter. Also thank you for responding to my message a while back!

I use Proton 10.0-2 (beta) without any further tweaks.

@Photon89 you have to use an older version of proton, I think 9.0-4 will work with your hardware, because it uses an older version of dxvk that doesen't require vulkan 1.3

Or, the other alternative is to use the mesa NVK driver, but it's not ready for use, as performance is very worse compared to the proprietary driver, and support for older gpus like the one you have has just been added, so it still has to mature

Hello all,

I am having similar issues too, AMD 7900 GRE, Need for Speed Heat runs but takes a very long time to start, and when it does the performance in cutscenes is pretty much 0.5FPS. And when I load into the game its about 15FPS, the game does not utilize my system resources either, I have tried GE, experimental, hotfix, and some other Proton versions to no avail, and tried some launch options. If anyone would like more info let me know, and if anyone can help that would be very appreciated.

Thanks,

that's because of the split lock issue.

https://www.phoronix.com/news/Linux-Splitlock-Hurts-Gaming

you have to add split_lock_detect=off to the grub configuration and regenerate it

@kisak-valve @Milli189
Thanks for the fast and comprehensive replies! Well, looks like I need to think about a hardware upgrade soon...

In the mean time I tried to use older Proton versions and get stuck installing the EA launcher with them (that's why I had to switch to Proton 10 eventually). In the log the only error I see is

err:steam:run_process Failed to execute L"link2ea://launchgame/1222680?platform=steam&theme=nfsh"

Full log is attached below.

steam-1222680.log

Dont have the game on my end to check on deck, but seeing posts saying the headlights and tail lights are now green on cars for Heat and Payback

Dont have the game on my end to check on deck, but seeing posts saying the headlights and tail lights are now green on cars for Heat and Payback

Yes, i can confirm that the latest Proton Experimental version gives green headlights in NFS heat. Going back to Proton 10.0-2 Beta fixes it.

Using Proton 10.0-2 Beta fixes the crash, as does Proton 9.0.4. Hopefully these bugs get sorted soon.

My setup has an Intel Arc a770m card, using an Intel Nuc 12 enthusiast with 32gb ram. It was all running quite nicely until recently on Bazzite Os. I have set the two NFS games to use Proton 9.04 for now, until some updates come out.

Update (2025-09-24): The Latest GE-Proton 10-16 also has the green light bug that Proton Experimental has in NFS Heat

I've occassionally been playing NFS Heat on my arch (garuda) laptop for a while now and it's always without issues. I've installed the same garuda (hyprland) installation on my pc now, but steam completely fails to launch the game on my pc.

Initially I was getting an error saying System.exception: wayland,x11 not available, which I bypassed by launching steam using unset SDL_VIDEODRIVER; steam which prevented that issue, but instead of that error occuring, it just gets "launched", no window ever appears, and a few seconds later steam reports that the game is not running.

My PC is using:
Linux 6.17.5-zen1-1-zen kernel
hyprland 0.51.1 (wayland)
and an RTX 4060 GPU using proprietary drivers
Attempted and got same result on proton hotfix, experimental, 9, and 10

One of the full logs:

steam-1222680.log

Hey,
i have been trying to get Need For Speed Heat working properly, but after playing 6-7 Minutes the Game always crashes for absolutely no reason. The Game is booting up perfectly fine, but wherever i am for example in a cutscene or a race or in open world, the game crashes for absolutely no Reason.

I have tried these commands when launching NFS Heat but nothing works, it is still crashing.
"PROTON_USE_DXVK=1 PROTON_USE_NTSYNC=1 PROTON_ENABLE_WAYLAND=1 DXVK_ASYNC=0 mangohud %command%"

I have an RX 6800XT with and Ryzen 7 5700x and 32gb RAM. I am on Arch Linux with Hyprland fully up to date.

Here is a screenshot i captured during the crash with the hardware Stats.

Here are my logs:
steam-1222680.log

How can i fix it?

Replying to https://github.com/ValveSoftware/Proton/issues/3955#issuecomment-3508072507

Let's understand these environment variables as using these with normal proton not all will work or aren't being used anymore.

PROTON_USE_DXVK won't do anything on a game that will always use dxvk by default as it is a dx11 game.

PROTON_USE_NTSYNC will only work on proton runners that have NTSYNC included which only ge-proton, cachy_proton, proton-em include that, normal proton does not include it yet.

PROTON_ENABLE_WAYLAND is the same thing, only available on custom proton runners like above but not normal proton yet.

DXVK_ASYNC no longer is being used In custom proton runners and was never used in normal proton.

Simply run the game with the latest experimental and latest mesa + kernel the distro provides, if it has a crash then PROTON_LOG=1 %command% is all you need to add then upload the log which you have and that is great.

You can also try experimental(bleeding edge)
(find Proton Experimental in Steam's Library -> properties -> betas). It automatically picks up latest developemnt in dxvk, vkd3d-proton, dxvk-nvapi, vkd3d and Proton's wine.

It can eat your game prefix / saves. Use it at your own risk.

I already tried different Proton Versions such as ProtonGE-Latest, Proton Experiemetal and Proton Hotfix.
Do you have any idea by looking over the Log File what is crashing my Game?

@Schnurzel700 I didn't see a smoking gun in your logs. I tried the game with proton 10 and experimental, 1 hour each. Did the game work normally at some point? it might be worth finding what might have change din your setup from then to now. Might also be worth checking your dmesg log after the game crashes to see if anything's there with sudo dmesg > dmesg.log

Thanks for trying to help! After some troubleshooting, I realized the issue was not Proton related. It was my RAM overclock causing instability. Setting the timings back to the default DOCP profile fixed everything, and now it’s working perfectly, including NFS Heat.

Hey!

Has anyone managed to get Need For Speed with the Logitech G29 working? I can start the game normally but the G29 is not detected in NFS Heat. 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-latest. I also disabled Steam Input.

Do you have any clue why?

Any solution or update on this?

The best racing wheel workaround I have found so far, is input-remapper-gtk + oversteer.
You can map your racing wheel to a virtual Xbox controller.
With oversteer you can set autocenter strength + wheel degrees.
In this way you can play any racing game that doesn't support a wheel.

@Arborescent Will the built-in force feedback from the game still work with that method, or will it not function?

@Arborescent Would you mind sharing your preset for Input-remapper-gtk?