Displacement not using correct information for instanced object that uses Object Info Random #86779

New Issue

Rodrigo Neira · 2021-03-21T03:19:43+01:00

Rodrigo Neira commented

2021-03-21 03:19:43 +01:00

System Information
Operating system: Linux-5.8.0-7642-generic-x86_64-with-glibc2.32 64 Bits
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.56

Blender Version
Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-03-20 21:00, hash: 9ca67c47a1

NOTE: Also, the same happens in Blender 2.92.0

Short description of error
In a scene with multiple instance objects (instanced from a collection), the Object Info --> Random attribute is working for the Bump node, but not for the Displacement node. Better explained with images:

Here, you can see that the information that the information input of the Height of both Bump and Displacement is the same. A mask showing a number, and that random number selected through a ColorRamp will be the input for both at the same time, ensuring the bump node has the same information as the displacement node.
Still, the bump works fine, as expected:
But the displacement only displaces the information assigned to the original piece inside the collection:

Exact steps for others to reproduce the error

Open the attached scene Rodrigo Neira - Bug Report - Displacement not working in instances.blend
Check the shader editor, and material of ficha.005 --> material ficha_numero
If Bump only is selected for Surface displacement options, and the Bump node connected to the PBR Node --> Normal it works as expected.
If Displacement only is selected for Surface displacement options, and the Displacement node is connected to the Displacement of the Material Output, the displacement only shows the original displacement of the object inside the collection.
- Expected behaviour: Displacement should be using the same number mask/shape as when the bump is used.

NOTE: The same happens if you select Bump & Displacement in Surface displacement options of the material options.
I think this might be a bug - couldn't find if it's a limitation of the displacement already known.
Thanks in advance!!

**System Information** Operating system: Linux-5.8.0-7642-generic-x86_64-with-glibc2.32 64 Bits Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.56 **Blender Version** Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-03-20 21:00, hash: `9ca67c47a1` NOTE: Also, the same happens in Blender 2.92.0 **Short description of error** In a scene with multiple instance objects (instanced from a collection), the **Object Info --> Random** attribute is working for the Bump node, but not for the Displacement node. Better explained with images: - Here, you can see that the information that the information input of the Height of both Bump and Displacement is the same. A mask showing a number, and that random number selected through a ColorRamp will be the input for both at the same time, ensuring the bump node has the same information as the displacement node. ![3_direct_node_number.png](https://archive.blender.org/developer/F9901822/3_direct_node_number.png) - Still, the bump works fine, as expected: ![1_bump_only.png](https://archive.blender.org/developer/F9901824/1_bump_only.png) - But the displacement only displaces the information assigned to the original piece inside the collection: ![2_displacement_only.png](https://archive.blender.org/developer/F9901827/2_displacement_only.png) **Exact steps for others to reproduce the error** 1) Open the attached scene [Rodrigo Neira - Bug Report - Displacement not working in instances.blend](https://archive.blender.org/developer/F9901821/Rodrigo_Neira_-_Bug_Report_-_Displacement_not_working_in_instances.blend) 2) Check the shader editor, and **material of ficha.005 --> material ficha_numero** 3) If Bump only is selected for Surface displacement options, and the Bump node connected to the PBR Node --> Normal it works as expected. 4) If Displacement only is selected for Surface displacement options, and the Displacement node is connected to the Displacement of the Material Output, the displacement only shows the original displacement of the object inside the collection. - > Expected behaviour: Displacement should be using the same number mask/shape as when the bump is used. NOTE: The same happens if you select Bump & Displacement in Surface displacement options of the material options. I think this might be a bug - couldn't find if it's a limitation of the displacement already known. Thanks in advance!!

Rodrigo Neira commented

2021-03-21 03:19:43 +01:00

Added subscriber: @paiorlolo

blender-admin commented

2021-03-21 03:19:43 +01:00

#93990 was marked as duplicate of this issue

Germano Cavalcante commented

2021-03-24 20:54:29 +01:00

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

Germano Cavalcante commented

2021-03-24 20:54:29 +01:00

Added subscriber: @mano-wii

Anthony Pilon commented

2021-05-14 22:58:51 +02:00

Added subscriber: @AnthonyPilon

Kostik Poloskin commented

2021-05-24 02:52:17 +02:00

Added subscriber: @welldoneconan

Germano Cavalcante commented

2021-12-15 19:51:59 +01:00

Added subscriber: @Rowan-Ibbeken

Brecht Van Lommel commented

2021-12-15 20:49:33 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2021-12-15 20:49:33 +01:00

Changed status from 'Confirmed' to: 'Archived'

Brecht Van Lommel closed this issue

2021-12-15 20:49:33 +01:00

Brecht Van Lommel commented

2021-12-15 20:49:33 +01:00

This is a known limitation. If we give every instance a different displacement, that means it's no longer instanced and uses more memory. We may add an option to uninstance objects for this purpose, but for now it's not considered 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

Displacement not using correct information for instanced object that uses Object Info Random #86779