<h3 id="not-so-simple-(or-is-it)-krea-2-turbo-worklow">Not so simple (or is it?) Krea 2 Turbo worklow</h3>This is my personal workflow for Krea 2 Turbo text-to-image generation.My workflow is very basic. Krea 2 Turbo is already good out of the box and doesn't need an excessive amount of features to get good results.<h3 id="this-workflow-includes-standard-features-such-as:">This workflow includes standard features such as:</h3>Diffusion Model, CLIP, VAE, and lora loaders:<ul><li>Why mention this? - This workflow requires your models to be placed in the model/diffusion_models folder.</li><li>AIO models seem kind of pointless when the model files are already big and most of us probably have the CLIP and VAE models installed already. As a result, there is no standard Load Checkpoint node in this workflow.</li></ul>No CFG setting on the initial image<ul><li>This workflow is setup under the impression that you are using CFG 1. The Basic Guider node handles this. If you need to be able to adjust the CFG for some reason, then the Basic Guider node will need to be swapped for a CFG Guider node or something similar.</li></ul>Positive Prompt<ul><li>The node for your positive prompt has three text boxes available and will combine all three before it is sent to the CLIP Text Encode (Prompt) node.</li><li>Why use this? - This makes it easy for me when I have specific prompts that I like to reuse.</li></ul>Wildcards<ul><li>Ever feel lazy and just want to use some ready made prompts for clothing, backgrounds, etc.?</li><li>The ImpactWildcardProcessor node is here for you. Just save your wildcard files to the custom_nodes/comfyui_impact_pact/wildcards folder and now you can be lazy like me.</li><li>Connect the output of the ImpactWildcardProcessor node to one of the text boxes on the Positive Prompt node and you're set to use them.</li></ul>Upscale<ul><li>Upscaling is done via the Upscale Image node with the option to use an upscale model.</li><li>After the upscale, the image can optionally be refined in Ultimate SD Upscale.</li></ul>Detailers<ul><li>Three detailer groups have been added as of v1a and use the standard detection and SAM models. By default, each detailer node will handle everything that was detected in on go. Toggle off 'combined' on the MASK to SEGS node if you want it to do one detected item at a time.</li><li>Not always needed and will increase the overall generation time if used.</li></ul>Save Image via Image Saver<ul><li>The saved image includes metadata that CivitAI can properly read including resources, prompts, sampler, scheduler, resolution, etc.</li></ul>Other stuff<ul><li>I included CFGZeroStar for the initial image. It can be toggled off without any issues.</li><li>Krea 2 Conditioning Control is included as a test and can be toggled off without any issue.</li><li>A markdown note with links and URLs to all the custom nodes used in this workflow can be found at the start of the workflow. If you are unsure of how to use any of the related nodes, check out the related project page or have your preferred AI chat bot do it for you.</li><li>Runtime from start to finish (while using INT8 versions) at SDXL resolutions 1024x1024 is about 1 minute on a 5060ti 16GB. Bumping up the initial resolution 1.5x increases this to 3 minutes.</li></ul><h3 id="questions-i-will-probably-get-asked:">Questions I will probably get asked:</h3>Will I add &lt;insert feature here&gt;?<ul><li>Short answer: No.</li><li>Long answer: If it's something I decide to use, then yes.</li></ul>Why do I use Ultimate SD Upscale instead of another KSampler/SamplerCustomAdvanced?<ul><li>Answer: I like the results better and I'm just used to using it.</li></ul>Will I post my workflow to &lt;insert some other platform here&gt;?<ul><li>Short answer: No.</li><li>Long answer: If I ever lose enough social credit here to be banned, then yes.</li></ul>

Not so simple (or is it?) Krea 2 Turbo worklow

Minor Update:Added 3 detailer groups using the same setup as my Anima and Illustrious workflows.<ul><li>These use the standard detection models that work with the UltralyticsDetectionProvider nodes from Impact Pack.</li><li>BBox/SEGM detection models should be placed in your models/ultralytics folder.</li><li>SAM models should be place in your models/sams folder.</li><li>There are several markdown notes explaining how the detailers work on the workflow. If your questions aren't covered there: you can check the Impact Pack project page for more information.</li><li>Impact Pack was already in this workflow, so no new custom nodes to install on this version.</li></ul>

Files with SHA256: f8a0d410b54b4212105413f9e2d7b9e7fbe63db6d34cb4885b2b4ab1a68fd5a4