Object information is lost when applying geometry nodes #89632

New Issue

brunnerh · 2021-07-03T15:38:27+02:00

brunnerh commented

2021-07-03 15:38:27 +02:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14830 Core Profile Context 21.4.1 27.20.21002.112

Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-07-02 18:27, hash: 5f5cf21a83
Worked: Unknown

Short description of error
Applying geometry nodes loses a lot of relevant shader information, which can cause the object to be completely unusable after the application.

Exact steps for others to reproduce the error

Add an object to be instanced using geometry nodes
Create a material that uses object-specific data, e.g.
- Object Info > Random
- Texture Coordinate > Generated
Add a new object with a geometry nodes modifier that uses Point Instance to instantiate the first object.
Apply the geometry nodes or add another modifier that implicitly applies it (e.g. Array)

To repro from file:

Open .blend file
Apply Geometry nodes modifier

Effect in example file:

Before	After

Example material:

Example file:
geo-apply.blend

Could maybe a special Apply function be added, that causes the instances to be created as actual separate objects?
(That would not solve the situation with additional modifiers after the Geometry Nodes though...)

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14830 Core Profile Context 21.4.1 27.20.21002.112 **Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-07-02 18:27, hash: `5f5cf21a83` Worked: Unknown **Short description of error** Applying geometry nodes loses a lot of relevant shader information, which can cause the object to be completely unusable after the application. **Exact steps for others to reproduce the error** - Add an object to be instanced using geometry nodes - Create a material that uses object-specific data, e.g. - Object Info > Random - Texture Coordinate > Generated - Add a new object with a geometry nodes modifier that uses *Point Instance* to instantiate the first object. - Apply the geometry nodes or add another modifier that implicitly applies it (e.g. *Array*) --- To repro from file: - Open .blend file - Apply Geometry nodes modifier Effect in example file: | Before | After | | -- | -- | | ![image.png](https://archive.blender.org/developer/F10210420/image.png)| ![image.png](https://archive.blender.org/developer/F10210423/image.png) | | ![geo-apply-1.jpg](https://archive.blender.org/developer/F10210431/geo-apply-1.jpg) | ![geo-apply-2.jpg](https://archive.blender.org/developer/F10210433/geo-apply-2.jpg) | Example material: ![image.png](https://archive.blender.org/developer/F10210426/image.png) Example file: [geo-apply.blend](https://archive.blender.org/developer/F10210428/geo-apply.blend) --- Could maybe a special *Apply* function be added, that causes the instances to be created as actual separate objects? (That would not solve the situation with additional modifiers after the Geometry Nodes though...)

brunnerh commented

2021-07-03 15:38:27 +02:00

Added subscriber: @brunnerh

Pratik Borhade commented

2021-08-19 12:59:53 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2021-08-19 12:59:53 +02:00

Thanks for the report. I think this is similar to: #85962 (Many Nodes (Join geometry, Boolean, Object Info?) and realizing instances remove UVs (output float2, not MLoopUV).)

brunnerh commented

2021-08-19 19:18:23 +02:00

@PratikPB2123 Yes, this is similar in that data is lost, but this is not about the UVs.

Aside from object IDs, curves also are lost, presumably because the resulting singular object cannot be a mesh and curve at the same time.
If you look at my book shelf example, you can see curve based ornaments at the bottom, they can be joined using Join Geometry but upon application they disappear.

@PratikPB2123 Yes, this is similar in that data is lost, but this is not about the UVs. Aside from object IDs, curves also are lost, presumably because the resulting singular object cannot be a mesh and curve at the same time. If you look at my book shelf example, you can see curve based ornaments at the bottom, they can be joined using Join Geometry but upon application they disappear.

Pratik Borhade commented

2021-08-20 07:09:47 +02:00

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

Jacques Lucke commented

2021-08-25 16:59:25 +02:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2021-08-25 16:59:25 +02:00

Changed status from 'Confirmed' to: 'Archived'

Jacques Lucke closed this issue

2021-08-25 16:59:25 +02:00

Jacques Lucke commented

2021-08-25 16:59:25 +02:00

When you combine multiple objects into one, then the Object Info node in cycles will output the same random value for every vertex in that object. That is expected. However, I can see that it can be a bit confusing sometimes when you are not aware that your shader depends on there being separate objects.
There are some limitations when it comes to applying instances, but I don't consider this to be a bug currently.

Could maybe a special Apply function be added, that causes the instances to be created as actual separate objects?

You can use the F3 -> Make Instances Real operator for that.

When you combine multiple objects into one, then the Object Info node in cycles will output the same random value for every vertex in that object. That is expected. However, I can see that it can be a bit confusing sometimes when you are not aware that your shader depends on there being separate objects. There are some limitations when it comes to applying instances, but I don't consider this to be a bug currently. > Could maybe a special Apply function be added, that causes the instances to be created as actual separate objects? You can use the `F3 -> Make Instances Real` operator for that.

brunnerh commented

2021-08-25 21:56:06 +02:00

Make Instances Real is good to know about, though it also has the limitation that the result will not be equivalent.
The names of the generated instances will affect the randomness in the shader, so all those instances will look different than those in the source object.

`Make Instances Real` is good to know about, though it also has the limitation that the result will not be equivalent. The names of the generated instances will affect the randomness in the shader, so all those instances will look different than those in the source object.

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 information is lost when applying geometry nodes #89632