Open f1nbar opened 1 year ago
You have to call vkcube
with --width
and --height
set. Because the app itself still thinks it's run in a window and it doesn't have its own binding to fullscreen/maximise. See also #547
You have to call
vkcube
with--width
and--height
set. Because the app itself still thinks it's run in a window and it doesn't have its own binding to fullscreen/maximise. See also #547
Thanks for the reply. This happens with any program or game regardless of arguments, including calling vkcube with these args. Anything running in gamescope fullscreen causes artifcacting.
I've encountered the same issue with Star Citizen
when running via lutris.
Also tried to confirm with gamescope -- vkcube
and gamescope -W 1280 -H 720 -- vkcube
I've also experienced similar artifacts with Guilty Gear Strive while running via Steam/Proton when VK_ICD_FILENAMES
wasn't present in the steam's process environment.
export VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/intel_icd.x86_64.json:/usr/share/vulkan/icd.d/intel_icd.i686.json
The result of vkcube
is:
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel (0x8086)
Device: Mesa Intel(R) Arc(tm) A770 Graphics (DG2) (0x56a0)
Version: 23.0.2
Accelerated: yes
Video memory: 16288MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Arc(tm) A770 Graphics (DG2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.0.2
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.0.2
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.0.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
Replying to https://github.com/ValveSoftware/gamescope/issues/836#issuecomment-1519198186
What happens if you use INTEL_DEBUG=norbc
?
Fascinating!
Results of INTEL_DEBUG=norbc gamescope -W 1280 -H 720 -- vkcube
I've also set this as an envrionment variable for Star Citizen and it runs without the artifacts anymore!
With worse performance than when not running with gamescope
though, but I guess that's expected?
Replying to https://github.com/ValveSoftware/gamescope/issues/836#issuecomment-1519229390
For the best experience with Intel you'll want to use mesa_glthread=true INTEL_DEBUG=norbc
Toggling fullscreen with Super+F or including the -f flag causes artifcating.
gamescope -- vkcube
glxinfo -B