<h1 id="hades-moss-turbo">HaDeS MOSS Turbo</h1>A single-file, eight-step MOSS-Image text-to-image checkpoint for ComfyUI. It starts from <a target="_blank" rel="ugc" href="https://huggingface.co/OpenMOSS-Team/MOSS-Image-Base">MOSS-Image-Base</a>, with three LoRAs baked into the diffusion weights. It offers a different rendering choice from MOSS-Image-SFT; the comparisons below do not show that either model is better for every prompt. No separate Turbo or other LoRA is needed to run this file.This is only the diffusion model. It does not contain the MOSS text encoder or VAE.<h2 id="use-in-comfyui">Use in ComfyUI</h2><ol><li>Put the <code>.safetensors</code> file in <code>ComfyUI/models/diffusion_models/</code> and select it in a MOSS-compatible loader. The measured workflow used the <a target="_blank" rel="ugc" href="https://github.com/Devildonia/HaDeS-MOSS-Suite">HaDeS MOSS Suite</a> <code>MOSS Loader</code>.</li><li>Load the MOSS-compatible <code>qwen3.5_9b_int8_convrot.safetensors</code> text encoder and <code>flux2-vae.safetensors</code> VAE. Both are available in <a target="_blank" rel="ugc" href="https://huggingface.co/Comfy-Org/MOSS-Image">Comfy-Org/MOSS-Image</a>. These are the exact companion files used in the comparisons here.</li><li>Enter a text-to-image prompt, create an empty latent, sample, then decode with the VAE. If using the Suite, set <code>MOSS Prompt Enhancer</code> to as written or caption, connect <code>MOSS Latent</code> and <code>MOSS KSampler</code>, and use these starting settings:</li></ol>Setting Measured referenceSize: 1/2 MpxSteps: 8CFG: 1.0Sampler: EulerScheduler: SimpleFlow shift: 5.0 (0 in HaDeS MOSS Suite)Denoise 1.0SLG: OffLeave the KSampler's separate <code>turbo</code> LoRA input unconnected: its Turbo weights are already in this checkpoint. These settings were exercised on ComfyUI 0.43.0. Other resolutions works perfectly, but the comparisons used 1152 × 1536.CFG 1 is the reproducible starting point, not a universal aesthetic optimum. In a paired four-scene, two-seed screen, raising CFG from 1 to 2 at eight steps increased saturation and near-clipped pixels, darkened all eight images, and took about 1.8 times as long in that session. Some reviewers preferred stronger CFG on particular images. Increasing steps also changed compositions; it was not a consistent quality improvement.<h3 id="other-step-counts-and-cfg">Other step counts and CFG</h3>Measured on eight scenes, one seed each (<a target="_blank" rel="ugc" href="https://github.com/Devildonia/HaDeS-MOSS-Suite/blob/main/tools/RESULTS.md">measurement log</a>): no image broke or burned from 6 to 50 steps at CFG 1, nor up to CFG 3 at 20 steps. More steps add texture and fine detail and take longer (about 4 s at 8 steps, 9.5 s at 20 and 23 s at 50 on an RTX 5090 at 1152 × 1536), but the image does not settle: each step count gives a different image of the same scene, so pick the count you like rather than expecting more steps to refine the 8-step one. In one scene a short sign was only right from 12 steps. Higher CFG darkens and saturates the image and doubles the time per step.ConstructionCheck the model card on Hugging Face for more details: <a target="_blank" rel="ugc" href="https://huggingface.co/DeVilDoNia/HaDeS-MOSS-v0.9.4-Turbo">https://huggingface.co/DeVilDoNia/HaDeS-MOSS-v0.9.4-Turbo</a>Some Quick Start Workflows<a target="_blank" rel="ugc" href="https://civarchive.com/models/3039368/hades-moss-suite-workflows">https://civarchive.com/models/3039368/hades-moss-suite-workflows</a>

HaDeS MOSS Turbo

v0.9.4 BF16. Check model card for more details.

Files with SHA256: 32c215fc08ee8ec0e55459507e0712936adccf5804e94b6a7264bc33efd68770