#DIRT 3 PC COVER 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 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. This isn't actually the first time I'm trying out the game. 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 other system activity, even IO, so it's not like it's busy loading game data or anything. Not sure if I just didn't notice it on previous launches. Seventh launch: same thing as the previous launch, except wine64 is taking up 100% of one CPU core. 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. Sixth launch: black logo screen like the first launch, except my cursor isn't being held hostage. No significant GPU activity from radeontop either so no 3D stuff is running.

htop doesn't show the process taking any CPU cycles really, and iotop doesn't show any IO activity. I forgot to copy/rename this log and it was lost the next time I ran the game.įourth launch: completely black screen, no logo or anything else. 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)'. Radeontop showed the maximum GPU usage was around 67%. I was able to play the game at 1080p, 8xMSAA, and the highest other graphical settings at a solid 60 fps. Third launch, the game seems to work completely normally. Īfter 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.

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

#DIRT 3 PC COVER DRIVERS#

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. I've got a pair of increasingly exasperated feet to placate.There is something very strange about the behaviour of this game. You've got a dazzlingly varied, relentlessly entertaining rally celebration to buy. When you're haring towards a hairpin at 100mph or more, it's not particularly helpful to hear, “Easy left – opens” from the passenger seat.īut enough nitpicking. The current batch can be a little overeager when it comes to pace notes. Some smarter co-drivers wouldn't have gone amiss, either. However, a few more catastrophe cues would have been useful. The cars handle intuitively, though, especially when you've tweaked things such as brake bias and gear ratios to suit your driving style. If you're a SimBin veteran, you're likely to find the lack of audio feedback from tyres, transmissions and brakes mildly perturbing. I just wish the rides were a tad more talkative. Tearing along the game's forest tracks in vintage Ford Escorts, Opel Mantas and Audi Quattros is as delightful as it is horribly dangerous.

Talking of ageing technology, the 50-strong vehicle selection includes a range of '60s, '70s, '80s and '90s machines that are sure to please the generation of gamers taught road safety by huge squirrels and crappy superheroes.

Dirt 3 pc cover