"Object Info" shader node doesn't works with Geometry Nodes #87819

New Issue

Aleksandr · 2021-04-26T12:24:02+02:00

Aleksandr commented

2021-04-26 12:24:02 +02:00

System Information
Operating system: Linux-4.15.0-142-generic-x86_64-with-glibc2.27 64 Bits
Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.119.03

Blender Version
Broken: version: 2.93.0 Beta, branch: master, commit date: 2021-04-25 22:55, hash: db3b610040
Worked: (newest version of Blender that worked as expected)

Short description of error
"Object Info" shader node "Random" socket doesn't works with Geometry Nodes instances. Couple of builds before, it was workable.

Exact steps for others to reproduce the error
Open my file and check that "Object Info" shader node works fine with regular copies and instances but absolutely doesn't works with Geometry Nodes.

GeoNodes_ObjectInfo_Bug.blend

**System Information** Operating system: Linux-4.15.0-142-generic-x86_64-with-glibc2.27 64 Bits Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.119.03 **Blender Version** Broken: version: 2.93.0 Beta, branch: master, commit date: 2021-04-25 22:55, hash: `db3b610040` Worked: (newest version of Blender that worked as expected) **Short description of error** "Object Info" shader node "Random" socket doesn't works with Geometry Nodes instances. Couple of builds before, it was workable. **Exact steps for others to reproduce the error** Open my file and check that "Object Info" shader node works fine with regular copies and instances but absolutely doesn't works with Geometry Nodes. ![Screenshot_20210426_131414.png](https://archive.blender.org/developer/F10038974/Screenshot_20210426_131414.png) ![Screenshot_20210426_132142.png](https://archive.blender.org/developer/F10038976/Screenshot_20210426_132142.png) [GeoNodes_ObjectInfo_Bug.blend](https://archive.blender.org/developer/F10038973/GeoNodes_ObjectInfo_Bug.blend)

Aleksandr commented

2021-04-26 12:24:02 +02:00

Added subscriber: @viadvena

Aleksandr commented

2021-04-26 12:45:27 +02:00

Actually, materials completely unworkable with GeoNodes instances. Now I tried to change color of material of the instance source and it's broken.

Aleksandr commented

2021-04-26 13:06:54 +02:00

Sorry! I didn't know that modifiers after GeoNodes modifier are influence on top of the source and also on instances. Is that final concept of GeoNodes? It's inconvenient for me. It would be much better and much useful for procedural modeling if modifiers after GeoNodes modifier will influence only on target mesh and instances could have own modifiers (it's logical because you can continue edit instance source and adds some modifiers on them as it was all the time). Or using nodes to influence on instances (i think this way will be implemented in the future - roadmap is to add many modifiers inside of nodes i believe).

Aleksandr commented

2021-04-26 13:18:36 +02:00

Materials working if I place GeoNodes modifier in the end. But it's bad way because instead of 1 instance I get 8 on cross of edge due generated mesh in Wireframe modifier. Now I need to copy mesh without modifiers but with GeoNodes and synchronize it with mesh that includes Wireframe modifier. I hope developers will change the way how processing of modifiers priority works.

Materials working if I place GeoNodes modifier in the end. But it's bad way because instead of 1 instance I get 8 on cross of edge due generated mesh in Wireframe modifier. Now I need to copy mesh without modifiers but with GeoNodes and synchronize it with mesh that includes Wireframe modifier. I hope developers will change the way how processing of modifiers priority works. ![Screenshot_20210426_140746.png](https://archive.blender.org/developer/F10039035/Screenshot_20210426_140746.png)

Hans Goudey commented

2021-04-26 18:32:57 +02:00

Added subscriber: @HooglyBoogly

Hans Goudey commented

2021-04-26 18:32:57 +02:00

Changed status from 'Needs Triage' to: 'Archived'

Hans Goudey closed this issue

2021-04-26 18:32:57 +02:00

Hans Goudey commented

2021-04-26 18:32:57 +02:00

Thanks for the report, but this is not a bug. Modifier evaluation will always happen in order, and if you add a modifier after the geometry nodes modifier, it will realize the instances, meaning they won't be seen as separate objects in a renderer. These are pretty fundamental ideas.

The real solution here is supporting the wireframe modifier as a node. I'm sure that will come eventually, but yeah, it's not a bug.

Thanks for the report, but this is not a bug. Modifier evaluation will always happen in order, and if you add a modifier after the geometry nodes modifier, it will realize the instances, meaning they won't be seen as separate objects in a renderer. These are pretty fundamental ideas. The real solution here is supporting the wireframe modifier as a node. I'm sure that will come eventually, but yeah, it's not a bug.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

"Object Info" shader node doesn't works with Geometry Nodes #87819