ValveSoftware
Need for Speed™ Heat (1222680)
Compatibility Report
- Name of the game with compatibility issues: Need for Speed™ Heat
- Steam AppID of the game: 1222680
System Information
- GPU: RX 580
- Driver/LLVM version: Mesa 20.1.0
- Kernel Version: 5.4.0-33-generic
- Link to full system information report as Gist: https://gist.github.com/guustflater/55a4f84ad206aad4cabf8737788401f1
- Proton version: 5.08
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.
Symptoms
The game starts and runs but there's unplayable stuttering (see protondb also since more people have issues with the game). Even with all settings on low it doesn't make any difference.
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
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
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.
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 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?
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?
I just switched to ACO with stock Mesa from Ubuntu 20.04 (20.0.4) and Proton-5.11-GE-1-MF on the RX590 machine. The issue remains: Heat opens up and closes itself after 5 seconds. If I compare this procedure on my FX8350/GTX960 machine, then there is a similarity: Heat initially opens up on the NVIDIA machine with a black window too, but minimizes itself to the tray and loads the introduction video with the "Press Start" message in the background. On the RX590 machine, instead of minimizing, the application just crashes. So I guess, that the crashing has to do with loading the window / game content...?
Btw, the Wireless XBOX 360 Controller works ootb and perfectly!
The game doesn't even launch in my case when using 5.0.9. Origin doesn't pop up either. However, when using Proton-5.11-GE-1-MF, Origin pops up and says something about not being able to install in the current location but closes after a while. Game doesn't launch.
I tried to generate a steam-log with 5.0.9 but it didn't work. Only 5.11-GE-MF generated a steam-log.
The game doesn't even launch in my case when using 5.0.9. Origin doesn't pop up either. However, when using Proton-5.11-GE-1-MF, Origin pops up and says something about not being able to install in the current location but closes after a while. Game doesn't launch.
I tried to generate a steam-log with 5.0.9 but it didn't work. Only 5.11-GE-MF generated a steam-log.
I know that message from Origin you are talking about. This message pops up at my system too, although after a few seconds Origin minimizes and Heat opens with the before mentioned black window (or in case of the NVIDIA system, Heat starts).Does not really matter wheter I am using Proton 5.0.9 or 5.11
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.