rgthree
[rgthree-comfy][Reroute] - ComfyUI has removed support for this.
Hello, I am a regular user of your excellent rgthree-comfy nodes, specifically the Reroute node, which is highly valuable for organizing complex workflows.
Since a recent update to the ComfyUI core, I've been seeing the following deprecation warning in the console when using your Reroute nodes in conjunction with the standard ComfyUI Primitive node:
[rgthree-comfy][Reroute] You are using rgthree-comfy reroutes with a ComfyUI Primitive node. Unfortunately, ComfyUI has removed support for this...
I understand that this change was caused by an update in the ComfyUI core, not in your code. The warning suggests using the native ComfyUI Reroute node or your Power Primitive node as a workaround.
Could you please provide some clarity on the future of the rgthree-comfy Reroute node concerning the ComfyUI Primitive node?
Are you planning to release an update that resolves the compatibility issue with the native Primitive node?
Or should users permanently transition to using the Power Primitive node for these specific use cases?
Thank you very much for your hard work and for maintaining this essential Custom Node package.
Best regards,
Murphylanga
All fair points, and I don't really know the answer. I think, in short, users should permanently transition off of either rgthree-comfy reroutes or primitive nodes, especially in these cases.
I'm not a fan of breaking workflows, though, so if I can in a future update, I would detect the conflict in rgthree-comfy and allow the user to move forward without breaking; simplest would probably be to replace the troublesome reroute nodes with the ComfyUI reroute nodes, as the existing Primitive Nodes may be more difficult to replace.
Yes, I was afraid of that. I'm not really looking forward to it. Maybe I will switch to Get and Set nodes everywhere. It's a real shame, because all other variants are much more confusing in large workflows. Thanks for your work.
Hi, first of all thank you for your amazing work on rgthree-comfy. Your reroute nodes and power primitives have really improved my workflows compared to the standard ComfyUI options.
I have one question: do you consider it critical if I continue to use ComfyUI’s standard INT or FLOAT primitive nodes together with your reroute nodes? I noticed that your Power Primitive nodes are visually quite large, and even if I resize them, they return to their oversized appearance after a refresh. For layout reasons, I sometimes prefer the smaller standard primitives, but I don’t want to risk breaking compatibility with your reroute nodes.
Thanks again for all the effort you put into this project – it makes a huge difference for users like me.
Yes, I’ll probably have to remove support for Primitive Nodes and reroute at some point.
On the size, you can remove the type selector if you aren’t changing it in the node properties. It should be smaller than the built-in primitive node. If items changing size, that may be a fixable issue.