CPU model dees not metter if it sit much lower then on windows... with CPU bound i usually mean app scenario and driver is generally more CPU bound then it should be, so there is no what to feed your GPU enough to be used more.
Announcement
Collapse
No announcement yet.
More AMD PowerPlay Fixes Queued For Linux 4.9
Collapse
X
-
Originally posted by dungeon View PostCPU model dees not metter if it sit much lower then on windows... with CPU bound i usually mean app scenario and driver is generally more CPU bound then it should be, so there is no what to feed your GPU enough to be used more.
Well, on Windows I already know both GPUs are maxed out because I can see the LEDs on both cards fully light up. But on AMDGPU (with either Mesa or proprietary user space - it doesn't matter) those LEDs don't work properly so I can't tell at a glance. That's another issue with the Fury X GNU/Linux drivers right now.
Comment
-
-
boltronics you can try radeontop, i have GPU which is not supported by pro driver by now so i don't know for sure but it may work.
Comment
-
Originally posted by pal666 View Postsecond assignment overwrites first one, remove it
However, commenting the second line makes no difference (aside from removing the OpenGL version pop-up warning from the game completely). The screen remains completely black, but I can hear the audio. I have the Steam overlay with the FPS counter and I can see different frame rates showing for the intro video and the main menu (which can be brought up by hitting space twice with about a second or more between each press). I can then exit the game cleanly by hitting Escape followed by Enter. So all game behaviour seems normal except no picture.
Comment
-
boltronics... and you should override GLSL rather than GL:
Code:MESA_GLSL_VERSION_OVERRIDE=450
Comment
Comment