search

Kosinkadink / ComfyUI-Advanced-ControlNet

ControlNet scheduling and masking nodes with sliding context support
GNU General Public License v3.0
622 stars 60 forks source link

KeyError: 'control_model.out.2.weight' following ComfyUI 2024-01-02 update #49

Closed andrewlabx closed 11 months ago

andrewlabx commented 11 months ago

Hi, First of all, happy new year and all the best.

I would need your help.

Following the latest ComfyUI update, I get the attached error when using controlnet nodes in workflows that worked just fine before the update. Whatever the adapter I load, the message is the same.

Versions : ComfyUI: 1872[8e2c99] - (2024-01-02) Manager: V1.13.7

I also updated ComfyUI-Advanced-ControlNet custom node but that doesn't change anything.

Has anyone a clue of what could be the issue? Thank you

control_model_out_2_weight_error_20240103

Kosinkadink commented 11 months ago

Hey, can you try using the Load Advanced Control net node from this repo? The one you're using there is the default ComfyUI one. I don't think that will fix your problem as I reuse the comfy code for normal ControlNet loading, but I want to see what happens.

Can you also provide a screenshot of your workflow, as well as the output from your console? The error implies whatever controlnet model you're trying to load does not have the expected key.

andrewlabx commented 11 months ago

Thanks for your quick response. I removed the node and cloned the one from the repo but as you anticipated, I get the same message.

You'll also find the workflow below (and its json file)

Note: I had my previous ComfyUI version saved locally. I just tested it and it works. The issue I observe on my side is definitely linked to the new version.

control_model_out_2_weight_error_20240103_3 test_1_workflow test_1.1.json

Kosinkadink commented 11 months ago

Looks like it was a temporary issue with ComfyUI: https://github.com/comfyanonymous/ComfyUI/commit/2c4e92a98b8338f754855a0db7dce164945e366e

If you update your ComfyUI and try again, hopefully your error will go away.

andrewlabx commented 11 months ago

I confirm, after updating a second tme my confyui, there is no longer any error. Thanks for your time and help on this.