Plugins + Scripts Xtoys Connect 2

Seiryuu submitted a new resource:

Xtoys Connect 2 - Connect your toys via Xtoys. No external app this time.

This plugin allows you send and receive data from Xtoys script via local websocket.
For example you can control your toys from inside the scene or trigger something in the scene with coyote button or motion sensor.
Should work much faster and more reliable then the first. And easier to setup.
Doesn't require external app.
I'll leave the first version cause it allows you to connect to Xtoys running on a different pc or phone. This one only works on the same pc.

[ATTACH...

Click to expand...

Read more about this resource...

Seiryuu updated Xtoys Connect 2 with a new update entry:

Reconnect fix

Small update.
Fixed spikes caused by auto-reconnect (hopefully)
Switched trigger name and trigger button.

Click to expand...

Read the rest of this update entry...

Can this be used to allow an existing script to control an atom in a scene?

Luuube69 said:

Can this be used to allow an existing script to control an atom in a scene?

Click to expand...

What do you mean?
You can send triggers and floats (sliders) to xtoys script that interprets this messages to control your toys (you'll need need to set this up yourself, cause there are infinite number of toys combinations you could use, but It's really simple). Also you can generate some signals from various sensors or tools connected to xtoys and send them to this plugin to activate triggers in VAM.

Where do I get this Xtoys script?

Is it not an external app?

It's unclear how to set this up from the perspective of being a brand new user to this.

Xtoys is an app that is used to control toys. It's pretty simple, but you'll need to install chrome extension and XToys Windows Utilities to connect to VAM.
xtoys.app
Short guide for basics:
Click here and check if your toy is supported. add it to session. (for this guide I added launch and switched it to position mode)
Then add blank script.
Click script name and select edit.
First we need to add blocks that will be used for control and connection. For toy control "Generic Output" block is enough for many cases(for simple vibes and strokers), but you may need something more specialized for toys with multiple parameters (like e-stim boxes). You will also need "Local webhook" block to connect to VAM.


Next we'll need a trigger. Local webhook : sliders will trigger whenever data is received from my VAM plugin (in form of numbers 0-100) and store it's values in temporary variables.

Then we need to add an action. Whenever data is received it will set intensity of our generic output block to value stored in {trigger-sl1} variable. And it's a value of slider 1 in my VAM plugin. Sliders trigger block will receive values of every slider from plugin so you can add multiple actions here with multiple output blocks if you need.
Here is our trigger. Save the script.

Click here to connect script to your toy and add webhook block to session.
Click on webhook. You'llneed to install extension and XToys Windows Utilities for it to work. Follow instructions.
Disable Webhook Id and SSL. Connect. At this point VAM plugin should already be able to connect to xtoys.
Connect your toy. Start script. Done. You can now control your toy with a slider from VAM plugin (with no delay if everything works as it should).
Now you can connect some triggers to control the slider. For example depth trigger of BodyLanguage plugin or Timeline.

Tell me if you need to connect something specific. I'll see if I can help with settings.

Well, after wasting about 2 hours on this, it's just way too complex and has too narrow a use case to actually be useful with VAM.

1. There is no exposed variables within timeline that work for a variable trigger. Hip position, for example, is a quaternion and can't be used. And there's no corresponding linear variable that makes any sense.

2. BodyLanguage doesn't have any exposed variables, either; at least none that I could find working on a variable trigger. All there is is "processID".

So, unless I'm missing something, it's a neat idea, but setup is way too intensive for using across different scenes.

Nice idea though!

ajtrader23 said:

Well, after wasting about 2 hours on this, it's just way too complex and has too narrow a use case to actually be useful with VAM.

1. There is no exposed variables within timeline that work for a variable trigger. Hip position, for example, is a quaternion and can't be used. And there's no corresponding linear variable that makes any sense.

2. BodyLanguage doesn't have any exposed variables, either; at least none that I could find working on a variable trigger. All there is is "processID".

So, unless I'm missing something, it's a neat idea, but setup is way too intensive for using across different scenes.

Nice idea though!

Click to expand...

1. In timeline you just add slider from this plugin as a target and place points corresponding with the animation you need to connect.
2.


And for step animations there are transition action triggers. They are harder to setup but it works.
I wish there was a simple depth trigger plugin but I couldn't find it yet.

Seiryuu said:

1. In timeline you just add slider from this plugin as a target and place points corresponding with the animation you need to connect.
2.

And for step animations there are transition action triggers. They are harder to setup but it works.
I wish there was a simple depth trigger plugin but I couldn't find it yet.

Click to expand...

YES. That's the part that was missing. You should definitely add a use case for timeline on your front page.

I would consider including a very simple demo scene so others can see how it's all wired up.

Nice work!

Seiryuu said:

1. In timeline you just add slider from this plugin as a target and place points corresponding with the animation you need to connect.
2.

And for step animations there are transition action triggers. They are harder to setup but it works.
I wish there was a simple depth trigger plugin but I couldn't find it yet.

Click to expand...

Now, the last thing that we need is to map the actions of a controller on timeline, e.g. "Hip", to the plugin's trigger values.

Can you come up with a way to read a timeline (a pulldown menu populated by the current controllers holding data), and then just copy/paste those over to this trigger (normalizing from 0-1)?

Otherwise, we're stuck manually creating new animations from scratch.

The vision here should be plug-and-play. I add this to the person atom, and click a few buttons. "add to timeline" with some pulldowns." "sync with timeline" with pulldowns. Done.

As it stands, still very cool, but I'm not going to take the time to create another whole set of values for a new controller in timeline.

I know that KM and CMC have figured this out in their stuff, so it's possible. Just no idea how.