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
This is quite simple. The steps to reproduce simply consist in creating a group node with Apply Advanced ControlNet 🛂🅐🅒🅝, then bypassing that group node.
When bypassed, the positive and negative conditioning will switch places: the positive get linked to the negative and vice versa. which leads to... pretty creepy but sometimes hilarious stuff.
This is what we get when bypassing Apply Advanced ControlNet 🛂🅐🅒🅝 when ungrouped, so this is also what is expected when bypassing a grouped node: https://ibb.co/WWw3ZBT
But this is what we get when bypassing a grouped node containing Apply Advanced ControlNet 🛂🅐🅒🅝 (Warning: it hurts the eyes a little bit): https://ibb.co/x569F61
The text was updated successfully, but these errors were encountered:
I have no custom javascript at all in my node, so my hunch is this may be a bug with how ComfyUI handles bypassing grouped nodes. Can you see if the issue also happens if you use the vanilla Apply ControlNet (Advanced) node that's built into comfy?
This is quite simple. The steps to reproduce simply consist in creating a group node with Apply Advanced ControlNet 🛂🅐🅒🅝, then bypassing that group node.
When bypassed, the positive and negative conditioning will switch places: the positive get linked to the negative and vice versa. which leads to... pretty creepy but sometimes hilarious stuff.
This is what we get when bypassing Apply Advanced ControlNet 🛂🅐🅒🅝 when ungrouped, so this is also what is expected when bypassing a grouped node: https://ibb.co/WWw3ZBT
But this is what we get when bypassing a grouped node containing Apply Advanced ControlNet 🛂🅐🅒🅝 (Warning: it hurts the eyes a little bit): https://ibb.co/x569F61
The text was updated successfully, but these errors were encountered: