ALWAYS LOOK INTO MY SAMPLES BEFORE DOWNLOADING TO UNDERSTAND IF THAT VERSION MEET YOUR EXPECTATIONS. Recommended generation parameters can be easily extracted in ComfyUI by dropping the sample into its window.
This is the CinEro NG Krea 2 series of checkpoints. Aimed to deliver the dark cinematic SFW / NSFW picture with unrestricted Qwen 3 VL Heretic Text Encoder. Trained with sci-fi horror themed moody portraits dataset. Developed mostly to be used in ComfyUI, but should work in other Stable Diffusion generation software.
This series of the models is focused on moody, atmospheric, creative portraits and picturesque landscapes.
Drop my samples to ComfyUI to see the recommeded high quality and high realism workflow. Text-toImage is rendered with this model (low-noise draft). Image-to-Image HiRes Fix finishing is done with CinEro-NG-XL (with low-to-moderate denoise).
Versions info
v2a
BF16 is contrast and sharp, has more details in background. FP8 made by quantizing all tensors into FP8. My quick tests showed that FP8 sometimes give a textures with barely noticeable regular grid pattern (repeating grain noise on skin or sky, for example). It is needed to focus on textures to see, but sometimes noticeable. Let me know if you see such artifacts or other issues.
Recommended parameters and workflow can be extracted from my samples.
👇 READ THIS PLEASE 👇
I prefer 2-stage rendering. Text-to-Image at 0.75..1.2 MPx resolution (the lower resolution, the less stuff in scene) with any compatible sampler (Euler, sa_solver), er_sde, dpmpp_2m, seeds_2, seeds_3, gradient_estimation, exp_heun_2_x0_sde). Second pass (HiRes Fix) I'm doing with Details Daemon node. Krea 2 Turbo have a very tight CFG range (0.9..1.5). You cannot adjust contrast and details using CFG knob, because you need to be much more precise. Details Daemon let you smoothly regulate CFG scale depending on Time Step.
v1g INT8 COBVROT
Turbo workflow (10 steps) ==>> https://civarchive.com/images/141569765
Made from v1e (All in One) by applying more fine-tuning and quantization script to convert it into INT8 CONVROT.
For me it looks less contrast (better use 20 steps and CFG 3..5 or more). Also, it looks less stable. But twice smaller file.
Let me know please if that format works for you or you have any problem.
performance: someone might expect the speed increase, but unfortunately speed on 4060 TI and 5060 TI looks the same; below is the DEBUG output that lists the exact grouping of all tensors that depends on data bits of weight encoding.
[SaveAsSafeTensor] DEBUG: Tensors: 879, Dtypes: {'torch.bfloat16': 166, 'torch.float16': 40, 'torch.int8': 224, 'torch.float32': 225, 'torch.uint8': 224}
Roughly the half of the weights (insensitive ones) were encoded in INT8. Other tensors must be slower as they were encoded in FP32 or BF16.
troubles:
At least one user have problems with this version in ForgeNeo (don't know which version of it was used); looks like ForgeNeo do not properly recognize which loader needs to be used for Krea2 Turbo INT8 Convrot.
v1e All in One
It also has Qwen3VL Heretic Text Encoder and VAE baked in. Just use my workflow or use a regular Load Checkpoint node in ComfyUI combined with a regular KSampler. Nothing tricky needed. If you adapt the SDXL HiRes Fix technique described below, you may get better textures, but with v1e even single Text-to-Image pass at 1MPx resolution works well for me. Hope you will get good results also in your setup.
Recommended settings for Text-to-Image pass:
1216x832 (or 832x1216), Exp_heun_2_x0_SDE sampler (Simple, Normal, Beta, KL_Optimal schedulers), Steps 12, CFG 1.0...1.2.
v1
It has Qwen3VL Heretic Text Encoder baked in. So, by using this model you take full responsibility on the resulting safety of the rendered images. Qwen Image VAE also embedded. CLIP and Unet parts both quantized to FP8.
Description
Additional fine-tuning from v1e (All in One). BF16 Unet quantized to INT8 CONVROT format.
Half of weights are INT8 (signed and unsigned). Other half of weights are FP32 or BF16.
[SaveAsSafeTensor] DEBUG: Tensors: 879, Dtypes: {'torch.bfloat16': 166, 'torch.float16': 40, 'torch.int8': 224, 'torch.float32': 225, 'torch.uint8': 224}
FAQ
Comments (16)
I tried the newly added int8 convtor version in ForgeNeo but unfortunately got this message and broken outputs:
SingleStreamDiT Unexpected: ['model_sampling.sigmas']
Is there was more messages?
Unexpected keys usually not a problem until the renderer treat them as warnings.
Response from DuckAI
```
This sounds like a Forge Neo compatibility problem, not a corrupted checkpoint.
Unexpected: ['model_sampling.sigmas'] usually means Forge Neo has identified the model as a SingleStreamDiT, but its model wrapper is receiving a model_sampling configuration that it does not expect. ComfyUI and Forge Neo are not necessarily using the same loader path for Krea 2 or for the comfy_quant/INT8-ConvRot format.
Forge Neo’s current documentation lists Krea 2 Turbo/Raw support and int8_convrot among its supported mixed-precision formats. However, older Forge Neo builds may recognize the quantized tensors but fail while constructing the diffusion-model wrapper. GitHub
```
Forge Neo commit/version:
Operating system:
GPU and VRAM:
Checkpoint filename and file size:
Exact error traceback, including 20–30 lines above "Unexpected":
Selected Forge preset:Selected text encoder:
Selected VAE:
Installed quantization/model extensions:Can you share something of these bits of information?
@homoludens Removing the model_sampling.sigmas key didn't help so forge neo was ignoring it anyways - I am using the krea preset and standard qwen_image_vae + qwen3vl_4b_fp8_scaled - I guess forge neo just doesnt handle this one right and I would have to switch to using Comfy - thanks for looking into it anyway!
@schroeck Yep... As I wrote, msgs like "unexpected keys" are usually "ignorables". Maybe FN update can help? I didn't use that and can only give you that usual, "thanks-for-reaching-our-support-service" kind of suggestion.
BTW, "qwen3vl_4b_fp8_scaled" I recommend you finding the "qwen3vl 4b heretic" version if text encoder. For me it works better and this text encoder is embedded into v1e All in One (maybe you can extract it in Comfy by using Save CLIP node).
This is not a standard Krea 2 Turbo model, as such it doesn't work with 8 steps. The output is totally mangled. Please make that clear in the first sentence so those of us who don't want non-Turbo models will not waste our time and CivitAI's resources. Thank you. My PC can't handle 20 step models so why did I spend half an hour and 13GB downloading this.
1. There is no Turbo in version name
2. Reference workflow embedded in all my samples and generation params shown by Civit clearly show the 20 steps
3. Turbo LORA can be easily applied to get that 8 steps
What is the problem?!
"Made from v1e (All in One) by applying more fine-tuning and quantization script to convert it into INT8 CONVROT.
For me it looks less contrast (better use 20 steps and CFG 3..5 or more)."
In the beginning of version description. Is that unclear that 20 steps is recommended?
@homoludens the problem is misleading info. The vast majority of checkpoints here are Turbo that do in fact work with 8 steps. I have 31 of them right now. Yours is unusual you should make that clear. You never said it doesn't work with 8 steps. I had to test it to find out.
@ferrrett33 I tried to do that. What you suggested have equal negative effect. If I put the "non-Turbo" in version name, then some users will say that I am click-bating. Same term in description is useless until everybody start reading with attention. If visitors don't have time to read out "use 20 steps" and don't have time / ability to extract the recommended workflow or read generation params from meta info under my samples, then I have no idea how to fix this situation.
I've put the link for Turbo users in the beginning of version info. Hope it will work in some way...
@homoludens Ok thanks, it's not like a huge deal you could just write it as a first sentence that this model requires 12+ steps. It's also significant because maybe with 12 steps I would test it but not with 20. With 20 steps I would have to wait 2.5 minutes for an image which is way too long. Also I don't download sample images, they have little meaning to me as I test many models with my own tests.
@ferrrett33 I feel that this "non-Turbo" version is disappointing, honestly. Without Turbo LORA it feels too low contrast. And I agree with you that 20+ steps is too much for the most users.
In near future I plan to prepare FP8 and / or GGUF versions. In my experience those variants have more potential.
PS: And I am really sad when users of my models have unmet expectations and poor experience. Still tryin' to find the "Golden Path"...
For those who want Turbo and INT8 CONVROT in the same workflow... Look into ComfyUI workflow in the sample below
https://civitai.red/images/141569765
I just added Turbo LORA with weight of 0.6.
I cannot bake it in and save as CONVROT again (just don't know how if even possible).
CONVROT quantization procedure I used for v1g Int 8 version damages the Turbo lora effect.
sorry there is no worflow in there, only standard nodes nothing special ?
@warsound75 just added turbo LORA. except that LORA the workflow is dumb usual




