-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Unable to select a checkpoint model when starting from a clean or existing installation. #15568
Comments
The hash ( Deleting it will cause it to be re-downloaded the next time webui is started (unless other models are present), or it can be manually downloaded here. |
Well this is odd. I did what you said, and it fixed the clean install...the existing install on the other hand is still giving me trouble, and I fixed it by copying the 1.5 model over to it, and it started to work. I have over a dozen other checkpoints to use, and none of them could have been selected, so does this mean that the default 1.5 model is required to make the program run, even if you're not actively using it? |
No, it can safely be deleted. |
If it can be deleted then why did replacing it with the uncorrupted version fix it? Does this mean that if some model get's corrupted, that the entire thing will grind to a halt, or is it something else? I'm trying to figure this out should this same issue reappear in the future. |
So it's not the default model, but whatever model is currently pointed to first at program load that is the culprit...interesting. |
Checklist
What happened?
Can't choose a checkpoint to run Stable Diffusion. This only happened after I switched out my old power supply for an upcoming 4090 I ordered, so it may be hardware related, or it could just be coincidental.
Steps to reproduce the problem
Attempt to select checkpoint...
...fail.
What should have happened?
Checkpoint should have been automatically loaded, so I can start my next image generation.
What browsers do you use to access the UI ?
Microsoft Edge
Sysinfo
sysinfo-2024-04-19-03-28.txt
Console logs
Additional information
No response
The text was updated successfully, but these errors were encountered: