stable-diffusion-webui-forge
stable-diffusion-webui-forge copied to clipboard
New update cannot select VAE
Cannot select VAE/Text Encoder from quick setting. Dropdown list doesnt show up, text input doent work.
Yup. Same here.
if you're sharing folders with A1111 and you don't have a launch flag for VAE location, then it'll use the Forge location. So moving that to the Forge directory could work, if that's the problem.
For now move or copy your VAEs to models\text_encoder, text encoders also go there obviously. This is something that hopefully will get fixed for VAEs.
Can't test right now but it might only be happening when using --vae-dir, so VAEs might also still work when placed in Forge's own VAE dir.
Thank you guys.
I solved this problem.
--vae-dir causes the problem, it cannot override the default path when launch. So I make a symbolic link to my VAE folder.
where and how,I add --vae-dir “D:\forge\stable-diffusion-webui-forge\models\VAE” in webuser.bat still can not select
Also there should be at least an "Auto" option, even with no VAEs
Yes, --vae-dir parameter is broken now, no items in VAE/Text encoder drop-down menu.
Thanks to Illyasviel,I confirmed this issue has been fixed at commit "df0fee"
--vae-dir arguments is functional now.
I'm using symlink, and it works for models, text-encoder etc. everywhere, but in the VAE folder it doesn't seem to work. Any ideas? (models put directly there are shown normally.) maybe Forge does not scan deeper than the VAE main folder contrary to other folders?
side note: hasn't there been a "Automatic" selector at the dropdown menu for VAE?
@cuom1705 should be working fine now. Please check and close the issue if so.
after fresh clean install on mac mini m2 pro the VAE / Text Encoder dropdownlist automatic value is missing by default.
I came looking to report the same thing as the user above. Switched to Forge ui from A1111 and noticed that there is no "automatic" option for vae anymore, and there is no info about if it should be used differently now.
Same issue with downloaded releases, someone have a fix ?
@df917 I believe you should make a new issue to bring the... *issue* back into focus, nobody seems to be following this thread anymore.