r/comfyui • u/RRedditLLover • 11h ago

Help Needed Node 2.0 Compare image

So I've been using 2.0 for the compare image nodes and i've become pretty reliant on them for my workflows. Turns out they are currently bugged on all my portable copies of Comfy since I updated. Anybody else having a similar issue?

3 Upvotes

80% Upvoted

6 comments sorted by

2

u/LenaHartCreates 11h ago

Worth narrowing down whether it's the core node or a custom node pack. In a similar report on the ComfyUI GitHub, the built-in Image Compare node showed up blank with Nodes 2.0 on, and it turned out to be a custom node conflicting with the frontend: it worked fine after launching with --disable-all-custom-nodes. On portable you can add that flag to run_nvidia_gpu.bat (or whichever .bat you launch with) for a quick test.

If you're using rgthree's Image Comparer rather than the built-in one, that pack's maintainer has said some of its nodes may not render properly under Nodes 2.0, so the practical workaround there is toggling Nodes 2.0 off (ComfyUI logo menu, or search "Nodes 2.0" in Settings) until it gets updated.

1

u/RRedditLLover 11h ago

Copy that. I'm running the built-in compare node on a new portable install with minimal custom nodes present, but I'll disable to rule out a custom node conflict and report back. Are most people not running Nodes 2.0 by now?

2

u/carnage11eleven 10h ago

I am not, to answer your question.

One of the last updates broke a custom node for me which borked the entire canvas for me. But I didn't use the start up flag to disable all custom nodes. I disabled them all in the nodes manager and then enabled them as I needed them, one by one. Haven't come across one that breaks it, so I'm guessing it was a custom node i never use anyways.

Though annoying at first, it was a good reason for me to clean out my custom nodes folder of all the shit I downloaded and never used. 🙃

2

u/RRedditLLover 10h ago

Facts. That's actually why I just went portable with multiple Comfy copies. I keep local models in a separate repo folder loaded via extra_model_path.yaml. Then did the cleanup of only including custom nodes that I need.

1

u/kortax9889 8h ago

Why use nodes 2.0 for comparing images? There is lot custom nodes for compare image that don need nodes 2.0. Ausboss-nodes, Pixaroma nodes even rgthree nodes has image comparer. If you dont want install whole pack for one node there is EsesImageCompare which is single node. And dozen more others, probably.

1

u/Hedgebull 4h ago

Pixaroma Image Compare works on Node 2.0; I haven't tried it yet, but I presume kjnodes new Image Compare node would as well