Only "None" OpenSubDiv option in preferences to choose from #45717

Closed
opened 2015-08-07 07:46:13 +02:00 by first last · 40 comments

System Information
Linux X64, HD5770, OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.2 but Blender system info reports only OpenGL 3.0

Blender Version
Broken: 2.75-44384c6

Short description of error
I don't know if GLSL backends are using something higher than OGL3.3 but there should be atleast CPU and OpenMP backends to choose from.

**System Information** Linux X64, HD5770, OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.2 but Blender system info reports only OpenGL 3.0 **Blender Version** Broken: 2.75-44384c6 **Short description of error** I don't know if GLSL backends are using something higher than OGL3.3 but there should be atleast CPU and OpenMP backends to choose from.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @StasSidorenko

Added subscriber: @StasSidorenko
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Sergey Sharybin was assigned by Aaron Carlisle 2015-08-07 16:22:41 +02:00
Member

OpenSubdiv uses OpenGL 4 so that might be why. But Sergey know more then I

OpenSubdiv uses OpenGL 4 so that might be why. But Sergey know more then I
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

@Blendify, It should be still be possible to choose CPU or OpenMP.

Lets wait on Sergey to investigate.

@Blendify, It should be still be possible to choose CPU or OpenMP. Lets wait on Sergey to investigate.

Added subscriber: @Harvester

Added subscriber: @Harvester

Here, on Windows 7 Pro 64bit, these are the options available in the OpenSubdiv Compute Type's drop-down menu in Preferences | System for the current Windows 64bit build Hash:44384c6 (by default it's set to None):

T45717_OSD_ComputeOptions_Win7_64bit_Hash_44384c6.png

Here, on Windows 7 Pro 64bit, these are the options available in the OpenSubdiv Compute Type's drop-down menu in Preferences | System for the current Windows 64bit build Hash:44384c6 (by default it's set to None): ![T45717_OSD_ComputeOptions_Win7_64bit_Hash_44384c6.png](https://archive.blender.org/developer/F221416/T45717_OSD_ComputeOptions_Win7_64bit_Hash_44384c6.png)
Member

I dont have GLSL Transform Feedback

I dont have GLSL Transform Feedback
Author

In #45717#326865, @Harvester wrote:

I don't have this list even though in my understanding atleast CPU and OpenMP should be there. You're using Windows and 100% proprietary drivers. For my case(OpenCL probably won't work on pre GCN cards) under Linux there is no point using those as i've tested some time ago, i get overall better experience with OSS ones and performance in Blender is roughly the same. Also i don't understand what does it have to with CPU backends, hopefully its a simple bug.

> In #45717#326865, @Harvester wrote: I don't have this list even though in my understanding atleast CPU and OpenMP should be there. You're using Windows and 100% proprietary drivers. For my case(OpenCL probably won't work on pre GCN cards) under Linux there is no point using those as i've tested some time ago, i get overall better experience with OSS ones and performance in Blender is roughly the same. Also i don't understand what does it have to with CPU backends, hopefully its a simple bug.

Added subscriber: @mont29

Added subscriber: @mont29

I can confirm here that with my default intel 'GPU' and free driver, I have no choice at all in the OSD compute type menu. Once I launch Blender on my nividia GPU (with primusrun), all choices become available…

I can confirm here that with my default intel 'GPU' and free driver, I have no choice at all in the OSD compute type menu. Once I launch Blender on my nividia GPU (with primusrun), all choices become available…
Member

Even I have coices for Intel card I have 4600

Even I have coices for Intel card I have 4600

Added subscriber: @mib2berlin

Added subscriber: @mib2berlin

Hi, can reproduce on Elementry Freya 64 with Mesa 3.0.
Intel HD 4400.

system-info.txt

Cheers, mib
P. S. Windows 10 is working with Intel driver

Hi, can reproduce on Elementry Freya 64 with Mesa 3.0. Intel HD 4400. [system-info.txt](https://archive.blender.org/developer/F221617/system-info.txt) Cheers, mib P. S. Windows 10 is working with Intel driver
Member

Added subscriber: @MartijnBerger

Added subscriber: @MartijnBerger
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Member

This is not a bug.

To use opensubdiv you need to be able to both render one or more backends AND support all the following OpenGL extensions:

  • Geometry shader support ( Part of OpenGL 3.2)
  • GL_ARB_gpu_shader5 ( Part of OpenGL 4.0 or an extension )
  • glProgramParameteri, glProgramParameteriEXT, glProgramParameteriARB ( Part of OpenGL 4.1 or as an extention )

Using mesa 10.6 is not expected to work. Mesa 11.x git might work. (based on -> http://mesamatrix.net/ it should work)

This is not a bug. To use opensubdiv you need to be able to both render one or more backends **AND** support all the following OpenGL extensions: - Geometry shader support ( Part of OpenGL 3.2) - GL_ARB_gpu_shader5 ( Part of OpenGL 4.0 or an extension ) - glProgramParameteri, glProgramParameteriEXT, glProgramParameteriARB ( Part of OpenGL 4.1 or as an extention ) Using mesa 10.6 is not expected to work. Mesa 11.x git might work. (based on -> http://mesamatrix.net/ it should work)
Author

Even CPU backends needs OpenGL support, why?
From my point of view it doesn't make much sense. If my card and its driver support those OGL extensions why would i even try CPU backends, why do they exist in the first place?

Even CPU backends needs OpenGL support, why? From my point of view it doesn't make much sense. If my card and its driver support those OGL extensions why would i even try CPU backends, why do they exist in the first place?

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'

While compute could happen on CPU you still need to be able to draw stuff in the viewport. It's possible to use approach which is similar to non-opensubdiv case but that's not very efficient.

We probably will look into this later but for now it's not considered a bug.

While compute could happen on CPU you still need to be able to draw stuff in the viewport. It's possible to use approach which is similar to non-opensubdiv case but that's not very efficient. We probably will look into this later but for now it's not considered a bug.
Author

Thanks for more clear answer.

Thanks for more clear answer.
Author

This comment was removed by @StasSidorenko

*This comment was removed by @StasSidorenko*

Added subscriber: @sanctuary

Added subscriber: @sanctuary

In #45717#327081, @Sergey wrote:
While compute could happen on CPU you still need to be able to draw stuff in the viewport. It's possible to use approach which is similar to non-opensubdiv case but that's not very efficient.

We probably will look into this later but for now it's not considered a bug.

Maybe you should add in the doc page something about the opengl requirement even for those "CPU"and "OpenMP" backend to avoid further bug reports about those options missing for the opensubdiv, because from an user point of view, it's not obvious having "None" as the only option is not a bug and that high OpenGL is still required as the current doc does not suggest opengl involvement for those backends :
//
CPU - single threaded CPU implementation. it is mainly useful in cases when GPU compute is possible and threaded CPU option causes artifacts (it is unlikely to happen, but still possible).
OpenMP - multi-threaded CPU implementation. It is similar to threading model of old subsurf code. Use it for maximum performance in cases when GPU compute is not available. //

> In #45717#327081, @Sergey wrote: > While compute could happen on CPU you still need to be able to draw stuff in the viewport. It's possible to use approach which is similar to non-opensubdiv case but that's not very efficient. > > We probably will look into this later but for now it's not considered a bug. Maybe you should add in the doc page something about the opengl requirement even for those "CPU"and "OpenMP" backend to avoid further bug reports about those options missing for the opensubdiv, because from an user point of view, it's not obvious having "None" as the only option is not a bug and that high OpenGL is still required as the current doc does not suggest opengl involvement for those backends : // CPU - single threaded CPU implementation. it is mainly useful in cases when GPU compute is possible and threaded CPU option causes artifacts (it is unlikely to happen, but still possible). OpenMP - multi-threaded CPU implementation. It is similar to threading model of old subsurf code. Use it for maximum performance in cases when GPU compute is not available. //

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Docs are still work in progress, but will make sure it's clear what's going on in the final doc version.

Also didn't really meant to re-open the report, it's a TODO so far rather than a bug.

Docs are still work in progress, but will make sure it's clear what's going on in the final doc version. Also didn't really meant to re-open the report, it's a TODO so far rather than a bug.

Just for your information, today I installed the latest 64bit zipped version of Blender (Hash: 6a80c2c) and differently from my previous post (see above), now none of the previously listed options is available in the System Preferences, and therefore I cannot enable Use OpenSubdiv in the Subsurf Modifier.

I understand that my graphics card is quite old (GeForce GTS 360M, 1GB, OpenCL 1.1), that's the reason why I use only CPU rendering or external render farms, but I don't understand why those options are now gone, and if the minimum requirements for the graphics card have been raised up to the point that OSD is now excluded from my notebook's capabilities.

Thanks.

Just for your information, today I installed the latest 64bit zipped version of Blender (Hash: 6a80c2c) and differently from my previous post (see above), now none of the previously listed options is available in the System Preferences, and therefore I cannot enable Use OpenSubdiv in the Subsurf Modifier. I understand that my graphics card is quite old (GeForce GTS 360M, 1GB, OpenCL 1.1), that's the reason why I use only CPU rendering or external render farms, but I don't understand why those options are now gone, and if the minimum requirements for the graphics card have been raised up to the point that OSD is now excluded from my notebook's capabilities. Thanks.

@Harvester, afraid it's one of those cases when some extension is not reported by driver but actually supported. It's a bit tricky to solve without making someone's else configuration to crash, but will see what we can do.

@Harvester, afraid it's one of those cases when some extension is not reported by driver but actually supported. It's a bit tricky to solve without making someone's else configuration to crash, but will see what we can do.

Thank you Sergey for your kind reply. FYI, the currently installed NVIDIA driver is version 341.81 and if there is any further information I can provide to help you find a fix, please let it me know.

Thank you Sergey for your kind reply. FYI, the currently installed NVIDIA driver is version 341.81 and if there is any further information I can provide to help you find a fix, please let it me know.

Just a brief update having downloaded the second testbuild and I still have NONE only option in the OpenSubdiv compute's dropdown list, being on CPU only mode (Compute Device is None).

Just a brief update having downloaded the second testbuild and I still have NONE only option in the OpenSubdiv compute's dropdown list, being on CPU only mode (Compute Device is None).

Added subscriber: @YAFU

Added subscriber: @YAFU

@MartijnBerger wrote:
Using mesa 10.6 is not expected to work. Mesa 11.x git might work. (based on -> http://mesamatrix.net/ it should work)

Hello.
Desktop PC, Kubuntu 15.04 64bit, GTX 960 - 346.59 driver, intel HD 4000, Blender 2.75-26041f9 from buildbot.
Using iGPU as primary display.
I installed Mesa 11.1.0-devel from this PPA:
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers

CUDA is available under "Compute Device". But only option "None" appears under "OpenSubdiv Compute".
This is what shows glxinfo:
http://www.pasteall.org/61120

>@MartijnBerger wrote: > Using mesa 10.6 is not expected to work. Mesa 11.x git might work. (based on -> http://mesamatrix.net/ it should work) Hello. Desktop PC, Kubuntu 15.04 64bit, GTX 960 - 346.59 driver, intel HD 4000, Blender 2.75-26041f9 from buildbot. Using iGPU as primary display. I installed Mesa 11.1.0-devel from this PPA: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers CUDA is available under "Compute Device". But only option "None" appears under "OpenSubdiv Compute". This is what shows glxinfo: http://www.pasteall.org/61120

Do you mind attaching system-info.txt generated by blender?

The glxinfo doesnt' contain any information about GL_EXT_geometry_shader4 extension which is required for visualizing OpenSubdiv meshes.

Do you mind attaching system-info.txt generated by blender? The glxinfo doesnt' contain any information about `GL_EXT_geometry_shader4` extension which is required for visualizing OpenSubdiv meshes.

Hello Sergey.
Here it is:
http://www.pasteall.org/61121

Hello Sergey. Here it is: http://www.pasteall.org/61121

Yes, the video driver doesn't support geometry shaders which are required for displaying OpenSubdiv meshes.

In theory we could make drawing code requiring less features from GPU, but in practice it'll mean much much less optimal code which will eliminate benefits of OpenSubdiv.

Yes, the video driver doesn't support geometry shaders which are required for displaying OpenSubdiv meshes. In theory we could make drawing code requiring less features from GPU, but in practice it'll mean much much less optimal code which will eliminate benefits of OpenSubdiv.

Hi Sergey, I am not sure if my GPU can support OpenSubDiv and since you mentioned above GL_EXT_geometry_shader4 which apparently seems supported by my graphics card, would you mind checking my system-info.txt report below and let me know about it? Thank you.

http://www.pasteall.org/61124/text

Hi Sergey, I am not sure if my GPU can support OpenSubDiv and since you mentioned above GL_EXT_geometry_shader4 which apparently seems supported by my graphics card, would you mind checking my system-info.txt report below and let me know about it? Thank you. http://www.pasteall.org/61124/text

You can consult the actual function which checks for whether GPU draw is allowed or not there https://developer.blender.org/diffusion/B/browse/master/intern/opensubdiv/opensubdiv_capi.cc;45a875fec4c00ccf87c5605d85f004f6dd4be8a0$297

SO currently you need return EXT_geometry_shader4, ARB_gpu_shader5 and ARB_uniform_buffer_object but that might be changing over time.

You can consult the actual function which checks for whether GPU draw is allowed or not there https://developer.blender.org/diffusion/B/browse/master/intern/opensubdiv/opensubdiv_capi.cc;45a875fec4c00ccf87c5605d85f004f6dd4be8a0$297 SO currently you need return EXT_geometry_shader4, ARB_gpu_shader5 and ARB_uniform_buffer_object but that might be changing over time.

Thank you Sergey. As far as I can see in my laptop's system-info.txt my graphics card is missing ARB_gpu_shader5 at least. Time to consider buying a new, more modern laptop.

Thank you Sergey. As far as I can see in my laptop's system-info.txt my graphics card is missing ARB_gpu_shader5 at least. Time to consider buying a new, more modern laptop.
Member

Added subscriber: @MikeErwin

Added subscriber: @MikeErwin
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
11 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#45717
No description provided.