Fixing Layer Incompatibilities #259
null-prophet
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Been working on a more complex hierarchy of images and wanted to share my findings:
Sometimes you have objects that can't work together and you can use the if/then that but what happens when one item in a type of thing just isn't compatible with a whole other type of thing?
You could write out all the ignores for a
Hat
that isn't compatible withHair
but that will make things really complex going forward.If this gets bigger or unwieldy you might want to do something to say ok
As your order of sublayer folders:
the reason we use a folder above with an ID on the front is to get the order right as these are sublayers. I guess you could do this in config and just put them in some order so let me know if that works better. this works for me and all attributes come out named correctly in the metadata.
And you want to say
If I get hat
X
then I don't want to includeHair
at all.I ended up altering the code to do this, its quite simple, it will work with specific exclusions still, like layers/specifics but also allows you to blanket ignore a layer if your previous picks have a design that would not make them show.
It's only capable in the order you have the layers in, so you can't say if hair
x
then no hats as the order isn't that easy to fix. It's a limitation in the code and quite hard to fix.Around line 527:
Then in your config:
This will mean if you draw
special_body_type
then. theClothing
layer will be ignored.You can still use the other code as well and it will work fine with specific DNA exclusions, this just makes blanket exclusions much easier.
Beta Was this translation helpful? Give feedback.
All reactions