I find Keon bluetooth doesnt have the farthest range, so maybe try a usb extender cable for your bluetooth, or get it close as possible to Toy/bluetooth, since Initface (regardless of the method, should just be using your PC’s bluetooth iirc @qdot)
I often actually find myself, disconnecting Initface from Scrtipplayer and reconnecting and re-scanning a couple times if I have issues @shiningsomelier
@Realcumber thanks for the advice. I managed to make it work somewhat but it’s still not completely smooth process. So for anyone who has same/similar issue, I can make script player find Keon by doing following:
in script player setting, tab ‘Buttplug’ I set Connect to Buttplug, Search for Devices to true
start Intiface and start server
now I just have to start and close script player over and over until it detects Keon, usually takes about 2-4 tries (at least in my case, distance of Keon to the bluetooth receiver didn’t seem to matter)
Not exactly ideal but it sure beat going through the tutorial every time.
@shiningsomelier - I just tested and I was able to reproduce the same issue you had:
Keon not being found on first attempt - So keep having Initface open, then closing Scriptplayer latest beta, then reopening Scriptplayer, connecting to buttplug and scanning devices - worked everytime on the 2nd attempt
@Liquid / @qdot - does this makes any sense why this would be happening or how to prevent?
It’s probably me. I think I broke something when trying to fix a memory leak in our bluetooth core earlier this week. I’ll try to get this patched up in the next couple of days.
Just updated to your v21 Engine in Initface - gave it a scan - sorry @qdot sad news is same issue - I still need to close then re-open Scriptplayer and repeat connect and scan for it to pick up Keon
I also notice it crashes it Scriptplayer ongoing if you have more than 1 device scanned and picked up in Initface (like XInput gamepad And Keon together)
Yup. My fault again. Tracking bug here, bug patched and testing now, will announce with v22 is out.
Note:
THIS IS NOW FIXED IN v22. However this discourse installation won’t allow more than 3 consecutive replies so I’m having to edit this one. I checked with a Keon and Edge, came up in ScriptPlayer just fine. However right after my Keon ran out of power, so I didn’t get too much long term testing in. Please let me know if you continue to have issues.
BTW, while I may sound grumbly, that’s just me getting mad at myself. Please keep reporting this stuff! There’s gonna be a ton of bug churn over the next few weeks as I nail down all of the issues in the new code I just released. The bluetooth work is difficult to test other than manually, and I will miss some cases, so y’all are basically my QA team.
Just confirmed and tested @qdot - works like a dream again - thanks for the awesome support and quick fixes! Im sure all Keon users are very thankful for it