Just bought VacuScripter… I have about 7 different einseo/joyhub toys and they normally all worko through intiface… can get them do anything on here. does this just not work with those?
1 Like
Thank you for purchasing VacuScripter!
I’m sorry to hear you are having issues with your devices on VacuScripter, hopefully we can get your issue resolved.
The buttplug.io logic in VacuScripter is coded for buttplug device sendVibrateCmd and device SendLinearCmd.
Vibration/Rumble devices:
await device.SendVibrateCmd(new { 0, intensity }); //Motor 1
await device.SendVibrateCmd(new { 1, intensity }); //Motor 2
Linear devices:
await device.SendLinearCmd((uint)durationMs, position);
If the device pairs with VacuScripter and is either a vibration device or a linear device, it should function normally.
Do the devices successfully pair with VacuScripter?
VacuScripter was primarily created to give users the ability to operate the VacuGlide 2 while using their VR headset since the provided website interface that came with VacuGlide 2 did not provide a clean way to accomlish this.
I added buttplug.io functions so that I could attach a modified gamepad to act as additional vibration for the VacuGlide 2 while in use.
The linear functions I added later since I was already adding vibration function for the buttplug.io devices.
Then I decided to implement buttplug.io sever so devices could pair directly with VacuScripter instead of using Intiface Central as middleware.
However, because buttplug.io removed C# buttplug server starting in v3.0.0 of the nuget package, I implemented v2.0.6 because it still has the server implemented which allows VacuScripter to be able to pair devices directly to VacuScripter rather than rely on Intiface Central to be middleware for VacuScripter like it was in previous versions of VacuScripter.
Intiface Central as middleware for VacuScripter caused it to stop working after an update to Intiface Central and instead of causing myself more headaches chasing after continued compatibility with Intiface Central as middleware, I decided it would be better overall to simply implement buttplug.io server directly into VacuScripter.
Hopefully this is a simple fix to get your devices working, but the possibility exists that because I had to implement an older version of buttplug.io into VacuScripter, your devices may not work with VacuScripter directly.
I’m about to release update v1.0.33.0 for VacuScripter
1.0.33.0
- More adjustments to Auto Suction/Auto Pump function
- Update to VacuGlide 2 not starting reliably with Video/Script (VacuGlide 2 should now start more reliably)
- Fix for filenames when using XBVR and Hereshpere (reported by ingo7901)
I think this should resolve your issue with XBVR changing filenames and causing VacuScripter to be unable to find the scripts to load while using Heresphere.
I need to test VacuScripter one last time in a full session for the other fixes I have implemented and if all is good, I wlll submit it for certification in the Microsoft Store.
The new version of VacuScripter is live, v1.0.33.0.
1.0.33.0
- More adjustments to Auto Suction/Auto Pump function
- Update to VacuGlide 2 not starting reliably with Video/Script (VacuGlide 2 should now start more reliably)
- Fix for filenames when using XBVR and Hereshpere (reported by ingo7901)
Any plans on supporting devices other than The Handy, like the OSR2 or The Autoblow AI Ultra?
1 Like
Hmm, I’m not opposed to it, but I don’t have the other devices so it would be like making a cake with ingredients I’ve never tasted.
As far as the Autoblow AI Ultra, I am using the Autoblow API for communicating with the VacuGlide 2. I believe it was originally written for the Autoblow AI Ultra and then double purposed for the VacuGlide 2.
Have you tried connecting the Autoblow AI Ultra to VacuScripter?
If so and it didn’t work, then I’ll need to investigate what needs adjusted to allow it to work (I’m sure it wouldn’t be very much that would need to be changed).
For the OSR2, I would need to know how their API works.
The OSR2 uses Tcode-v03 through serial COM ports. After looking at the buttplug.io developer page, it seems that adding the OSR2 to the device configuration file will allow it to connect. However, because different users may have different COM ports in use at any given time, they will need a way to modify these settings. To fix this, you could either give users direct access to the configuration file or implement a feature within the app that allows them to change these values easily, which could also allow users to add devices other than the OSR2. I have left an example of what my device config looks like. As for AI Ultra, I will need to test it when I have time.
1 Like
You’d need to look into implementing the tcode protocol over usb serial communication. GitHub search the keywords and you’ll probably see a bunch of good examples.
OSR2, SSR1, etc are derived from TempestMax, T-code is the protocol it speaks, a spin off from g-code, a protocol used for CNC machines.
There should be a bunch of good implementations out there that can be found with a bit of GitHub searching.
1 Like
Thanks, I’ll look into it ASAP.
Thank you, for the link. I will put this on my priority list.
1 Like
FYI I’ve solved the issue with pausing the video/script and VacuScripter becoming desync’d from the VacuGlide 2, which caused you to have to toggle play/pause a few times to get them to sync back up again.
I just tested and seemed to be resolved with the new update I’ll be releasing soon.
v1.0.34.0
- Update to eliminate VacuScripter becoming desync’d from the VacuGlide 2 when you pause the video/script
I’ve begun looking into support for the OSR2 and similar T-Code v03 devices over USB.
cc: @amango134
I have an initial TCode OSR2 integration update I’ll be releasing soon.
v1.0.34.0
I need to test to make sure I didn’t break anything when I added the OSR2 / TCode functionality but as soon as I confirm everything is ok, I’ll submit it for certification in the Microsoft store.
1 Like
Update submitted for certification in the Microsoft Store.
v1.0.34.0
- Update to eliminate VacuScripter becoming desync’d from the VacuGlide 2 when you pause the video/script
- Added Support for OSR2 (first attempt, will need refined through user testing)
v1.0.34.0 is live in the Microsoft Store.
v1.0.34.0
- Update to eliminate VacuScripter becoming desync’d from the VacuGlide 2 when you pause the video/script
- Added Support for OSR2 (first attempt, will need refined through user testing)
The OSR2 connects fine, but running scripts in the app doesn’t work. Using third-party sites like FapTap works a little bit, but there is almost zero movement.
1 Like
Good info, thanks!
This tells me that the values for movement need a multiplier.
In order to make things efficient and easier to troubleshoot, I direct all commands to a central background task that handles distributing the speed, position, and vibration values for all devices that are connected. Those values are base values and since each device translates those values to its movements differently, a multiplier is needed because they have different scales.
I’m sure it was receiving commands from the script if it was receiving commands from FapTap but the script commands were being interpreted as exteremely small values compared to FapTap…so it appeared the script wasn’t working but most likely it just was being interpreted as such small values the device wasn’t actuating.
I will need to increase the scale of the position value before sending it to the OSR2. I had to do something similar when testing the Handy movements.
I will make an adjustment and push the update.
Getting it connected was the hurdle, now it just needs adjusted.
1 Like
v1.0.35.0 submitted for certification in the Microsoft Store
1.0.35.0 - Update to add multiplier for OSR2 values
NOTE
I incremented it slightly… I don’t want to push values that will be too extreme for the OSR2 since I don’t have one to do real time real world testing on here, I have to kind of guess at the values and let you guys test it. Be aware when testing it, if it starts to do some crazy movements, stop it immediately and then let me know and I’ll have to adjust the values more.
Once it is live, I’ll let everyone know.
1 Like
v1.0.35.0 is live in the Microsoft Store
Change log:
1.0.35.0
- Update to add multiplier for OSR2 values
Please test this with the OSR2 and let me know if the values made a difference.
Haven’t heard back from you and wondered if you had a chance to test the update.