search

sipie800 / ComfyUI-PuLID-Flux-Enhanced

Apache License 2.0
67 stars 8 forks source link

PuLID stays persistent #21

Open MoonMoon82 opened 2 weeks ago

MoonMoon82 commented 2 weeks ago

It seems, once a sampling process with Flux PuLID started, it stays persistent even if the node is removed:

1st samling process: grafik 2nd sampling process: grafik

Could you please check?

Kind regards!

sipie800 commented 2 weeks ago

perhaps you loose the seed and run again

MoonMoon82 commented 2 weeks ago

@sipie800 the PuLID still stays persistent even if I change the seed: image

jaszczw commented 2 weeks ago

My workaround is to set weight to 0, which 'resets' the model - not perfect but works for my use case.

https://github.com/balazik/ComfyUI-PuLID-Flux/issues/41 - this is the original issue

MoonMoon82 commented 2 weeks ago

@jaszczw Unfortunately that does not appear to be a proper workaround. I found this issue while I was trying to integrate FluxPuLID into a more complex workflow which samples at first without FluxPuLID, later with FluxPuLID. As soon I restart the whole workflow all sample processes are using FluxPuLID.

jaszczw commented 2 weeks ago

Yeah, you would need to put pulid with basically anything in it with weight 0 - which I do.

MoonMoon82 commented 2 weeks ago

@jaszczw Unfortunately your suggestion does not work: image

cchance27 commented 2 weeks ago

This is because Apply pulid flux is monkeypatching the unet, the current comfyui modelpatcher doesn't support the required block patching needed for plux so it's basically a hack (all implementations for flux not just this repo).

So if you use apply pulid, that unet is officially THAT pulid, it can't just be swapped again later or in a different line like above...

Use a different unet loader into the second apply pulid, though i dont know if that will work given internal comfy caching of models, but worth a try.