Plugins + Scripts Body Triggers (Touch and Gaze)

[BossG]

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!

 

[Dragontales]

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!

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.

 

[Dragontales]

Dragontales updated Body Triggers (Touch and Gaze) with a new update entry:

Small tweak to read collisions by external triggers

Requested function added - Log information accessible via external plugins - @BossG

Read the rest of this update entry...

 

[Dragontales]

@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

 

[Dragontales]

both vr and desktop.

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.

 

[VAMFantasy]

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).

 

[Dragontales]

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).

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]

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...

Read the rest of this update entry...

 

[MetalVam]

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.

 

[Dragontales]

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.

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.

 

[cnorton76]

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?

 

[Dragontales]

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?

hi. Yes. that should be easy enough. I'll add it to my list of updates.

 

[Saint66]

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:

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

 

[cyberdelique]

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:
View attachment 591215

New scene, different order, triggers are broken after loading preset, because the receiver has changed:
View attachment 591221

View attachment 591227

that's unfortunatly a VAM issue, all you can do is edit the json file, like copy from scene A to scene B and modify the plugin number in the json. it works but a pin in the butt. I would love to see a tool that manages that

 

[cyberdelique]

I'm also unable to trigger the gaze system, should we see something in the trigger log?

 

[cyberdelique]

I'm also unable to trigger the gaze system, should we see something in the trigger log?

Mhh nevermind, I didn't looked close enough After further inspection, this is a great plugin !

 

[FreeMaster69]

Will you be adding end triggers to glance/gaze/stare section in the future? I can only create start triggers.

 

[vamjungel]

In fact, gaze or glance cannot be seen in the trigger log

 

[BossG]

Dragontales updated Body Triggers (Touch and Gaze) with a new update entry:

Complete Rewrite — Full Plugin Independence



Read the rest of this update entry...

Sorry for reporting back so late, vacation and work got in the way.

The update works fine for me and the extra features are highly appreciated, as well.
Thank You very much!

 

[Dragontales]

Dragontales updated Body Triggers (Touch and Gaze) with a new update entry:

bugs and fixes

Body Triggers v5: Fix Update​

No more stuck touch triggers

• Fixed: turning off Enable Touch Triggers while a body part was still being touched left its trigger stuck "on". Contact Start fired, but Contact End never did.
• Switching the master toggle off now closes every active contact cleanly.
• Turning off an individual body part's toggle now releases just that zone.
• Fixed: a contact could stay latched if the...

Read the rest of this update entry...