From c212052318df030b55531c00b23c69e1ff159dc3 Mon Sep 17 00:00:00 2001 From: Jesse Yurkovich Date: Thu, 8 Feb 2024 08:18:25 +0100 Subject: [PATCH] EEVEE: Document attribute and property limitations Related to https://projects.blender.org/blender/blender/issues/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. ``` /* Hardware limit is 16. Position attribute is always needed so we reduce to 15. * This makes sure the GPUVertexFormat name buffer does not overflow. */ #define GPU_MAX_ATTR 15 /* Determined by the maximum uniform buffer size divided by chunk size. */ #define GPU_MAX_UNIFORM_ATTR 8 ``` 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 https://projects.blender.org/blender/blender/issues/117967, seems to be used when Custom Object Properties are set. --- manual/render/eevee/limitations.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/manual/render/eevee/limitations.rst b/manual/render/eevee/limitations.rst index 07034a91d..e2abe1e9c 100644 --- a/manual/render/eevee/limitations.rst +++ b/manual/render/eevee/limitations.rst @@ -9,6 +9,13 @@ may be impossible to implement into EEVEE's architecture without compromising pe Here is a rather exhaustive list of all the limitations you can expect while working with EEVEE. +Attributes and Properties +========================= + +- Only 14 attributes from Geometry Nodes are supported in a material +- Only 8 custom object properties are supported in a material + + Cameras ======= -- 2.30.2