search

ValveSoftware / Proton

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

GRID Legends (1307710) #5619

Open cow-killer opened 2 years ago

cow-killer commented 2 years ago

Compatibility Report

System Information

I confirm:

Had to upload Proton log as a zip file since it's so huge (~60 MB): log.zip

Symptoms

First, upon launching the game, the game thinks I'm using an AMD card and tells me my graphics drivers are out of date:

startup_error

I can ignore the error and continue playing the game. However, the game crashes after a race. Not sure what's causing it.

Reproduction

  1. Install GRID Legends
  2. Launch to get the AMD driver error
  3. Ignore the error, continue playing the game, do a race, crash when the race is over
CSahajdacny commented 2 years ago

Have you tried with PROTON_ENABLE_NVAPI=1 and a dxvk.conf file on the folder of the game executable with the line dxgi.nvapiHack = False ?

cow-killer commented 2 years ago

Yup, after trying that the results weren't any different.

cow-killer commented 2 years ago

Okay, scratch that. I forgot to delete the "#" in dxvk.conf. I don't get the launch error anymore but the game still crashes after a race.

the-outcaster commented 2 years ago

So, after doing a little more research, I've come to the following conclusions:

200Puls commented 2 years ago

The game crashes after every race for me on AMD too (Radeon 5600XT). I get to race the initial race and it will crash after the end of the race. Having to race that initial race again next time.

the-outcaster commented 2 years ago

@200Puls try setting the graphics to medium or lower

200Puls commented 2 years ago

Hi @linuxgamingcentral ,

thanks for the tip. That did actically work. Dropping from ulta hight to medium fixed the crashing. Has anybody tried to figure out the single setting that causes this?

the-outcaster commented 2 years ago

I haven't spent the time trying to figure out what setting it is, and I got the game as part of my EA Play subscription. So since my subscription is no longer active I can't test this anymore.

Dar13 commented 2 years ago

I'm getting a crash on start-up after a long (30+ seconds) black screen. Occasionally I'll get through and then won't have any crashes even after races but I've only managed that once or twice between 10+ attempts.

GPU: AMD Vega 56 CPU: AMD Ryzen 9 5900X RAM: 32 GiB Proton version: 7.0-3 OS: Arch Linux, kernel 5.18.6, mesa 22.1.2

Running with PROTON_LOG=1 %command% -dx12, log attached. steam-1307710.log

saschabrunner commented 2 years ago

System Information

Logs: (including Proton and kernel logs) steam-1307710.zip

Symptoms

Launching the game with high graphics preset (game needs reboot after changing graphics settings!) the game will crash after almost every race, sometimes even causing a full system crash. This happens right when it transitions to the loading screen.

Reproduction

  1. Launch game
  2. Ensure graphics are at least set to high preset, restart game after changing preset
  3. Launch Benchmark from advanced section in graphics settings
  4. Wait for benchmark to finish
  5. Continue past benchmark results
  6. Either game or system crashes/freezes
leillo1975 commented 2 years ago

It is common for the game to crash between loading screens after races. It also has no online connection, and notifies you at startup. I should clarify that I have tested with the Origin version and Proton-GE 7-21 (@GloriousEggroll ) through Lutris.

GenocideStomper commented 2 years ago

I too run the Origin version with Lutris-GE-Proton7-19. I don't have the crashing issues, and the game runs surprisingly well with dx12 and on my Nvidia Pascal-generation card.

The biggest issue for me is that I too don't get online connection, and by the looks of it on ProtonDB, other people don't have that too. I assume multiplayer doesn't work because of this.

cooperaj commented 2 years ago

I realise now that although my Steam deck review on proton-db says it works fine (which it does) I forgot to mention that I'm running the Origin version - not the Steam version. The online thing I can only imagine is an anti-cheat that is not functional. This makes me sad as I imagine online play would be quite fun.

Dar13 commented 2 years ago

With kernel 5.18.14-arch1-1 and Mesa 22.1.3, I no longer have the very long wait before entering the main menu and no longer have the periodic crashes during that wait.

I do still have crashes after races when graphics settings are set to 'Ultra'.

saschabrunner commented 2 years ago

Just to update on my previous post here, I tried AMDVLK Open (2022.Q3.3-1) today and it runs the game stable and doesn't crash the game or my system in between races. Performance roughly gets cut in half compared to RADV however.

RADV still crashes on loading screens after a race (Kernel 5.19.2-arch1-2 and Mesa 22.1.6-1 on Arch).

Also, online services for the game don't connect either way unfortunately.

minervadreaming commented 1 year ago

Issue is still present on the latest build of Steam Deck. In game mode, game won’t launch because the error is in the background. In desktop mode, error can be bypassed but sometimes game won’t launch.

fastoslinux commented 1 year ago

RX 580 - Steam Flatpak - mesa 22.3.2 keeps crashing after some time.. proton 7.0-5

Etaash-mathamsetty commented 1 year ago

I tried playing this game with wine-tkg-staging 8.0 + dxvk 2.1 + vkd3d 2.8 and online seems to work as well! at least when I am playing with the EA app, the game requires shared resources, which is why tkg patches are needed (shared resources are part of proton exp already, so if you are using proton exp, don't worry about it). no crashes here unless you alt-tab

I still need to do more testing though

fastoslinux commented 1 year ago

with protonGE works

Etaash-mathamsetty commented 1 year ago

Online working really well

Etaash-mathamsetty commented 1 year ago

I played for a few hours, I didn't see any crashes (even when online), was a flawless experience with the EA app (unless you alt tab :p)

wine version: wine 8.0-rc5 tkg staging

Tkg/proton patches are REQUIRED, the game seems to use shared resources

Mesa version: Mesa-git with rx 6800

Etaash-mathamsetty commented 1 year ago

found the code responsible for getting rid of the outdated driver popup: https://github.com/ValveSoftware/wine/blob/f497ac98efbb3c924a7ab9630963b88e20385ca4/dlls/amd_ags_x64/amd_ags_x64_main.c#L539

all you have to do in theory is add a DLL override, since normal wine doesn't have this dll, I simply replaced it and the popup is gone!

zaskokus commented 1 month ago

Hi @linuxgamingcentral ,

thanks for the tip. That did actically work. Dropping from ulta hight to medium fixed the crashing. Has anybody tried to figure out the single setting that causes this?

Did you figure it out by any chance?

sklynic commented 2 weeks ago

Hi @linuxgamingcentral , thanks for the tip. That did actically work. Dropping from ulta hight to medium fixed the crashing. Has anybody tried to figure out the single setting that causes this?

Did you figure it out by any chance?

sorry for the ping, I believe the setting is "Texture Quality", set it to Medium or below should solve the after-race crash issue.

However I only have a graphic card with 6GB of VRAM (Nvidia RTX 3060 laptop), is it running out of VRAM then crash?

zaskokus commented 2 weeks ago

Replying to https://github.com/ValveSoftware/Proton/issues/5619#issuecomment-2348593438

I spent 3 days and got banned for a day by denuvo crap actually for it (every start of the game == new proton prefix id == new computer, times over 100 crashes I had).

The issue seems to be more complex, to the point it seems like a VRAM allocation issue.

I started with everything set to all-lowest. I was able to reliably complete a race with everything maxed out with exclusion of: AA, XeSS, Textures, Crowds, Shadows, Smoke shadows -- these were set to off/lowest.

And now the fun begins. Setting shadows to high did not let me move textures to even medium (same with smoke shadows or crowds). Having crowds off and shadows to the lowest has once allowed me to have textures high, but crashed next race, and medium reliably for all the time.

AA has also effect on VRAM usage - was making things even less reliable, but I keep it disabled most of the time, as I use XeSS at balanced for most of the time. With crowds off and shadows to low, textures set to medium and everything below that 100% maxed out - I am able to have 90-95% success rate past the race.

Also - fsck denuvo. It blocked me from playing a legally purchased game for a stupid reason.