🛠️ 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.
⚠️ 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
v4f changes:
Generation time from start to finish on a 3060 RTX:
Everything but wildcards enabled took 133 seconds.
Bypassing all the extras and doing 2x upscale in the 2nd KSampler took 73 seconds.
Testing used euler_ancestral_cfg_pp (sampler) + karras (scheduler) on lobotomizedMix_v10 (v-pred model).
Adjusted the prompting order. It seems to give better results. YMMV.
Thanks to @TsunSayu for the suggestion
Adjusted the layout (again).
Changed groups names to reflect what can and cannot be bypassed in the workflow.
You can see on the Fast Groups Bypasser Node that anything marked with DNB is what cannot be bypassed for the workflow to run from start to finish.
Some of the items not marked DNB are situationally able to be bypassed. Example: if you bypass the Detailer Loaders groups, then obviously the Detailers are not going to work and cause the workflow to stop before finishing.
Same with the Watermark stuff. If you bypass any part of it, you need to bypass all the Watermark Groups. The only exception is the Alternative Watermark Removal group since it’s not connected to anything.
The v-pred group should be bypassed if you are not using a v-pred model.
Technically, you can bypass/change whatever you want, but then it is on you to figure out why the workflow stopped working.
Detailers have been moved to after upscaling:
This has yielded better results for me. I do the face first and then the eyes.
Info regarding the Color Correction groups:
These cannot be bypassed.
You can either delete these from the workflow or change all the settings in the Color Correct nodes to 0 except for gamma.
Why do I use the Color Correction nodes?
Upscaling with KSampler/Ultimate SD Upscale strips/alters the color from the original image (in my experience).
Using these nodes helps bring the color closer to the original image colors.
Altering any of the settings in the Watermark portion of the workflow will probably break the watermark removal. All that should be changed there is:
Detection Threshold (higher = less detection, lower = more aggressive detection)
Watermark Detection Model (use whichever one you prefer)
Steps, scheduler, denoise on the Watermark Remover node can be adjusted.
Anything else, I do not recommend messing with in the watermark portion of the workflow. I didn’t come up with it and cannot advise you on what all the buttons, numbers, and settings will do.