Did the suit update make it more difficult to do this job?
Well, yes, at some given data complexity level (when lots of different instances is mixed with lots of unique objects for example) a modifier-driven datamanagement is able to bring a severe overload.
Sorry, I am not a native speaker, so struggling with proper wording.
1 Like
Sure, instancing is known to be one of the remaining issues.
1 Like
Hey @thinsoldier , I think I just got just something like that working! 
Linked Modifier instances, using WIP versions of Key Ops: Toolkit + Modifier List
The modifiers can also be ovveridden:
5 Likes
Hey, its officially out now! Also, works great together with Modifier List!
There are some limitations currently, but it has worked great in my experience so far!
6 Likes
TLDR: i was an idiot.
I was scratching my head for a two hours trying to realize why the hell my model get some extra sharp edges after Auto Soooth modifier which should not even exist?!
Checking custom split normal data, non manifold geometry, all that stuff.
Until i checked what sort of crap was inside the modifier itself.
How on the freaking earth someone who implement this was not understand what the whole section with matID should be exposet to modifier settings?!
Thats not default modifier. Youre using addon
No. No addon was used. Its just me being an dumbass who actually implement this while was trying to make some stuff with geonodes and after that complitely forgot what i was made such changes in default autosmooth file.
What. A. Shame. 