![]() 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. ![]() ![]() 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. There is something very strange about the behaviour of this game. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |