pythongosssss / ComfyUI-Custom-Scripts

Enhancements & experiments for ComfyUI, mostly focusing on UI features
MIT License
1.38k stars 104 forks source link

Checkpoint loader VS Load checkpoint (default) - an issue, maybe bug or data loss #199

Open AdolfB opened 4 months ago

AdolfB commented 4 months ago

I just noticed that upon loading checkpoint with these two loaders gives two different image results. I used identical settings and generation data for the images, the only difference is that I loaded first checkpoint with Checkpoint loader from this project, and the second generation I used default ComfyUI loader Load Checkpoint. I got deviations in image generation, even worse I noticed that default checkpoint had a bit less strange artefacts and/or deformations of prompts. now I wonder why is it so?

I love Checkpoint loader with his functionality of drop down folder selection... but the image quality is still a key factor and default loader has the upper hand as of this moment, unfortunately

pythongosssss commented 4 months ago

The checkpoint loader is exactly the same as the default ComfyUI one, just with a different selection, I don't have any model loading or generation code: https://github.com/pythongosssss/ComfyUI-Custom-Scripts/blob/e597e7ef183ab8eb4ed0e062076ac6a48369c3d4/py/better_combos.py#L114

I think what you are seeing is something else unrelated to this.

AdolfB commented 4 months ago

Hmm, I see. Then the mystery deepens indeed but I don't see what else that could be. The only thing I changed in the workflow is the physical output of the loaders themselves and nothing more. I will show you the example of the issue with these 2 pics, everything was the identical except as I described the loader used for output. I'm really don't making thing up, trust me.

934629538868108_00002  pysssss Checkpoint loader used 934629538868108_00003 default load checkpoint used