Blender+Tahiti+DRI3+Unity+Linux GUI corruption/not rendering #48946

New Issue

d g · 2016-07-26T08:41:30+02:00

d g commented

2016-07-26 08:41:30 +02:00

System Information
OS: Ubuntu 16.04 xenial
Kernel: x86_64 Linux 4.7.0-040700rc5-generic
Uptime: 5m
Packages: 2937
Shell: bash 4.3.46
Resolution: 1920x1080
DE: Unity 7.4.0
WM: Compiz
WM Theme: Ambiance
Ambiance [GTK2]
, Ambiance [GTK3]
Icon Theme: ubuntu-mono-dark
Font: Ubuntu 11
CPU: AMD Phenom II X4 965 @ 3.4GHz
GPU: Gallium 0.4 on AMD TAHITI (DRM 2.45.0 / 4.7.0-040700rc5-generic, LLVM 4.0.0)
RAM: 2129MiB / 16049MiB

=glxinfo output=-
client glx vendor string: Mesa Project and SGI
OpenGL core profile version string: 4.3 (Core Profile) Mesa 12.1.0-devel - padoka PPA
OpenGL version string: 3.0 Mesa 12.1.0-devel - padoka PPA
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 12.1.0-devel - padoka PPA

Blender Version
Broken: 2.77a abf6f08
Also Broken but not limited to older version 2.60 r41226

Short description of error
When using blender parts of the GUI don't render

Here is a link to a video of the bug happening
https://youtu.be/tMs4QSW0OmY

I originally reported it to the mesa developers, and they have now directed me to report it here.
https://bugs.freedesktop.org/show_bug.cgi?id=97059

Exact steps for others to reproduce the error
Happens just by using blender and modifying the GUI. e.g.: https://youtu.be/tMs4QSW0OmY

How to make the problem stop happening
CTRL+ALT+U > System > Window Draw Method
Default is Automatic and if set to 'Triple Buffer' this issue goes away

**System Information** OS: Ubuntu 16.04 xenial Kernel: x86_64 Linux 4.7.0-040700rc5-generic Uptime: 5m Packages: 2937 Shell: bash 4.3.46 Resolution: 1920x1080 DE: Unity 7.4.0 WM: Compiz WM Theme: Ambiance Ambiance [GTK2] , Ambiance [GTK3] Icon Theme: ubuntu-mono-dark Font: Ubuntu 11 CPU: AMD Phenom II X4 965 @ 3.4GHz GPU: Gallium 0.4 on AMD TAHITI (DRM 2.45.0 / 4.7.0-040700rc5-generic, LLVM 4.0.0) RAM: 2129MiB / 16049MiB - =glxinfo output=- client glx vendor string: Mesa Project and SGI OpenGL core profile version string: 4.3 (Core Profile) Mesa 12.1.0-devel - padoka PPA OpenGL version string: 3.0 Mesa 12.1.0-devel - padoka PPA OpenGL ES profile version string: OpenGL ES 3.1 Mesa 12.1.0-devel - padoka PPA **Blender Version** Broken: 2.77a abf6f08 Also Broken but not limited to older version 2.60 r41226 **Short description of error** When using blender parts of the GUI don't render Here is a link to a video of the bug happening https://youtu.be/tMs4QSW0OmY I originally reported it to the mesa developers, and they have now directed me to report it here. https://bugs.freedesktop.org/show_bug.cgi?id=97059 **Exact steps for others to reproduce the error** Happens just by using blender and modifying the GUI. e.g.: https://youtu.be/tMs4QSW0OmY **How to make the problem stop happening** CTRL+ALT+U > System > Window Draw Method Default is Automatic and if set to 'Triple Buffer' this issue goes away

d g commented

2016-07-26 08:41:30 +02:00

Changed status to: 'Open'

d g commented

2016-07-26 08:41:30 +02:00

Added subscriber: @kurikai

Sergey Sharybin commented

2016-07-26 13:12:58 +02:00

Added subscribers: @MikeErwin, @Sergey

Mike Erwin was assigned by Sergey Sharybin

2016-07-26 13:12:58 +02:00

Sergey Sharybin commented

2016-07-26 13:12:58 +02:00

@MikeErwin, can you comment on this? There's some disucssion about GLX_EXT_buffer_age, GLX_OML_swap_method and GLX_INTEL_swap_event extension in the mesa bug report, which i'm not so familiar with.

Brecht Van Lommel commented

2016-07-27 01:40:22 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2016-07-27 01:40:22 +02:00

Probably we should remove the exception in wm_automatic_draw_method and just make the AMD open source drivers use triple buffer as well. The performance issue that this exception existed for is likely already fixed or only exists on GPUs that's we don't support anymore. That's difficult to verify of course, but perhaps we should just switch and see what happens.

For 2.8 I'd even like to remove all the other draw methods and keep only triple buffer. The overlap draw modes ideally should indeed check such extensions to figure out the swapping method used, but if we remove them anyway we won't need to.

Probably we should remove the exception in `wm_automatic_draw_method` and just make the AMD open source drivers use triple buffer as well. The performance issue that this exception existed for is likely already fixed or only exists on GPUs that's we don't support anymore. That's difficult to verify of course, but perhaps we should just switch and see what happens. For 2.8 I'd even like to remove all the other draw methods and keep only triple buffer. The overlap draw modes ideally should indeed check such extensions to figure out the swapping method used, but if we remove them anyway we won't need to.

Julian Eisel commented

2016-07-27 01:46:39 +02:00

Added subscriber: @JulianEisel

Julian Eisel commented

2016-07-27 01:46:39 +02:00

I agree on getting rid of the other draw methods for 2.8. However, I think the full drawing would be useful to keep for debugging. Maybe as a comandline option, like --window-full-draw or using G.debug_value.

I agree on getting rid of the other draw methods for 2.8. However, I think the full drawing would be useful to keep for debugging. Maybe as a comandline option, like `--window-full-draw` or using `G.debug_value`.

blender-admin commented

2016-07-27 16:06:18 +02:00

This issue was referenced by e4646c52c0

This issue was referenced by e4646c52c04f87d0d914a4741bb64cf9de89118e

Sergey Sharybin commented

2016-07-27 16:07:23 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2016-07-27 16:07:23 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender+Tahiti+DRI3+Unity+Linux GUI corruption/not rendering #48946