EEVEE: Document attribute and property limitations #104697
No reviewers
Labels
No Label
Meta
Good First Issue
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Eevee & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds, Tests & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-manual#104697
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "deadpin/blender-manual:deadpin-patch-1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Related to blender/blender#108534
Folks keep running into this it seems so I put the PR together to get things moving.
There looks to be 2 limits but one of them seems a bit broken.
The first, from an empirical test seems to indicate 14 useful Geometry Node attributes before the shader "breaks". Are we off by one somewhere?
The second, from blender/blender#117967, is correctly handled when Custom Object Properties are set.
Clement is better suited to review this as it concerns some internal areas of EEVEE.
To fill in more details, the reason why I've put 14 here is that it looks like it's not only the Position attribute that is reserved behind the scenes, but the
nor
Normal attribute as well.When trying to use 15 geometry node attributes:
When trying to use 16 attributes:
This is correct. The normal used to be optional but isn't nowadays.
So the limit is actually 14 attributes until we do some big refactoring of the attribute fetching.
I'm late, but I just noticed this. I think this "attributes from Geometry Nodes" is misleading: the limit applies to Geometry attibutes, as in, attributes associated with vertices. IIRC the same limit will apply to ordinary UV maps, vertex colors, etc.
Also, the 8 attribute limit applies to any Object and Instancer attributes, whether they be custom properties, built-in properties, or instance attributes provided by those same geometry nodes.
I think the correct phrasing would be just that: referring to the mode dropdown of the Attribute node: