Random Per Island working incorrectly with sharp edges and volumes #72284

New Issue

mantissa · 2019-12-09T00:09:21+01:00

mantissa commented

2019-12-09 00:09:21 +01:00

System Information
Operating system: Linux-5.0.0-36-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: TITAN X (Pascal)/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.50

Blender Version
Broken: version: 2.82 (sub 4), branch: master, commit date: 2019-12-07 19:38, hash: 416e66c7fe
Worked: (optional)

Short description of error
Random Per Island not working correctly with sharp edges or volumes.

Exact steps for others to reproduce the error

Sharp Edges:

Create Cube
Add Bevel Modifier with Harden Normals
Set Smooth Shading
Set Auto Smooth
Random Per Island is affected incorrectly by sharp edges, even after applying Bevel modifier

Volumes:

Create cube (or array of objects)
Create volume shader
Assign Random Per Island to volume shader
No random colors

random_per_island.blend

**System Information** Operating system: Linux-5.0.0-36-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: TITAN X (Pascal)/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.50 **Blender Version** Broken: version: 2.82 (sub 4), branch: master, commit date: 2019-12-07 19:38, hash: `416e66c7fe` Worked: (optional) **Short description of error** Random Per Island not working correctly with sharp edges or volumes. **Exact steps for others to reproduce the error** Sharp Edges: - Create Cube - Add Bevel Modifier with Harden Normals - Set Smooth Shading - Set Auto Smooth - Random Per Island is affected incorrectly by sharp edges, even after applying Bevel modifier Volumes: - Create cube (or array of objects) - Create volume shader - Assign Random Per Island to volume shader - No random colors [random_per_island.blend](https://archive.blender.org/developer/F8200178/random_per_island.blend)

mantissa commented

2019-12-09 00:09:21 +01:00

Added subscriber: @Mantissa

blender-admin commented

2019-12-09 00:09:21 +01:00

#102001 was marked as duplicate of this issue

blender-admin commented

2019-12-09 00:09:21 +01:00

#102710 was marked as duplicate of this issue

blender-admin commented

2019-12-09 00:09:21 +01:00

#95619 was marked as duplicate of this issue

blender-admin commented

2019-12-09 00:09:21 +01:00

#85265 was marked as duplicate of this issue

Benny Govaerts commented

2019-12-21 01:04:29 +01:00

Added subscriber: @BennyG

Benny Govaerts commented

2019-12-21 01:04:29 +01:00

I have the same problem with blender v2.82.6

Sharp Edges:

Create Cube
Add Bevel Modifier with Harden Normals
Set Smooth Shading
Set Auto Smooth On Angle to 30
Random Per Island is affected incorrectly by sharp edges, even after applying Bevel modifier or weld modifier

I have the same problem with blender v2.82.6 Sharp Edges: Create Cube Add Bevel Modifier with Harden Normals Set Smooth Shading Set Auto Smooth On Angle to 30 Random Per Island is affected incorrectly by sharp edges, even after applying Bevel modifier or weld modifier

Jacques Lucke commented

2019-12-29 17:14:16 +01:00

Added subscribers: @OmarEmaraDev, @Sergey, @JacquesLucke

Jacques Lucke commented

2019-12-29 17:14:16 +01:00

Hm, not sure if there is a good fix for that. It seems that Blender splits edges apart when the Auto Smooth option is used.

@OmarEmaraDev @Sergey Is there a way to access the connectivity data in cycles before the splitting happens?

Hm, not sure if there is a good fix for that. It seems that Blender splits edges apart when the Auto Smooth option is used. @OmarEmaraDev @Sergey Is there a way to access the connectivity data in cycles before the splitting happens?

Omar Emara commented

2019-12-29 18:27:18 +01:00

I am not sure, I haven't seen anything in the code that indicates that.

Sergey Sharybin commented

2020-01-02 11:04:29 +01:00

This is more of a limitation of attributes and auto-smooth in Cycles. This affects pointiness and random-per-island, but also motion blur to some extent.

Ideally, attributes for those featured would be calculated prior to auto-smooth is applied and then copied over to a newly created vertices.
There isn't really simple solution, so will consider this a known limitaiton of the system which will be eventually resolved. See the developer note below.

More in-dept developer note.

This is actually how Cycles was initially dealing with attributes: it was creating them for vertices/faces and only after this it was splitting sharp edges. Tricky thing is, the way how Cycles splits edges need to match the way how Blender does it and with an addition of custom normals this became more and more problematic. Eventually, the sharp edge split was left to a Blender side, so then all areas are doing it exactly the same (modifier stack, viewport, Cycles render).

From possible ways to solve the issue I see:

Move pointiness and random-per-island attributes to Blender side, calculated prior to sharp edge split. This will additionally make it possible to use those attributes in Eevee, yay!
Add a version of sharp edge split utility which will only tag edges which are to be split. This will allow Cycles to use same splitting rules as the rest of Blender, but will allow Cycles to keep track of its attributes.

This is more of a limitation of attributes and auto-smooth in Cycles. This affects pointiness and random-per-island, but also motion blur to some extent. Ideally, attributes for those featured would be calculated prior to auto-smooth is applied and then copied over to a newly created vertices. There isn't really simple solution, so will consider this a known limitaiton of the system which will be eventually resolved. See the developer note below. More in-dept developer note. This is actually how Cycles was initially dealing with attributes: it was creating them for vertices/faces and only after this it was splitting sharp edges. Tricky thing is, the way how Cycles splits edges need to match the way how Blender does it and with an addition of custom normals this became more and more problematic. Eventually, the sharp edge split was left to a Blender side, so then all areas are doing it exactly the same (modifier stack, viewport, Cycles render). From possible ways to solve the issue I see: - Move pointiness and random-per-island attributes to Blender side, calculated prior to sharp edge split. This will additionally make it possible to use those attributes in Eevee, yay! - Add a version of sharp edge split utility which will only tag edges which are to be split. This will allow Cycles to use same splitting rules as the rest of Blender, but will allow Cycles to keep track of its attributes.

Philipp Oeser commented

2020-01-15 20:21:24 +01:00

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

Guilherme Maia commented

2020-03-12 04:45:41 +01:00

Added subscriber: @Maia3D

Guilherme Maia commented

2020-03-12 04:45:41 +01:00

Yes, I'm having the same problem. This needs to be fixed, specially because even after we apply the bevel, it continues broken.

Really, it is the Auto Smooth splitting the edges.

also check this file:
AutoSmooth_RandomPerIsland.blend

I only add suzanne, activated auto smooth and applied random per island.

Also, why Bevel modifier doesn't use the same method as Weighted Normals? Weighted Normal doesn't splits the edges (at least when Keep Sharp is off).
Bevel could use Weighted Normal under the hood, but feeding it with the new created faces. Well, I'm only a user, not a developer, so maybe i'm wrong.

Yes, I'm having the same problem. This needs to be fixed, specially because even after we apply the bevel, it continues broken. Really, it is the Auto Smooth splitting the edges. also check this file: [AutoSmooth_RandomPerIsland.blend](https://archive.blender.org/developer/F8401729/AutoSmooth_RandomPerIsland.blend) I only add suzanne, activated auto smooth and applied random per island. Also, why Bevel modifier doesn't use the same method as Weighted Normals? Weighted Normal doesn't splits the edges (at least when Keep Sharp is off). Bevel could use Weighted Normal under the hood, but feeding it with the new created faces. Well, I'm only a user, not a developer, so maybe i'm wrong.

Andrew Grabko commented

2020-03-23 09:48:56 +01:00

Added subscriber: @ttrevan

Eugene Du commented

2020-06-25 14:57:28 +02:00

Added subscriber: @APEC

Philipp Oeser commented

2021-02-01 10:24:51 +01:00

Added subscribers: @NahuelBelich, @lichtwerk

Christopher Kumm commented

2022-01-27 09:18:23 +01:00

Added subscriber: @ChrisCrossCrash

Christopher Kumm commented

2022-01-27 09:18:23 +01:00

At a minimum, perhaps a note could be added to the Geometry Node documentation so that users will know of this limitation.

At a minimum, perhaps a note could be added to the [Geometry Node documentation](https://docs.blender.org/manual/en/latest/render/shader_nodes/input/geometry.html) so that users will know of this limitation.

Philipp Oeser commented

2022-03-28 14:18:51 +02:00

Added subscribers: @slowburn, @HooglyBoogly, @PratikPB2123

Shmuel Israel commented

2022-08-30 15:16:41 +02:00

Added subscriber: @shmuel

Shmuel Israel commented

2022-08-30 15:16:41 +02:00

the volume never worked and as it says in the documentation that most the inputs of the geometry node doesn't work for volumes

Germano Cavalcante commented

2022-11-23 14:08:00 +01:00

Added subscribers: @mod_moder, @mano-wii

Iliya Katushenock commented

2022-11-23 15:30:36 +01:00

Would it be possible to consider using geometry groups to auto-generate this? That is, so that temporary nodes would be created, executed and their result used in the render. Then, it would also allow working versions of implementations of this from geometry nodes to be reused.

Hans Goudey commented

2023-01-17 00:49:44 +01:00

Added subscriber: @crantisz

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Random Per Island working incorrectly with sharp edges and volumes #72284