š ļø 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
v5 changes:
Dropped ComfyUI-APG_ImYourCFGNow from the workflow.
Ran into an issue when using FaceDetailer on certain setting that would break the workflow. Performed testing using non-custom nodes with FaceDetailer and added in custom nodes one by one. APG node was found to be the cause.
Dropped sd-dynamic-thresholding.
While testing (with the same seed/prompts) on the v5 workflow with/without this, I found the results to be better without it.
You can just use your normal CFG values now (if you weren't already).
Dropped MaHiRo
It seemed to do the opposite of it's intended function for me.
Added sd-perturbed-attention
If you want to know what it does, the paper on it can be found here.
My experience so far with PAG seems to be that you should take the total of your CFG + PAG scale to equal what you would normally use for your CFG setting by itself.
Example: if you are using a sampler from CFG++SamplerSelect, then your total should equal 2. CFG 0.5 + scale 1.5 = 2.
So if you are using a normal sampler that would be something like CFG 6, then you could do something like CFG 3 + scale 3.
This is just from a non-technical standpoint and personal testing, so I could still be wrong.
Most of the groups in the workflow can be bypassed again since this workflow is not using the SET/GET nodes.
The tradeoff is oodles of noodles.
FAQ
Comments (8)
My experience so far with PAG seems to be that you should take the total of your CFG + PAG scale to equal what you would normally use for your CFG setting by itself.
Example: if you are using a sampler from CFG++SamplerSelect, then your total should equal 2. CFG 0.5 + scale 1.5 = 2.
So if you are using a normal sampler that would be something like CFG 6, then you could do something like CFG 3 + scale 3.
This is just from a non-technical standpoint and personal testing, so I could still be wrong.
Updating the zip file with these changes.
1 plus 1 = 3 , got it.
Very much appreciate the detail and thoughtfulness of OP. Awesome to see your activeness answering questions, cause comments fixed some issues I also ran into.
Hey there!
v5 is working great for me. Out of the box, very fast and capable of doing what I want it to do. I just realized, however, that the images generated aren't saving anywhere. :( Nothing in the ComfyUI output folder(s) for any of the checkpoints I've tried.
All of the steps leading to the 2nd UDSU occur, but the image doesn't appear to save. I've also noticed that the Before & After Detailer/Color Correction node isn't populating either.
I've attempted to troubleshoot this myself and cannot find what the culprit is. ComfyUI is up-to-date on my end, and I don't see any flagrant errors. It's likely a very simple fix and I'm overcomplicating it. Any assistance would be greatly appreciated!
Hello,
It should save into your default output directory in folder with the model name via the Image Saver node on the far right of the workflow as it is set up by default, but you can try changing what is listed in the "path" on the Image Saver node to your output directory. example: "C:\My Pictures\output"
Alternatively, you could delete the Image Saver node and use the default Save Image node or whatever your prefer.
Everything after USDU should be able to be bypassed, so I don't think that would cause any issue other than bypassing the Image Saver node.
@GladasĀ Appreciate the response! Iāll tinker around with it. Thank you :)
@leirtesĀ No problem, there isn't much else I can think of to cause it to stop after the 2nd USDU node other than something being disconnected or maybe missing detailer models. I think in either of those cases one of the nodes would light up with a red border.