• Hi Guest!

    Please be aware that we have released another critical security patch for VaM. We strongly recommend updating to version 1.22.0.12 using the VaM_Updater found in your installation folder.

    Details about the security patch can be found here.
Make it up

atani

Invaluable member
Wiki Contributor
Featured Contributor
Messages
3,152
Reactions
3,032
Points
143
Website
atani12.gitlab.io
atani submitted a new resource:

Make it up - I'm so sorry, Clint!

View attachment 405484
Kate got cocky.
She tried to bring down a crime syndicate all by herself,
and ultimately had to be rescued by Clint.
Now Clint missed his flight to get home for Xmas with his family.

She needs to make it up to Clint...
somehow...

I'm so sorry, Clint!

If you saw a show that this scene appears to be inspired from, the you hit the...

Read more about this resource...
 
I believed the male cum sound is missing in the var file.
I wonder if the male and female cum sound can play during orgasms.
From my experience, it's either or, since both sound tend to not mix well with each other from two different atoms.
 
I believed the male cum sound is missing in the var file.
I wonder if the male and female cum sound can play during orgasms.
From my experience, it's either or, since both sound tend to not mix well with each other from two different atoms.

Do you mean the orgasm moan? Asking because there's a cumflation fill sound too, but only active when cumflation is on.
The orgasm moans are triggered with VAMMoan, being the male on VAMM 1 and the female on VAMM 2. As the source is the head audio of each person, they should work simultaneously without any problem.
The sounds come from VAMM and they are triggered based on the plugin's "will", but the result audio, especially with the female, will vary a lot and sometimes not be noticeable or be so delayed a following moan type sound will take over.
I'll take a look at the triggers to make sure there's nothing missing, mistakes may exist.
 
Do you mean the orgasm moan? Asking because there's a cumflation fill sound too, but only active when cumflation is on.
The orgasm moans are triggered with VAMMoan, being the male on VAMM 1 and the female on VAMM 2. As the source is the head audio of each person, they should work simultaneously without any problem.
The sounds come from VAMM and they are triggered based on the plugin's "will", but the result audio, especially with the female, will vary a lot and sometimes not be noticeable or be so delayed a following moan type sound will take over.
I'll take a look at the triggers to make sure there's nothing missing, mistakes may exist.
i believe the moan audio is from the "story director" (sorry, i dont remember the actual name) plugin # 2 from "CONTROL SEX" .
it's fine though, i just manually added the male cum sound from your other pack.

as for the female orgasm, my intention is to manually add in a "pee" sound trigger with the female moan via different plugin (AUDIO MATE), it worked out so far.

Also, I'd like to make a request if possible.
I'd make changes to the body part position (ex: head, hip, arm) every time you have major update in TIMELINE.
Is there a way for me to update the scene new feature (for future NEXT update) and keep my version of the timeline plugin? (usually take me hours to make all the position adjustment to my liking 😅)
Thanks again for all your contribution to the VAM community.
 
I can assure you the orgasm sound comes from VAMMoan and the trigger for that is in VAMstory director.
I made it this way on purpose, where it's not a direct trigger in the Timeline animation and instead it's piped through a director trigger to wherever one wants, in this case VAMMoan. This makes it much easier to change things, like you did, to use a different sound source than the one I chose without needing to go to Timeline and make changes there. And as all orgasm calls for the 9 sex animations go to this single point, they are all updated to the new sound.

In ControlSex you have another Director plugin called "Timeline ...". Those triggers act as a relay between Timeline triggers and whatever else scene triggers you want. You can add or remove triggers there for different sounds and whatever else you want for when the Timeline animation triggers that action.

As NEXT is a scene, when I update it, everything in it is updated, even if I don't make changes to some parts. If you make changes to the NEXT template or a scene made from it, and save it on your disk, then that's a new scene and only available to you. If I push a update it will not affect your locally saved scene.
If say I push a update to NEXT or MIU (this scene) and you want to also update your locally saved and customized scene to the updates, then you're on your own. You'd need to replicate the changes, whatever they may be, to the updated NEXT. Animations in Timeline can be exported and imported relatively easy, other changes will depend on what they are.
 
Hello, please tell me why when I launch a scene and select a pose, the animation does not start?
 
Hello, please tell me why when I launch a scene and select a pose, the animation does not start?
Do you mean you click on one of the buttons in "Animations", it fades out and in, and the persons are not moving? They do if you haven't set the checkbox to "frozen/pause animation" in the VaM UI.
If instead you mean when you click on "Stand pose", "Flat pose", "Sit pose" and "Reset" and they just stay in a pose, well, that's what a pose is.
 
Do you mean you click on one of the buttons in "Animations", it fades out and in, and the persons are not moving? They do if you haven't set the checkbox to "frozen/pause animation" in the VaM UI.
If instead you mean when you click on "Stand pose", "Flat pose", "Sit pose" and "Reset" and they just stay in a pose, well, that's what a pose is.

2024-12-24_19-36-06.png
for some reason it doesn't respond at all to pressing buttons(
 
Wow, that's some messed up collision problems.
The message log chatter from DiviningForeskin is fine, while for Postmagic is related to your session plugins as the scene does not use it. You should check your error log too, it's often much more important to know what could be wrong.

As I see your screenshot I notice something that will absolutely compromise the scene, you're using a old VaM version. I mention in the resource description that you need 1.22.0.3 or higher because it's a requirement for the plugin vamstory.
There's no need for you to try any of my NEXT-based scenes and maybe a couple of older ones, they won't work properly until you have a updated VaM.
 
Wow, that's some messed up collision problems.
The message log chatter from DiviningForeskin is fine, while for Postmagic is related to your session plugins as the scene does not use it. You should check your error log too, it's often much more important to know what could be wrong.

As I see your screenshot I notice something that will absolutely compromise the scene, you're using a old VaM version. I mention in the resource description that you need 1.22.0.3 or higher because it's a requirement for the plugin vamstory.
There's no need for you to try any of my NEXT-based scenes and maybe a couple of older ones, they won't work properly until you have a updated VaM.
yes, you are right. After the update everything started working)
 
Back
Top Bottom