search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.42k stars 1.07k forks source link

Need for Speed™ Heat (1222680) #3955

Open guustflater opened 4 years ago

guustflater commented 4 years ago

Compatibility Report

System Information

I confirm:

steam-1222680.log

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.

mlrsrt8 commented 4 years ago

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

TobiPeterG commented 4 years ago

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.

mlrsrt8 commented 4 years ago

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?

TobiPeterG commented 4 years ago

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.

mlrsrt8 commented 4 years ago

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?

guustflater commented 4 years ago

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.

mlrsrt8 commented 4 years ago

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.

Arsconyl commented 4 years ago

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.

guustflater commented 4 years ago

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.

mlrsrt8 commented 4 years ago

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.

kisak-valve commented 4 years ago

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.

Arsconyl commented 4 years ago

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

mlrsrt8 commented 4 years ago

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.

guustflater commented 4 years ago

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?

mlrsrt8 commented 4 years ago

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!

GottaSlay commented 4 years ago

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.

steam-1222680.log

mlrsrt8 commented 4 years ago

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.

steam-1222680.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

aradapilot commented 4 years ago

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?

mlrsrt8 commented 4 years ago

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.

aradapilot commented 4 years ago

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 commented 4 years ago

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?

Arsconyl commented 4 years ago

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.

ragasubekti commented 4 years ago

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).

ragasubekti commented 4 years ago

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 commented 4 years ago

@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?

GottaSlay commented 4 years ago

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.

mlrsrt8 commented 4 years ago

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?

GottaSlay commented 4 years ago

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.

Arsconyl commented 4 years ago

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 ?

GottaSlay commented 4 years ago

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.

Arsconyl commented 4 years ago

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.

GottaSlay commented 4 years ago

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.

hakzsam commented 3 years ago

Do you still experiment issues with RADV?

mlrsrt8 commented 3 years ago

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.

hakzsam commented 3 years ago

On what AMD GPU did you try?

mlrsrt8 commented 3 years ago

Sapphire Nitro+ RX 590 8G

hakzsam commented 3 years ago

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

Arborescent commented 3 years ago

Regarding racing wheel support, this is what I have found so far.

My setup:

I went to the wine control panel...

WINEESYNC=1 WINEPREFIX=/opt/steam_apps/steamapps/compatdata/1222680/pfx WINEPATH="~/.local/share/Steam/steamapps/common/Proton\ -\ Experimental/dist/bin" ~/.local/share/Steam/steamapps/common/Proton\ -\ Experimental/dist/bin/wine64 control

And under "Game Controllers", you can see that the racing wheel is detected by wine. You can also see how the different axis are detected:

You can see that all buttons work, and force feedback works. It's just that the game detects the wheel as a regular controller rather than a wheel.

If you press the 3rd pedal half-way, y becomes 0 and you menus becomes usable.

Under Windows, the documentation asks you to install Logitech G Hub in order for the wheel to work. I wonder how this affects things.

dfryer1193 commented 3 years ago

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.

NodokaHanamura commented 3 years ago

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

ZereoX commented 3 years ago

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.

kisak-valve commented 3 years ago

Hello @mlrsrt8, based on the last comment, can you retest with Proton 5.13 and an updated mesa stack and see if you can reproduce the issue you were seeing?

If you are, then 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 share an updated system information from Steam (Steam -> Help -> System Information) in a gist.

mlrsrt8 commented 3 years ago

Hi, thanks for the update, unfortunately, I just retested it, and I still have the problem. I am running Mesa-21.2.0-devel with Kernel 5.11 on Ubuntu 20.04 LTS with Proton 5.13-6.

My system information:

https://gist.github.com/mlrsrt8/34a4a03163bfceb7a96df98620d8dbda

steam-1222680.log

kisak-valve commented 3 years ago

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?

mlrsrt8 commented 3 years ago

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.

kisak-valve commented 3 years ago

Looking at the system information and Proton log, there's access violations (c0000005) that are loosely near threads loading up rsaenh.dll that leads to something dying, but the position in the log hints that might be something non-essential in Origin? I'm also seeing 627.293:088c:08e0:trace:seh:dispatch_exception code=c0000005 flags=0 addr=000000014E3F80CF ip=4e3f80cf tid=08e0 and wine: Unhandled page fault on read access to 0000000000000288 at address 000000014E3F80CF (thread 08e0), starting debugger... later in the log, and could be the actual game dying. That part I'm not really able to decipher any usable hints on my own.

I'm not seeing a known issue with your system information and it hints that your system is mostly healthy overall.

Blind guess that some left over from previous test attempts is interfering. Maybe try moving/removing the wine prefix at ~/.local/share/Steam/steamapps/compatdata/1222680 and see if that has an effect?

Tentatively dropping the RADV label until there's a stronger hint that @mlrsrt8's issue is video driver related.

mlrsrt8 commented 3 years ago

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

nonchip commented 2 years ago

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

7HEPOW commented 2 years ago

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.

howels commented 2 years ago

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