Normal Map node gives strange artifacts #121166
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#121166
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Blender Version
Broken: 4.1.1
Short description of error
The "Normal Map" node gives strange artifacts (it should look uniform) in this setup.
Exact steps for others to reproduce the error
The report should be simplified more properly.
I am not familiar with "normal map" node enough to say if this is a bug or anything.
You're applying a tangent space normal map with no tangent space.Normally the shader uses the active UV channel to compute one, but a curve doesn't have UV channels.Typing the name of the attribute in the Normal Map node should intuitively do the trick, but currently doesn't. Not sure if oversight or todo.(note: can't do that on a mesh either - face corner attributes can't be selected on Normal Map node)Alternatively, it's possible to switch normal map to world space mode, and compute tangents/bitangents manually, but that's quite a bit more involved.Edit: actually, the fix is simple: change Store Named Attribute from "Vector" to "2D Vector", then it will be recognized as a UV Map properly
This seems weird to me. I wouldn't expect this to happen with the simplified case (not setting and using any attributes), but it does. But then when setting this attribute as 2D vector, but not using it anywhere it really makes UV mapping correct...
I guess I will confirm on this basis, but I also am not super knowledgeable in this area.
I'll add that the example blend file has two more problems unrelated to the tangent space issue.
Not sure if this is issue on geometry nodes side.
Thank you everyone! Your solutions worked! There were multiple problems (the ones you described). Guess this can be closed now.
Thanks for update, will close then.