Joining meshes or realizing instances in geometry nodes removes custom normals data #91048
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#91048
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?
System Information
Operating system: macOS Big Sur 11.5.2
Graphics card: Apple M1
Blender Version
Broken: 2.93 and 3.0 Alpha
Short description of error
Using the collection info node in geometry nodes destroys custom normals data when the geometry node modifier is applied (or when the project is exported).
Exact steps for others to reproduce the error
Apply the geometry node modifier on the "Dummy" object in the attached blender project. I've also included a video that shows the issue.collection_info_test.blend
collection_info_bug.mov
Added subscriber: @nis
Added subscriber: @PratikPB2123
Added subscribers: @HooglyBoogly, @JacquesLucke, @lichtwerk
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
A bit will survive as attributes (but not really usable as-is):
@JacquesLucke : @HooglyBoogly : this would also be the same ballpark as {#89054}?
(though normals are not even stored into attributes...)
Yeah, we haven't looked into supporting custom normals in geometry nodes yet. They should be a vector attribute on the face corner domain, editable just like any other attribute. But I wouldn't expect it to work until then.
collection info node in geometry nodes destroys custom normals datato Joining meshes or realizing instances in geometry nodes removes custom normals dataUntil we decide how to handle custom normal data in geometry nodes, this situation is unlikely to change.
Theoretically it might not be complicated-- there could be a "Set Custom Normals' node that evaluates a vector field on the face corner domain. But that may require other changes or more design thought.
Sure. I find it a bit confusing though, that the normals are only destroyed the moment the geometry nodes modifier is baked down when hitting apply. If geometry nodes can't handle custom normals the logical thing would be to remove the custom normals as soon as the modifier is added to the object. Currently, the modifier behaves differently when it is applied (compared to how it works when it is attached) which feels buggy.
Added subscriber: @Festivity