Fucktoy Noir KR2 is a custom NSFW Krea 2 Turbo checkpoint built around a balance of photographic realism, strong character rendering, cinematic contrast, and the darker, more stylized visual language suggested by the Noir name.
The goal with KR2 is not simply to push one particular aesthetic. It is intended to retain the flexibility that makes Krea 2 useful while giving the model a more opinionated visual baseline: convincing skin and materials, strong lighting response, expressive faces, detailed environments, and compositions that hold together without requiring excessively complicated prompting.
It is particularly well suited to photorealistic and cinematic image generation, but it remains responsive to changes in wardrobe, environment, lighting, camera position, framing, and overall art direction. It can move from clean contemporary photography into much moodier, higher-contrast imagery without immediately collapsing into a single baked-in look.
This is a Krea 2 Turbo model, so it is designed around the fast Turbo sampling regime rather than long diffusion schedules. For our own testing, 8 steps / CFG 1 / Euler / Simple is the primary baseline and a good place to start.
BF16 and FP8 Versions
Fucktoy Noir KR2 is provided in two precision levels. They contain the same underlying KR2 model, but they are stored and executed at different numerical precision.
BF16 — Maximum Fidelity
The BF16 version (~23.9 GiB) is the reference version of KR2 and preserves the model weights at bfloat16 precision.
Use BF16 when maximum image quality is the priority and your hardware can comfortably accommodate it. In side-by-side testing, BF16 retains slightly better micro-detail, fine texture and edge definition. The difference is not transformative: the overall composition, identity, aesthetic and behavior of the model remain very similar, but it can become visible when examining skin texture, hair, fabric, small environmental details and other high-frequency information.
BF16 is therefore recommended for:
Final-quality renders where hardware resources are not a concern
High-resolution generation
Detailed character and portrait work
Benchmarking or evaluating the model at its highest available precision
Users with sufficient VRAM/system memory who simply want the least quantized version available
If you have the hardware and don't care about the additional storage and memory requirements, BF16 is the definitive version of KR2.
FP8 — Recommended for Most Users
The FP8 version (~12.2 GiB) is a purpose-built quantized release of the same checkpoint.
Rather than simply forcing every tensor into FP8, KR2's FP8 release was constructed using a Krea 2-compatible mixed-precision quantization layout. Eligible model weights are stored as FP8 E4M3FN with freshly calculated scaling data, while the checkpoint maintains the structure required for proper Krea 2 execution in ComfyUI.
This cuts the checkpoint size roughly in half while retaining remarkably close behavior to the BF16 reference.
The principal compromise is a small reduction in micro-detail and sharpness. In our testing, FP8 can appear slightly softer than BF16 when the same generation is examined closely. This is an expected consequence of reducing weight precision rather than a different model or aesthetic.
FP8 is recommended for:
Most everyday generation
Lower VRAM overhead
Faster/easier model loading and switching
Systems where BF16 creates unnecessary memory pressure
Users maintaining large local checkpoint libraries
Iteration and experimentation where the small BF16 quality advantage isn't worth doubling the checkpoint footprint
For the majority of users, FP8 should be the default download.
Which Version Should I Use?
If you aren't sure, start with FP8.
It gives you essentially the full KR2 experience at approximately half the checkpoint size and is the version we expect to make the most sense for normal generation.
Move to BF16 when you have sufficient hardware and want to squeeze the maximum available fidelity from the checkpoint. BF16 becomes especially worthwhile when the output is intended as a final image rather than an exploratory generation, or when subtle texture and fine-detail reproduction matter.
Importantly, these are not two differently trained editions of KR2. FP8 is a quantized representation of the BF16 reference checkpoint. Prompts and workflows developed against one should therefore translate naturally to the other.
Recommended Starting Settings
Architecture: Krea 2 Turbo
Sampler: Euler
Scheduler: Simple
Steps: 8
CFG: 1.0
Denoise: 1.0
Text Encoder: Krea 2-compatible Qwen3-VL
VAE: Qwen Image VAE
Description
FAQ
Comments (7)
Thank you so much for this promising KR2 model. 👍
I have a few questions. How does your model address the two main drawbacks of most KR2 models:
- Does the model prioritize anal penetration over vaginal penetration as 99.9% of others KR2 models if not using any LoRA to prevent that flaw?
- Does your model have the same tendency as most KR2 models to force a massive quantity of body fluids when only a small amount is prompted?
Last but not least, do you have any plan for a INT8 ConvRot version?
Hi! Thanks for the early feedback and request. I'll respond honestly based on what I know so far with early testing. #1 doesn't seem to be a problem. I haven't had any issues with anal being over prioritized. I do tend to be pretty specific when it comes to positioning but as far as I can see that's not an issue with this model #2 I'm leaning toward saying its not a big problem but occasionally I do see the fluid bias. I think that can be corrected 85% of the time with correct prompting but its something for me to be mindful of for future iterations. Lastly, I haven't given much thought to an INT ConvRot version but I may with time if this becomes popular and the community wants it. I hope you enjoy it and thanks again for commenting and sharing your ideas.
@MarisGolding Thanks a lot for the clarification. If i m not mistaken, INT8 ConvRot offers results of a quality closer to those of BF16, for half the weight and requirements. It is a better format than FP8.
I've never had a checkpoint prioritize anal, but it could be because I'm including anal and your including vaginal in our prompts, that we experience the opposite priorities
@civitdude1342 @civitdude1342 This is a well known flaw of KR2 right now. It forces to use dedicated LoRA such as SNOFS or Pussy Helper to bypass it. TextFusion Refusal-Reduction LoRA aren't enough to get rid of this flaw all the time.
@civitdude1342 Yea that was news to me. I almost kinda wish it did prioritize anal sometimes lol 😂
@antarek i made a program that allows you to convert to int8 convrot and other formats on your own pretty easily https://github.com/qskousen/ggufy and yeah int8 is pretty good for a format, i have a small comparison here https://civitai.red/articles/33661/w4a8-support-in-ggufy







