🛠️ 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
Added Impact Wildcard Processor
this can be used to add wildcards to your prompt easily
add your wildcard files to the custom nodes/impact pack/wildcards folder before starting comfyui to make use of them
this is bypassed by default
Added Concat Conditioning again
This is meant for adding "flavor" to your prompt and is a built-in Comfy Core function
this is bypassed by default
Added ClipTokenCounter again
this requires the ppm custom node pack and is easily found in ComfyUI-Manager
if you do not want to use this, you can easily delete it without issue
FAQ
Comments (9)
Had to leave a comment. This workflow is so much better than the others I use. Thanks man!
Thanks! Glad you like it!
I love this workflow, but I'm trying to use comfy couple and for the life of me can't make it work without getting into the same error. xD so much nodes
Any help be appreciated
Hi. Not sure what you mean by "comfy couple". Typo?
Also what's the error? If you have any custom node packs installed that aren't in the workflow, there can be some conflicts causing errors, even if they are not in the workflow. This is based on what others have ran into.
If it's a bunch of technical jargon in the error, then I probably can't help you.
@Gladas pretty much its a custom node that has the ability to do more than one character (not in your workflow)
the error is like not correctly setting the node because that paths for conditioning and/or model are wrong for the custom node. I been trying to get it to work but no success. I'm also using the v12c workflow.
@Zachman18 ah, yeah sorry I have no idea tbh. I'll take a look at the node, but you might need to hit up the project page of that node for help. I can take a look, but I'm not going to try and get "too deep into the weeds" so to speak.
My uninformed and probably wrong observations: from what I can see you're basically needing 2 sets of Positive Prompts based on their sample workflow image. To use it with mine, you would have to add another Clip Text Encode node and connect the Comfy Couple into the conditioning inputs across the workflow probably. Plus with that width/height settings on there, I am not sure how that would interact with all the nodes.
@Gladas
UltimateSDUpscaleNoUpscale
Sizes of tensors must match except in dimension 0. Expected size 231 but got size 77 for tensor number 1 in the list.
that's the error i'm running into
@Zachman18 it's probably not compatible with Comfy Couple. USDU is very picky about what it does and does not work with. You would probably have to go another route for upscaling like Iterative Upscale or upscale via KSampler since it seems to work with the Initial KSampler at least.