The viewport artifacts associated with the use of normal maps. #46305

New Issue

Alexander Romanov · 2015-09-28T17:47:45+02:00

Alexander Romanov commented

2015-09-28 17:47:45 +02:00

System Information
Ubuntu 14.04.3 LTS

Blender Version
Broken: 2.76 rc2
Worked: 2.75a

Short description of error

Open the attached file
Press Tab to switch into edit mode and backwards several times. See shading artifacts during switching.
In the Geometry node remove UV_01 uvmap. The artifacts will disappear.
In the Texture tab uncheck "beer_column_norm" texture. The artifacts will be removed with the normal map.

Quite a lot of blend4web samples have these unwelcome artifacts in 2.76rc2. So this is very important for us that this bug will be fixed.
uv_bug.blend

**System Information** Ubuntu 14.04.3 LTS **Blender Version** Broken: 2.76 rc2 Worked: 2.75a **Short description of error** 1) Open the attached file 2) Press Tab to switch into edit mode and backwards several times. See shading artifacts during switching. 3) In the Geometry node remove UV_01 uvmap. The artifacts will disappear. 4) In the Texture tab uncheck "beer_column_norm" texture. The artifacts will be removed with the normal map. Quite a lot of blend4web samples have these unwelcome artifacts in 2.76rc2. So this is very important for us that this bug will be fixed. [uv_bug.blend](https://archive.blender.org/developer/F240536/uv_bug.blend)

Alexander Romanov commented

2015-09-28 17:47:45 +02:00

Changed status to: 'Open'

Alexander Romanov commented

2015-09-28 17:47:45 +02:00

Added subscriber: @AlexanderRomanov

Bastien Montagne commented

2015-09-28 19:03:38 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2015-09-28 19:03:38 +02:00

Cannot reproduce any artifact here with latest master (debian64 testing, nvidia 850m, 340 drivers).

Please state your precise GPU & driver versions, and you can also try to start in software OpenGL mode (use the blender-softwaregl distributed with official blender, will be slow, but will show whether this is a driver issue or not).

Cannot reproduce any artifact here with latest master (debian64 testing, nvidia 850m, 340 drivers). Please state your precise GPU & driver versions, and you can also try to start in software OpenGL mode (use the `blender-softwaregl` distributed with official blender, will be slow, but will show whether this is a driver issue or not).

Alexander Romanov commented

2015-09-29 09:29:08 +02:00

GeForce GTX 780
NVIDIA driver version: 352.30

blender-softwaregl crashes:
/tmp/blender.crash.txt:

Blender 2.76 (sub 0), Commit date: 2015-09-23 14:02, Hash `e24ea81`

backtrace

./blender(BLI_system_backtrace+0x1d) [0x1a3d97d]
./blender() [0x10563b4]
./blender() [0x1056591]

GeForce GTX 780 NVIDIA driver version: 352.30 blender-softwaregl crashes: /tmp/blender.crash.txt: # Blender 2.76 (sub 0), Commit date: 2015-09-23 14:02, Hash e24ea81 # backtrace ./blender(BLI_system_backtrace+0x1d) [0x1a3d97d] ./blender() [0x10563b4] ./blender() [0x1056591]

Bastien Montagne commented

2015-09-29 09:53:57 +02:00

Can you make a screenshot of those artifacts, please?

Alexander Romanov commented

2015-09-29 10:22:35 +02:00

With the help of "git bisect" I found that 2ec00ea0c1 is the reason.
And in this commit I see the crash.
Artifact:

With the help of "git bisect" I found that 2ec00ea0c1be1ace7cd0c7b68e43cc8e87dd07c7 is the reason. And in this commit I see the crash. Artifact: ![Screenshot from 2015-09-29 10:36:39.png](https://archive.blender.org/developer/F240815/Screenshot_from_2015-09-29_10_36_39.png)

ronan ducluzeau commented

2015-09-29 10:56:15 +02:00

Added subscriber: @zeauro

ronan ducluzeau commented

2015-09-29 10:56:15 +02:00

I also see same artifacts with an nvidia titan black nvidia driver 355.11.

I confirm that it appears if same UVmap is precised twice.
No problem if UVmap name is set once into Geometry node for AO Texture or into Mapping panel of Texture Tab for normalmap and the other fieldname is blank.
All is black if both fieldnames are blank.

If a second UVmap , copy of first is made and a different UVmap is precise for AO texture and normalmap.
Display is correct.

I also see same artifacts with an nvidia titan black nvidia driver 355.11. I confirm that it appears if same UVmap is precised twice. No problem if UVmap name is set once into Geometry node for AO Texture or into Mapping panel of Texture Tab for normalmap and the other fieldname is blank. All is black if both fieldnames are blank. If a second UVmap , copy of first is made and a different UVmap is precise for AO texture and normalmap. Display is correct.

Bastien Montagne commented

2015-09-29 11:07:48 +02:00

Added subscribers: @Psy-Fi, @ideasman42