Sorry, the second time I started the apliaction works , and runs awesome with no errors and a excellent framerate....I can't explain.
Only one thing, my Logitech G27 wheel is not detected, but my Steam Controller works perfect

Intermittently have (presumably) the same problem as the OP - either nothing launches, or a black screen launches (and I can't close the black screen, I have to reboot my PC).

When I get in-game, it works pretty much perfectly: 60fps on max settings, and my Logitech F310 gamepad works out of the box with Proton 3.7-5 beta (it didn't work at all with Proton 3.7-3). My Logitech G29 wheel doesn't seem to get picked up at all though.

Can't seem to load up my save file from steam cloud - it says that it's corrupted, but I vaguely recall encountering this in Windows too

System Info

Won't start on my machine.

It appears that this game is affected by #165. This workaround fixes the issue on Nvidia GPUs.

System info: https://gist.github.com/vanyasem/f787469ec8c50cdd3728340ef4c73269

Some days ago I try to play DIRT but only havea black screen with the DXVK_HUD in the top left corner or the Screen. If I switch to Proton 3.7.3 it works again. The black screen is displayed with 3.7.5 and 3.7.6 beta

@leillo1975 this is most likely not related, as it works for me with 3.7-6. Please check the issue that I linked above.

Thanks vanyasem, now works with 3.7.6 Beta!

There is something very strange about the behaviour of this game.

On my Radeon RX 470 system using the FOSS drivers from Padoka's PPA, at the first launch I only got a black screen with the Dirt 3 logo in the middle. This screen captured the mouse input in a way that made the mouse cursor invisible even when switching away from the game's screen by changing window focus with something like alt+tab or when switching to a different workspace. So I effectively couldn't kill the process using the System Monitor GUI because the mouse was captured, and the only way to kill the process was to do it via a terminal (I was able to open one with ctrl+alt+T) with the command kill -s 9 .

After running the game a second time (with absolutely no modifications or changes to anything at all) I got past the initial logo and was presented with the AMD Gaming Evolved and the Codemasters intro videos. After that, crash.

Third launch, the game seems to work completely normally. I was able to play the game at 1080p, 8xMSAA, and the highest other graphical settings at a solid 60 fps. Radeontop showed the maximum GPU usage was around 67%. From this play session I got a whopping 16 MB log that was mostly due to a 170782.964:0025:0075:err:d3d:wined3d_debug_callback 0x7f0f700: "GL_INVALID_ENUM in glMatrixMode(mode)". message being repeated over and over. I forgot to copy/rename this log and it was lost the next time I ran the game.

Fourth launch: completely black screen, no logo or anything else. htop doesn't show the process taking any CPU cycles really, and iotop doesn't show any IO activity. No significant GPU activity from radeontop either so no 3D stuff is running. This is the log: https://gist.github.com/veikk0/8c8f319177cc26b8000924156a2df66a

Sixth launch: black logo screen like the first launch, except my cursor isn't being held hostage. As the game didn't progress beyond this screen after about a minute of waiting and the process was only using about 2 percent of a single CPU core, I killed the .exe via the System Monitor. Log: https://gist.github.com/veikk0/16a5fb18992a99c6fcf661e9c50e6724

Seventh launch: same thing as the previous launch, except wine64 is taking up 100% of one CPU core. Not sure if I just didn't notice it on previous launches. No other system activity, even IO, so it's not like it's busy loading game data or anything. Log: https://gist.github.com/veikk0/c501fd0044eaf45a63b531b190a50076

This testing was done on Proton 3.7-6. Switching to Proton 3.7-6 Beta made no difference, black logo screen still, except this time dirt3_game.exe was taking two CPU cores to the max. No IO activity.

This isn't actually the first time I'm trying out the game. I tried launching the game a few times before, on the same system but with a Radeon R7 260X video card and stock 18.04 FOSS graphics drivers, and and on the same system but using my current Radeon RX 470 with the default 18.04 FOSS graphics drivers. All of these attempts resulted in the mouse-captured logo screen issue and I didn't pursue the issue further at those times.

I would also include other logs but I can't see proton_run and the associated files in my /tmp/. Has this method been replaced by the current way of logging?

My system info: https://gist.github.com/veikk0/d0ebb1ddda8f9582d1799df343bfefe5

Intermittently have (presumably) the same problem as the OP - either nothing launches, or a black screen launches (and I can't close the black screen, I have to reboot my PC).

When I get in-game, it works pretty much perfectly: 60fps on max settings, and my Logitech F310 gamepad works out of the box with Proton 3.7-5 beta (it didn't work at all with Proton 3.7-3). My Logitech G29 wheel doesn't seem to get picked up at all though.

Can't seem to load up my save file from steam cloud - it says that it's corrupted, but I vaguely recall encountering this in Windows too

System Info

CTRL+ALT+F3 log in, run top to find the PID of the game then kill -9 (PID) then CTRL+Alt+F2 to get back to your still running Desktop session.

I was testing if there was a GPU hang still happening with Intel Mesa and it seems fixed. However, the game froze after it being open for a long time. The messages that appeared when it froze are:

21553.818:0008:002a:err:ntdll:RtlpWaitForCriticalSection section 0x7297f68 "?" wait timed out in thread 002a, blocked by 0057, retrying (60 sec)

I noticed other Wine software can cause this message when opening, it's strange DiRT 3 triggered it after being open for so long.

System specifications and the log.

System Information

• GPU: GTX 970
• Driver/LLVM version: NVIDIA 396.54
• Kernel version: 4.4.0-135-generic
• Link to full system information report as Gist
• Proton version: 3.7-7 Beta

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

steam-321040.log

Symptoms

Experiencing the same issue and as @leillo1975 and others

I only obtain a Black Screen

Result is the same using DXVK_CONFIG_FILE with NVAPI workaround:

• dxgi.customDeviceId = E366
• dxgi.customVendorId = 1002

Reproduction

• Select the title within your Library using the Steam client and press the Play button

Dirt 3 Complete Edition (321040)

Issue transferred from #1734.
@kassindornelles posted on 2018-10-13T23:06:58:

Whitelist Request

• Name of the game to be whitelisted: Dirt 3 Complete Edition
• Steam AppID of the game: 321040

System Information

• GPU: GTX 750 2 GB
• CPU: Intel Core 2 Quad Q9550 2.83 Ghz
• Driver/LLVM version: NVIDIA Vulkan 396.54.09, works too on 396.54 stable release
• Kernel version: Liquorix 4.18
• Link to full system information report as Gist: https://gist.github.com/kassindornelles/a3f9c31a31b5b6cef5be3d23254b7e08
• Proton version: 3.16-1 Beta

Tested on Antergos Linux, Ubuntu 18.04.1 and Elementary OS. in all of this distros works out of the box.

I confirm:

• that pressing the Play button in the Steam client is sufficient.
• that runtime config options
  are not necessary to run the game.
• that no workarounds are necessary
• Performance is great.

Issues

• I haven't experienced any issues.

Tried this again briefly with Proton 3.16-1 beta

Game still launches with a black screen sometimes; but now when I get in-game, my Logitech G29 wheel works. I have to manually configure it, but I think this is the same in Windows. Wheel buttons don't seem to work in menus, but in-race works fine.

System info

With Proton 3.16-1 Beta there is graphics degradation on resolution 960x540 compared to 3.7-8 Beta.

System specifications, steam-321040.log, dirt3_game_dxgi.log and dirt3_game_d3d11.log

The entire game has difference, but it is already noticeable in the first video:

3.7-8 Beta:

3.16-1 Beta:

Tried this again briefly with Proton 3.16-1 beta

Game still launches with a black screen sometimes; but now when I get in-game, my Logitech G29 wheel works. I have to manually configure it, but I think this is the same in Windows. Wheel buttons don't seem to work in menus, but in-race works fine.

System info

It works!

Thanks for the advice. With my g27 and setting degrees to 240º (using pyLinuxWheel ) I can drive in game with force Feedback

I feel that the wheel don't work properly, I don't play in Windows to this game, but... is possible that the wheel is detected like a gamepad?

Scaling regression in Proton 3.16-1 is now being tracked in #1739.

3620.221:0008:0057:err:ntdll:RtlpWaitForCriticalSection section 0x19cb4f0 "?" wait timed out in thread 0057, blocked by 0034, retrying (60 sec)
3622.179:0008:002a:err:ntdll:RtlpWaitForCriticalSection section 0x7299998 "?" wait timed out in thread 002a, blocked by 0057, retrying (60 sec)

Is happening after 10 minutes playing with Proton 3.16-2 Beta, freezing the game.

With 3.16 this is being very common, while before 3.16 that happened only once since the first Steam Play release (3.7-3), in more than 100 hours and sessions as long as 16 hours (replays playing to test GPU bugs, don't worry).

steam-321040.log

Edit: the following link has a video showing how the game freezes when that messages appear:

https://cdn.discordapp.com/attachments/457747189616214019/502177833234464792/result.webm

System Information

• GPU: Intel HD Graphics 630 (i7-7700K)
• Driver/LLVM version: mesa 18.2.3
• Kernel version: 4.18.16
• Proton version: 3.16
• ArchLinux

I get black screen as reported, I was able to make the game run fine by setting PROTON_NO_D3D11=1, the only issue remaining is that it gets stuck on start at random, sometimes it starts fine, sometimes not (I currently pkill the game and start again). I was also able to avoid the black screen just by setting PROTON_LOG=1, without PROTON_NO_D3D11=1. I dunno why the log would make any difference for it to work.

I think DiRT 3 fails to start because it fails to start the audio streams. It opens two audio streams by default and I noticed that every time no audio stream is open when the game is open it fails to start. If the stream is open then the game works.

It's important to say that the audio streams are open BEFORE the video starts.

Also, if setting to make the WINEPREFIX use alsa instead of pulse, it's possible to see there is a consistent problem with the audio streams, constantly being destroyed and recreated, which cause sound quality degradation. That happens with pulseaudio, but it's not visible, only audible.

@FurretUber do you mean the game works for you only if you're playing some audio before starting it?

There's a very old issue with Linux audio playback which I fix employing a continuous silent noise daemon in the background (through play -qn). Not sure if it's related to what you mean, but due to this service I think I shouldn't be affected. My system is always running a silent noise in the background.

No, I mean that it seems to fail to start because it fails to create the audio stream. Maybe the failure to create the audio stream is a consequence and not the cause, but I observed the following:

-Creates audio streams on startup: works;
-Don't create audio streams on startup: fails;

Here is a video showing a replay showing the audio issue in-game. Maybe that stream problems causes the game freeze if they happen on startup:

https://www.youtube.com/watch?v=iowAAAWcQlE

Edit: another important factor: memory allocation stops earlier too. It stops after allocating around 205 MB of RAM then it freezes. When it works it allocates that 205 MB, the audio streams start (this game opens two streams) and then it allocates more memory.

When it fails it allocates 205 MB of RAM and the audio stream never starts.

Edit 3 (Edit 2 was a typo): Winamp with Wine 3.19 has the same problem:

https://cdn.discordapp.com/attachments/457747189616214019/508309069375995904/saidawine.webm

Dirt 3 Complete Edition launch just fine with the latest proton version, don't have any issue with esync.
played for more than 2 hours without any issue.

There is a regression on 3.16-7 Beta. Game doesn't start anymore.

Hello @Leopard1907, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

I had a similar problem with all games once Proton updated to 3.16-7 Beta, all the games complained that they couldn't find libvulkan.so and failed to start. The only way to fix was to close Steam, delete the directory Steam/steamapps/common/Proton 3.16 Beta/ and the file Steam/steamapps/appmanifest_996510.acf, and restart Steam. Proton 3.16 Beta will be downloaded and it should work again.

Specifically about DiRT 3, I still need to use PROTON_NO_ESYNC=1 to make it work reliably. A shame as this option is the difference between 60 and 35 FPS.

@kisak-valve Here it is.
steam-321040.log

@FurretUber

Witcher3 still works for me.

@kisak-valve Regression is fixed at 4.2-2.

Fixed some games failing or crashing in certain locales like Turkish.

PROTON_NO_ESYNC=1 PROTON_NO_D3D11=1 %command% works for me on Intel Corporation Haswell-ULT Integrated Graphics Controller (HD4400) on Dell E7440 (https://www.cnet.com/products/dell-latitude-e7440-14-core-i5-4300u-4-gb-ram-500-gb-hdd-english/).

Proton 4.2. High load but quite smooth, no need for editing hardware conf xml and I'm not quite sure if this makes any in-game difference.

When not on Intel Graphics, PROTON_NO_D3D11=1 most possibly not needed.

I have a notebook with Intel Core i3-6100U and Intel HD Graphics 520, and I use PROTON_NO_ESYNC=1 %command% to make it work. As Skylake GPU is Gen 9 and has Vulkan support, it's possible to use DXVK with it. Using DirectX 9 option works, but I would wait for iris to work properly with Gallium Nine. Using DirectX 9 option currently, the performance impact is really bad, around 50% FPS loss when using i965 (the default).

When using the iris driver instead of i965 for DirectX 9 (MESA_LOADER_DRIVER_OVERRIDE=iris PROTON_NO_ESYNC=1 PROTON_NO_D3D11=1 %command%), performance is better (still a 20% FPS loss compared to Vulkan) but loading times are really bad. Good thing iris renders correctly too and FPS is higher. Iris is definitively the future for Intel GPUs OpenGL.

With DiRT 3, many bugs on Intel ANV (Vulkan driver for Intel GPUs) were found: at least four different GPU hangs and two memory leaks. Use Vulkan whenever possible.

The biggest problem with this game currently is the need of the PROTON_NO_ESYNC=1: the performance impact on this game is pretty significant. The sound bug wastes a lot of CPU too. On my notebook I observe the GPU render/3D is under 70% load but FPS is below 60 because the CPU load is too high.

Thanks FurretUber! So I read about DXVK and now I know my HD4400 DOES support DXVK (I was assuming it does not). There is tool for checking if vulkan does work on system: vulkan-smoketest. And it was not! I had to enable DRI3 in my xorg conf and now it works. After that I was able to remove PROTON_NO_ESYNC=1 but not NO_DXD11. I've also changed "AccelMethod" from "uxa" to "sna". Now, I'm quite sure it does work smoother.

I was trying to add other system variables like Your's MESA_Loader to my user_settings.py in proton's directory, but I'm not quite sure if it works. Anyone can say something about it? Or it just works with predefined vars?

The MESA_LOADER_DRIVER_OVERRIDE only works with pretty recent Mesa versions and is used to override the OpenGL driver used. By default, Intel HD Graphics uses the driver i965 but with that variable it's possible to set iris, the new OpenGL driver.

Iris is pretty experimental today, so expect bugs and crashes with it. i965 is currently better on nearly all cases, DiRT Rally being a notorious exception. To make the MESA_LOADER_DRIVER_OVERRIDE=iris work you would need to use Mesa git and configure Mesa git to build iris.

If the vulkan-smoketest works, DiRT 3 should work too. What Mesa version are you using now (glxinfo -B | grep "profile version string")? And what Vulkan API version ( vulkaninfo | grep apiVersion)?

As a reference, the outputs on my system are:

OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.1.0-devel (git-ad8c145658)
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.1.0-devel (git-ad8c145658)

and

	apiVersion     = 0x401066  (1.1.102)

Unfortunately, I was looking for solution, so I didn't respond, my mesa is below 19 (can't check at the moment) and I'm on Mint KDE based on Ubuntu Xenial which is not supported by oibaf PPA.
As far as i can understand I can only wait for Mint 19 KDE and upgrade, move to another distro (non-LTE) or compile mesa on my own. I'll propably wait...

Update.
After moving to Kubuntu, oibaf's mesa and solving problems with new drivers (enable sna and TearFree) and enabling in-gme vsync everything works fine. Smooth (almost without any lags), even on snowy locations. No need for workarounds.

OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.1.0-devel (git-4122f55 2019-04-11 cosmic-oibaf-ppa)
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 19.1.0-devel (git-4122f55 2019-04-11 `cosmic-oibaf-ppa)

INTEL-MESA: warning: Haswell Vulkan support is incomplete
INTEL-MESA: warning: ../src/intel/vulkan/anv_device.c:1343: FINISHME: Implement pop-free point clipping
        apiVersion     = 0x401066  (1.1.102)

Tested this on Proton 4.2-2 and it works amazing, first startup was just blank but every single start since has been flawless. If anything it runs better than it did native on windows (for me at least)

GPU: GTX 1080
Driver/LLVM version: nvidia 418.56
Kernel version: 5.0.7
Link to full system information report
Proton version: 4.2-2

steam-321040.log

Benchmark with all settings maxed (2560x1440), impressive for not running natively.

For some reason this game went from borked to platinum to borked again for me with the past 3 versions of Proton.

With 4.2-7 this game was borked for me and had remained borked for all previous versions of Proton.
With 4.2-8 suddenly it worked flawlessly and I was able to play it.
With 4.2-9 it's now regressed back to borked again.

Distro: Linux Mint 19.1 Tessa
Kernel: 4.18.0-16-generic
RAM: 32 GB
GPU Driver: NVIDIA 415.27
GPU: NVIDIA GeForce GTX 980
CPU: Intel Core i7-4790K @ 4.00GHz

Hello @mindinsomnia, there's very little difference between 4.2-8 and 4.2-9, only 22354ec changed.

Please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

I only get a black screen and after a few seconds land back on the desktop again.

system specs | steam-321040.log

for me setting "PROTON_USE_WINED3D=1 %command%" as the launch options and disabling "composition" on my desktop allows me to successfully launch the game

Edit: Added a log with D3D11 disabled.

May as well wake this thread up from the dead.
Still looks as if this is broken in Proton 6.3-7 and Proton Experimental.

Compatibility Report

• Name of the game with compatibility issues: DiRT 3
• Steam AppID of the game: 321040

System Information

• GPU: RTX 2070
• Driver/LLVM version: NVIDIA 495.44
• Kernel version: 5.14
• Link to full system information report as Gist: https://gist.github.com/ProjectSynchro/f0d4e4f102ca29c71a683ea49dd4df7e
• Proton version: Proton Experimental (bleeding-edge branch)

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

steam-321040.log
steam-321040.log (PROTON_NO_D3D11=1)

Symptoms

This game does not launch correctly. The game starts up, spawns a black window and then crashes.

Looking in the proton log shows both D3D9 and D3D11 calls to DXVK. Out of curiousity I disabled D3D11 using PROTON_NO_D3D11=1 and the game launches, leaving me to believe that the game is calling both D3D9 and D3D11 for various reasons.. This could be why having both enabled causes issues.

Perhaps a bug should probably be filed with DXVK if this game uses some weird collection of both D3D11 and D3D9 calls at the same time (if D3D11 is available). More digging is definitely needed.

Reproduction

1. Launch the game using Proton Experimental or Proton 6.3-7.
2. Observe the window spawn and then the game crashing.

System Information

• GPU: RTX 2070
• Driver/LLVM version: NVIDIA 510.47.03
• Kernel version: 5.16.9
• Link to full system information report as Gist: https://gist.github.com/ProjectSynchro/f0d4e4f102ca29c71a683ea49dd4df7e
• Proton version: Proton Experimental (bleeding-edge branch)

Proton 7.0-1 and Proton Experimental (1645691642 experimental-bleeding-edge-7.0-10193-20220224-p35a410-wad15cd-db42c07-vedbf49) now have this game as working correctly without disabling either ESYNC or FSYNC. The in-game overlay causes the game to freeze rendering and appears to lose focus. Multiple alt-tabs and shift-tabs are required to get the game to come back to focus.

Here is a log when running under Proton Experimental and attempting to open the overlay:
steam-321040.log

There appears to be a regression from Proton 7.0 to 8.0 and onwards.

After some tweaks this game now works without issues in Proton 9, and Proton Experimental, however there are some steps required to get the game to launch.

It appears that OpenAL32.dll is not provided by Proton which causes an issue that is also present in Windows as this game does not install redistributables correctly on Steam.

To work around this you need to install OpenAL in your prefix by running oalinst.exe from ./gamedir/_CommonRedist/OpenAL/2.0.7.0/. The easiest way to do this is with protontricks.

Alternatively you can run protontricks 321040 openal to install the winetricks verb for OpenAL.

With OpenAL installed correctly, this game works flawlessly. The freezing issue with the Steam overlay as I outlined above is no longer present.

Relevant log output: 46478.640:0134:0138:err:module:import_dll Library OpenAL32.dll (which is needed by L"Z:\\home\\synchro\\.local\\share\\Steam\\steamapps\\common\\DiRT 3 Complete Edition\\dirt3_game.exe") not found
Full log: steam-321040.log

@ProjectSynchro Thank you for reporting this! Wine stopped shipping OpenAL.dll because it is not shipped with Windows, and games that rely on it are supposed to ship it themselves. Unfortunately, based on the fact that this game is no longer listed on the Steam store, it seems unlikely that the game devs will be inclined to update the game :( In the meantime, thank you for providing a workaround for folks who would like to play on newer versions than 7.0-6 :)

@ProjectSynchro Thank you for reporting this! Wine stopped shipping OpenAL.dll because it is not shipped with Windows, and games that rely on it are supposed to ship it themselves. Unfortunately, based on the fact that this game is no longer listed on the Steam store, it seems unlikely that the game devs will be inclined to update the game :( In the meantime, thank you for providing a workaround for folks who would like to play on newer versions than 7.0-6 :)

Unfortunate, but fair enough! Thanks for looking.