-
Notifications
You must be signed in to change notification settings - Fork 13
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
Compatibility with SD Forge (stable-diffusion-webui-forge) #25
Comments
Hey glad you're enjoying it so far and I appreciate you looking into making it better! If you notice anything else weird happening on forge definitely let me know. |
Adetailer is another popular extension that leverages ControlNet and recently added support for Forge. It might be worth looking at the way that they are checking which version of ControlNet is available. The following two commits seem relevant: Bing-su/adetailer@d6f62d5 and Bing-su/adetailer@763278c. Hope this helps! |
So far I have been able to reproduce the issue you've mentioned with not being able to direct forge instances using cni (controlnet integrated). Something seems to be going haywire with the cn payload im sending as what seems to be part of one of cni's caching mechanism is not being initialized? Here Still looking into it. |
First of all, thank you for this incredible extension. It seems very well designed and worked right away with very little configuration needed.
Assuming this is not already in the works, have you considered making the extension compatible with lllyasviel/stable-diffusion-webui-forge? That distribution is quite a bit faster than automatic1111, especially for lower RAM GPUs (50-75% speedup) which makes it a great platform to use on worker nodes.
As far as I can tell most everything is already working well, but there are some incompatibilities with ControlNet. One quick fix was to change the expected name from
UiControlNetUnit
toControlNetUnit
in distributed.py so that the ControlNet units are detected. After making that small change, a master server can now successfully send jobs that rely on ControlNet to workers running automatic1111. But there are still some issues sending those jobs to workers running on SD Forge, which I have not been able to figure out.Anyway, I just wanted to see if this was on your radar. Thanks again for your hard work on this!
The text was updated successfully, but these errors were encountered: