Open BlankDiploma opened 6 months ago
At least upstream, it was determined CLIP skip should not affect the output of any SDXL generations since all models were trained using the penultimate layer (which was not the case for SD1). https://github.com/AUTOMATIC1111/stable-diffusion-webui/pull/12518#issuecomment-1676364751
At least upstream, it was determined CLIP skip should not affect the output of any SDXL generations since all models were trained using the penultimate layer (which was not the case for SD1). AUTOMATIC1111/stable-diffusion-webui#12518 (comment)
Oh. Well, that certainly explains it. Maybe it should be hidden from the UI when an SDXL model is loaded? It's at least a bit misleading the way it's currently displayed.
i can fix it in 5 minutes but forge will try to get same result with webui
however if most users vote for a functional sdxl clip skip but upstream refuse to have it, Forge may still implement it after multiple user reports because it can be seen as a part of backend thing
Checklist
What happened?
All checkpoints based off Stable Diffusion XL, including the base checkpoint, do not show any variation when changing Clip Skip, even if you set it to 12.
Image generation parameters show that the changing Clip Skip value is being recognized, it shows up in the image info text after generation is complete, but the value doesn't actually affect the output at all.
Steps to reproduce the problem
Observe that Stable Diffusion checkpoint properly recognizes the Clip Skip parameter during image generation, but Stable Diffusion XL checkpoints do not.
What should have happened?
Clip Skip should modify the image output normally.
What browsers do you use to access the UI ?
Google Chrome
Sysinfo
sysinfo-2024-02-24-05-27.json
Console logs
Additional information
No response