<h1 id="generation-guide">Generation Guide</h1><h2 id="model-information">Model Information</h2><ul><li>Model Name: <code>{model_name}</code> (replace with the actual filename you downloaded, e.g., <code>gngsfimZIB.safetensors</code>)</li><li>Trigger Word: <code>{trigger_word}</code></li></ul><h2 id="recommended-settings">Recommended Settings</h2><h3 id="resolution">Resolution</h3><ul><li>2:3 ratio: 821×1232 (portrait)</li><li>3:2 ratio: 1232×821 (landscape)</li><li>Square: 1:1</li><li>Note: You can vary these resolutions with limited success</li><li>FT15 models: Lower max resolution at 512×768</li></ul><h3 id="generation-parameters">Generation Parameters</h3><ul><li>Sampler: Euler (typically)</li><li>CFG Scale:<ul><li>Standard models: 3-7</li><li>Turbo models: 1</li></ul></li><li>Steps:<ul><li>Standard models: 20-50</li><li>Turbo models: 9</li></ul></li><li>LoRA Strength: 0.6-1.0<ul><li>If images look "cooked" or overprocessed, lower the strength</li></ul></li></ul><h2 id="model-series-identifiers">Model Series Identifiers</h2><ul><li>FT15 - Stable Diffusion 1.5 (max resolution: 512×768)</li><li>XLrd - SDXL Run Diffusion X based</li><li>CHHD - Chroma models</li><li>ZIMG - Z-Image Turbo</li><li>ZIB - Z-Image Base</li><li>FKFB - Flux Klein 4B</li><li>QWN - Qwen</li></ul>Note: LoRA files are large and can be resized if neededCurrent Recommendation (January 2026): Use ZIB/ZIT or Chroma models for best results.<h2 id="dataset-type-indicators">Dataset Type Indicators</h2><ul><li>mx - Vastly larger datasets with less consistency, typically trained at lower learning rates for longer durations</li><li>lncc - Smaller, more specific aesthetic-focused datasets</li></ul>Training Data Scale: Datasets vary from 20-30 images to over 1,000,000 images. The median dataset size is closer to 10,000 images.Training Techniques: Models starting at SDXL use mixed resolution training, multi-subject crop, and flips for improved generalization.<h2 id="using-the-wildcard-prompt-template">Using the Wildcard Prompt Template</h2>The piped string format below is designed for ImpactPack Wildcard Processor or Automatic1111 Dynamic Prompts. Copy and paste it into either extension to generate a new randomized prompt each time, built on the distribution of the training dataset.<h3 id="prompt-format">Prompt Format</h3><pre><code>&lt;lora:{model_name}:{0.6|0.7|0.8|0.9|1}&gt; {trigger_word}, {wildcard_tags}</code></pre>Example:<pre><code>&lt;lora:gngsfimZIB:{0.6|0.7|0.8|0.9|1}&gt; example_triggerword, {additional|tags|here}</code></pre><h3 id="understanding-the-wildcard-tags">Understanding the Wildcard Tags</h3><ul><li>More pipes (|) in a tag group = rarer tags in the training data</li><li>Fewer pipes or repeated options = more common tags with better model performance</li><li>More examples in the training data mean the model is better at that particular task or concept</li></ul><h3 id="manual-usage-(without-wildcards)">Manual Usage (without wildcards)</h3>If you're not using dynamic prompts:<ol><li>Load the LoRA manually in your interface</li><li>Start with the trigger word <code>{trigger_word}</code> at the beginning of your prompt</li><li>Add additional tags after the trigger word to vary the composition</li><li>Tags that appear more frequently in the wildcard examples will produce more consistent results</li></ol><h2 id="tips">Tips</h2><ul><li>Always start with the trigger word (the first tag) for best results</li><li>Check sample images for embedded generation parameters</li><li>Add additional tags to vary composition and style</li><li>Experiment with LoRA strength if results don't match expectations</li><li>Tags with more training examples will be more reliable and consistent</li><li>Reference the sample images on this page for working parameter combinations</li></ul><hr /><h1 id="faq:-dataset-filename-and-trigger-word-conventions">FAQ: Dataset Filename &amp; Trigger Word Conventions</h1><h3 id="what-problem-does-this-filename-format-solve">What problem does this filename format solve?</h3>The filename is designed to avoid collisions with generic or common names while also serving as a programmatic signal. It encodes both the trigger word and the dataset type, making it easy for scripts and training pipelines to identify and handle the dataset correctly.<h3 id="why-not-use-a-generic-filename">Why not use a generic filename?</h3>Generic filenames tend to overlap across projects and environments. This format ensures:<ul><li>Uniqueness across datasets</li><li>Clear intent when parsed programmatically</li><li>No ambiguity about dataset content or usage</li></ul><h3 id="what-do-the-suffix-codes-mean">What do the suffix codes mean?</h3>The suffix in the filename specifies:<ul><li>The resolution of the dataset</li><li>The model architecture tier it is intended for</li></ul>This makes it immediately clear what kind of model configuration the dataset targets and helps avoid compatibility issues.<h3 id="what-does-&quot;mx&quot;-stand-for">What does "mx" stand for?</h3>mx means mix. It indicates that the dataset is diverse and vastly larger (potentially hundreds of thousands to over a million images), though less consistent than focused datasets. These models are typically trained at lower learning rates for longer durations to accommodate the dataset diversity.<h3 id="what-does-&quot;lncc&quot;-stand-for">What does "lncc" stand for?</h3>lncc indicates smaller, more specific datasets focused on a particular aesthetic. These are more consistent but cover a narrower range of content.<h3 id="how-are-trigger-words-determined">How are trigger words determined?</h3>Trigger words are embedded in the dataset and filename structure. They function as activation tokens that help the model recognize and generate content consistent with the training data. Always use the specified trigger word at the start of your prompt for best results.<h3 id="how-large-are-the-training-datasets">How large are the training datasets?</h3>Training datasets vary significantly:<ul><li>Minimum: 20-30 images</li><li>Maximum: Over 1,000,000 images</li><li>Median: Approximately 10,000 images</li></ul>Larger datasets (mx) enable broader capabilities but may be less consistent. Smaller datasets (lncc) are more focused and aesthetically coherent.<hr />For best results, always check the sample images on this model page—generation parameters are embedded in the metadata.&lt;lora:afslyoslnccXLrd:{0.6|0.7|0.8|0.9|1}&gt; {afslyoslnccft, }{1girl, }{ass, }{realistic, }{pussy, }{cum, }{lying, }{after sex, }{hetero, }{penis, }{1boy, }{anus, }{pubic hair, }{completely nude, }{dark skin, |}{erection, |}{dark-skinned male, |}{after vaginal, |}{on stomach, |}{looking back, |}{interracial, |}{cum in pussy, |}{imminent penetration, |}{male pubic hair, |}{open mouth, |}{female pubic hair, |}{looking at viewer, ||}{ass grab, ||}{solo focus, ||}{testicles, ||}{cumdrip, ||}{after anal, ||}{cum on ass, ||}{feet, ||}{spread legs, ||}{parted lips, ||}{imminent vaginal, ||}v1.0768x512 3:2 Landscape512 * 768 2:3 Portrait627*627 squareFT15c&lt;lora:afslyoslnccFT15:1&gt;, {afslyoslnccft, }{1girl, }{ass, }{realistic, }{pussy, }{cum, }{lying, }{after sex, }{hetero, }{penis, }{1boy, }{anus, }{pubic hair, |||}{completely nude, |||}{dark-skinned male, }{after vaginal, }{erection, }{interracial, }{on stomach, }{looking back, }{cum in pussy, }{imminent penetration, }{male pubic hair, }{open mouth, ||||||}{female pubic hair, |||}{looking at viewer, }{ass grab, |||}{solo focus, |||}{cumdrip, }{testicles, |||}{after anal, |||}{feet, |||}{cum on ass, |||}{imminent vaginal, |||}{spread legs, ||| }

Sarah Petersons lying after vaginal cum drip FT15

afslyoslnccXLrd.safetensors

Files with SHA256: 03e5c30d945a290ebbcedd4d95e163a26a8a55a59d93c5de1cb09bd8b1d2178e