For FL2VA Model.<h3 id="multiple-footjob-varieties-available!">👆 Multiple Footjob Varieties Available! 👣</h3><pre><code>
┌─────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│ Version │ Strength │ Description │
├─────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ Type A │ 1.0 │ Simple footjob, toes gripping shaft on both sides │
│ Type B │ 0.4~0.7 │ Toes grip on both sides, more 'head' action │
│ Type C │ 0.6~0.8 │ One foot stationary, one foot moving │
│ Type D │ 0.8~1.0 │ Cock between toes on both feet, both feet moving │
└─────────┴────────────┴────────────────────────────────────────────────────────────────────────┘</code></pre><hr />Technobullshit:Type C notes... Learning more and more about H3 training but still not totally nailed down. I am still struggling with the tendency for it to zoom in on the feet or make the penis extra huge. I assume this is because the training data contains a lot of close-ups which it is trying to reproduce. In an effort to correct this I trained Type C with a reduced max_timestep, 700. Trying to apply the same kind of high/low noise logic I learned from Wan 22. 700 is probably still too high but I didn't want to eliminate all high noise movement training. This deserves further experimentation. I also increased min_timestep a little bit, to 100, in an effort to reduce the compression-artifacteyness seen at higher strengths. It maybe worked?Type B notes... I switched from Diffsynth-Studio to Musubi-Tuner for Type B (only because I am familiar with musubi from Wan). I was having terrible luck training with the fl2va "task" in musubi, would not seem to learn motion much at all. So I switched it to t2va and seem to be getting better motion learning, possibly because it's not pulling first and last frames that are nearly identical, but tbh I have no idea. I experimented with lower res cache data (192 px) and found it trained quickly but easily overbaked and low res artifacts started appearing in my generations before the movement did. However, this did seem to be a good indicator of how well the dataset and parameters would work for higher res training. This seems like a useful method for relatively quick checks for future training runs. I also experimented with rank 32 / alpha 32, 32/1, 16/1 and 16/16. The final published Type B was trained on five 512x512x124 clips, one of which had repeats=6 so basically 10 clips. rank 16 alpha 16, lr 1e-4, trained on the int8_convrot. swapped 32 blocks and took about 15 hours to train to 400 epochs/4000 steps on the 5090.

H3 Footjobs

Files with SHA256: acb60dba1f24fabf3d6d41f76be7f354ec3eb70806fa985e6b545dadc78f5730