Per Instance Custom Data is, when you use a single HISM and change material properties of the instances, per instance. Lumen cant do that, so the HISM is black in the scene, while the same HISM would work in Lumen if it wasnt created with PICD.
It still must be recalculating a lot, otherwise performance would be better.
What I would like is: if there is no change around a probe, then skip it, since in most games the vast majority of probe never changes.
Probably not that easy to do, but could bring a lot of performance.
Only SWRT, since HWRT is kinda dumb (for now - until “RT-Cores” have become the standard even in potato-tier hardware etc.).
Lumen has a bit of an issue, where it “cuts off” in the distance, and doesnt even do something, which kinda makes it very visible (especially in large interiors) and limits the size of stuff you can build, even if we now have infinite shadow draw distance because of VSM.
Still doesnt work for many meshes, but there is a workaround where you can subtract one mesh from the MDFs shape… it would be nice if we could just tell the engine: “make actual physical holes into that Mesh Distance Field” - which is possible, but needs manual intervention right now.
Lumen hates small bushes with dense leafs (if they arent floating in mid air), since it creates a dense MDF and Lumens own capabilities in “dealing with this” arent enough.
See this post for a visual representation: Lumen GI and Reflections feedback thread - #819 by Yaeko