Open guustflater opened 4 years ago
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
Need for Speed™ Heat, OriginThinSetup problem
Issue transferred from https://github.com/ValveSoftware/Proton/issues/6236. @septemba posted on 2022-10-16T13:29:55:
OriginThinSetup black window (https://imgur.com/a/SC0bdFM) The window seems to function but it's not that useful since i can't see what i am clicking
Launch Game
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.
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.
Hello @KibaGasteiz, your issue is being tracked at #6262 / https://github.com/ValveSoftware/steam-for-linux/issues/8864.
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)
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.
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)
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.
Logitech G29 Detected as an XBOX Joystick on NFS HEAT
Issue transferred from https://github.com/ValveSoftware/Proton/issues/6647. @izzijaz posted on 2023-03-25T18:01:21:
Logitech g29 Driving wheel is not bwing detected as a Wheel but as a joystick when i launch NFS heat.
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.
For most other NFS games, such as NFS Most Wanted, NFS Underground 2, etc. the way to enable wheel support was:
(NOTE: For NFSU2 specifically, the workaround above will break the commonly used widescreen fix workaround. If that is your case, rename the dinput8.dll from the workaround to d3d9.dll)
For Heat, the steps above will not be enough to produce a playable experience. The wheel will still be detected as an Xbox controller.
Because of this, steering to the sides (Axis 1) will work, but the accelerator pedal (Axis 2) will be interpreted as the Up and Down commands which will interfere with your ability to use the game menus. And because NFS Heat does not provide a configuration menu for the Xbox joystick, there is no direct way to fix this within the game itself.
If using Steam, enable the "Disable Steam Input" setting for this game from the Controller configuration.
Using Oversteer, set the wheel rotation range to a lower value, for example, 450.
To make the pedals usable, you can use AntimicroX to remap the pedal axis:
After these steps, you can steer, accelerate and break, which makes the game playable. You can remap other buttons and axis using AntimicroX as needed.
The menu issue caused by Axis 2 (accelerator pedal) persists. The workaround is to press the accelerator halfway through while using the menus so that the "down" key doesn't get pressed automatically, and the solution there would be to remap that axis to something else.
This greatly reduces the impact of the problem. You will have no in-game force feedback as a result of this workaround.
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
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
Hello @Alexander-Wilms, that reads like a kernel or video driver issue of some kind. Can you SSH into the system once it's entered the quirk state and see if there's any hints in dmesg or with the system logs?
Hi guys, I am able to run this on AMD 6700xt but with a terrible frametime, which makes everything VERY laggy from cut-scenes to game-play.
My specs: OS: Garuda (Arch) Arch: x86_64 Kernel: 6.5.9-zen2-1-zen Desktop: KDE Display Server: wayland CPU: 13th Gen Intel(R) Core(TM) i5-13500 GPU : AMD Radeon RX 6700 XT (navi22, LLVM 16.0.6, DRM 3.54, 6.5.9-zen2-1-zen) Driver: Mesa 23.2.1-arch1.2 Proton: GE-Proton8-21, proton experimental, hotfix, 8, 7
FrameTime screenshot: DXVK_HUD screenshot
Need for speed Heat (1222680)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7214. @SherLock707 posted on 2023-10-30T10:29:09:
Lot of stutter in gameplay with 10-15 FPS in lowest setting High frame-time observed through DXVK_HUD and mangoHud, Graph is red/at peak all the time
Expected: Game launches and is playable without stutter or frame-drops
Actual: Game launches, high frame-time in cut-scene and worst in game leading to laggy gameplay with 10-15 FPS and framerate graph is all in red (1 second +)
Hi guys, I am able to run this on AMD 6700xt but with a terrible frametime, which makes everything VERY laggy from cut-scenes to game-play.
My specs: OS: Garuda (Arch) Arch: x86_64 Kernel: 6.5.9-zen2-1-zen Desktop: KDE Display Server: wayland CPU: 13th Gen Intel(R) Core(TM) i5-13500 GPU : AMD Radeon RX 6700 XT (navi22, LLVM 16.0.6, DRM 3.54, 6.5.9-zen2-1-zen) Driver: Mesa 23.2.1-arch1.2 Proton: GE-Proton8-21, proton experimental, hotfix, 8, 7
FrameTime screenshot: DXVK_HUD screenshot
Need for speed Heat (1222680)
Issue transferred from #7214. @SherLock707 posted on 2023-10-30T10:29:09:
Compatibility Report
- Name of the game with compatibility issues: Need for speed : Heat
- Steam AppID of the game: 1222680
System Information
- GPU: AMD Radeon RX 6700 XT (navi22, LLVM 16.0.6, DRM 3.54, 6.5.9-zen2-1-zen)
- Video driver version: Mesa 23.2.1-arch1.2
- Kernel version: 6.5.9-zen2-1-zen
- Link to full system information report as Gist: https://gist.github.com/SherLock707/0f50c893aeaf07e5cb1faeaa9200f4bc
- Proton version: 8.0-4 | Experimental |Hotfix
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
Lot of stutter in gameplay with 10-15 FPS in lowest setting High frame-time observed through DXVK_HUD and mangoHud, Graph is red/at peak all the time
Reproduction
- launch steam
- Install Need for speed: Heat
- Turn on compatibility in setting
- Select run in steam
Expected: Game launches and is playable without stutter or frame-drops
Actual: Game launches, high frame-time in cut-scene and worst in game leading to laggy gameplay with 10-15 FPS and framerate graph is all in red (1 second +)
Proton log
Fixed! I had zen kernel, switched to AMD kernel 6.6.0-AMD works well now, 90FPS+ at ultra 1440p with GE-proton 8-22
NFS Heat doesn't open.
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7384. @Faccinetto posted on 2024-01-04T17:38:22:
Is a 1.3GB file, so, I can attach via post, this is the message shows (I tried to upload a .zip file):
Also, I upload the log on Google Drive: https://drive.google.com/file/d/1YGl0cz1W1n_wBV1BAprD9-EnZE2IOehU/view?usp=sharing
I can't make Need for Speed Heat run, so far. I've tried proton-ge and proton-experimental, and all that I get is this black screen, shortly after the game crashes. Also, I've try one comment for use proton 5.0 and PROTON_NO_ESYNC=1 and Steam don't install EA App script.
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!
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.