Heirloom Male XL started as a personal SDXL merge I built to solve one annoying problem: photoreal models love drifting back to female defaults, especially in couple / romance prompts. I mainly create male-focused (MM) content — including interspecies/fantasy couples — so I tuned this merge to favor male subjects, while keeping an overall clean, photoreal look.After testing it a bunch in my own workflow, I decided to share it in case it helps other creators who want a stronger male bias without needing ControlNet every time.<hr /><h2 id="what's-new-in-v3">🔥 What’s new in V3</h2>Version 3 uses the same merge ingredients as V2 — but with a big upgrade:✅ I trained a couples-focused LoRA and merged it into the checkpoint. That means:<ul><li>MM / gay couples generate easier with “normal couple prompts”</li><li>Less fighting to keep both subjects male</li><li>More reliable couple composition (still prompt-dependent, but way smoother)</li></ul>⚠️ Important: V3 is easier, not “automatic.” You’ll still get best results if you follow the prompt habits from V1/V2 samples (clear genders, clear roles, clear framing).<hr /><h2 id="changelog-(v2-v3)">🧾 Changelog (V2 → V3)</h2>✅ Couples consistency improved (built-in LoRA merge) ✅ Less drift during soft/romantic aesthetics ✅ Better reliability for MM romance prompts ✅ Still keeps the clean photoreal look + prompt-following improvements from V2<hr /><h2 id="prompt-tips-(v3-still-likes-&quot;good-prompting&quot;)">📝 Prompt tips (V3 still likes “good prompting”)</h2>Best starting point: use the exact prompts from the sample images on this model page. Those are the closest “what this checkpoint likes” baseline.If the model drifts away from male subjects, add one of these (start light, don’t over-weight):<ul><li><code>two men, two asian men,</code></li><li><code>male couple, gay couple</code></li><li><code>2boys</code></li><li><code>two male lovers</code></li><li><code>handsome men, masculine features</code></li></ul><h3 id="composition-tip-(for-couples)">👀 Composition tip (for couples)</h3>If you want the couple framed correctly, say the camera framing clearly:<ul><li><code>close-up portrait</code></li><li><code>mid shot, waist-up</code></li><li><code>full body</code></li><li><code>front view, eye level</code></li></ul><hr /><h2 id="recommended-settings-(forge-neo-baseline)">🎛️ Recommended settings (Forge Neo baseline)</h2>These are the general settings I recommend (same vibe as your V1/V2 samples):<ul><li>WebUI: Forge Neo</li><li>Sampler: <code>DPM++ 2M SDE</code> (recommended) / <code>DPM++ 3M SDE</code></li><li>Schedule: <code>Karras</code></li><li>Steps: <code>40–50</code></li><li>Resolution: <code>896 × 1344</code></li><li>CFG: 2.5 → 6.5 (sweet spot; too high can look “plastic”)</li></ul><hr /><h2 id="forge-neo-&quot;stable-diffusion&quot;-settings">⚙️ Forge Neo “Stable Diffusion” settings</h2>Go to: Settings → Stable Diffusion → SD UNetUse these:<ul><li>Clip Skip: <code>1</code></li><li>Emphasis Mode: <code>No norm</code> ✅ (helps avoid some SDXL weirdness)</li><li>[PR] Epsilon Scaling: <code>1.005</code></li><li>Token Wrap Length: <code>26</code></li><li>Tiling: OFF (unless you specifically need tileable images)</li><li>Random Number Generator: <code>GPU</code></li></ul>SDXL-specific fields (leave like this unless you know why you’re changing them):<ul><li>[SDXL] Crop-Top Coordinate: <code>0</code></li><li>[SDXL] Crop-Left Coordinate: <code>0</code></li><li>[SDXL] Low Aesthetic Score: <code>3</code></li><li>[SDXL] High Aesthetic Score: <code>6</code></li></ul><hr /><h2 id="side-note-(hard-mode-concepts-use-guidance-tools)">🧠 Side note (hard-mode concepts = use guidance tools)</h2>Some concepts are just hard mode with pure prompting — especially:<ul><li>fantasy couples</li><li>interspecies anatomy (tails/wings/etc)</li><li>complex poses / multiple characters</li></ul>If you use ControlNet (Canny + Reference Only) it can massively improve:<ul><li>couple posing + composition accuracy</li><li>identity consistency (faces/structure)</li><li>fantasy anatomy details</li></ul><hr /><h2 id="style-loras-+-consistency">🎛️ Style LoRAs + consistency</h2>Good news: V2 improved the “style LoRA feels weaker after heavy merges” issue, and V3 keeps that improvement.If a style LoRA still feels muted, try:<ul><li>increase LoRA strength slightly</li><li>lower CFG a bit</li><li>do an img2img style pass at low denoise</li></ul><hr /><h2 id="suggested-negatives-(starter-pack-safer-baseline)">🚫 Suggested negatives (starter pack — safer baseline)</h2>Use as a baseline and adjust per workflow:Negatives:<ul><li><code>anime, toon, 2d, 3d, painting, drawing, illustration</code></li><li><code>glitch, deformed, mutated, cross-eyed, disfigured, ugly</code></li><li><code>distant subjects, wide shot, long shot</code> (only if you want close shots)</li><li><code>female features</code> (use this only if you keep getting female drift)</li><li><code>nudity, explicit</code> (only if you want strictly clean outputs)</li></ul><hr /><h2 id="sample-image-transparency">📸 Sample image transparency</h2><ul><li>Same general generation settings as earlier versions</li><li>Some samples may include ADetailer for faces/details (when noted)</li></ul><hr /><h2 id="prompt-helper-extension-(optional-but-super-useful)">🧩 Prompt helper extension (optional but super useful)</h2>If you struggle with prompts, tags, or consistent workflows, I built a helper extension (it was made for my personal use, sharing in case anyone finds it useful):Prompt Suite Bridge 🔗 <code>https://github.com/EditwithLak/prompt_suite_bridge.git</code>What it helps with:<ul><li>🗃️ Vault (tag libraries, packs, base prompts, LoRA/TI registry)</li><li>🧱 Prompt Composer (autocomplete + structured prompting + GGUF LLM support)</li><li>🧪 Map Generator (canny/openpose/depth map creation + ControlNet routing)</li><li>🏷️ Caption Tools (optional caption/tag pipelines via separate env)</li></ul>⚠️ Real talk: I’m not a GitHub pro 😅 If git install is annoying, just Download ZIP from GitHub, extract it into your WebUI <code>extensions/</code> folder, then restart — follow the instructions in the repo README.<hr /><h1 id="version-2">Version 2</h1>is an upgraded refinement of Version 1, built using the same merge ingredients, but tuned for better prompt-following, stronger male/MM consistency, and cleaner results with less “drift.” The goal stays the same: male-first photoreal, especially for MM romance/couples and fantasy/interspecies concepts — but now it’s more cooperative.What’s improved in V2<ul><li>Better prompt adherence (less “model does its own thing”)</li><li>MM / gay couples generate easier with normal couple prompts</li><li>Fantasy male subjects are more consistent, including interspecies concepts when prompted</li><li>Keeps the clean photoreal look, but with better control and reliability</li></ul>🧾 Changelog (V1 → V2)<ul><li>✅ Improved prompt-following / instruction compliance</li><li>✅ More consistent MM / gay couple generation</li><li>✅ Better fantasy male consistency</li><li>🎛️ Improved behavior with style LoRAs (see note below)</li><li>🧪 V2 sample images include an ADetailer pass (V1 samples were generated without helper tools)</li></ul>📝 Prompt tips<ul><li>Best starting point: check the exact prompts used in the sample images on this model page. Those prompts are the closest “what this checkpoint likes” baseline.</li></ul>🧠 Side note (hard-mode concepts = use guidance tools)Some concepts are just hard mode with pure prompting — especially: fantasy couples, interracial, interspecies, complex composition/poses.If you use ControlNet (Canny + Reference Only) it can drastically improve consistency for:<ul><li>couple posing + composition accuracy</li><li>identity consistency (faces/structure)</li><li>fantasy anatomy details (tails, wings, wingspans, etc.)</li></ul>🎛️ Style LoRAs + style consistency (V2 update)Good news: in Version 2, the “style LoRA feels weaker after heavier merges” issue is largely improved — at least for the styles/LoRAs I personally use and previously had issues with.That said, I can’t test every single LoRA or style out there. If a LoRA still feels muted, try:If a style LoRA feels weak, try:<ul><li>Increase LoRA strength slightly</li><li>Lower CFG a bit</li><li>Use img2img with low denoise for a style pass</li></ul>⚙️ CFG Scale tips (recommended)Don’t crank CFG too high — it can make outputs look over-saturated / plastic. Don’t go too low either — you’ll lose prompt control.✅ Personal recommended range: CFG 2.5 → 6.5 (Experiment depending on prompt complexity + LoRAs)If using IP-Adapter FaceID Plus (my V2 workflow)<ul><li>Keep CFG around ~1.5 for best results (FaceID tends to behave better at low CFG)</li><li>If using ADetailer + IP-Adapter together: In ADetailer settings, set ControlNet model to “Passthrough” (so ADetailer doesn’t fight the identity guidance)</li></ul>🚫 Suggested negative prompts (starter pack)Use this as a baseline and adjust depending on your workflow:Negatives: <code>((female, women, girl, pussy, breasts, vagina)), anime, toon \(style\), 2d, 3d, wide shot, long shot, distant subjects, painting, drawing, illustration, glitch, deformed, mutated, cross-eyed, ugly, disfigured</code>🧍 If the model keeps drifting female (quick fix)Even with a male-biased checkpoint, some prompt setups can still pull female by default — especially things like:<ul><li>“couple portrait” without specifying genders clearly</li><li>“romance scene” + soft aesthetic keywords</li><li>certain style LoRAs that bias feminine faces/body language</li><li>prompts that mention “beautiful / pretty” without adding male descriptors</li></ul>Try adding this tag:<ul><li><code>(1boy:1)</code> with weights<ul><li>Start without weights first (<code>1boy</code>)</li><li>If no improvement, start at 1.0 and slowly increase</li><li>Usually works well up to around 2.5 (don’t overdo it or it can get weird)</li></ul></li></ul>📸 Sample image transparency (V2)<ul><li>Same base generation settings as Version 1</li><li>V2 samples include an ADetailer pass (mainly for faces/details)</li></ul><hr /><h1 id="version-1">Version 1</h1><h2 id="what-it's-good-at">What it’s good at</h2><ul><li>Male-focused realism (better “male by default” behavior than my original bases)</li><li>Gay couples / MM prompts</li><li>Fantasy/escape vibes with realistic lighting and mood</li><li>Works well for interspecies concepts when prompted (merman, etc.)</li></ul><hr /><h2 id="merge-credits-(please-support-the-original-creators)">Merge credits (please support the original creators)</h2>Base (merge):<ul><li>photorealisticAllPurpose_v40</li><li>xlSatIORImitationOf_xlSATIorv72</li></ul>“Spices” added:<ul><li>sdxlYamersRealistic5_v5Rundiffusion — (dreamy realism / mood)</li><li>pornworksBadBoysPhoto_v06 — (male focus / MM bias)</li><li>waiIllustriousSDXL_v150 — (slight prompt-following boost)</li></ul>Links (kept together for easy copy/paste):<pre><code>photorealisticAllPurpose_v40
https://civarchive.com/models/659428?modelVersionId=2113674

xlSatIORImitationOf_xlSATIorv72
https://civarchive.com/models/1713256?modelVersionId=2379373

sdxlYamersRealistic5_v5Rundiffusion
https://civarchive.com/models/127923/sdxl-yamers-realistic-5?modelVersionId=299716

pornworksBadBoysPhoto_v06
https://civarchive.com/models/1197994/pornworks-bad-boys-photo-realistic-gay-and-male-nsfw-aesthetics-sdxl-checkpoint

waiIllustriousSDXL_v150
https://civarchive.com/models/827184?modelVersionId=2167369
</code></pre><hr /><h2 id="recommended-settings-(what-my-samples-use)">Recommended settings (what my samples use)</h2>WebUI: ForgeNeo<ul><li>Sampler: DPM++ 2M SDE (recommended) / DPM++ 3M SDE</li><li>Schedule: Karras</li><li>Steps: 40–50</li><li>Resolution: 896 × 1344</li></ul>All sample images were generated with the above settings. No ADetailer, ControlNet, or other helper tools were used.<hr /><h3 id="more-examples-(my-galleries)">More Examples (My Galleries)</h3>You can see more images I’ve created (including male-focused + interspecies couples) on my pages below:DeviantArt: <a target="_blank" rel="ugc" href="https://www.deviantart.com/moodpixel">https://www.deviantart.com/moodpixel</a>Patreon: <a target="_blank" rel="ugc" href="http://patreon.com/MoodPixel">http://patreon.com/MoodPixel</a>Note: Not every image on these pages is a “raw checkpoint-only” result. Some posts include additional workflows (for example: LoRAs, inpainting, ADetailer, ControlNet, upscalers, or post-processing). The sample images attached to this model page are the closest representation of the checkpoint using only the settings listed above.<hr /><h2 id="notes-known-quirks">Notes / Known quirks</h2><ul><li>This is my first public merge, so if you hit odd edge cases, consider it “merge-life” and feel free to experiment.</li><li>After heavier merges, some style LoRAs can feel weaker. If that happens, try:<ul><li>increasing LoRA strength slightly</li><li>lowering CFG a bit</li><li>using img2img with low denoise for style passes</li></ul></li></ul><hr /><h2 id="important-content-note">Important content note</h2>One ingredient used for stronger male bias is NSFW-leaning, so this checkpoint may sometimes “suggest” more skin than requested depending on prompts. If you want clean outputs, use clear clothing terms and negatives like: <code>nude, naked, nsfw, explicit</code>I recommend ADetailer for the faces and other details.

Files with SHA256: 881b39480384b11edab4c4abaa9efc2448ea0b0987d1f5c4552d60d3e45b51f6