Normal Map in Material Node going wrong #41829

New Issue

Doc Holiday · 2014-09-14T14:27:16+02:00

Doc Holiday commented

2014-09-14 14:27:16 +02:00

Win7 64bit; Radeon HD 6950

Blender 2.71 - 9337574

Short description of error

Set Blender to "Blender Game" Mode.

Adding a normal Map to a regular Material working fine.
Set a Material to Node-Mode, and add a Normal Map there, it behaves incorrectly.

best regards.

Mat_Nor_vs_Node_Nor.blend

Win7 64bit; Radeon HD 6950 Blender 2.71 - 9337574 **Short description of error** Set Blender to "Blender Game" Mode. Adding a normal Map to a regular Material working fine. Set a Material to Node-Mode, and add a Normal Map there, it behaves incorrectly. best regards. [Mat_Nor_vs_Node_Nor.blend](https://archive.blender.org/developer/F110337/Mat_Nor_vs_Node_Nor.blend)

Doc Holiday commented

2014-09-14 14:27:16 +02:00

Changed status to: 'Open'

Doc Holiday commented

2014-09-14 14:27:16 +02:00

Added subscriber: @doc_holiday

Fabian Hachenberg commented

2014-09-15 22:13:40 +02:00

Added subscriber: @FabianHachenberg

Fabian Hachenberg commented

2014-09-15 22:13:40 +02:00

The difference in appearence is due to a general difference between the normals.
You can achieve the same appearance in node mode as in regular mode by adding an additional transformation for the normals of (manually approximated)

Rotation: X 311°, Y -40°, Z -27°
Scale: X 1.0 Y 1.0 Z -1.0

The difference in appearence is due to a general difference between the normals. You can achieve the same appearance in node mode as in regular mode by adding an additional transformation for the normals of (manually approximated) Rotation: X 311°, Y -40°, Z -27° Scale: X 1.0 Y 1.0 Z -1.0

Fabian Hachenberg commented

2014-09-15 22:15:17 +02:00

And the bug is also present in Blender Render mode

Fabian Hachenberg commented

2014-09-15 22:21:51 +02:00

I have to correct my previous statement:
It appears that the normals are simply inverted and there's an additional difference in the weighting factor of the normal mapping in the material color.

I have to correct my previous statement: It appears that the normals are simply inverted and there's an additional difference in the weighting factor of the normal mapping in the material color.

Adam Friesen commented

2014-09-15 23:37:52 +02:00

Added subscriber: @Ace_Dragon

Adam Friesen commented

2014-09-15 23:37:52 +02:00

The issue is that the type of normal data expected by the material node is different from the data produced by a normal map.

This has likely been the case since the introduction of nodes in Blender 2.40, it extends to the GLSL system because that has been designed to mimic the results from BI.

To get what you want, you need to perform operations using normal and coordinate data, like seen here in this concept node group that produces a reasonable approximation derived from a normal map.

To be honest though, it would be nice to have a 'normal map' node for BI and the BGE that does the conversion for you like already seen with Cycles.

The issue is that the type of normal data expected by the material node is different from the data produced by a normal map. This has likely been the case since the introduction of nodes in Blender 2.40, it extends to the GLSL system because that has been designed to mimic the results from BI. To get what you want, you need to perform operations using normal and coordinate data, like seen here in this concept node group that produces a reasonable approximation derived from a normal map. ![bge_normalNodesEx.jpg](https://archive.blender.org/developer/F110638/bge_normalNodesEx.jpg) To be honest though, it would be nice to have a 'normal map' node for BI and the BGE that does the conversion for you like already seen with Cycles.

Alexander N. commented

2014-09-16 19:23:13 +02:00

Added subscriber: @beta-tester

Alexander N. commented

2014-09-16 19:23:13 +02:00

I can confirm that strange behavior. (windows 8.1 64bit, blender 2.71 64bit)
the shown workarounds are not satisfactory to me.
the behavior should be the same in all cases - with or without using nodes - it should give the same result.
I would like to see a easy, logical and consistent solution here.

I can confirm that strange behavior. (windows 8.1 64bit, blender 2.71 64bit) the shown workarounds are not satisfactory to me. the behavior should be the same in all cases - with or without using nodes - it should give the same result. I would like to see a easy, logical and consistent solution here.

Jorge Bernal commented

2015-02-17 10:42:38 +01:00

Added subscriber: @JorgeBernalMartinez

Jorge Bernal commented

2015-02-17 10:42:38 +01:00

Differential D1120 related to this task

Differential [D1120](https://archive.blender.org/developer/D1120) related to this task

Mike Pan commented

2015-02-20 02:57:21 +01:00

Added subscriber: @MikePan

Mike Pan commented

2015-02-20 02:57:21 +01:00

Neither Omni nor Ace_dragon's solution seem to approximate the built-in normal map functionality. Am thinking it's not going to be possible until D1120 is implemented because we don't have access to Tangent data right now from the geometry node.

Neither Omni nor Ace_dragon's solution seem to approximate the built-in normal map functionality. Am thinking it's not going to be possible until [D1120](https://archive.blender.org/developer/D1120) is implemented because we don't have access to Tangent data right now from the geometry node.

Jeff Whiteside commented

2016-06-05 00:41:03 +02:00

Added subscriber: @jsidewhite