š ļø Purpose & Design Philosophy
This workflow is a high-fidelity environment built for Illustrious. It prioritizes stability and professional texture over generation speed. It follows an "all-in-one" philosophy: configure your prompts, hit queue, and let the workflow handle the multi-stage refinement from start to finish.
Not for Speed: This is a heavy-duty refinement tool. If you want 2-second previews, use a basic workflow.
Personal Use: Built for my specific production needs. It is shared as-is for those who want a "set-and-forget" pipeline for Illustrious. Adjust the settings and models to fit your needs. The defaults on v19+ will be what I used for the sample images.
All-in-One Logic: The workflow handles generation, detailing, and upscaling in one continuous pass.
If you're needing something with more features: Try checking out Silly All-in-one, Multiple Characters With Regional Loras which is on civitai. I have no plans to implement additional features.
ā ļø Disclaimer & Compatibility
Install at Your Own Risk: Custom nodes can break your environment. I am not responsible for troubleshooting your specific installation.
ComfyUI: Built and tested on the non-app version. Desktop app users may face additional hurdles.
The "Your Version" Factor: Your node versions and environment are 99.9% likely to differ from mine.
Nodes 2.0: I do not recommend using Nodes 2.0. It creates unpredictable UI behavior; I will not provide support for issues involving this feature.
š¤ Support & Boundaries
I have not and never will monetize my workflow. CivitAI is the only platform I am maintaining this workflow on. If you find a version of my workflow posted and/or monetized anywhere and use it, then whoever posted it is responsible for providing you any support. This is the main reason why I don't monetize this: I don't want to be or feel obligated to provide support.
No DMs: DMs are disabled due to repeat spam. Please check the Discussions tab below; most questions have already been answered.
Modifications: You are free to hack this workflow apart. However, you are responsible for fixing it if it breaks.
Custom Requests: I do not make private workflows. If you need a custom solution, post a Bounty on CivitAI. There are many talented creators ready to help you for a fee.
Description
If you are not using the latest (bad IMO) update for comfyui (0.3.75), then you probably should not use this version of the workflow.
Works with Illustrious and NoobAI. Bypass Epsilon Scaling if you are using a v-pred model.
The recent comfyui update broke/partially broke all sorts of custom nodes resulting in very minimal use of custom nodes compared to some of my other workflows.
Workflow was setup with the Nodes 2.0 feature toggled on.
What does this workflow do?
Text to Image
Upscale via USDU
optional 2nd USDU for refining (bypassed by default).
2 FaceDetailer nodes (the normal ones) for whatever you want to detail (face, eyes, etc.)
What doesn't it do?
Watermark Detection/Removal
Civitai will not autodetect the resources used
I do not recommend using this version of the workflow, but wanted folks to see how janky Nodes 2.0 is and why newer is not always better (IMO).
What's janky about Nodes 2.0 other than making many existing custom nodes useless?
You can't set seeds to "fixed". The option is gone.
Resizes nodes on its own
When you are resizing a node, sometimes it will glitch out and display the node in one place, but it's actually not. You'll know when it happens.
Dropdown fields get hidden behind other nodes
FAQ
Comments (11)
Oh nice a new WF, thanks G!
It's pretty bare bones to try out Nodes 2.0, but it'll probably work fine without Nodes 2.0 enabled too.
comfyui 0.3.76
still hot garbage as far as all the old stuff is still broke or partially broke even with Nodes 2.0 toggled off.
The main gripe I have is the lack of ability to use any custom Save nodes (I tried several) for images and still be able to drop those images into comfy to load the workflow from it. That is completely busted, even for old images generated/saved before the previous update.
I did have a slightly updated version of the Nodes 2.0 workflow ready to go, only to find it doesn't save the Positive Prompt metadata, which would be even more manual work when posting here on civitai. 100% not worth it.
I'm a pretty solid "HELL NO" on Nodes 2.0 at this time.
I'll work on an update for v14 either when the custom node authors are able to get things adjusted to work with the new frontend (which I don't realistically expect to happen) OR I'll just abandon v14 and make a simple workflow similar to the Nodes 2.0 workflow and go from there.
Where is the toggle to turn Nodes 2.0 off? I've looked all over the place. It's likely right in front of me, but I miss it. I've rolled back to the most stable version prior to the Nodes 2.0 release to even use ComfyUI.
It's just awful :(
@leirtesĀ I can only speak for the "portable" version of comfy, but if you click on the comfyui icon it should open the menu where you can load workflows and such, the toggle should be right there. The menu should show New, File, Edit, View, Theme. Below that is the toggle for Nodes 2.0.
I think you can also toggle it off by opening settings and it should be the very first thing listed.
@GladasĀ
Right in front of me, as I had expected :). I tore the settings menu up looking for it. Thanks for the help as always. Have a great weekend.
Hello, I have comfy UI and the front end updated to the latest version, still while trying to use the version 13e of your workflow, the ksampler select and basic scheduler highlights in red, any ideas? I mostly use it for control net, and I know your latest one works just fine.
No idea. I know the last couple comfyui updates broke all kinds of things. My guess is something you have installed for comfy is causing a conflict, but I have no way to know. I'll try a barebones workflow with those nodes and see what happens, but I'm feeling like it's gonna give me the same issue.
@FlowSpecialist I added the test workflow I used. I had no issues with BasicScheduler or KSamplerSelect, even with RES4LYF installed. I recommend trying it and see if the error still happens. If it does, then you now have something conflicting with those nodes, even if they didn't conflict before thanks to the recent comfyui updates (most likely). SamplerCustomAdv Tester
@GladasĀ Thank you, you tried with latest comfy ui, and front end right?
@FlowSpecialistĀ yep that's correct