Damn dotnet....

I'm not sure it's totally due to NetFramework. I installed the windows version of steam in a 32-bit prefix via lutris and for some reason the installation continues to fail even though it should work in a 32-bit prefix. but despite this the game starts after the failure of the netframework installation (Steam tries to install it at every attempt to start the game and the installation via winetricks fails as happens in the 64bit version for some reason).
I wonder if it is due to some error in the implementation of proton in steam. In the 32bit prefix the game does not start if grid2.exe is executed directly, unlike other steam games, it does not even attempt to start steam-windows which is in the same prefix. only works if started from windows-steam.
when I have time I will try to create a 64bit prefix with steam-windows and see if the game work.
sorry for my english
GPU:Gtx970
Cpu:Amd FX 8350
Nvidia Driver : 418.43
Proton 3.16.8
Lutris Wine Runner : wine 4.3

UPDATE
I installed windows-steam in the 64 bit prefix created by proton during the first start of GRID2 with steam play in ~/.steam/steam/steamapps/compatdata/44350/pfx and as already mentioned the installation of NetFramework fails but the game works on windows-steam with the same prefix that uses linux-steam for grid2. later I tried to start Grid2 with linux-steam and as I expected the game won't start.
The problem does not seem to be corelated with the lack of NetFramework. I also add that in the windows-steam version, the game freezes in the loading screen of the career mode.
this happens even with a clean 32bit prefix, but I think it's something related to having copied the game from linux-steam into the windows-steam folder. to the other people who installed grid2 through lutris this does not happen.

NOTE:
if the NetFramework installation does not finish, go to the steam library and to the .vdf file located in steamapps / common / Steamworks Shared / _CommonRedist / DotNet / 3.5 / installscript.vdf
Change:
"process 1" "%INSTALLDIR%\_CommonRedist\DotNet\3.5\dotnetfx35.exe"

With:
"process 1" "%INSTALLDIR%\_CommonRedist\DotNet\3.5\dotnetOTHERfx35.exe"
.
if you're stuck at the "preparing to start game" screen, check the game's integrity(ONLY ON WINDOWS-STEAM, Don't do it on Linux-Steam).

UPDATE2
the game now starts but remains stuked on the loading screen (I think it's just my problem), I don't know what happened. I will try with a clean prefix and I will update you.

UPDATE3
I tried everything but couldn't figure out what happened.
the strangest thing is that even a copy of the working prefix does not start the game, only the original prefix continues to work.

https://youtu.be/rNFmsEIk7DA

Log+Settings files:
Steam_log.tar.gz

UPDATE:THE MAGIC EXIST.

I have understood which "" file "" causes the problem.
in the folder: "/pfx/drive_c/windows/system32/"
there is a folder called "mui". I thought the culprit was a dll or a symlink but I was wrong. the folder is completely empty !!! .
the result of "ls -lha | grep 'mui'" gives as a result:
drwxr-xr-x 2 danilo danilo 4,0K 19 Mar 16.33 mui
drwxr-xr-x 2 danilo danilo 4,0K 19 Mar 22.19 mui_old

mui_old is the working folder and mui is the copy of the same folder, the original works and starts the game and the copy does not.

I no longer know what to think, I begin to believe in magic and fairy worlds.

P.S.
Steam installed in the proton prefix is required

UPDATE
I figured out how to start the game.
https://www.youtube.com/watch?v=zwfCZJd56AY&feature=youtu.be

I can't start career mode(Note that this also happens to me with lutris in a 32bit prefix and doesn't seem to happen to other people) , but as I wanted to prove, netframework is not the cause of the impossibility of starting the game.

Linux-Steam breaks the game, so you need to install Windows-Steam in the GRID2 prefix to check the integrity of the game files.
NEVER check the integrity of game files from Linux-Steam, otherwise the game will break again.
If you need to update the game or install the dlc, do it via Windows-Steam.

Windows-Steam is required to start the game. It seems to be corelated to the files in the folder: "PROTONGRID2PREFIX/pfx/drive_c/Program Files (x86)/Steam2/config/", altering them does not start the game.

This is probably the reason why it doesn't work, in fact you have to start the game through Windows-Steam the first time.

I don't know if it can help, but I realized that the steam folders needed to start the game are:
config, bin, clientui, drivers, graphics,appcache.

even if the cause of the grid start problem is due to the drm, I don't understand what these folders are for.

Looks like this game uses CEG (#753).

Does Valve recognize CEG as actually preventing some games from starting?

(You haven't closed that topic and make a reference to it but yet at least one CEG labelled game does start.)

My log from crash on Linux Mint https://github.com/tele1/Steam.logs/blob/master/steam.44350.Grid2.log

Not working with proton 4.2

Proton 4.2-3 tested, nothing doing for now.
steam-44350.log

Same as @felisucoibi and @lucifertdark on Ubutnu 19.04, Kernel 5.0 stable, Proton 4.2.3.

Not working with proton 4.2.3
OS: Arch Linux x86_64
Kernel: 5.1.3-arch1-1-ARCH
CPU: AMD FX-7600P Radeon R7 4C+8G (4) @ 2.700GHz
GPU1: AMD ATI Radeon R7 Graphics
GPU2: AMD ATI Radeon R9 M270X/M280X

Proton 4.2-7game not working.
Hardware Info: https://github.com/tele1/Steam.logs/blob/master/Hardware Info
Log: https://github.com/tele1/Steam.logs/blob/master/2019.06.12/GRID.not working.steam-44350.log.zip

Same issue with Proton 4.11-2.

With Proton 5.13 seems a bit different, now there's an exception thrown somewhere because I see on the log

6966.165:0058:0084:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x17dfda0,4,(nil)) 6966.166:0058:0068:trace:seh:dispatch_exception code=6ba flags=0 addr=000000007B010E0E ip=7b010e0e tid=0068 6966.166:0058:0068:trace:seh:dispatch_exception rax=000000007b010dc0 rbx=0000000000f9f1a8 rcx=0000000000f9eed0 rdx=0000000000000000 6966.166:0058:0068:trace:seh:dispatch_exception rsi=00000000000000cc rdi=00000000000000be rbp=0000000000000000 rsp=0000000000f9eeb0 6966.166:0058:0068:trace:seh:dispatch_exception r8=0000000000000000 r9=0000000000000000 r10=00000000008ead18 r11=0000000000f9ecd8 6966.166:0058:0068:trace:seh:dispatch_exception r12=0000000000f9f1a8 r13=00000000008e76b0 r14=0000000000000000 r15=00000000ffba0000 6966.166:0058:0068:trace:seh:call_vectored_handlers calling handler at 0000000067A0D3E0 code=6ba flags=0 6966.166:0058:0068:trace:seh:call_vectored_handlers handler at 0000000067A0D3E0 returned 0 6966.166:0058:0068:trace:seh:call_vectored_handlers calling handler at 000000007B636150 code=6ba flags=0 6966.166:0058:0068:trace:seh:call_vectored_handlers handler at 000000007B636150 returned 0 6966.166:0058:0068:trace:seh:RtlVirtualUnwind type 1 rip 7b010e0e rsp f9eeb0 6966.166:0058:0068:trace:seh:dump_unwind_info **** func 10dc0-10e47 6966.166:0058:0068:trace:seh:dump_unwind_info unwind info at 000000007B0A1394 flags 0 prolog 0x11 bytes function 000000007B010DC0-000000007B010E47 6966.166:0058:0068:trace:seh:dump_unwind_info 0x11: subq $0xc8,%rsp 6966.166:0058:0068:trace:seh:dump_unwind_info 0xa: pushq %rsi 6966.166:0058:0068:trace:seh:dump_unwind_info 0x9: pushq %rdi

Full log 5.13_steam-44350.log

Compatibility Report

• Name of the game with compatibility issues: GRID 2
• Steam AppID of the game: 44350

System Information

• GPU: AMD Radeon RX 580
• Driver/LLVM version: Mesa 21.2.4/ LLVM 12.0.1
• Distro version: Arch Linux
• Link to full system information report as Gist:
• Proton version: experimental-6.3-20211027

I confirm:

• [ ] 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

• Crash after selecting 'World Series Racing' or 'GRID Online' in the Main Menu.

Reproduction

• Start the game.

Logs

• grid2_avx_d3d11_start_grid_online.log
• grid2_avx_dxgi_start_grid_online.log
• steam-44350_start_grid_online.log
• grid2_avx_d3d11_start_world_series_racing.log
• grid2_avx_dxgi_start_world_series_racing.log
• steam-44350_start_world_series_racing.log

Notes

Retest for CEG DRM.

Can confirm the same behavior on Ubuntu 21.04

It seems to work mostly OK with the bleeding-edge beta of Proton Experimental.

Signing in to RaceNet doesn't work, but I'm not sure if that's a bug or just because the game is too old?

I was able to get this to launch with only minor issues, detailed below, I will list the steps to prepare as if you already have the (nonworking) game installed:

1. Go to the tools section of steam, locate proton experimental, right click > properties > betas > bleeding-edge
2. Right click on Grid 2 > properties > Compatibility > force > proton experimental
3. Right click on Grid 2 > properties > local files >verify integrity of game files (It should say it needs to redownload some)
4. After download completes, play the game

Doing these steps I was able to launch and play the game. On my first launch, it did not let me change the graphics options until I was seconds before starting a race. Neat in concept if you're on a console, but not neat if you're on a PC and it's running medium settings 720P Changed settings to max 1080p, ran fine. As others have said, Racenet doesn't work, but I don't think this is a proton issue, you can find forums talking about being unable to connect to racenet on other places running it on playstation and windows. You can enter the online game mode, but I was unable to find a race, and could only host one. I was unable to launch an online session solo though, so I'm uncertain if this works. I also tried splitscreen since I saw it was available and saw this game supports steam remote co-op, and it worked fine, I didn't have 2 controllers to try with, but it worked fine with one person on keyboard and one on controller.

✅ - Game Launches Fullscreen
✅ - Video cutscenes play with no issues
❌ - Game is able to take input from controller OR Keyboard, must choose at launch, cannot hot-swap between
✅ - Rumble feature works on controller
✅ - No visible graphical issues, played 4 races with no issues
❌ - Some online features appear to be disabled

Can confirm that the game seems to work with Steam Beta + Proton experimental on Bleeding-edge.

x - Game is able to take input from controller OR Keyboard, must choose at launch, cannot hot-swap between

This seems to be a game limitation not a Proton limitation.

x - Some online features appear to be disabled

Same, when "Singing into Racenet" shows then "connection refused" message is shown.
Online racing not sure if no one is playing or does not work.

Steam integration seems to be work fine - Leaderboards shows the Steam Friends' names on it.

Re-tested the game with Proton Experimental without the Bleeding-edge beta, still works.

Proton: 1635803517 experimental-6.3-20211101
SteamGameId: 44350
Command: ['/home/user/.steam/steam/steamapps/common/grid 2/grid2.exe']
Options: {'forcelgadd'}
depot: 0.20211014.30
pressure-vessel: 0.20210906.2
scripts: v0.20210917.0-0-g1cf127d
soldier: 0.20211013.0 soldier 0.20211013.0
Kernel: Linux 5.11.0-38-generic [#42](/issue/ValveSoftware/Proton/42)-Ubuntu SMP Fri Sep 24 14:03:54 UTC 2021 x86_64
======================
esync: up and running.

Please notice that if you manually remove the compatdata at /home/user/.steam/steam/steamapps/compatdata/44350 you need to verify local files integrity so that the game starts again.

The game crashes to desktop sometimes. I felt this when I try to see online content, or the track times of my friends. This is a log:
steam-44350.zip

Also , the Logitech G29 Wheel works after redefine the keys with the buttons and axes, and have FFB, but when you restart the game you must make this again, because this bindiings was not saved on game.

Also , the Logitech G29 Wheel works after redefine the keys with the buttons and axes, and have FFB, but when you restart the game you must make this again, because this bindiings was not saved on game.

Did you load the same Save? I noticed that the game stores the controls settings into the Save so starting a new save requires settings the controller settings again.

The game crashes to desktop sometimes. I felt this when I try to see online content, or the track times of my friends.

Same for me but I was able to reproduce it on specific Steam integration features.

• Clicking to open the DLC Store with Proton the game crashes, works fine on Windows (opens Steam store page which is empty)
• Trying to open a player Steam Profile page crashes the game, works fine on Windows.

I have looked at the logs but I have no idea if this is related to Proton, Wine, Steam or Steam CEG.

PS: Also tested Racenet on Windows and it seems to work fine.

Did you load the same Save? I noticed that the game stores the controls settings into the Save so starting a new save requires settings the controller settings again.

Yes, I did it

PS: Also tested Racenet on Windows and it seems to work fine.

Seems that game has a problem with network with Proton

I Can confirm that the game seems worked (probably still working) with Steam Beta + Proton experimental.
OS: Linux Mint 20.2 Uma
Kernel: 5.13
GPU: GeForce GTX 660
driver: nvidia v: 470.82.00

I was able to fix the game not starting by verifying local game files and then starting the game again. This re-triggers Steam CEG DRM generating the game executable.

Game doesn't launch at all, tried multiple proton versions. Log is proton experimental.

steam-44350.log

I can confirm the game crashes after the logo fmvs on my oled deck with proton Experimental too, tried it with proton 8.0-5 and 7.0-6 and they both just silently crashed without getting to the logos.

steam-44350.log

Update:
Apparently Grid Autosport also stopped working with proton 9.0 checking protondb and the community hub, I can't check that one though since it got delisted before I could buy it, bringing it up since it's deck verified and likely might be suffering from the same problem this game has.

Replying to https://github.com/ValveSoftware/Proton/issues/1647#issuecomment-2234878784

Was able to get the same logo fmvs crash using "GRID 2 v1.0.85.8679 [MULTI8] Fixed Files" from GameCopyWorld then GE-Proton 7-33 got it working flawlessly. Not ideal but works!

@alasky17
Sorry for the ping, but I believe like Alan Wake and American Nightmare, Grid 2 (And I have a feeling Grid Autosport too), needs NVAPI turned off to avoid the game crashing before the title screen, at least for the Steam versions when I tested them.

I don't have Grid Autosport to check, but considering both games on protondb and the community hub said they stopped working on proton 9.0 and above, I think it's the same issue.

Hello @waspennator, your ping is highlighting games that have already been evaluated: c48b88d 75a1d3f e8ae65d (These commits are still working their way into more stable builds of Proton)

Terribly sorry about that, I wasn't sure if this was looked into or not and I couldn't find that specific commit that turned off nvapi for the 2 games cause it's hard to comb through sometimes with how many commits go through.

Edit: I can confirm that using experimental bleeding edge fixes Grid 2 crashing before the title screen on my oled deck.

Fix has officially hit proton stable and works fine for my steam copy now.

@waspennator FWIW - we have a section in the proton script with a list of all the games with NVAPI disabled (that's just the file called "proton" in the common/Proton [version X] folder. That is probably the easiest place to check - indeed it is hard to comb through all the commits for all the submodules :)

Right now, this section is ~line 1129 - you can search for "disablenvapi" to skip right to the correct section. I hope this helps! We greatly appreciate all the feedback about the random games that are breaking with nvapi enabled so that we can investigate them :)

Fix has officially hit proton stable and works fine for my steam copy now.

Can confirm that Proton Experimental is working now, I then tried verifying files after that and the game still won't launch without the GameCopyWorld exe's for me. Something to do with CEG DRM as someone mentioned previously?

The game crashes after the logo appears. I tried a bunch of versions of Proton and Proton-GE, from 6 to the latest, nothing helped.

UPD: I found what the reason was specifically in my case. I saw that users also complained about Alan Wake, and I decided to check how the GOG version of the game would work in Heroic Launcher. It turned out that Alan Wake also does not work. I started to figure it out and saw an error in the logs related to MangoHud, and remembered that I had it enabled at the system level. I disabled MangoHud and rebooted the system. And voila, Alan Wake and GRID 2 started and work. As I understand it, MangoHud is incompatible with 32bit games, which leads to an immediate closure of the game.

@kar1kam1 it's possible you're missing the 32bit version of mangohud

Tried launching Grid 2 based on these new posts and vanilla OOTB just works™ now.