🛠️ 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
Minor changes:
Dropped all Color Match nodes from the workflow.
When these nodes were bypassed, they would still pass the reference image through resulting in the initial image being sent to the next step instead of the upscaled image.
Replaced with Color Correct nodes to try and offset the color loss from upscaling.
Color Correct nodes can be bypasses without the same issue as Color Match.
I am going to be exploring other options for upscaling instead of multiple KSamplers and USDU. This method works okay, but for me it's not ideal.
I will probably drop USDU from the workflow after this, unless I have some sort of breakthrough.
Most of the time it looks fine, but if doing things with embroidery details (as an example) a lot of those details get lost.
FAQ
Comments (8)
v11 uploaded. Hope this is the last update for at least a week. T.T
Thanks for riding the v10 roller coaster with me!
Looks like the CR Simple Text Watermark bugs out on Detailer 1 group. I've tried fully replacing the detailer node by using a new FaceDetailer node and also tried it with a Detailer (SEGS) node.
In both cases the CR Simple Text Watermark doesn't do its thing.
If I take the output noodle from the detailer node and feed it into the comparer node, it works with no problems.
I'll probably drop the CR Simple Text Watermark in the next update.
I also tried it with some other newer custom node for adding "watermarks" and it also failed. So whatever. Not a dealbreaker for me. Was just a QoL feature for the comparer node.
Also made sure it wasn't the comparer node. I fed the output from the "After" CR Simple Text Watermark into a preview image node and got nothing.
Also tested with a fresh CR Simple Text Watermark node.
Might just be a delay in the images being sent to the comparer node too. IDK.
I figured out how to make it possible to add LoRAs to later parts of the workflow (Detailer groups specifically) and have Image Saver detect them so that civitai adds it to "used resources" automatically. Will make sure to include that in the next update.
Edit: I found this to not be as helpful as I would like. So, I'm leaving it out.
If you want to know how to do it:
Add another ImpactWildcardEncode node and any sort of node that can "concatenate" text.
Take the existing noodle feeding into Image Saver for the positive prompt and connect it to the Text Concatenate node.
Connect the model output from the WildcardEncode node to whatever USDU, Detailer, etc., node you want and make sure to connect the inputs feeding into WildcardEncode (model and clip).
Then you would just use the "Click to add LoRA" button and something like this will appear: <lora:IAMALORA> will populate in the text box.
From there you can set the strength of the lora by adding numbers like this: <lora:IAMALORA:0.5>.
v11a coming soon. v11a uploaded.
Will be having it set with Dynamic Thresholding, Detail Daemon, FreeU_V2, etc. all bypassed.
Initial example images will be generated this way.
Not sure if you if you have ever heard of ComfyUI-Lora-Manager but it has some awesome integration features for using and maintaining Loras. I can set it up on my simpler workflows but it's a little more intimidating to try it with advanced ones! I still have lots to learn I suppose.
I haven't but looks similar to how ImpactWildcardEncode works (for the text part at least).
That should be compatible with Image Saver since it has a text output and seems to use the same formatting.