Page MenuHome

Musgrave texture incorrectly displayed in the viewport Cycles
Closed, ArchivedPublic

Description

System Information
Windows10 x64, intel hd graphics 2000

Blender Version
Broken: 2.78rc1 0e5089c - 2.78 a267710

Short description of error
Procedural texture Musgrave (coloring fBM, Hetero Terrain, Hybrid Multifractal, Ridged Multifractal, Multifractal) incorrectly displayed on an object in the viewport shading mode Cycles material


Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

  1. Use a default blender scene.
  2. Toggle to render Cycles, viewport shading - Material
  3. Select the cube. On the materials settings tab click on the button "use nodes"
  4. Under the surface dropdown in material parametres in node socket Color choose Voronoi Texture
  5. Then change the coloring with fBM on Hetero Terrain. Then Hybrid Multifractal. Then Ridged Multifractal. Then Multifractal.

Details

Type
Bug

Event Timeline

Sergey Sharybin (sergey) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Sep 15 2016, 10:01 AM

Very interesting and annoying at the same time because it all works on Linux for me :(

Could be a limitation of your graphics card tho. Some things to try:

  • Make sure your video drivers are the latest one from intel download center (worth re-installing them because sometimes Win10 will override your manually installed drivers :()
  • Check on the system console (Window -> Show Console or something like that). Are there any error prints in there?
  • Try downloading opengl32.dll from http://download.blender.org/ftp/sergey/softwaregl/ and put it next to blender.exe. This will switch Blender to fully software OpenGL mode which is slower but free from driver/card specific issues. Will that make texture to appear correctly?

With opengl32.dll white cube. And viewport slows down mercilessly:

console log with opengl32.dll

Read new prefs: C:\Users\╨Я╨░╨▓╨╡╨╗\AppData\Roaming\Blender Foundation\Blender\2.78\config\userpref.blend
AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
Warning! Legacy WGL is unable to select between OpenGL versions.found bundled python: C:\Users\╨Я╨░╨▓╨╡╨╗\Downloads\blender-2.78-a267710-win64-vc14\blender-2.78.0-git.a267710-windows64\2.78\python
B4W Warning: Blender 2.77 is recommended for the Blend4Web addon. Current version is 2.78
read blend: D:\3D\Noise texture incorrectly displayed in Cycles viewport.blend

console log without opengl32.dll:

Read new prefs: C:\Users\╨Я╨░╨▓╨╡╨╗\AppData\Roaming\Blender Foundation\Blender\2.78\config\userpref.blend
AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
found bundled python: C:\Users\╨Я╨░╨▓╨╡╨╗\Downloads\blender-2.78-a267710-win64-vc14\blender-2.78.0-git.a267710-windows64\2.78\python
B4W Warning: Blender 2.77 is recommended for the Blend4Web addon. Current version is 2.78
read blend: D:\3D\Noise texture incorrectly displayed in Cycles viewport.blend

Installed the latest supported driver version 15.28.24.64.4229 (9.17.10.4229)

I googled and found that: Officially hd graphics 2000/3000 on Windows driver support is limited to OpenGL 3.1. OpenGL 3.2 functions are available only through the extension. On OSX and Linux - OpenGL 3.3.
ReleaseNotes_GFX_15.28.24.4229.pdf
List_of_Intel_graphics_processing_units on wiki

I am attaching GPU Caps Viewer v1.31.1.0 report in xml and txt file version.

Bastien Montagne (mont29) claimed this task.

So guess conclusion here is that old intel HD driver is crap? We cannot fix GPU drivers really, so am afraid you'll either have to get a new (real) GPU, or live with HD2000 bugs, or with softwareGL slowness.

Thanks for the report anyway.