VAMLock

hazmhox

Moderator
Featured Contributor
Messages
1,511
Reactions
7,322
Points
173
If I understand this plugin correctly, should I be able to take an existing story such as 2069 or the MeshedVR Apartment scene, and from the start lock the person look to that of my own choice and the same person will remain throughout all subsequent scenes. Is that correct?

Maybe I'm misunderstanding something in the documentation, but I haven't managed to have this work successfully for me.
 
On 2069 you should be able to do this, I'm not sure that the apartment scene is working the same tho.

You could load a scene, lock parameters on the first scene and then have all the subsequent scenes with the same girl / guy. The merge load has to keep the same character name.

If you have troubles with 2069 i'd be glad to know what you do exactly, it should be usefull to improve the plugin :)
 
hazmhox submitted a new resource:

VAMLock - Preset manager locking system for person atoms



Read more about this resource...

Yo gj with the plugin however I'm too dumb to make it work.
If I want to add it to a person in an existing like the 2069.
Select the character > add the plugin and check what to save then do this from your guide? or i need to create the button and do all that too?

All you have to do is :
- Open your favorite scene, look, or story.
- Select your female character
- Click on the Appearance presets tab
- In the preset name field, type "vamlock-demo-custom" (without the quotes). If the field is not empty, clear it then type it.
- Click Create a new preset and DON'T save the scene. Go back to the main menu or load VAMLock demo.

Also I can't find the demo, and given open the package from the plugin download.
sorry again but thank you anyway
 
This plugin sounds amazing but I haven't been able to make it work. I've tried it in all of SCAMP's andrea/milf scenes as well as a few Sapuzex scenes without success. I add the plugin to the female, i make sure morphs, skin, appearance, clothing, hair, and plugin are checked, then advance to the next scene, and her entire appearance is reverted (she also loses the plugin). What am i doing wrong?

The demo scene is the only story i've seen it work.

Hazmhox perhaps you could try some of the community scenes like the ones listed by myself and overkooked to see what the problem is.

I've been wanting a plugin like this for a long time so I am happy to help in any way to get it working!
 
Last edited:
Ok I think I found out why you have these issues. This is kind of my fault, I've made a documentation that is "creator focused" not "user focused".

@floralis, in your case, forget the custom look, this is only for demo purpose for creators, and in the case of VAMLock's demo :)

Anyway, in both your cases @floralis and @itsgus, when you check the checkboxes you have to understand that this is an automatic feature. It means that it will work only at the load of the scene. What the plugin enables is the creators to have a way to switch between appearance in a start scene.

If you just want to experience a scene with a custom girl, you don't even need the plugin, you can just switch the appearance in the first scene, check all the checkbox you want in "Preset lock overview" in the "Control and physics 1" tab, and play through the scene.

But... if you are dedicated, and you want to enjoy a specific scene with a few of your favourite looks... you'll have to build your own menu to swap appearances based on the plugin.

It makes me think I could produce an extension of the plugin that would allow you to easily integrate an "appearance swapper" for players and not only a plugin restricted to creators. Is that something you'd like ?
 
Another nice plugin from hazmhox !
Was wondering why you use a .cslist and a /src subfolder with your plugins when there's only one script to load.
If plugin contains a single script why not just load the .cs directly ?
 
Thanks @VeeRifter :D
That's just for evolution / improvements sakes.

I have some kind of OCD's when it comes to maintainability / compatibility. With the cslist made at the beginning, I know that if someday I want to improve drastically the plugin or add a ton of features, I don't have to break the compatibility with old versions and explaining "well, in you old scenes, replace with the new version" or "you were using the .cs, now use the cslist".

It's easy for me to upgrade, and easy for users because nothing will change in the potential future updates.

And well... it's text so, not really a problem with optimization. I'm more drastic when it comes to shaders / textures / sounds and content that costs memory and disk space ;)
 
Back
Top Bottom