Encountered a bug . Dresses seem to work just fine. Seems like kink it up is at fault. Whenever I equip heels - a square area of textures disappears at the groin area. Affects both Frocking Splendors and vanilla dresses. Double checked without any mods but these two on - the result is the same

引用自 screwy22：

Encountered a bug . Dresses seem to work just fine. Seems like kink it up is at fault. Whenever I equip heels - a square area of textures disappears at the groin area. Affects both Frocking Splendors and vanilla dresses. Double checked without any mods but these two on - the result is the same

@screwy22 I just tested it myself, can't seem to replicate this. Can you please let me know exactly what combination of clothing items are causing this issue? Thanks! Also, make sure you disable Kink it Up **Extended** and have **Extra** loaded after the base mod - having the wrong load order may mess things up. Frockin Splendor can be loaded before or after.

The load order is in order. Heels No1-3 eat the textures on the groin level (like every piece of clothing in the game, that goes below the waistline and covers the legs completely: Dresses, hospital gowns etc. However, heels work just fine with trousers). Boots(Low, Knee high) seem to work just fine with both trousers and dresses. It affects the outer layer only, though. Underwear is fully visible under the eaten textures. I must add, that not all the textures on the groin level disappear. It only erases the square that covers the front, back and inner parts of thighs. Outer thighs are still covered. (Also, it affects both male and female models)

@screwy22 I still can't replicate this, even with the hospital gowns and vanilla dresses, but that's more than enough info to troubleshoot. It looks like a missing masks problem, which I thought I had fixed. I will see about pushing out a hotfix to Extra soon. Thanks for letting me know!

No prob. Just cheked some other combinations. Heels work with rubber skirt. Also, with a suit jacket on, there's a bikini-like cutout on it's front side

Issue identified and properly fixed in Extra, hotfix deploying soon :D