-
-
Notifications
You must be signed in to change notification settings - Fork 282
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
merged checkpoint works but lora weights does not work with kohya-ss sd-webui-additional-networks #1020
Comments
The additional networks feature in a1111 was written by for kohya_ss model format. The main of this model uses the cloneofsimo implementation for LoRA and is not compatible. There is an option in dev to also have additional networks Loras for the non-extended version if you want to give it a try |
Also that non-extended version should get merged to main sometime today or tomorrow |
Thanks! |
@gammagoat @ArrowM I see a PR merge #1014 did this merge "additional networks Loras for the non-extended version"? how to use/enable this? Any pointer? Thanks a lot! |
I pulled from dev and don't know which saving option will make lora compatible with https://github.com/kohya-ss/sd-webui-additional-networks |
Generate Lora weights for extra networks will save a file in the model/lora directory that will work (as long as you don't use extended Lora). I recommend deleting or moving all the old incompatible .pt files out of there. |
awesome - will try and report back! Thanks!! |
@gammagoat I trained again and the new lora weights work perfectly!! Thanks! |
I trained a model - training completed successfully. The merged model works (shows beckham):
however, when I use the generated Lora weights using https://github.com/kohya-ss/sd-webui-additional-networks, it has no effect:
I used another Lora weights I got from Civitai.com and it works - to confirm the extension is working.
The files are:
I found the following error in the log:
I guess this is the cause but don't know why - Can anyone help? What did I miss?
BTW, I found the following two closed related issues:
#695
#723
The text was updated successfully, but these errors were encountered: