<p>Since support for MOSS-Image in OneTrainer—the tool I usually use—is lagging, I’m testing a full fine-tuning (FT) process using a different tool.</p><p>I’ve set this up as a "Finetune Experimental Test" using a separate model instance.</p><h3 id="ver.-0.1">ver. 0.1</h3><p>Honestly, it’s been quite a struggle; I tried modifying various other tools, but they all failed—resulting in nothing but bizarre, garbled images. This time, I used "<a target="_blank" rel="ugc" href="https://github.com/shootthesound/Fizgig">Fizgig</a>." It’s an interesting tool, though it breaks the training process into four separate stages, which makes getting results a rather slow affair. It keeps the model in VRAM using NF4 quantization for the actual training, then writes the data back to BF16 format in the main system memory. Since the optimizer state is maintained in BF16 precision, the overall precision isn't actually that low; the theory is that any shortfall in computational precision is compensated for by a higher number of training steps (S<em>ince settings vary depending on the environment, it is highly likely that processing is being performed using BF16 in this instance.</em>).</p><p>The output here is from the very first epoch, so this is strictly an experimental, preliminary test.</p><p></p><h3 id="ver.0.13-lora">ver.0.13 LoRA</h3><p>Actually, I had already finished up to epoch 3 by yesterday, but in terms of balance, epoch 1 felt the most practical to use. As the epochs progress, elements that weren't originally in an anime style shift closer to an anime aesthetic, while things that were already in an anime style in epoch 1 remain largely unchanged. I don't plan on releasing the full checkpoints, but I have created a LoRA based on the difference between epoch 3 and the base model, which I’ve added as an optional file.</p><h3 id="ver.0.2">ver.0.2</h3><p>This is a test of fine-tuning (FT) using a local checkpoint (ckpt) within Fizgig. Since this cannot be specified via the GUI, I modified the configuration file directly. This also serves as a functional check, as changes to configuration files in this tool are not always applied correctly.</p><p>I used MOF-FET v0.1 as a base, along with a small dataset (just under 10,000 images) featuring a different artistic style. The model leans toward a "semi-realistic" aesthetic, though it lacks any particularly distinct characteristics. Compositional quality and prompt adherence have both declined; given how well-crafted the base model is, it is likely better not to stray too far from it.</p><p>To be honest, the results aren't great, but I’ve decided to release it as a "test model." Another reason is that I needed a suitable model to use as an example when explaining how to use the merger tool—there aren't many models available to mix, after all.</p><p>Incidentally, when generating images with MOSS-Image without providing a prompt, the output often consists of documents, erotic manga, or pamphlets; perhaps "eromanga" is the prompt this model handles best.</p><h3 id="ver.0.3">ver.0.3</h3><p>It’s a bit hard to define, but this version uses a "base model" in the literal sense. I had originally intended to use a less powerful, pre-trained model as the foundation for this test, but an error—likely triggered by an update to Fizgig—prevented that.</p><p>Compared to ver.0.1, this is a standard, "typical" anime-style character model. Since it seems that lighter fine-tuning (FT) works well for MOSS-Image, I used this as an opportunity to test a more streamlined, less labor-intensive approach; the total training time was only about 3 hours. About an hour of that was spent on cache generation (though I suspect the cache might not even be necessary for a single-epoch run). Even so, it performs reasonably well.</p><h3 id="ver.0.4">ver.0.4</h3><p>This is an experiment to see how effective "minimal" training can be. I tested this using a photorealistic model, with a dataset of 300 images trained for 5 epochs. I also tried 10 epochs, but the quality -specifically regarding composition- seemed to decline. Additionally, I incorporated <a rel="ugc" href="https://civarchive.com/models/3037959/moss-fet-loras">LoRAs</a> derived from previous anime-style models. Overall, through a combination of light fine-tuning and model merging, I’ve ensured that elements like composition remain consistent with the base model. The core concept is to create a versatile, general-purpose model capable of handling a wide range of prompts, achieved through minimal training. While there are certain things it cannot express, I believe that if you require more, using a LoRA is the better approach. For anime-style imagery, versions of 0.1 or 0.3 may be likely more appropriate.</p><p>As with many recent models, if you don’t explicitly specify the composition or pose, the subject may end up standing stiffly? which is to be expected, given that no specific instructions were provided. While it is possible to adjust the training process to reduce this "stiffness," MOSS-Image is a highly structured model, so I have avoided doing so. Therefore, please rely on your prompts to make the necessary adjustments. Using a prompt enhancer is a good option, though they can be quite resource-intensive; for a quick test, I recommend including the following tags:</p><pre><code>from side, close up, dynamic angle, dynamic pose, photo realistic, detailed, cinematic lighting, deep shadow</code></pre><p>MOSS-Image has limited precision regarding orientation, so you might find it helpful to include "from side" even when the subject isn't strictly facing sideways. For this model, I suggest starting by adding "close up." If you are accustomed to the outputs of models like SDXL, try using "dynamic angle" or "dynamic pose" though you should adjust these if the results look off. I’ve included "detailed," though I’m not entirely certain of its actual impact. For photorealistic outputs, try incorporating "cinematic lighting" and "deep shadow," then adjust as needed; in the world of AI image generation, images with strong contrast and underexposed (darker) tones are generally preferred.</p><p>A new version of the prompt enhancer node (which was included in the ver. 0.3 workflow) will be released soon.</p>

MOSS-FET

MOSSFET.safetensors

MOSS-FET_v01_INT8.safetensors

Files with SHA256: 34fae07ffedee0f0c58fa5672db19ecdd4d8093c10619425af9de08f97ed5f88