Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for device with mutliple outputs of same type #158

Open
Tracked by #164
Random-Cow opened this issue Dec 11, 2023 · 2 comments
Open
Tracked by #164

Add support for device with mutliple outputs of same type #158

Random-Cow opened this issue Dec 11, 2023 · 2 comments

Comments

@Random-Cow
Copy link

What is an example of this type of device? (Provide link to iostindex.com entry or product page.)

Devices like https://iostindex.com/devices/Satisfyer/Rotator%20Plug%202_/ have multiple vibrator outputs (iostindex is partial wrong for that device, buttplug.io recognizes the rotator as a vibrator as it only moves in one direction).
Currently only one of the outputs works, it would be nice if multiple where supported, with individual settings per output.
Don't know that would translate to in-game, maybe switch after x amount of time, orgasm, by probability, or allow for both or single usage.

Do you volunteer to test this feature if it gets implemented? (I take no responsibility for accidents.)

Yeah, sure. I have the device that I linked and can test it.

@Sauceke
Copy link
Owner

Sauceke commented Dec 11, 2023

Currently only one of the outputs works

Can you turn on the other output in Intiface?
LM is supposed to use all vibrator features in sync, so either that's broken, or the Buttplug integration is.

Don't know that would translate to in-game

I do. We need phase mapping, group role mapping, and body part mapping for each feature. And a toggle to hide all that clutter. I'm actually going to need this for something I'm working on, so thanks for reminding me.

@Random-Cow
Copy link
Author

Can you turn on the other output in Intiface?
LM is supposed to use all vibrator features in sync, so either that's broken, or the Buttplug integration is.

Now that you mention it: Yeah the features work in sync, it's just not that noticeable because they are in perfect sync 😄 . So it works as intended.

I do. We need phase mapping, group role mapping, and body part mapping for each feature. And a toggle to hide all that clutter. I'm actually going to need this for something I'm working on, so thanks for reminding me.

Not that it was intentional but no problem 😉 .
So the better name for the issue would be, allow individual settings for each features, or something like that.

@Sauceke Sauceke mentioned this issue Feb 26, 2024
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants