Haha, that would be a lot of data if you stored the target positions every frame. But I think I get what you mean. My next plugin will keep track of what bodyregions you have looked at recently and does some interesting stuff with it
The face is ddaamm estel. Sooner or later I'll release a scene and I will try to include her. But I don't have experience in this and I don't know what I have used for her, maybe some things are paid.
I've posted a link to the demo scene from FreeTheLegs in the discussion. It's just the .json but you can try and see what you get from there.
I already noticed the typo in 'SetInteractble ', but it works like that for me (and others). What VAM version are you running? Maybe an update will fix it.
Running version 1.20.77.9
Basically everything you said is already done
May be too old.
Yep, this one's on me. I just updated to current and it works fine now. Thanks!
But to go a bit more in detail what I have:
Oh WOW ok you're my hero. I think when you release that, it will be one of the best plugins created for VAM then, honestly. I'm glad you're so thorough with your work too. Take your time! Also, you should start a Patreon so even if you want to release things for free, we can still support the time and effort you're putting into these things.But to go a bit more in detail what I have:
Every body region like Breasts, Ass, Thighs, etc. has it's own sub folders OnTouch, OnSlap, OnLookAt where you can put an arbitrary number of sound files in. These get played randomly if the specific event happens. OnTouch is further separeted into OnEnter, OnStay and OnExit. This is not only useful for caressing events, but also for the orifices
You can use a local file system with loose files or, how I do it, package them in an assetbundle for way faster load times and no scene clutter. You can also set up different voices/personalities you can choose from.
But as you can imagine it is really hard to make everything configurable by the user. While most of it is done, I have to get back into the project after the distractions of ShakeIt and so on. And there are still some things to take care of. For example it is not easy to filter out the collisions you don't want to trigger something. Like ass on couch, differentiate between self collision and collision with others or the player and so on. Imagine the girl occasionally touching her leg and she reacts with "Ohh, I love it when you toch my leg". So there really should be way more folders for every possible occasion... This gets complicated as hell. So don't expect me to release this tomorrow.
I have tried deleting the plugin and the LightSettings save file and redoing it all, but that didn't work. It also likes to randomly default back to base light settings instead of loading my saved light config. Is there any way you could add a load light config button next to save light config as backup if it doesn't load? It is a pain to manually set everything again.
Thanks, especially for the M-tip! I do know more or less what causes it, but I couldn't reliably reproduce it. I'll try some more later.
So you load a scene which has the plugin on an atom or as a scene plugin? Because LateRestoreFromJSON should only be called while loading a scene (or on VAM startup if you have it as a session plugin). Could you please go a bit more in detail what you do? Do you also have it installed as a session plugin? Does the loading work, if you just reload the plugin?
A second question and probably a dumb one, but does this work in VR?Haha, that would be a lot of data if you stored the target positions every frame. But I think I get what you mean. My next plugin will keep track of what bodyregions you have looked at recently and does some interesting stuff with it
Yes it does!
I'm on it. The preset system will also come soon.
