OpenSubdiv Adaptive subdivision not displaying on HD4000 HD4600

[Jeremy_C_2]

Note that this code is working on the same machine using other GPUs.

https://github.com/PixarAnimationStudios/OpenSubdiv/issues/757

From the linked bug:

Adaptive subdivision doesn't seem to work on Intel chips. No crash or errors; the surface just doesn't appear on screen. Non-adaptive displays fine.

I suspect it's a GL drawing issue since the surface is invisible for CPU and GPU evaluators.

Ran OpenSubdiv 3.0.3 glViewer & glFVarViewer on these systems:
Intel HD 4000, Mac OS 10.11
Intel HD 4600, Windows 10

glFVarViewer also shows some interesting geometry in the right pane:

[Michael_C_Intel2]

Hi Jeremy,

Before we can investigate we need additional information. Can you fill in the template below.

Thanks,

-Michael

System Setup Information:
-----------------------------------------

System Used: (Manufacturer/Model)
CPU SKU: (i3, i5, Pentium, Celeron, etc.)
GPU SKU: (HD4400, HD5100, etc.)
Processor Line: (Y-Series, U-Series, etc.)
System BIOS Version:
CMOS settings:
Graphics Driver Version:
GOP/VBIOS Version:
Operating System:
OS Version:
API:
Occurs on non-Intel GPUs?:

Steps to Reproduce:
-------------------------------
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Expected Results:
-------------------------------

Actual Results:
-------------------------------

Additional Information:
-------------------------------

[Jeremy_C_2]

Hi Michael,

This bug was reported by one of the OpenSubdiv contributors (a Blender developer), so I don't have the details. I've asked him to post an update here, but in case he doesn't, I've copied the details from above into this template.

System Setup Information:

-----------------------------------------

System Used: 
CPU SKU: 
GPU SKU: HD 4000, HD4600
Processor Line:
System BIOS Version: 
CMOS settings: 
Graphics Driver Version:
GOP/VBIOS Version:
Operating System: OS X, Windows
OS Version: OS X 10.11, Windows 10
API:
Occurs on non-Intel GPUs?: NO

Steps to Reproduce:
-------------------------------
1. Build OpenSubdiv
2. Run ./bin/glViewer  OR glFVarViewer (likely gl*)

Expected Results:

-------------------------------

Actual Results:

[Jeremy_C_2]

Is it possible to start investigating with what we have here?

[invisible-cow]

Hi, this is the original bug reporter.

System Used: Apple MacBook Pro 15" (summer 2012)
CPU SKU: i7
GPU SKU: HD4000
Operating System: Mac OS X
OS Version: 10.9 and 10.11 (latest)
API: OpenGL 4.1
Occurs on non-Intel GPUs?: No. The "good" screenshot above came from the nVidia GT 650M on the same system.

I know this config fails. Let me rebuild the OSD examples on Windows to gather details and verify failure there.

-- Mike

[invisible-cow]

 System Used: custom built PC, Asus Z87-PLUS
CPU SKU: Haswell i5-4670K
GPU SKU: HD4600
System BIOS Version: American Megatrends 0801
Graphics Driver Version: 10.18.15.4279
Operating System: Windows
OS Version: 10
API: OpenGL 4.3
Occurs on non-Intel GPUs?: No. Tested on a different system: AMD A10 PRO-7850B running Windows 10.

Initial run of glViewer on Windows showed same result as on Mac -- no surface displayed at all. Continued testing soon led to system hang. Reboot, rerun, hang again.

-- Mike

[Michael_C_Intel2]

Thanks for all additional information. I am talking with the driver team and getting an investigation started.

-Michael

[Michael_C_Intel2]

Hi Jeremy,

Well this is a good news, bad news situation. Good news we found the root cause and fixed the issue. The bad news is the fix is too complex to add to the current 15.40 baseline. What does the mean? We were able to fix it in the newer baselines, but I do not have an ETA when the first public release of that baseline will be. 

-Michael 

[invisible-cow]

Thanks for the update. Blender will use OpenSubdiv more extensively in the future (next year) but for now it's just an option. Looking forward to it working on all hardware! Only care about Ivy Bridge & newer from you guys.

-- Mike

[invisible-cow]

Hi Michael,

Has the fix made it out to a released driver? Should we expect the fix on Mac too, or Linux & Windows only?

Thx -- Mike

[Michael_C_Intel2]

Hi Mike,

I am still waiting on ETA when the new driver branch will get released to the public. When it does get released it will have this fix. I am unsure if Mac will get the fix, it should though. 

-Michael