Open BlafKing opened 1 year ago
I can confirm this. SDXL Model => only safetensor files will be listed in embeddings SD1.5 Model => only .pt files will be listed.
its the same for me except for that no embeddings are displayed if i use a xl model, doesnt matter what xl model. if i use a non xl model the embeddings are displayed included the xl embeddings. doesnt matter if its a .pt or a .safetensors file.
Same for me. Are you guys using Civitai Helper too?
Same for me. Are you guys using Civitai Helper too?
I'm not, it's not caused by an extension, this is just the way that SD-WebUI currently works, it only shows models compatible with the selected stable-diffusion model
Then I guess the relevant code is here: https://github.com/AUTOMATIC1111/stable-diffusion-webui/commit/6f0abbb71a3f29d6df63fed82d5d5e196ca0d4de
Is there an existing issue for this?
What happened?
When SDXL 1.0 is selected, it doesn't list any models incompatible with SDXL 1.0 So my Textual Inversions models for example, do not get listed when a SDXL 1.0 checkpoint is being used.
The current description is quite confusing, since it states that nothing is in the folder, instead of explaining to the user that no compatible models for SDXL 1.0 are found.
I think it would be a lot clearer if the info displayed correctly states that the folder isn't empty, but nothing shows up because nothing is compatible with SDXL 1.0, for me this was really confusing and I didn't realize that the folder was showing empty because of the selected checkpoint's base model version:
with SDXL 1.0 Base selected:
Steps to reproduce the problem
What should have happened?
I'm not exactly sure what the best solution would be, Maybe a check could be done to see if the folders contain any models and change the message according to the presence of models in the folder?
For example if models are found but Automatic1111 has no available models to select a message like this could be shown:
Otherwise maybe the easiest solution is to change the message all together to something more general like:
Anything that would indicate to the user that the current Base Model of the Checkpoint is causing the model selection window to be empty, not because of an empty folder.
Another solution could be to dim any models that aren't compatible to indicate to the user that the models are found but not compatible with the current checkpoint Base Model.
Sysinfo
sysinfo-2023-09-21-17-56.txt
What browsers do you use to access the UI ?
Brave
Console logs
Log is irrelevant since no errors occur but here is the log regardless:
Additional information
A similair bug report (https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/13101) exists but I wouldn't consider this issue fixed yet since the current "Nothing here" message is very confusing.