3D View shading issue dependent on Normal map channel #48772

New Issue

Jerry Yeung · 2016-07-01T11:17:50+02:00

Jerry Yeung commented

2016-07-01 11:17:50 +02:00

Macbook Pro late 2013, Intel core i7 2,6 Ghz, 16 GB Ram
OS X El Capitan v10.11.5
Intel Iris Pro, NVIDIA GeForce GT 750M 2048 MB

Blender 2.77a official
Broken: 2.77a official, latest daily blender-2.77.0-git20160629.29a7310-x86_64
Worked: 2.76b

Shading in 3D View will brake when Normal Map channel is checked. I made a video here
https:*www.youtube.com/watch?v=fi_c4SfH2xI
Blender 2.77a and 2.76b running simultaneously.testfile.blend

Macbook Pro late 2013, Intel core i7 2,6 Ghz, 16 GB Ram OS X El Capitan v10.11.5 Intel Iris Pro, NVIDIA GeForce GT 750M 2048 MB Blender 2.77a official Broken: 2.77a official, latest daily blender-2.77.0-git20160629.29a7310-x86_64 Worked: 2.76b Shading in 3D View will brake when Normal Map channel is checked. I made a video here [https:*www.youtube.com/watch?v=fi_c4SfH2xI ](https:*www.youtube.com/watch?v=fi_c4SfH2xI) Blender 2.77a and 2.76b running simultaneously.[testfile.blend](https://archive.blender.org/developer/F319177/testfile.blend)

Jerry Yeung commented

2016-07-01 11:17:50 +02:00

Changed status to: 'Open'

Jerry Yeung commented

2016-07-01 11:17:50 +02:00

Added subscriber: @Jerry_Yeung

Campbell Barton commented

2016-07-04 07:53:46 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2016-07-04 07:53:46 +02:00

Tested in 2.77a on Linux, GeForce GTS 450 and its working properly.

Could you show the output of the console by running Blender from a terminal?
https://www.blender.org/manual/render/workflows/command_line.html#mac-osx

(GLSL errors may be printed there).

Tested in 2.77a on Linux, GeForce GTS 450 and its working properly. Could you show the output of the console by running Blender from a terminal? https://www.blender.org/manual/render/workflows/command_line.html#mac-osx (GLSL errors may be printed there).

Jerry Yeung commented

2016-07-04 10:16:32 +02:00

Nothing special happens in the Terminal. Even when I change the normal map channel.
This is the only output I get:
xxx-MBP:blender.app akirawillow$ /Users/akirawillow/Desktop/blender_2.77a/blender.app/Contents/MacOs/blender
found bundled python: /Users/akirawillow/Desktop/blender_2.77a/blender.app/Contents/MacOs/../Resources/2.77/python
read blend: /Users/xxx/Dropbox/xxx/Jobs/2016/xxx/3d_Assets/testfile.blend
^[^[^[^[^[^[Saved session recovery to '/tmp/quit.blend'

So if it's ok in Linux it seems to happen only on Mac. I tested it in Windows on the same machine and on another. Its working properly.

But Blender is somehow behaving awkward when it's started from the Terminal. It's impossible to control blender. The mouse seems to has an offset long way to the right. Well, but that's another issue though.

Nothing special happens in the Terminal. Even when I change the normal map channel. This is the only output I get: xxx-MBP:blender.app akirawillow$ /Users/akirawillow/Desktop/blender_2.77a/blender.app/Contents/MacOs/blender found bundled python: /Users/akirawillow/Desktop/blender_2.77a/blender.app/Contents/MacOs/../Resources/2.77/python read blend: /Users/xxx/Dropbox/xxx/Jobs/2016/xxx/3d_Assets/testfile.blend ^[^[^[^[^[^[Saved session recovery to '/tmp/quit.blend' So if it's ok in Linux it seems to happen only on Mac. I tested it in Windows on the same machine and on another. Its working properly. But Blender is somehow behaving awkward when it's started from the Terminal. It's impossible to control blender. The mouse seems to has an offset long way to the right. Well, but that's another issue though.

Brecht Van Lommel commented

2016-07-04 18:46:52 +02:00

Added subscribers: @MikeErwin, @brecht

Brecht Van Lommel commented

2016-07-04 18:46:52 +02:00

I can't reproduce this bug on OS X 10.11.5 with Intel Iris Graphics 6100. I also can't find a specific commit between 276b and 2.77a that could have caused this.

@MikeErwin, do you by any chance have OS X + NVidia to narrow down this bug to a specific commit?

I can't reproduce this bug on OS X 10.11.5 with Intel Iris Graphics 6100. I also can't find a specific commit between 276b and 2.77a that could have caused this. @MikeErwin, do you by any chance have OS X + NVidia to narrow down this bug to a specific commit?

Mike Erwin commented

2016-07-04 18:58:25 +02:00

Yes my Mac is the previous year's model, with Intel HD 4000 + NVIDIA GeForce GT 650M. Will check it out.

Mike Erwin commented

2016-07-04 19:06:32 +02:00

Confirmed broken on nVidia + Mac.
Works fine on Intel + Mac same system.

Confirmed broken on nVidia + Mac. Works fine on Intel + Mac same system.

Mike Erwin commented

2016-07-04 19:17:17 +02:00

Broken in the official 2.77 (no letter) release, so it was before that.

Sergey Sharybin commented

2016-07-27 14:59:09 +02:00

Added subscriber: @Sergey

Mike Erwin was assigned by Sergey Sharybin

2016-07-27 14:59:09 +02:00

Sergey Sharybin commented

2016-07-27 14:59:09 +02:00

Mike, since you're the only one who can reproduce the issue afraid you're the only candidate to fix it ;)

Mike Erwin commented

2016-07-31 10:31:56 +02:00

This broke between 2.75a and 2.76. Getting closer...

Mike Erwin commented

2016-08-02 04:27:57 +02:00

Had to reboot into MacOS 10.9 to build older code with older XCode/SDK. Problem never appears on 10.9! Even with latest Blender 2.77a from web site.

Making a few test builds in 10.9 and running them on 10.11 narrows the problem:

1 Sept 2015 — WORKS
1 Oct 2015 — BROKEN

Should find the exact commit that broke things soon.

Had to reboot into MacOS 10.9 to build older code with older XCode/SDK. Problem never appears on 10.9! Even with latest Blender 2.77a from web site. Making a few test builds in 10.9 and running them on 10.11 narrows the problem: 1 Sept 2015 — WORKS 1 Oct 2015 — BROKEN Should find the exact commit that broke things soon.

Mike Erwin commented

2016-08-02 09:14:07 +02:00

a9c5e1d9b7 from 17 Sept 2015

BLENDER_VERSION transition from 275 to 276 caused the break.

Is this a file versioning issue? Which only affects nVidia on MacOS 10.11??

Remember that 277 is also affected, so it seems like a VERSION > 275 problem.

@Jerry_Yeung can you confirm Blender 2.76 does work on your system? On mine 2.75 works but 2.76 is broken. Visually it's the exact same problem shown in your video.

a9c5e1d9b7 from 17 Sept 2015 BLENDER_VERSION transition from 275 to 276 caused the break. Is this a file versioning issue? Which only affects nVidia on MacOS 10.11?? Remember that 277 is also affected, so it seems like a VERSION > 275 problem. @Jerry_Yeung can you confirm Blender 2.76 **does** work on your system? On mine 2.75 works but 2.76 is broken. Visually it's the exact same problem shown in your video.

Jerry Yeung commented

2016-08-02 12:09:05 +02:00

@ Mike Erwin (merwin) Ok! I just tested it. Blender 2.76 works on my system!

Jerry Yeung commented

2016-08-02 12:09:21 +02:00

Added subscriber: @(Deleted)

Mike Erwin commented

2016-08-02 15:34:04 +02:00

@Jerry_Yeung In 2.76 go to Help > System Info and verify the NVIDIA GPU is active. I expected NVIDIA to be broken here, while Intel works fine.

On my laptop:

****
renderer:	'Intel HD Graphics 4000 OpenGL Engine'
vendor:		'Intel Inc.'
version:	'2.1 INTEL-10.14.73'

vs

renderer:	'NVIDIA GeForce GT 650M OpenGL Engine'
vendor:		'NVIDIA Corporation'
version:	'2.1 NVIDIA-10.10.13 310.42.25f01'

I use a tool called gfxCardStatus that lets you switch between the integrated and discrete GPU; it usually switches automatically.

@Jerry_Yeung In 2.76 go to Help > System Info and verify the NVIDIA GPU is active. I expected NVIDIA to be broken here, while Intel works fine. On my laptop: ```OpenGL **** renderer: 'Intel HD Graphics 4000 OpenGL Engine' vendor: 'Intel Inc.' version: '2.1 INTEL-10.14.73' ``` vs ``` renderer: 'NVIDIA GeForce GT 650M OpenGL Engine' vendor: 'NVIDIA Corporation' version: '2.1 NVIDIA-10.10.13 310.42.25f01' ``` I use a tool called gfxCardStatus that lets you switch between the integrated and discrete GPU; it usually switches automatically.

Jerry Yeung commented

2016-08-02 15:57:22 +02:00

@MikeErwin Mine looks like this when using Nvidia:

OpenGL

renderer: 'NVIDIA GeForce GT 750M OpenGL Engine'
vendor: 'NVIDIA Corporation'
version: '2.1 NVIDIA-10.10.10 310.42.25f01'

And this with integrated graphic:

renderer: 'Intel Iris Pro OpenGL Engine'
vendor: 'Intel Inc.'
version: '2.1 INTEL-10.14.66'

I'm using gfxCardStatus as well.
And Blender 2.76 works on both cards. Tried again with 2.77a and it's still broken on Nvidia mode.

@MikeErwin Mine looks like this when using Nvidia: OpenGL **** renderer: 'NVIDIA GeForce GT 750M OpenGL Engine' vendor: 'NVIDIA Corporation' version: '2.1 NVIDIA-10.10.10 310.42.25f01' And this with integrated graphic: renderer: 'Intel Iris Pro OpenGL Engine' vendor: 'Intel Inc.' version: '2.1 INTEL-10.14.66' I'm using gfxCardStatus as well. And Blender 2.76 works on both cards. Tried again with 2.77a and it's still broken on Nvidia mode.

Mike Erwin commented

2016-08-02 16:44:33 +02:00

Thanks for the info!

Just to recap what we know so far:

We're running the same OS on similar (not identical) hardware.

Current OS 10.11 shows the problem. Older OS 10.9 (with older bundled drivers) works with any Blender version, up to the latest release. MacOS 10.10 was not tried.

Mike first sees problem on Blender 2.76, the moment BLENDER_VERSION changes from 275 to 276. Jerry first sees the problem on Blender 2.77a.

Does the earlier 2.77 (no letter) work for you @Jerry_Yeung?

Thanks for the info! Just to recap what we know so far: We're running the same OS on similar (not identical) hardware. Current OS 10.11 shows the problem. Older OS 10.9 (with older bundled drivers) works with any Blender version, up to the latest release. MacOS 10.10 was not tried. Mike first sees problem on Blender 2.76, the **moment** BLENDER_VERSION changes from 275 to 276. Jerry first sees the problem on Blender 2.77a. Does the earlier 2.77 (no letter) work for you @Jerry_Yeung?

Jerry Yeung commented

2016-08-02 16:54:47 +02:00

@MikeErwin Blender 2.77 is not working as well. So for me it is broken after Blender 2.76b.

Brecht Van Lommel commented

2016-08-12 01:41:04 +02:00

@MikeErwin, do you have different user preferences for 2.75 and 2.76? That seems like the most logical explanation for BLENDER_VERSION causing changes, since they are stored separate per version.

Another possibility is some versioning thing in versioning_270.c, but I can't see anything suspicous.

@MikeErwin, do you have different user preferences for 2.75 and 2.76? That seems like the most logical explanation for BLENDER_VERSION causing changes, since they are stored separate per version. Another possibility is some versioning thing in `versioning_270.c`, but I can't see anything suspicous.

Mike Erwin commented

2016-08-12 01:50:38 +02:00

Good point @brecht. I'll try factory settings for both versions and see if results still differ.

I also looked at versioning_270 and saw nothing weird.

Good point @brecht. I'll try factory settings for both versions and see if results still differ. I also looked at versioning_270 and saw nothing weird.

Jaimi McEntire commented

2017-03-02 19:41:45 +01:00

Added subscriber: @jaimi

Jaimi McEntire commented

2017-03-02 19:41:45 +01:00

I'm seeing this issue as well, it's like it's using the wrong format for normal maps (inverted green channel?) Using the "renderer" shading for the viewport works correctly, just not the "material". I originally assumed it was object vs tangent normal maps, but changing the normal map type on the material did not work (seems like tangent is the only thing that has an effect).

In addition, the normal map occasionally "glitches" in the scene, and looks like dark splotches.

I'm seeing this issue as well, it's like it's using the wrong format for normal maps (inverted green channel?) Using the "renderer" shading for the viewport works correctly, just not the "material". I originally assumed it was object vs tangent normal maps, but changing the normal map type on the material did not work (seems like tangent is the only thing that has an effect). In addition, the normal map occasionally "glitches" in the scene, and looks like dark splotches.

Germano Cavalcante commented

2019-10-28 14:04:38 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2019-10-28 14:04:38 +01:00

Changed status from 'Open' to: 'Archived'

Germano Cavalcante closed this issue

2019-10-28 14:04:38 +01:00

Germano Cavalcante commented

2019-10-28 14:04:38 +01:00

Blender 3D viewport has been rewritten in newer versions (2.80).

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

3D View shading issue dependent on Normal map channel #48772