Graphical artefacts on OpenGL renderer

[GermanAizek]

Describe the bug Graphical bugs when we move ComboList slider manually by pulling it sharply, effect is more noticeable.

To Reproduce Steps to reproduce the behavior:

1. Watch video

Screenshots

https://github.com/OpenXRay/xray-16/assets/21138600/d3693a0f-fe22-4784-b73f-bd490e0a6f59

Desktop (please complete the following information):

• OS: Ubuntu 22.04
• OpenXRay commit hash [dfa2bd]

[xrModder]

Hardware?

[GermanAizek]

@xrModder,

ubuntu@ubuntu-NB:~$ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon Vega 8 Graphics (raven, LLVM 15.0.6, DRM 3.47, 5.19.0-43-generic) (0x15dd)
    Version: 22.2.5
    Accelerated: yes
    Video memory: 1024MB
    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
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 675 MB, largest block: 675 MB
    VBO free aux. memory - total: 3327 MB, largest block: 3327 MB
    Texture free memory - total: 675 MB, largest block: 675 MB
    Texture free aux. memory - total: 3327 MB, largest block: 3327 MB
    Renderbuffer free memory - total: 675 MB, largest block: 675 MB
    Renderbuffer free aux. memory - total: 3327 MB, largest block: 3327 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 4442 MB
    Currently available dedicated video memory: 675 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon Vega 8 Graphics (raven, LLVM 15.0.6, DRM 3.47, 5.19.0-43-generic)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.2.5
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 22.2.5
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 22.2.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

[sobkas]

Under similar hardware but with new soft couldn't reproduce it:

glxinfo -B name of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: AMD (0x1002) Device: AMD Radeon Vega 8 Graphics (raven, LLVM 15.0.7, DRM 3.54, 6.5.0-0-amd64) (0x15d8) Version: 23.1.6 Accelerated: yes Video memory: 2048MB 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 Memory info (GL_ATI_meminfo): VBO free memory - total: 1080 MB, largest block: 1080 MB VBO free aux. memory - total: 8719 MB, largest block: 8719 MB Texture free memory - total: 1080 MB, largest block: 1080 MB Texture free aux. memory - total: 8719 MB, largest block: 8719 MB Renderbuffer free memory - total: 1080 MB, largest block: 1080 MB Renderbuffer free aux. memory - total: 8719 MB, largest block: 8719 MB Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 2048 MB Total available memory: 10976 MB Currently available dedicated video memory: 1080 MB OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon Vega 8 Graphics (raven, LLVM 15.0.7, DRM 3.54, 6.5.0-0-amd64) OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.1.6-1 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.1.6-1 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.1.6-1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Can you try new drivers?

[Xottab-DUTY]

This may be related with #878, where UI is even more screwed... That's drivers for sure, but I wonder if we can fix something in the renderer on our side.

Also may be related to #1144.