CivArchive
    qwen 2512 - general nudes and sex stuff - GNASS - v1.0
    NSFW
    Preview 116552813
    Preview 116550845
    Preview 116548126
    Preview 116548150
    Preview 116548225
    Preview 116549266
    Preview 116549703
    Preview 116550119
    Preview 116550446
    Preview 116551662

    s3x_2512_qwen - Explicit & Intimate Nude Photography LoRA

    Model: Qwen/Qwen-Image-2512

    LoRA Type: Diffusion

    Base Model: Qwen-Image-2512 (Quantized: qfloat8)

    Training Details:

    • Trained using a LoRA network with linear 32 / alpha 32 and conv 16/alpha 16.

    • Dataset comprised of explicit nude photography, focusing on intimate poses and scenarios – both partnered and solo.

    • Resolution trained at 512x768 & 1024x1024

    • Training steps: 30,000 using the "flowmatch" noise scheduler and AdamW8bit optimizer.

    • Dtype: bf16 for efficient performance.

    Intended Use: This LoRA is designed to enhance the generation of realistic and explicit nude photography with a focus on detail, intimacy, and often featuring shaved genitalia. It works well with prompts describing specific poses, settings, and characters. Expect detailed skin textures, sensual lighting, and overall high-quality results. Frequently produces images suitable for mature audiences.

    Key Characteristics (Based on Training Data):

    • Poses: Common poses include lying on backs/stomachs, legs spread wide, squatting, and partnered positions (e.g., cunnilingus, intercourse).

    • Subjects: Often features women with fair to light skin tones, frequently blonde or brunette with long hair. Body types tend towards slender builds with small-to-medium sized breasts. Tattoos are common, particularly on the abdomen or lower back.

    • Settings: Images range from outdoor settings (patios, gardens) to indoor scenes – bedrooms with rumpled sheets, luxurious Eastern-inspired interiors, and more casual living spaces.

    • Explicit Details: Shaved vulvas/vaginas are very commonly generated.

    Sample Prompts (and included in training data):

    This LoRA excels at generating images like these:

    • A photograph shows a young woman with light skin and long brown hair, wearing a white lace dress, squatting with legs apart, exposing her vagina. She covers her left breast with her hand. Background: green grass and flowers.

    • In this photograph, a naked woman with long, dark hair and medium-sized breasts, sits between a man's legs leaning forward, holding his erect penis near her face. handjob. The man, also naked, lies on his back in shallow water, with his legs spread. The background features a serene lake surrounded by lush greenery. The scene suggests a sexual encounter.

    • In this explicit photograph, a naked Caucasian woman with long brown hair is kneeling on a brown couch, performing oral sex on a standing naked man with a large erect penis. blowjob. The woman's breasts are visible, with a medium size, and she is holding the base of his penis with her left hand. The man has a muscular build, light skin, and a tattoo on his right arm. The background features beige curtains, a large window with natural light, and a yellow gaming table. The scene suggests a private indoor setting, likely a living room or a similar domestic space.

    • Explicit sexual acts between a couple - vaginal intercourse, cunnilingus, etc.

    • Topless woman sitting in a wicker chair with a polka dot dress revealing her breasts

    Tips:

    • Use descriptive prompts to define the pose, setting, and characters.

    • Experiment with guidance scales (around 4-7) for optimal results.

    • When using the lora with character loras reduce the strength between 0.6 and 0.8 for best results.

    • Consider using negative prompts to refine the output and avoid unwanted details.

    • Works well with "highly detailed," "photorealistic", “intimate”, “shaved”, "erect penis", "cum", "partially visible penetrating", "labia", "blowjob", "reverse cowgirl", "cowgirl", "missionary", "doggystyle" keywords.

    Enjoy creating beautiful and sensual images!

    Description

    FAQ

    Comments (19)

    yakitoritamagoJan 7, 2026· 6 reactions
    CivitAI

    It works fine with Edit2511 used lightning lora. Thank you for the wonderful Lora.

    kaytransg196Jan 12, 2026· 1 reaction

    how it works with qwen Edit? just prompt what you want to change?

    KiraNuggetJan 7, 2026· 2 reactions
    CivitAI

    Will it work with qwen 2509?

    SuperHawk7
    Author
    Jan 7, 2026· 1 reaction

    I haven't tested 2509, but I suspect it will just with diminishing returns. It does work pretty well with 2511 edit.

    chubakaa01560Apr 16, 2026

    @SuperHawk7 do you have a workflow for edit 2511, to integrate a 2nd (this) lora

    razzzJan 7, 2026
    CivitAI

    Don't how big was the DS, but from my testing I recommend to increase the rank passed 100+ images.

    SuperHawk7
    Author
    Jan 7, 2026

    Dataset was 260 images, I did a low rank for a slow stable burn. Still refining my understanding of this, what would you suggest for 260 images? I also did batches of 12 images for stability.

    razzzJan 8, 2026· 1 reaction

    @SuperHawk7 Big batch is a must so that's perfect if you have enough VRAM. I suggest 64/32 rank/alpha or maybe even 128/64 to have enough room for all the new knowledge. 32/16 should be use only for styles or single new concept/character.

    ForeverNecessary737716Jan 8, 2026· 6 reactions
    CivitAI

    this is great but any change you could introduce more futa and males?

    mistaniaJan 9, 2026
    CivitAI

    wonderful lora,thanks for your work,i have an ask,when i use it,the output image getting blur,why?thank you.btw,i used another lighting lora with it

    SuperHawk7
    Author
    Jan 9, 2026

    1️⃣ The lighting LoRA is overriding detail‑preserving layers

    What’s happening:
    Many lighting‑or‑color‑grade LoRAs are trained to modify the overall tonal balance of an image. They often do this by pushing the model toward a smoother, more “glow‑y” look. When you stack that on top of a detail‑heavy LoRA (like the Qwen‑2512 General Nudes & Sex Stuff), the smoothing effect can bleed into edges and fine textures, making the final picture look soft or out‑of‑focus.

    What to try:

    Reduce the strength (alpha) of the lighting LoRA. Start with a value around 0.2–0.3 and increase only if you need more light effect.

    Apply the lighting LoRA after the main generation step (e.g., use it as an “up‑scale/finetune” pass rather than part of the initial prompt). In many pipelines you can run a second pass with just the lighting LoRA at a low strength.

    2️⃣ Sampling steps / CFG scale mismatch

    What’s happening:
    If you’re using a relatively low number of diffusion steps (e.g., 20–30) or a very high CFG (classifier‑free guidance) value (>12), the model can converge too quickly and produce a “soft” result, especially when multiple LoRAs are fighting for control.

    What to try:

    Increase sampling steps to 50–80 (or even 100 if you have GPU headroom). More steps give the network more opportunity to refine edges.

    Lower CFG to somewhere between 7–9. This lets the LoRAs express their learned details rather than being forced into a single, overly‑sharp interpretation.

    3️⃣ Resolution & Latent Upscaling

    What’s happening:
    If you generate at a low base resolution (e.g., 512×512) and rely on a post‑upscale (ESRGAN, SwinIR, etc.) that isn’t tuned for the specific LoRA, the upscaler can introduce softness.

    What to try:

    Generate at a higher native resolution (768×768, 1024×1024, or whatever your GPU can handle) before applying any external upscaler.

    If you must upscale, use a high‑quality upscaler with a “sharp” preset (e.g., “Real‑ESRGAN x4 + sharp”).

    4️⃣ Prompt wording & Negative prompts

    What’s happening:
    Sometimes the prompt itself asks for “soft lighting”, “dreamy”, or “glowy” attributes, which reinforce the smoothing effect of the lighting LoRA.

    What to try:

    Add a negative prompt such as blur, out of focus, soft, dreamy to explicitly discourage softness.

    Include positive terms that promote crispness: sharp details, high definition, 8k, fine texture.

    5️⃣ Model & LoRA compatibility

    What’s happening:
    The Qwen‑2512 General Nudes & Sex Stuff LoRA was trained on a specific base model (e.g., SDXL‑1.0 or SD‑2.1). If you’re using a different version (or a custom checkpoint), the weight alignment can be off, resulting in artefacts like blur.

    What to try:

    Confirm you’re using the exact base model mentioned on the Civitai page.

    If you must use a different checkpoint, try merging the LoRA with a lower strength (e.g., 0.5) and see if clarity improves.

    QUICK “cheat‑sheet” checklist

    StepActionTypical Value
    1️⃣Reduce lighting LoRA strength0.2–0.3
    2️⃣Increase diffusion steps50–80
    3️⃣Lower CFG scale7–9
    4️⃣Raise base resolution768×768+
    5️⃣Add negative prompts for blurblur, out of focus
    6️⃣Verify base model versionMatch Civitai page
    7️⃣Use a sharp upscaler (if needed)Real‑ESRGAN + sharp

    Example prompt & settings

    Prompt: "portrait of a confident woman, detailed skin, soft natural light, sharp focus, 8k, cinematic lighting" Negative: "blur, out of focus, soft, dreamy" Base model: SDXL‑1.0 LoRA A (Qwen‑2512 General Nudes & Sex Stuff) : strength 0.7 LoRA B (your lighting LoRA) : strength 0.25 Steps: 70 CFG: 8 Resolution: 768×768

    Run a single pass with those values, then optionally run a second “refine” pass using only the lighting LoRA at strength 0.15 if you still want a touch more glow.

    TL;DR

    Blur usually comes from an overly‑strong lighting LoRA, low steps/high CFG, low resolution, or mismatched base model.

    Dial down the lighting LoRA, bump up steps, lower CFG, generate at higher native resolution, and add a negative “blur” prompt.

    Check that you’re on the correct base checkpoint; otherwise reduce LoRA strength.

    Give those tweaks a try and let me know how it turns out! If you still see issues, feel free to share your exact settings (steps, CFG, strengths, resolution) and I can help fine‑tune further. Happy generating!

    TimmyHodorJan 9, 2026· 1 reaction
    CivitAI

    Great job on the Lora! I'm the author of another Qwen NSFW Lora so i guess that puts us as (friendly) competitors. I was quite impressed with the poses of characters in GNASS. What captionning method did you use? For what it's worth, if you want to go for a second training run, I believe that lowering your learning rate by a factor 1.5-2 will help your Lora keep good performance with Lightning 4/8 steps. Keep up the good work!

    TimmyHodorJan 9, 2026· 2 reactions

    Oh and, I saw a few watermarks bleed out. Cropping them out of the training data should fix that.

    SuperHawk7
    Author
    Jan 9, 2026

    Good note, thank you! Yeah, I need to do a bit more post processing to my images. I think the next run I do I will process all of them through Qwen Edit 2511 to remove things I don't want like watermarks. I'm able to get decent results with the lightning loras, but I'll five those a shot.

    TimmyHodorJan 10, 2026

    @SuperHawk7 What captionning method did you use to create your dataset?

    ChillDesireJan 10, 2026

    @SuperHawk7 What methods are you using with the Lightning Lora? I tend to get either extreme contrast or body horror with it enabled.

    SuperHawk7
    Author
    Jan 10, 2026· 1 reaction

    @TimmyHodor I did a multi-pass method. First process them all with
    qwen3-vl-8b-nsfw-caption-v4.5, then manually clean up anything the model did wrong as well as add common keywords (ex. reverse cowgirl) that the LLMs just don't get.

    SuperHawk7
    Author
    Jan 10, 2026· 1 reaction

    @ChillDesire Generally I drop the CFG a lot with the lighting LoRa's when I'm seeing the high contrast / body horror stuff. I noticed that Qwen does pretty well all the way down to 0.6 CFG and still adheres to the prompt pretty well assuming that it's well written. I've also noticed you can get great results going higher than the LoRa steps prescribe. So use 8 steps on the 4 step LoRa.

    gtan33Apr 19, 2026
    CivitAI

    <Error>

    <Code>NoSuchKey</Code>

    <Message>The specified key does not exist.</Message>

    </Error>