Geometry Node: Order of connection to Join Geometry node affect on shader local space #106578

Open
opened 2023-04-05 00:51:43 +02:00 by Rincewind · 6 comments

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18

Blender Version
Broken: Main
Worked: Never

Simplified report:

Short description of error
Order of connection to Join Geometry node affect on shader local space:

image image

Video example

Exact steps for others to reproduce the error

  1. On default cube:
    a. Created shader with noise.
    b. Create geometry node tree.
  2. Create other cube, trhansform that.
  3. In first cube, add Object Info node for represent second cube.
  4. Add Join Geometry node, connect Object Info and Group Input nodes in Join Geometry node input.
  5. Try to render this object. Switch connection in Join Geometry node.
    Expect: Local space of noise used only for one of joined objects and depend of connections order.
    Example File

Original report:

Short description of error
The way how normals are rendered are affacted when I use a geometry node with delete and join.

Exact steps for others to reproduce the error

Setup:

grafik

grafik

Output without geometry node:

grafik

Output with geometry node:

grafik

The normals seems to have a different scale.

This is the follow up of #102189, which fixed the uv maps. These are working now as expected, seems to be a normal only issue.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18 **Blender Version** Broken: Main Worked: Never ### Simplified report: **Short description of error** Order of connection to Join Geometry node affect on shader local space: | | | | -- | -- | | ![image](/attachments/b1e316d4-1c7b-4c6b-b5d6-37ec478a8648) | ![image](/attachments/3e54287c-4a68-486d-b80a-0826202e648f) | ![Video example](/attachments/4e43bd27-a4ab-4ea7-9cd6-144dcbe7f91b) **Exact steps for others to reproduce the error** 1. On default cube: a. Created shader with noise. b. Create geometry node tree. 2. Create other cube, trhansform that. 3. In first cube, add `Object Info` node for represent second cube. 4. Add `Join Geometry` node, connect `Object Info` and `Group Input` nodes in `Join Geometry` node input. 5. Try to render this object. Switch connection in `Join Geometry` node. Expect: Local space of noise used only for one of joined objects and depend of connections order. ![Example File](/attachments/49983afd-0ef9-4ff0-95ad-f1d916a623c5) ### Original report: **Short description of error** The way how normals are rendered are affacted when I use a geometry node with delete and join. **Exact steps for others to reproduce the error** Setup: ![grafik](/attachments/eae96820-3a8b-457e-b9c0-e5f9405ef9b7) ![grafik](/attachments/bc798d40-431a-46eb-bab1-dca421920275) Output without geometry node: ![grafik](/attachments/4d3049e3-ec3c-4644-9db3-44ccdb3681ed) Output with geometry node: ![grafik](/attachments/f21ffd44-5bee-4588-a229-4eca302525fc) The normals seems to have a different scale. This is the follow up of #102189, which fixed the uv maps. These are working now as expected, seems to be a normal only issue.
Rincewind added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-04-05 00:51:44 +02:00
Iliya Katushenock changed title from Geonodes delete and join geometry might change normal output in an unintended way to Geometry Node: Order of connection to Join Geometry node affect on shader local space 2023-04-05 14:35:17 +02:00
Iliya Katushenock changed title from Geometry Node: Order of connection to Join Geometry node affect on shader local space to Regression: Geometry Node: Order of connection to Join Geometry node affect on shader local space 2023-04-05 14:49:14 +02:00
Iliya Katushenock changed title from Regression: Geometry Node: Order of connection to Join Geometry node affect on shader local space to Geometry Node: Order of connection to Join Geometry node affect on shader local space 2023-04-05 15:09:29 +02:00
Author

@mod_moder
Just tested todays Blender Alpha build bc86223975.

Either your bugfix #106578 didn't work or it's not in today's build.

Still broken for me.

@mod_moder Just tested todays Blender Alpha build bc8622397557. Either your bugfix #106578 didn't work or it's not in today's build. Still broken for me.

@Rincewind3D This is not yet an accepted option. And as a result, it will simply remove the dependency on the order.

@Rincewind3D This is not yet an accepted option. And as a result, it will simply remove the dependency on the order.
Author

@Rincewind3D This is not yet an accepted option. And as a result, it will simply remove the dependency on the order.

sorry I'm not understanding your answer.
about which option you are talking? and what dependeny order?
Discalaimer: I'm a non Blender developer.

> @Rincewind3D This is not yet an accepted option. And as a result, it will simply remove the dependency on the order. sorry I'm not understanding your answer. about which option you are talking? and what dependeny order? Discalaimer: I'm a non Blender developer.

The local texture space of the object (mesh) is determined based on your transformations.
In geometry nodes, now when you joined multiple meshes, the texture space is only used from the first mesh. From this dependence on the order.
I suggested a fix. It hasn't been accepted yet. Its essence is that all texture spaces are used to average them.
But if you don't enter 1 mesh, the result will be different anyway.

The local texture space of the object (mesh) is determined based on your transformations. In geometry nodes, now when you joined multiple meshes, the texture space is only used from the first mesh. From this dependence on the order. I suggested a fix. It hasn't been accepted yet. Its essence is that all texture spaces are used to average them. But if you don't enter 1 mesh, the result will be different anyway.
Author

Arg I was blind. Didn't regocnized that your PR wasn't merged yet. My bad.

Arg I was blind. Didn't regocnized that your PR wasn't merged yet. My bad.
Author

Tested in Blender 4.0.2. This is still an open issue. Is there any reason why the fix #106711 from @mod_moder is not merged yet?

Tested in Blender 4.0.2. This is still an open issue. Is there any reason why the fix #106711 from @mod_moder is not merged yet?
Iliya Katushenock added
Type
Known Issue
and removed
Type
Report
labels 2024-01-02 16:27:27 +01:00
Sign in to join this conversation.
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
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#106578
No description provided.