Shemale and female skins

[ronnie]

I assure you, if the skin is being ignored by V11, it contains a flaw that VX is ignoring.

You missed a crucial point: files they need to be female_white_etc

Some are now showing up - but they only display as the default skin 2 - white activemod.

So that's nice.

[The End]

I assure you, if the skin is being ignored by V11, it contains a flaw that VX is ignoring.

You missed a crucial point: files they need to be female_white_etc

Some are now showing up - but they only display as the default skin 2 - white activemod.

So that's nice.

As far as I'm aware, the only two options for "Female_" skins are "White" & "African".

I just checked. "African" skins are not loading. I'll report it to The Team. Thx.

Update: Hmm. Further testing shows the skins DO appear to be loading, but are added at the end of the list, not alphabetically. I'll continue to look into it.

Note: The icon for "African" skins is different from the Icon for "White" skins, making them easier to spot in the list.

[ronnie]

As far as I'm aware, the only two options for "Female_" skins are "White" & "African".

I just checked. "African" skins are not loading. I'll report it to The Team. Thx.

Update: Hmm. Further testing shows the skins DO appear to be loading, but are added at the end of the list, not alphabetically. I'll continue to look into it.

Note: The icon for "African" skins is different from the Icon for "White" skins, making them easier to spot in the list.

The do show up alphabetically, after the three default skins - as they always did in VX.

The problem is - none of them actually load onto the model when selected. They default to skin 2 called "Activemod White".

EDIT UPDATE: I finally got some things to work after more digging:

- my skins are (I believe) 4x as I got them from the 4x archives. however, they only actually load onto a model if you choose 8x on the resolution drop down.

- choosing "auto" on the resolution dropdown does not work.

[The End]

The do show up alphabetically, after the three default skins - as they always did in VX.

The problem is - none of them actually load onto the model when selected. They default to skin 2 called "Activemod White".

EDIT UPDATE: I finally got some things to work after more digging:

- my skins are (I believe) 4x as I got them from the 4x archives. however, they only actually load onto a model if you choose 8x on the resolution drop down.

- choosing "auto" on the resolution dropdown does not work.

I'm finding African skins loading towards the end of the list regardless of name (eg: on my system, "7_min_abs" is skin #98, but "7_min_abs_mocha" is 110.)

In my testing, all of my "African" skins are 1x, so that may explain some of my differing results.

I've suspected "Auto" doesn't work. I've had better success using "Default Body, Face", but that may only be for 1x skins.

[ronnie]

...

next update:

I tested a skin called "Miley Cyrus" as it had identifying tattoos baked onto the PNGs.

I converted all the norm/spec .dds files to .png (losing the mipmaps)

It only loaded onto the model if I played with the "colour" options in the customizer.

I've absolutely no idea if the passfiles actually load the norms, specs and subs - they seem to have no real effect.

EDIT: Shemale skins show up when files are titled shemale_white_etc now.

[ronnie]

Okay some things I've learned:

1. skins taken from the 4x archive ONLY load onto a model if 8x body, face is chosen in the customizer

2. you may need to tweak colour settings to get them to fully load.

3. white female skin naming convention is female_white_etc

4. white shemale skin naming convention is shemale_white_etc

5. V11 does not convert .dds files - your norms/specs/subs need to be .png

6. i'm not entirely sure if the norms/specs/subs actually have an effect.

*** I've tried to include a fully working 4x skin for review, but the website won't let me.

[ronnie]

etc

see above. think I've solved this.

[The End]

5. V11 does not convert .dds files - your norms/specs/subs need to be .png

V11 is unable to decode certain DDS formats, but it handles most others.

If you can't load the DDS file into an image viewer like "IrfanView", chances are V11 can't decode it either.

In these situations, I use "Paint.net" (download

[To see links please log-in or register here]

) which can read encrypted DDS files and save them out as PNGs.

[ronnie]

In these situations, I use "Paint.net" (download

[To see links please log-in or register here]

) which can read encrypted DDS files and save them out as PNGs.

I have photoshop cc so I'm sorted on that thanks.

But what's the point in supporting .dds if it doesn't support all .dds? that's just stupid.

Anyway you have my observations given even the devs don't seem to know how things work.

Checked in, decided no thanks.

Dead game.

[The End]

In these situations, I use "Paint.net" (download

[To see links please log-in or register here]

) which can read encrypted DDS files and save them out as PNGs.

I have photoshop cc so I'm sorted on that thanks.

But what's the point in supporting .dds if it doesn't support all .dds? that's just stupid.

Anyway you have my observations given even the devs don't seem to know how things work.

Checked in, decided no thanks.

Dead game.

TK17 never supported DDS files. That was "Hook". V11 does it's best to convert DDS files to provide minimal "Hook-like" shader support, but it's no Hook (a "Hook64" is still in the planning stages.)

Remember, "The Team" didn't write V11. We are only patching a deeply flawed Beta to make it usable.