Jump to content

Long-running error with Honoka-body versions of some older mods.


Recommended Posts

I've tried off and on to figure this problem out but I'm at wits end.  It's hard to explain so I'll just show it.

 

Lobelia in a custom skin.  Looks normal, yes?

1982906942_DOAX_VV2023-03-3009-18-59.jpg.e5d4b9830f7f23a8f25911af58baabd7.jpg

 

Lobelia in the all range bikini mod, which is available for all body types.  This looks perfect normal, yes?  You can still see the custom skin I made "underneath" the bikini.

 

373084171_DOAX_VV2023-03-3009-19-37.jpg.6ca95eaf18a74a033c1cec8fa6e6a9fe.jpg

 

Here's a shot of Elise using a custom skin:

 

608254801_DOAX_VV2023-03-3009-17-12.jpg.0c380ba7250aaa840e5378ebca77f50f.jpg

 

Now here's a shot of her wearing that same bikini mod:

974393126_DOAX_VV2023-03-3009-17-53.jpg.a37fc7d441fb8990bc2207f99cb59049.jpg

 

Notice how I can no longer see the custom skin "underneath".  Instead it's showing a skin with.... I don't know if that's supposed to be semen or sweat but... well I'm not a fan. 

 

 

Here's the views from the front:

 

Normal:

121580442_DOAX_VV2023-03-3009-27-10.jpg.85586e1cb59d6447a3d986f303b05d15.jpg

 

All-Range Mod:

1918959496_DOAX_VV2023-03-3009-26-26.jpg.a08df573668001a0f5bfcb7e8e273807.jpg

 

You can tell it's a whole new skin because there's purple pubes on this one and not my custom one.

 

 

 

So you're probably saying "well, there's something wrong with the mod then."  NO! You can check the all range mod for yourself.  It calls a custom body VB and IB but no texture for the skin. There aren't even any dds files in the mod apart from the bikini itself. 

 

[TextureOverrideBody]
if $\mods\_id\id.ini\swimsuit1 != $id && $\mods\_id\id.ini\swimsuit2 != $id
    run = CommandListID
endif
hash = ae100bc7
vb0 = ResourceBodyVB
ib = ResourceBodyIB
handling = skip
drawindexed = auto
$mod_active = 1

 

Another clue: If I inspect the vs c523c6339eefee69 I get this:

668949725_DOAX_VV2023-03-3009-33-11.jpg.7e8ed2876796422a187b2ecdbf2dbb42.jpg

 

When I inspect vs c523c6339eefee69 I can see my custom skin.  I'm not sure what that means, though.  It means it's drawing the proper texture on the model but it's being covered up by something associated with vs c523c6339eefee69, perhaps?

 

And here's the real kicker: I disabled ALL my mods except All-Range and it still looks the same.  Including all my custom skin mods, make up mods, costume mods, everything in my main mod folder.  Obviously, her custom face textures disappeared when I did that, but the "sweaty" skin texture remained.

 

And this isn't just limited to the All-Range mod.  Some other mods to this as well, it's just that All Range is the most accessible to show it off on.

 

DOAX_VV 2023-03-30 09-20-21.jpg

Edited by SolomonSTB1973
Link to comment
6 hours ago, SolomonSTB1973 said:

I've tried off and on to figure this problem out but I'm at wits end.  It's hard to explain so I'll just show it.

 

Lobelia in a custom skin.  Looks normal, yes?

1982906942_DOAX_VV2023-03-3009-18-59.jpg.e5d4b9830f7f23a8f25911af58baabd7.jpg

 

Lobelia in the all range bikini mod, which is available for all body types.  This looks perfect normal, yes?  You can still see the custom skin I made "underneath" the bikini.

 

373084171_DOAX_VV2023-03-3009-19-37.jpg.6ca95eaf18a74a033c1cec8fa6e6a9fe.jpg

 

Here's a shot of Elise using a custom skin:

 

608254801_DOAX_VV2023-03-3009-17-12.jpg.0c380ba7250aaa840e5378ebca77f50f.jpg

 

Now here's a shot of her wearing that same bikini mod:

974393126_DOAX_VV2023-03-3009-17-53.jpg.a37fc7d441fb8990bc2207f99cb59049.jpg

 

Notice how I can no longer see the custom skin "underneath".  Instead it's showing a skin with.... I don't know if that's supposed to be semen or sweat but... well I'm not a fan. 

 

 

Here's the views from the front:

 

Normal:

121580442_DOAX_VV2023-03-3009-27-10.jpg.85586e1cb59d6447a3d986f303b05d15.jpg

 

All-Range Mod:

1918959496_DOAX_VV2023-03-3009-26-26.jpg.a08df573668001a0f5bfcb7e8e273807.jpg

 

You can tell it's a whole new skin because there's purple pubes on this one and not my custom one.

 

 

 

So you're probably saying "well, there's something wrong with the mod then."  NO! You can check the all range mod for yourself.  It calls a custom body VB and IB but no texture for the skin. There aren't even any dds files in the mod apart from the bikini itself. 

 

[TextureOverrideBody]
if $\mods\_id\id.ini\swimsuit1 != $id && $\mods\_id\id.ini\swimsuit2 != $id
    run = CommandListID
endif
hash = ae100bc7
vb0 = ResourceBodyVB
ib = ResourceBodyIB
handling = skip
drawindexed = auto
$mod_active = 1

 

Another clue: If I inspect the vs c523c6339eefee69 I get this:

668949725_DOAX_VV2023-03-3009-33-11.jpg.7e8ed2876796422a187b2ecdbf2dbb42.jpg

 

When I inspect vs c523c6339eefee69 I can see my custom skin.  I'm not sure what that means, though.  It means it's drawing the proper texture on the model but it's being covered up by something associated with vs c523c6339eefee69, perhaps?

 

And here's the real kicker: I disabled ALL my mods except All-Range and it still looks the same.  Including all my custom skin mods, make up mods, costume mods, everything in my main mod folder.  Obviously, her custom face textures disappeared when I did that, but the "sweaty" skin texture remained.

 

And this isn't just limited to the All-Range mod.  Some other mods to this as well, it's just that All Range is the most accessible to show it off on.

 

DOAX_VV 2023-03-30 09-20-21.jpg

Try this, this is a common error for Honoka Body Type, and if your skin doesn't show up, at least those spots will go away:

 

[TextureOverrideBody]
if $\mods\_id\id.ini\swimsuit1 != $id && $\mods\_id\id.ini\swimsuit2 != $id
    run = CommandListID
endif
hash = ae100bc7

match_first_index = 0
vb0 = ResourceBodyVB
ib = ResourceBodyIB
handling = skip
drawindexed = auto
$mod_active = 1

 

DOAX-VenusVacation_230330_172827.thumb.jpg.5d1fd691d86713b87784a527c60e5fa5.jpgDOAX-VenusVacation_230330_172902.thumb.jpg.e0c977052002af702a8e5cbac6c1afe5.jpg

Link to comment

Hey!

 

That's completely fixed it.  Wow, thanks!

 

Though I'm still REALLY curious... where was it getting that skin from? Like I said, that's clearly a skin loaded form SOMEWHERE on my computer, since you can see purple pubes on it and i'm PRETTY sure the game doesn't normally draw pubes on the models.  Even after disabling ALL my mods save ALL Range, it was able to load that mod up from somewhere.  

 

But, still, thanks loads.  That error has been bugging me for YEARS.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. For more information, see our Privacy Policy & Terms of Use