WASasquatch / was-node-suite-comfyui

An extensive node suite for ComfyUI with over 210 new nodes
MIT License
1.22k stars 177 forks source link

CLIPTextEncode (NSP) doesn't seem to be noodling correctly in the latest update #45

Closed Yggdrasil777 closed 1 year ago

Yggdrasil777 commented 1 year ago

image

{__nationality__ __identity-female__|__monster__|__monster__ human hybrid|__rpg-class__} with __skin-color__ skin { |__skin-imperfection__| } and __body-shape__-shaped body, detailed {__color__ eyes|eyes of a __animals__}, __hair-color__ __hair-style__ with { |__hair-bangs__|__hair-braid__|__hair-texture__} and __breast-size__, wearing {__details__|transparent} {__costume-female__|__clothing-female__|__clothing__|__legwear__|__rpg-class__ armor} and {__accessory__|__accessory-hair__ in hair|__hat__ on head|__accessory-neckwear__ around neck| } and {barefoot|__footwear__}, feeling __expression__,

results in this: image

and this: image

It used to come out like this: Dominican young girl with ivory skin and barrelesque-shaped body, Light steel blue eyes, blonde emo hair with reverse french braid and medium breasts, wearing maternity wear and long necklace and barefoot, feeling indifferent.

and this: Cameroonian older woman with deep Wine eyes, aqua cropped hair and flipped hair large breasts, wearing leather jacket and panama hat on head and flip flops, feeling determined.

WASasquatch commented 1 year ago

I cant seem to reproduce this. It's working for me: WAS NS CLIPTextEncode NSP: Ocean Blue Southern Hognose Snake for __color__ __animals__ prompt.

One thing you could try is backing up the nsp_pantry.json and let the node download a fresh copy of the database.

Alternatively you can try the NSP Text Parse node which does the same thing, then you can just use the Text to Conditioning.

Yggdrasil777 commented 1 year ago

Oh! Did it make a backup?!? I think I found the issue, sorry. :)

WASasquatch commented 1 year ago

Oh! Did it make a backup?!? I think I found the issue, sorry. :)

It doesn't by default. I just suggested it as it could be the database isn't loading, thus nothing to find to "replace". JSON is finicky. You gotta use same encoding as the file, as well as make sure your syntax is correct if you edit the file to add new noodles.

Yggdrasil777 commented 1 year ago

Yeah, I had to reload a backup .json I have for those wildcards. It's all good.