š ļø 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 notes to pretty much everything on the workflow.
Trimmed down the Watermark Removal portion of the workflow thanks to a random person on the civitai discord providing a better one. No need for a detection model anymore. Yay!
Changed upscaling to use two USDU nodes. First to 1.5x, the second to roughly 2x.
Allegedly, this results in more detail (and I love details).
You can use a 2nd KSampler instead of the first USDU node, but that's up to you.
More re-arranging.
If you don't like spaghetti, install ComfyUI-Custom-Scripts. Go into your comfy settings, find "pysssss" on the menu. Click it. Find LinkRenderMode. Click on the dropdown menu in that section and pick "Straight" OR you can find a solution to hide them. I know that setting exists somewhere.
You are free to add or remove anything from this workflow. We all have different likes and dislikes. Make it your own!
FAQ
Comments (9)
Uploaded an updated file for v4c. This will have default settings that run quicker than the original. Start to finish for me took 165 seconds on a 3060.
4c doesn't seem to work for me. I'm getting "ApplyCLIPSeg+ tuple index out of range"
@vellaneĀ sounds like a technical error that I am not familiar with and I'm not a dev. I recommend checking with the author of comfyui_essentials at: https://github.com/cubiq/ComfyUI_essentials where that node is from. I'll take a look there too.
If you don't need watermark removal, you can just remove that section of the workflow or bypass it.
Looks like someone ran into this in July here: https://github.com/cubiq/ComfyUI_essentials/issues/48. They did a fresh install of comfy, but you can try just updating via update_comfyui.bat or update_comfyui_and_python_dependencies.bat in your local comfyui update folder.
Looks like I'll be putting the old watermark removal flow back in. The current one works sometimes, but in a recent image I ran, it completely destroyed the image AND left the watermark.
I tried stealing the watermark part for my own workflow, but I honestly have no idea what's happening there. Do you have a post explaining the reasoning for all the resizing and image flipping somewhere?
@hocepoĀ I do not because it's not my creation. I'll try to find the link of where I got most of it from.
@hocepoĀ here it the link to the original where I got it from: https://civitai.com/models/265571/dynamic-watermark-removal-during-render-or-image-upload-by-leinad882
@GladasĀ thank you, i'll check it out!