Comments

Log in with itch.io to leave a comment.

Heya! Just a quick bug update regarding Lovense toys with dual vibration motors - the functions are only mapping to the first/default motor. I looked into the file and it seems they're saving with a blank string instead of an identifier.

No clue if this project is still being worked on, but I'd love to be able to use both sides of a toy with this!

Thanks, sadly I don’t have one with multiple motors to test with. When you add a vibration node are you able to see multiple choices? Sometimes the functions returned from buttplug.io don’t always have names attached to them.

I am having issues getting the triggers to work. I really don't know what I am doing. Do you have a guide somewhere on how to operate your app?

No real documentation, sorry, it was never that serious of an endeavor. But the basic idea is to think of your trigger flow going left to right as a series of connected nodes.

Always start with a yellow trigger which is something that comes from the Twitch connection, a text value or a bits donation. Afterwards you can add an action node to the grid, usually to the right of the trigger (in practice, it doesn’t matter but makes for easier visualization). Say you pick vibrate, pick your device, the feature if needed, and set a duration and intensity.

Now you need to connect the nodes together to link them and complete the flow. So, click the right-most dot on your trigger, it should be yellow, and connect it to the left-most yellow dot on the action. Now the trigger knows that when it’s activated, to do this action. You can also do multiple actions all coming from the same trigger, or you can chain actions together. You also treat media nodes like actions in this same way.

Value generators are used to fill in values for the blue connectors. Either a constant value or a random one at the time it’s triggered. This just lets you manage your flow a bit better.

Pattern Generators load patterns used in the pattern editor, and both of their green connectors link to the blue duration/intensity connectors on actions and feed those values into the action, creating your saved pattern.

Hope that all makes some sense!

image.png

(1 edit)

This does help a bit. I am still confused on the increments for duration and intensity (especially when I connect a Blue box to the intensity node. Is the Duration values in Seconds? and when I use the Blue boxes for intensity, are they precents or values?
Also for "Users" in the text trigger box, if that is left blank will it default to everyone being able to trigger it? or do i need to put the intended channel I want the trigger used on?

Duration is in seconds. Intensity is a value between 0 to 1 (basically off through max power, so 0.5 would be half power).

Users acts as a whitelist for who can activate that trigger. If blank, everyone will trigger it, otherwise give it a comma-delimited list of users and only they will trigger it (User1,User2,User3)

Hi does the lovense premium sex machine and mini sex machine work with this app? I want to use this with those specific toys but don't know. 

I haven't bought the toys yet so just checking in thank you for this beautiful app!

They should work fine as buttplug.io supports those without issue. I don’t think anyone has tried this app with those machines specifically yet, so if you have feedback or suggestions just let me know!

Hello. I really like the concept of this app. However, I get a connection error every time I click on connect. It did work the first time I connected it though, but not the second time. I'm using Intiface Central which has my Lovense product connected to it. Any help?

When is the error occurring? When trying to connect to Intiface, or trying to connect to Twitch?

I just tested it here and encountered no errors unfortunately. I was able to connect to Intiface, get my toy and then connect to Twitch successfully. Have you downloaded the latest version here?

Hello sorry for the late reply.

Apparently it got fixed when I manually typed "localhost" as the server name instead of leaving it blank. It's a little bit odd because it did work the first time without me setting up any name for the server, since I thought it would be localhost anyway if left it blank. This did happen after I tried to change the server name once and then left it blank afterwards. So I believe if I never really tried to change the server name at all from the beginning, I think it would have continued working like nothing.

Yea it should have a value in it. Try using 127.0.0.1 as well to make it connect faster, bug with the engine.