Geometry nodes boolean uvs of operand lost in result #89357

New Issue

stephen leger · 2021-06-22T12:50:08+02:00

stephen leger commented

2021-06-22 12:50:08 +02:00

System Information
Operating system: Mint 20
Graphics card: irrelevant

Blender Version
Broken: (example: 2.93+)
Worked: (not aware of any working version)

Short description of error
Boolean geo node destroys source objects uvs

Exact steps for others to reproduce the error
#89357.blend

Open file
Apply geometry nodes modifier

Result loose box uvs, only cutter uvs are preserved.

**System Information** Operating system: Mint 20 Graphics card: irrelevant **Blender Version** Broken: (example: 2.93+) Worked: (not aware of any working version) **Short description of error** Boolean geo node destroys source objects uvs **Exact steps for others to reproduce the error** [#89357.blend](https://archive.blender.org/developer/F10187882/T89357.blend) - Open file - Apply geometry nodes modifier Result loose box uvs, only cutter uvs are preserved.

stephen leger commented

2021-06-22 12:50:08 +02:00

Added subscriber: @StephenLeger

Richard Antalik commented

2021-06-22 14:59:21 +02:00

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

Richard Antalik commented

2021-06-22 15:10:29 +02:00

Added subscriber: @iss

Richard Antalik commented

2021-06-22 15:10:29 +02:00

Actually I checked that when I replicate conventional modifier setup with just Object Info nodes and 2 boolean modifier nodes, UV seems to match conventional modifier setup.

So problem seems to be using Collection Info as geometry source. Not sure if this would be bug though.

Actually I checked that when I replicate conventional modifier setup with just Object Info nodes and 2 boolean modifier nodes, UV seems to match conventional modifier setup. So problem seems to be using Collection Info as geometry source. Not sure if this would be bug though.

Howard Trickey commented

2021-06-23 05:08:42 +02:00

Added subscriber: @howardt

Howard Trickey self-assigned this 2021-06-23 05:08:42 +02:00

Howard Trickey commented

2021-06-23 05:08:42 +02:00

I'll look at this.

Hans Goudey commented

2021-06-24 05:10:43 +02:00

Added subscriber: @HooglyBoogly

Hans Goudey commented

2021-06-24 05:10:43 +02:00

I'll note that though this might not be the issue here, currently there is a known issue with many geometry nodes that they output generic 2D float vector attributes instead of the special "UV" custom data types. This is because the loose plan is to move to generic attribute types here.

Philipp Oeser commented

2021-07-01 14:21:49 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-07-01 14:21:49 +02:00

So the underlying problem is the the same as #85962 (Many Nodes (Join geometry, Boolean, Object Info?) and realizing instances remove UVs (output float2, not MLoopUV).), right?

#89570 (UVs are destroyed after applying the geometry nodes modifier when object info node is used to pass the geometry.) also seems like a duplicate.

Will merge all these.

So the underlying problem is the the same as #85962 (Many Nodes (Join geometry, Boolean, Object Info?) and realizing instances remove UVs (output float2, not MLoopUV).), right? #89570 (UVs are destroyed after applying the geometry nodes modifier when object info node is used to pass the geometry.) also seems like a duplicate. Will merge all these.

Philipp Oeser commented

2021-07-01 14:25:06 +02:00

Closed as duplicate of #85962

Philipp Oeser closed this issue

2021-07-01 14:25:06 +02:00

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

Geometry nodes boolean uvs of operand lost in result #89357