GLSL Shading with Textured shading caused UI freezing #50493

New Issue

Bohdan · 2017-01-21T19:59:56+01:00

Bohdan commented

2017-01-21 19:59:56 +01:00

System Information
Elementary OS. Freya
Linux 3.19.0-65-generic #73~14.04.1-Ubuntu SMP Wed Jun 29 21:05:22 UTC 2016 x86_64 x86_64
01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1)
CPU: model name : Intel(R) Core(TM) i3-4170 CPU @ 3.70GHz
Memory [Mb]: 1598

Blender Version
Broken: 2.78a e8299c8
Broken: 2.74

Short description of error
When enabling GLSL shading mode in property panel (N) with Texture shading Blender just stuck an seems like it process one action per 30 seconds.

This behavior appear with Blender Render and Blender Game renderers.

Exact steps for others to reproduce the error

With just newly opened blender switch to Texture viewport shading
In property tab (N). Section Shading -> switch from Multitexture to GLSL

Additional words
With default cube created it still works (very slow) but as far as I add more object to a scene it is impossible to use Blender at all.

**System Information** Elementary OS. Freya Linux 3.19.0-65-generic #73~14.04.1-Ubuntu SMP Wed Jun 29 21:05:22 UTC 2016 x86_64 x86_64 01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) CPU: model name : Intel(R) Core(TM) i3-4170 CPU @ 3.70GHz Memory [Mb]: 1598 **Blender Version** Broken: 2.78a e8299c8 Broken: 2.74 **Short description of error** When enabling GLSL shading mode in property panel (N) with Texture shading Blender just stuck an seems like it process one action per 30 seconds. This behavior appear with Blender Render and Blender Game renderers. **Exact steps for others to reproduce the error** 1. With just newly opened blender switch to Texture viewport shading 2. In property tab (N). Section Shading -> switch from Multitexture to GLSL **Additional words** With default cube created it still works (very slow) but as far as I add more object to a scene it is impossible to use Blender at all.

Bohdan commented

2017-01-21 19:59:56 +01:00

Changed status to: 'Open'

Bohdan commented

2017-01-21 19:59:56 +01:00

Added subscriber: @Bohdan-Korniienko

Joey Ferwerda commented

2017-01-25 12:24:58 +01:00

Added subscriber: @TheOnlyJoey

Joey Ferwerda commented

2017-01-25 12:24:58 +01:00

Thanks for the report.

I am not able to reproduce this on Multiple (also slower) systems.
Are you able to run other GL applications? are you using the Official driver or the Open Source driver and what version?

Thanks for the report. I am not able to reproduce this on Multiple (also slower) systems. Are you able to run other GL applications? are you using the Official driver or the Open Source driver and what version?

Aaron Carlisle commented

2017-02-02 07:45:25 +01:00

Added subscriber: @Blendify

Aaron Carlisle commented

2017-02-02 07:45:25 +01:00

Changed status from 'Open' to: 'Archived'

Aaron Carlisle closed this issue

2017-02-02 07:45:25 +01:00

Aaron Carlisle self-assigned this 2017-02-02 07:45:25 +01:00

Aaron Carlisle commented

2017-02-02 07:45:25 +01:00

No news in over a week. Do to the policy of this bug tracker we have to archive this issue. If the information is provided then it can be re opened.

Bohdan commented

2017-02-03 18:13:24 +01:00

OpenGL seems to work.
There was standard Nouveau driver used.
Switching to proprietary Nvidia driver (367.57) did not change anything.

Below presented benchmarking with glmark utility:

Nouveau

~$ glmark2
=======================================================
glmark2 2012.08
=======================================================
OpenGL Information
GL_VENDOR: NVIDIA Corporation
GL_RENDERER: GeForce GTX 960/PCIe/SSE2
GL_VERSION: 4.5.0 NVIDIA 352.93
=======================================================
[build] use-vbo=false: FPS: 8696 FrameTime: 0.115 ms
=======================================================
glmark2 Score: 8696
=======================================================

~$ glmark2-es2
libEGL warning: DRI2: failed to authenticate
** Failed to set swap interval. Results may be bounded above by refresh rate.
=======================================================
glmark2 2012.08
=======================================================
OpenGL Information
GL_VENDOR: VMware, Inc.
GL_RENDERER: Gallium 0.4 on llvmpipe (LLVM 3.6, 256 bits)
GL_VERSION: OpenGL ES 3.0 Mesa 10.5.9
=======================================================
** Failed to set swap interval. Results may be bounded above by refresh rate.
[build] use-vbo=false: FPS: 269 FrameTime: 3.717 ms
** Failed to set swap interval. Results may be bounded above by refresh rate.
[build] use-vbo=true: FPS: 279 FrameTime: 3.584 ms
=======================================================
glmark2 Score: 274
=======================================================

nVidia

~$ glmark2
=======================================================
glmark2 2012.08
=======================================================
OpenGL Information
GL_VENDOR: NVIDIA Corporation
GL_RENDERER: GeForce GTX 960/PCIe/SSE2
GL_VERSION: 4.5.0 NVIDIA 367.57
=======================================================
[build] use-vbo=false: FPS: 7875 FrameTime: 0.127 ms
=======================================================
glmark2 Score: 7875
=======================================================

~$ glmark2-es2
=======================================================
glmark2 2012.08
=======================================================
OpenGL Information
GL_VENDOR: NVIDIA Corporation
GL_RENDERER: GeForce GTX 960/PCIe/SSE2
GL_VERSION: OpenGL ES 3.2 NVIDIA 367.57
=======================================================
[build] use-vbo=false: FPS: 9172 FrameTime: 0.109 ms
=======================================================
glmark2 Score: 9172
=======================================================

OpenGL seems to work. There was standard Nouveau driver used. Switching to proprietary Nvidia driver (367.57) did not change anything. Below presented benchmarking with glmark utility: > Nouveau > > - [x]~$ glmark2 > ======================================================= > glmark2 2012.08 > ======================================================= > OpenGL Information > GL_VENDOR: NVIDIA Corporation > GL_RENDERER: GeForce GTX 960/PCIe/SSE2 > GL_VERSION: 4.5.0 NVIDIA 352.93 > ======================================================= > [build] use-vbo=false: FPS: 8696 FrameTime: 0.115 ms > ======================================================= > glmark2 Score: 8696 > ======================================================= > - [x]~$ glmark2-es2 > libEGL warning: DRI2: failed to authenticate > ** Failed to set swap interval. Results may be bounded above by refresh rate. > ======================================================= > glmark2 2012.08 > ======================================================= > OpenGL Information > GL_VENDOR: VMware, Inc. > GL_RENDERER: Gallium 0.4 on llvmpipe (LLVM 3.6, 256 bits) > GL_VERSION: OpenGL ES 3.0 Mesa 10.5.9 > ======================================================= > ** Failed to set swap interval. Results may be bounded above by refresh rate. > [build] use-vbo=false: FPS: 269 FrameTime: 3.717 ms > ** Failed to set swap interval. Results may be bounded above by refresh rate. > [build] use-vbo=true: FPS: 279 FrameTime: 3.584 ms > ======================================================= > glmark2 Score: 274 > ======================================================= > > > nVidia > > - [x]~$ glmark2 > ======================================================= > glmark2 2012.08 > ======================================================= > OpenGL Information > GL_VENDOR: NVIDIA Corporation > GL_RENDERER: GeForce GTX 960/PCIe/SSE2 > GL_VERSION: 4.5.0 NVIDIA 367.57 > ======================================================= > [build] use-vbo=false: FPS: 7875 FrameTime: 0.127 ms > ======================================================= > glmark2 Score: 7875 > ======================================================= > - [x]~$ glmark2-es2 > ======================================================= > glmark2 2012.08 > ======================================================= > OpenGL Information > GL_VENDOR: NVIDIA Corporation > GL_RENDERER: GeForce GTX 960/PCIe/SSE2 > GL_VERSION: OpenGL ES 3.2 NVIDIA 367.57 > ======================================================= > [build] use-vbo=false: FPS: 9172 FrameTime: 0.109 ms > ======================================================= > glmark2 Score: 9172 > ======================================================= >

Aaron Carlisle commented

2017-02-04 02:24:09 +01:00

Changed status from 'Archived' to: 'Open'

Aaron Carlisle reopened this issue

2017-02-04 02:24:09 +01:00

Aaron Carlisle commented

2017-02-04 02:25:20 +01:00

Added subscriber: @MikeErwin

Aaron Carlisle commented

2017-02-04 02:25:20 +01:00

@MikeErwin any ideas here?

Mike Erwin commented

2017-02-04 07:29:50 +01:00

@Bohdan-Korniienko this happens even with default cube & no textures/materials, correct?

Try running from the terminal:
blender --debug-gpu

If that tells you something interesting, report it here. If not, grab a daily build and run it with --debug-gpu. (I enhanced our OpenGL debugging but can't remember if it was before or after 2.78a)

https://builder.blender.org/download/

@Bohdan-Korniienko this happens even with default cube & no textures/materials, correct? Try running from the terminal: blender --debug-gpu If that tells you something interesting, report it here. If not, grab a daily build and run it with --debug-gpu. (I enhanced our OpenGL debugging but can't remember if it was *before* or *after* 2.78a) https://builder.blender.org/download/

Bohdan commented

2017-02-04 11:09:54 +01:00

I am not sure if I need to run "blender --debug-gpu"
Here is why.

All my tries before was running blender-softwaregl script.
After your advice I just ran blender and switching to GLSL works perfectly.

I have no idea why it happening. So personally I can switch to another launcher.

P.S. If you need any debug info from me. May be there is still a reason to run debug mode, etc. Just tell me I will provide this intel.

P.P.S. Thank you for the help!

I am not sure if I need to run "blender --debug-gpu" Here is why. All my tries before was running blender-softwaregl script. After your advice I just ran blender and switching to GLSL works perfectly. I have no idea why it happening. So personally I can switch to another launcher. P.S. If you need any debug info from me. May be there is still a reason to run debug mode, etc. Just tell me I will provide this intel. P.P.S. Thank you for the help!

Aaron Carlisle removed their assignment 2017-02-05 01:07:42 +01:00

Mike Erwin commented

2017-02-05 01:43:14 +01:00

Why are you running software GL? Your hardware is definitely capable of running Blender.

Software GL is for debugging, and is not expected to be fast.

If it's working now we can close this issue.

Why are you running software GL? Your hardware is definitely capable of running Blender. Software GL is for debugging, and is not expected to be fast. If it's working now we can close this issue.

Bohdan commented

2017-02-08 20:46:55 +01:00

Changed status from 'Open' to: 'Resolved'

Bohdan closed this issue

2017-02-08 20:46:55 +01:00

Bohdan self-assigned this 2017-02-08 20:46:55 +01:00

Bohdan commented

2017-02-08 20:46:55 +01:00

Thank you for your help. Issue is resolved.

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

GLSL Shading with Textured shading caused UI freezing #50493