Open ZeroCool22 opened 1 year ago
Can you try with the first refiner version ? => sd_xl_refiner_1.0.safetensors
I tried with sd_xl_refiner_1.0.safetensors and didn't work!
Can you try with the first refiner version ? => sd_xl_refiner_1.0.safetensors
Fresh installation, no addons, no nothing.
Same issue happening with me after updating to 1.6.0.
You should set COMMANDLINE_ARGS=--no-half-vae
or use sdxl-vae-fp16-fix
If you have enough VRAM, you can avoid switching the VAE model to 16-bit floats. Otherwise, you will need to use sdxl-vae-fp16-fix.
Same problem here! I used model dreamshaper-xl10, I got a black pic every time. My webUI don't have a column named "SD VAE", I want to know if some settings were be ignored 🥺🥺🥺🥺
Same problem here! I used model dreamshaper-xl10, I got a black pic every time. My webUI don't have a column named "SD VAE", I want to know if some settings were be ignored 🥺🥺🥺🥺
You can add the sd_vae
tag in Setting -> User Interface -> Quicksettings list, then Reload UI. You will see the vae selection list at the top.
Same problem here! I used model dreamshaper-xl10, I got a black pic every time. My webUI don't have a column named "SD VAE", I want to know if some settings were be ignored 🥺🥺🥺🥺
You can add the
sd_vae
tag in Setting -> User Interface -> Quicksettings list, then Reload UI. You will see the vae selection list at the top.
Thank you! I got this. 👍👍👍
I had the same problem as the author of the thread, I have a 3090 with 24GB and it always had black images with the same arguments from 1.5.2 in the new 1.6.0. I could only get it working by adding --medvram, but I was itching to use --medvram with 24GB, so I kept trying arguments until --disable-model-loading-ram-optimization got it working with the same ones. old 1.5.2 arguments without the --medvram. Long story short, I had to add --disable-model-loading-ram-optimization to the existing arguments to fix the black image problem.
I don't know if it's a bug who affect more than 16xx user, so perhpas it can help you
I found a fix for my 1660 Super to work with half precision without any extra parameters (i launch only with ---xformers), perhaps it can help you too with your actual problem, even if it look different (Unet seems completly messy with prompt split/queuing)
Go in settings > Optimizations and check «Pad prompt/negative prompt to be same length» (and save) to try
I had the same problem as the author of the thread, I have a 3090 with 24GB and it always had black images with the same arguments from 1.5.2 in the new 1.6.0. I could only get it working by adding --medvram, but I was itching to use --medvram with 24GB, so I kept trying arguments until --disable-model-loading-ram-optimization got it working with the same ones. old 1.5.2 arguments without the --medvram. Long story short, I had to add --disable-model-loading-ram-optimization to the existing arguments to fix the black image problem.
Thank you so much for this, finally fixed it
And me help this setting set COMMANDLINE_ARGS=--autolaunch --theme dark --xformers --disable-safe-unpickle --lowvram
Is there an existing issue for this?
What happened?
https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/13344308/7f231192-83f5-428f-9887-aeade67814ba
Steps to reproduce the problem
What should have happened?
Create a normal image.
Sysinfo
sysinfo-2023-08-31-18-55.txt
What browsers do you use to access the UI ?
Mozilla Firefox
Console logs
Additional information
set COMMANDLINE_ARGS=--xformers --api --disable-nan-check --medvram-sdxl