VaM 1.x remove Foreskin morphs

[nagsugo]

Hi everyone, Can anyone help me removing définitely the foreskin morphs from the character morph presets please?

i tried to uninstall any related plugin and morphs but it keeps coming back, there is always this shittyn Babul Foreskin morphs that keeps running on my character's morphs.

Thanks in advance guys

 

[kakashisex]

My trick is to simply disable the related package in the package manager.

 

[SlimerJSpud]

Every plugin that uses that morph has a control to turn that effect off.

 

[kakashisex]

Every plugin that uses that morph has a control to turn that effect off.

But some creators bake those morphs (technically morph poses) into their Timeline animation poses. I used to remove them by hand and update the poses, but the fastest workaround I've found so far is to disable the morph plugin.

 

[SlimerJSpud]

That's actually true of a lot of things. Tittymagic also gets its morphs baked into Timeline, if it's active when the poses are saved. I don't like that. The auto Breast Impact morphs are a pain too. The plugin should override the pose, though. If you go into the plugin UI, you can try setting that morph to 0.001, just so the plugin will think it's setting something, but it is no longer visible. I don't like foreskin morphs either.

 

[nagsugo]

still didnt get any proper solution, if I disable the related package, it either comes back when I reload a female pluggin presets, or it totally disable Cheesy FX features, that is not intended initially, I just want to get rid of that foreskin shit that is absolutely a mess and is totally useless, I dont even understand why this pluggin exists or is related to everything, that doesnt make any sense honnestly...

 

[hazmhox]

First : please respect people's work. You can assess you don't like something, quality differs from resource to resource, it is true, but you don't need to go sweary and all. Thank you.

Second : Morphs use a unique ID to work. Which brings us to the most problematic situation, duplicated morphs inside of packages or in your local install. A morph cannot work out of thin air. So if it comes back, it means the morph exists somewhere. You need to find it at every location it exists.

Which means finding that morph in every possible var or in your local morphs.
When you'll have done that, you will finally have it gone.

 

[RunRudolf]

There are even 5 built-in foreskin morphs, called PBMFS01, 02, etc. Did you check that these are all set to zero?

 

[nagsugo]

First : please respect people's work. You can assess you don't like something, quality differs from resource to resource, it is true, but you don't need to go sweary and all. Thank you.

Second : Morphs use a unique ID to work. Which brings us to the most problematic situation, duplicated morphs inside of packages or in your local install. A morph cannot work out of thin air. So if it comes back, it means the morph exists somewhere. You need to find it at every location it exists.

Which means finding that morph in every possible var or in your local morphs.
When you'll have done that, you will finally have it gone.

my words went further than my thoughts, sorry for that, I just got really out of me because I tried everything and the more I was trying, the more I was messing up the whole installation, that is totally under my responsibility I know, but you know how it is sometimes, you quickly turn into a chaotic state that leads you to lose control on your own, sorry for that guys.
I think my solution for now will be to reinstall everything from scratch and keep a deep control on everything that is downloaded or added to my new game directory.

Thanks again for the help

 

[hazmhox]

No problem!

Be vigilant with some resources. People pack morphs without really knowing what they do sadly.

 

[nagsugo]

No problem!

Be vigilant with some resources. People pack morphs without really knowing what they do sadly.

do you have an advice on how to deal with ressources that are not really well packed as you said? I mean how to recognize a ressource that could mess up with the clean install?

 

[hazmhox]

It's really hard to say without looking into it.
Some markers can help :

• Unless a very obvious complex and detailled scene in the description/release, look at the var size, if it's big and the scene looks small/basic, it's not normal.
• Size of the var matters, if it's a look/appearance, and the var is massive it's not normal if the look is not supposed to contain textures
• Check amount of dependencies: dependencies are not bad, it's actually how content should be built... but a look with more than a couple dependencies is not normal, a look with 50 dependencies is definitely wrong.