I just updated to Chrome 61 on my Debian box, and whatever bug was holding up bluetooth usage on Chrome on Linux is fixed! The Fleshlight Launch now works fine with syncydink in local connect mode! Also tested the Lovense Hush Plug, it works too. I think this puts Linux Chrome in feature parity with macOS and Android for buttplug-js
Took a bit of a diversion from buttplug/syncydink over the past few days.Having finally gotten sick of reading all of the reports of people having their Fleshlight Launch bricked by firmware updates, I spent the weekend writing my own firmware loader. I now have a node.js/typescript based loader that can load Launch firmware (and as soon as I get one, Pearl 2 firmware) from desktops. I'll be porting this to work in Chrome, so that we can hopefully fix firmware loading from Android, which is usually where problems crop up.
I'll be writing a full blog post about the internals of firmware loading, but that may be a bit. Some fun facts I learned along the way:
New dev log post. Nothing too exciting since I usually post most of this kinda of info to patreon for patrons in real time, but hopefully helpful
Just a heads up since Lovense Hush toys seem to be pretty popular.We had a user show up on the Discord today reporting a Hush toy that would not connect to the Windows Buttplug App Suite. They had direct ordered it and received it sometime last week (last week of August 2017).
Turns out that Lovense is loading new firmware onto toys, and also changing their device names and service IDs. We've updated the Windows Buttplug Server for this new device, and CI Builds of 0.1.0.464 or later should work. I'm hoping to get support into buttplug-js this evening.
Yes ok I may have a slight chat protocol hoarding problem.Invite Link: https://discord.gg/BGNjpbf
For Patrons: If you join the discord and would like to have the special Patron role, just message me and I'll get that set up.
Just posted a new Dev Log on the blog! Now that we've got releases out, going to try to get back into a better writing cadence so we're not developing in a black hole.Right now, we're in the middle of the black hole, try to develop *out *of it. Buttplug was in development for so long and has so little documentation that it's hard for users to figure out what to use where, and what works on what platforms. This became very evident when I posted about syncydink on a couple of forums over the weekend and was met with a lot of either silence or "???" in response. I'm going to be spending the next while trying to fix that somehow. This may end up in me begging for tech writing help on twitter. :)
A couple of weekends ago, I got the stupid idea of "Hey. Rez Infinite came out. Wouldn't it be funny if I could make it work with the original USB Rez Trancevibrator?"48 hours and a lot of education about DLL Hooking later, it was done. We now have a way to control sex toys via Gamepad vibration command on Windows, with no modifications required to the game in question. This works with any game that supports XInput (XBox Compatible) gamepads, and I'll be extending it to work with vibration commands to Oculus/Vive controllers soon. Also, this currently only works with toys that vibrate, as that's all I've had time to implement. This certainly can work with the Launch, Vorze, and other toys, I just need to sit down and figure out the translation algorithms to do so.
I've now run it by a couple of testers, and it seems to work, so I'm releasing it only to Patreon members first. I'm planning on making a Buttplugin' With qDot video about this and releasing it to the general public next week, but figured it might be fun to have more people trying it with games first.
I've just updated the Syncydink tutorial, because thanks to some nudging from a new patreon on here, I just finished some fixes and we now work on Android Chrome with VR and no extra software/apps required
Basic steps:
As of yesterday, I managed to get the javascript web technologies version of the Buttplug Server done. This is now integrated into Syncydink:https://buttplug.world/syncydink
If you go to the site now in Chrome (and yes this requires chrome, for WebBluetooth, and you will need to use https), then go to the Buttplug tab and click on "connect local", the "Start scanning" button now triggers a search for devices.
We're in Vice
This article is a great overview of our goals with https://buttplug.io!