Note @ChristophWerner :
This fixes the default value assignment but due to the old flag bits are in conflict with used bits in the new flag variables, versioning changes are not included. This…
@brecht The LRT_GPENCIL_INVERT_COLLECTION flag actually cause more prominent error and is also placed at the collection filter drop down box where it's seen and frequently used. The feature from…
@rimidalv I should have made it more clear in the manual... This solution is very temporary, after we implement the node-based line art, this kind of filtering should not be needed.
I'll close…
It's really not ideal to do it that way... Yeah it's kinda weird because the "particle" now comes from another collection. Somehow this depends on your interpretation on "what belongs to this…
Hi!
It's actually not an issue, there's just another option under geometry processing "Crease on smooth" needs to be turned on:
…
Hi @TinyNick I just got around, will check.
I think the issue I found is that I'm using BKE_collection_has_object(c, (Object *)(ob->id.orig_id)) to check if a collection has the instance, and…
OK I know what's happening now.
From what I can see the 3.4 is actually the incorrect one, because the file have neither source nor target vertex group set, and internally the logic is…
Hi, I checked the problem and I think the issue is indeed with a wrongly assigned _DNA_DEFAULT_LineartGpencilModifierData. The correct way should be LRT_GPENCIL_MATCH_OUTPUT_VGROUP being…