My own workflow developed to generate Z-images (but it should work with any other type, as long as change the models and make minor adjustments).v5 new refatored version: <a target="_blank" rel="ugc" href="https://github.com/shirosaki33/shirotools">shirosaki33/shirotools: many utility tools made for different situations</a>v4 old version nodes: <a target="_blank" rel="ugc" href="https://github.com/shirosaki33/shirotools/releases/tag/comfynodes">Release old version v4 less · shirosaki33/shirotools</a>I particularly hate that scattered clutter of nodes where it's extremely difficult to locate where everything goes and ughh.I ended up simplifying its use considerably with several functions along the way to the final result. You start by choosing the method: T2i, I2i, and hybrid with ControlNet.The workflow includes an InPaint, Adetailer, SeedVR2 Upscaler, and normal upscaler system.It's up to the user which steps will be used along the way, in the order I've listed them. The InPaint is divided into at least 3 areas, in case the user wants to change at least 3 different things in the image.If you want more areas, you just need to clone an additional section and connect the points correctly.It's not necessary to use all 3; you can use just 1 if you prefer.Inpaint contains an additional internal checkpoint system in this section, since the turbo checkpoint isn't very suitable for this. Loading z-base yielded a much more satisfactory result in this part.The seed has universal control. So if the user leaves it "fixed," all processes will remain until the user makes the desired adjustments in specific areas, without having to redo the entire process. Didn't like the result of the adetailer? Just disable what you didn't like and redo it; it will only redo the adetailer section, for example.3 KSampler systems to suit everyone's taste. A simple system that every workflow typically uses with 1 KSampler. The other 2 are in a 2 KSampler system, each already configured for turbo mode and base mode. It's up to the user to choose what they prefer.<pre><code>I hope it's satisfactory at least. this simplifies my personal use, without all those lines and boxes everywhere. A version with more features might come later :)</code></pre>

Like a Boss workflow

<ul><li>The ksampler system has been completely reworked.</li></ul>The system now requires the use of my nodes from v4 onwards.The system now features a ladder of 4 ksamplers.It starts with 1 ksampler as the default, and the others are activated as desired. Each ksampler has a different function (generate/Polish/Hires/polish).If the user wants to generate the image and skip directly to Hires without the Polish ks2, they can.With this system, the image generated from ks1 will now be the default, unlike the previous method where 1 sampler generated different images than 2.<ul><li>KS4 will hardly be used, but keep in mind that it's still somewhat unstable.</li></ul><ul><li>New additions for adetailer.</li></ul>I2I - FIXjust connect inside of the graph the denoise node on KS1 again

Files with SHA256: 0705440d17bf87cbba83b0bfb1f613038fc04331579c1d97bbb203af89574fdf