Log in
Register
  • Hi Guest!

    We have posted a new VaM2 dev log on Patreon, starting a monthly cadence of written progress updates between Beta releases. Highlights include the new Gizmos System, Selection Carousel, and Modes System with Context-Specific Editing. Beta1.2 is 15 of 21 items complete.

    Read the full post on Patreon, or follow progress on the public Trello roadmap.
Body Triggers (Touch and Gaze)

Plugins + Scripts Body Triggers (Touch and Gaze)

Download [<1 MB]
Overview Updates (3) Reviews (5) History Discussion Dependency Usage (3)
I'll take another look, but it was working for me the other day. It is possible there's something conflicting so if you could send along a sample scene or setup, I can see what's going on.
 
Can I bother you with a feature request? In the plugin log, the information about the object that made the collision is displayed.
Could you make this info accessible for further processing, maybe as a string variable?
In any case, thank you for making this plugin!
 
BossG said:
Can I bother you with a feature request? In the plugin log, the information about the object that made the collision is displayed.
Could you make this info accessible for further processing, maybe as a string variable?
In any case, thank you for making this plugin!
Click to expand...
I'll try and look into it. I"m trying to finish up a huge scene and will take a look after. If by chance I seem to forget, feel free to nudge me again. :)
 
@BossG Can you take this for a spin and let me know if it now does what you were asking?

Here's a summary of the changes:
BodyTriggersUI.cs — two new lines after lastTriggerLog is created:
  • RegisterString(lastTriggerLog) — makes the existing display log readable by other plugins as storable "lastTriggerLog"
  • Creates and registers a new JSONStorableString("lastTouchingAtom", "") — a clean, dedicated atom-name string
BodyTriggers.cs — added the lastTouchingAtomJSON field declaration, and sync it alongside the plain string at both write sites (ENTERED and HIT paths).
GazeSystem.cs — same sync at all three gaze write sites (Stare/Gaze/Glance).

Now in VaM's trigger editor, another plugin can read two storables from BodyTriggers:
  • lastTouchingAtom — just the atom name (e.g. Person#2) or (gaze) for eye contact events — clean for downstream logic
  • lastTriggerLog — the full formatted string with timestamp and body part (e.g. [10:23:45] tease → chest\nby: Person#2) — same as what the log panel shows
 
MetalVam said:
both vr and desktop.
Click to expand...
I got this plugin back up on the rack and in both my local version and the packed VAR, the look at options are working for me and I can't reproduce your issue. My only suggestion would be to send me a sample scene so I can take a look at how you have it set up.
 
Plugin with high potential! May I ask that we can have onStart and onEnd triggers for every body part? This will be useful governing states, right now I can only do reactions. I would also appreciate gaze / stare regions like legs, butt, feet as they could have contextual meaning or just being relevant as semi-sexual zones (like thighs).
 
VAMFantasy said:
Plugin with high potential! May I ask that we can have onStart and onEnd triggers for every body part? This will be useful governing states, right now I can only do reactions. I would also appreciate gaze / stare regions like legs, butt, feet as they could have contextual meaning or just being relevant as semi-sexual zones (like thighs).
Click to expand...
Gaze additions should be easy enough. I'll look into it. Butt should already be there, it's called Glutes I think. I'll also look into the triggers, those should also be easy enough to add.
 
Dragontales updated Body Triggers (Touch and Gaze) with a new update entry:

More gaze zones and new tab for zone touch duration state triggers

New Gaze Zones (Stare Triggers tab)
  • Thighs — player looking at thighs or shins
  • Butt — player looking at the glutes
  • Feet — player looking at feet or toes
  • Each new zone gets the same three levels as existing zones: Glance, Gaze, and Stare
Contact Triggers (new tab) @VAMFantasy
  • On Contact Start — fires once when something first touches a body zone, regardless of how hard. Even a feather-light...
Click to expand...

Read the rest of this update entry...
 
So I finally managed to trigger the GAZE feature, but I have to move the male and female atom right next to each other.
Can I request a feature of Glance distance? or maybe you can extend the distance more for the trigger?
Thank you for all your hard work.
 
MetalVam said:
So I finally managed to trigger the GAZE feature, but I have to move the male and female atom right next to each other.
Can I request a feature of Glance distance? or maybe you can extend the distance more for the trigger?
Thank you for all your hard work.
Click to expand...
I didn't think there was a distance threshold, but will look into it. I do know it's precision is a bit tight, like the VR or Desktop needs to be aimed right at central point of the bodypart. I do like the idea of a distance threshold though so if you're farther, it won't actually trigger. And I'll see if there's a way to expand the target size for easier triggering.
 
Awesome plugin, this is much more flexible compared to the built in system. If I may make a request. Would it be possible to add a touch duration threshold to the "Touch Duration Triggers" so that the actions only trigger if a used specified threshold of X seconds is registered?
 
cnorton76 said:
Awesome plugin, this is much more flexible compared to the built in system. If I may make a request. Would it be possible to add a touch duration threshold to the "Touch Duration Triggers" so that the actions only trigger if a used specified threshold of X seconds is registered?
Click to expand...
hi. Yes. that should be easy enough. I'll add it to my list of updates.
 
Something not easy or impossible to fix:
I trigger i.e. a Voxta event on touches, works very well. Then I save the preset with all my triggers, also ok. Loading this preset in the same scene works like a charme.
But if you create another scene, add this and Voxta as plugins again and load the preset, it will fail if the Voxta plugin is on another position in the plugins list.
In the original scene Voxta is i.e. "plugin#5_Voxta". If it is "plugin#1_Voxta" in another scene, the triggers are broken because your plugin looks for slot 5.

Original scene order of plugins:
1778740341588.png


New scene, different order, triggers are broken after loading preset, because the receiver has changed:
1778740497082.png


1778740593953.png
 
You must log in or register to reply here.

Similar threads

Spacedog
Plugins + Scripts Easy Gaze - Finger and Kiss Motion
Replies
17
Views
6K
ScrunglyBungus
S
T
Plugins + Scripts Triggers: Inputs and Collisions
2
Replies
25
Views
3K
TBD
T
H3
Scenes touch her!
Replies
3
Views
2K
Virtyourmate
V
N
Scenes Erica's Touch
Replies
7
Views
3K
Edgeandgo
E
Acid Bubbles
Scenes Chloe Touch (simple touch reaction scene)
Replies
11
Views
3K
Acid Bubbles
Acid Bubbles
Back
Top Bottom