Object attribute node in material stops working from level of complexity(?) #117967

New Issue

Albert-OShea · 2024-02-07T23:53:43+01:00

Albert-OShea commented

2024-02-07 23:53:43 +01:00

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 522.30

Blender Version
Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: 9be62e85b727
Also broken in 4.2 alpha

Feel free to replace the title with something better, I don't really understand what is going on.

Short description of error
My material has a lot of attribute nodes that read the object's custom properties. For whatever reason, a specific area of the node group stops working, seemingly due to the number or complexity of attribute nodes elsewhere in the material, as when removing any of these nodes, it begins working again.

Exact steps for others to reproduce the error

Download attached blend file
See PULSE_STRENGTH custom property of cylinder, and relevant attribute node in material. This is the area that doesn't work - adjusting PULSE_STRENGTH property does nothing, even though the property is correctly referenced by the attribute node, proven by previewing the node with node wrangler's preview.
Remove the connection between the PULSE_STRENGTH attribute node and the emission node. Replace the connection with the Value node above it. Play with the value, this now works when reading it from the Value node.
Reconnect the PULSE_STRENGTH node to get back to the broken state. Then, disconnect any other attribute node in the material. For example, disconnect the wave_color attribute node from the leftmost Mix node. The PULSE_STRENGTH custom property now works correctly.

**System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 522.30 **Blender Version** Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: `9be62e85b727` Also broken in 4.2 alpha Feel free to replace the title with something better, I don't really understand what is going on. **Short description of error** My material has a lot of attribute nodes that read the object's custom properties. For whatever reason, a specific area of the node group stops working, seemingly due to the number or complexity of attribute nodes elsewhere in the material, as when removing any of these nodes, it begins working again. **Exact steps for others to reproduce the error** - Download attached blend file - See PULSE_STRENGTH custom property of cylinder, and relevant attribute node in material. This is the area that doesn't work - adjusting PULSE_STRENGTH property does nothing, even though the property is correctly referenced by the attribute node, proven by previewing the node with node wrangler's preview. - Remove the connection between the PULSE_STRENGTH attribute node and the emission node. Replace the connection with the Value node above it. Play with the value, this now works when reading it from the Value node. - Reconnect the PULSE_STRENGTH node to get back to the broken state. Then, disconnect any other attribute node in the material. For example, disconnect the wave_color attribute node from the leftmost Mix node. The PULSE_STRENGTH custom property now works correctly.

obj_attr_material_bug.blend

670 KiB

Albert-OShea added the

labels 2024-02-07 23:53:44 +01:00

Albert-OShea commented

2024-02-08 05:43:39 +01:00

Update: Looks like this is an EEVEE issue. Rendering it in cycles does make the property work.

Jesse Yurkovich commented

2024-02-08 06:56:03 +01:00

EEVEE material shaders have a limit of 8 attributes. This limitation is waiting to be documented as part of #108534. I'll close this as a duplicate but feel free to subscribe to that other issue for updates on the matter.

Jesse Yurkovich closed this issue

2024-02-08 06:56:06 +01:00

Blender Bot added

and removed

labels 2024-02-08 06:56:08 +01:00

Jesse Yurkovich added

Status

Duplicate