You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to inform you that I have found and fixed a compatibility bug between sd-webui-3d-open-pose-editor and the latest version of ControlNet v1.1.455. In the current version of sd-webui-controlnet, the variable opts.control_net_max_models_num has been renamed to opts.control_net_unit_count, which caused an error in openpose_editor.py on line 70.
I created a fork and made the necessary fixes. My fork version has been tested and is fully compatible with ControlNet v1.1.455. This solution works correctly without any hacks or temporary workarounds.
It's not working for me. I am using the latest version of A1111 with the latest controlnet. I generate a pose, and I have 4 pictures (see screenshot):
When I click "Send to txt2img" only the Control Model 0 transfers over. 1, 2 and 3 do not. Also with clicking the "Send to img2img", nothing transfers over. If you go to the Control Net 0 on img2img, and tick the "Upload independent control image" then the image transfers over to Control Net 0 but again, 1, 2 and 3 do not transfer.
I wanted to inform you that I have found and fixed a compatibility bug between sd-webui-3d-open-pose-editor and the latest version of ControlNet v1.1.455. In the current version of sd-webui-controlnet, the variable opts.control_net_max_models_num has been renamed to opts.control_net_unit_count, which caused an error in openpose_editor.py on line 70.
I created a fork and made the necessary fixes. My fork version has been tested and is fully compatible with ControlNet v1.1.455. This solution works correctly without any hacks or temporary workarounds.
You can find my fork at the following link: https://github.com/jQQj/sd-webui-3d-open-pose-editor
Installation Instructions:
Screenshots
Environment (please complete the following information):
Thank you for your attention!
The text was updated successfully, but these errors were encountered: