• Sex Toys & Scripts

  • Brand New Kiiroo Onyx+ now supported with SLR Interactive Synced Scripts!

This is a test build. if everything works fine we will release it during the day

RealcumberScripts So I tried it and have some problems. Onyx+ connected to SLR interactive with 2 Hello strokes and also SLR App. But every time I started a Video with script there was a kind of initialisation, Onyx+ tried to get to some point but then the motors got stuck and the LED flashes red quickly. After that I had to switch of and on again the Onyx+.
On one video I got 2 or 3 strokes and after that it want again move over some limit and the motor got stuck again.

      great feedback Samsonite121 - I had the red flashing too, actually, but only happened several minutes into a scene, and wasnt sure if this also happens on their official feelconnect app and videos too. Have u experienced the red flashing on other players/videos outside of slr interactive?

          RealcumberScripts With the official FeelConnect App and all associated videos and connected websites I haven't seen this behaviour before. It seems the FeelConnect App drives the Onyx+ every time only in the mechanical ranges the Onyx+ is capable of. Also I doesn't think the Onyx+ need this initialisation to the home position like the launch do it. And I don't know if SLR interactive tries such initialisation at the beginning of a video because in most of my cases the motor get's already stuck at the beginning of a video and normally there is no action at that times.
          Also I have to report that I've only tried the online streaming with the SLR App without locally downloaded funscripts but the scripts are purchased and I see a green fleshlight logo at that videos in the video overview and also a blue fleshlight sign in the UI during playback.

            2 years later

            RealcumberScripts Hi. I'm not sure if you're aware but this is a continuing issue that's causing permanent and repeatable crashes at set points through every script on the site for the Onyx+. Various forums are advising the issue is that if there is a gap of more than 3 seconds between instructions in the .funscript then it causes a connection error to the Onyx+ and it crashes with the flashing red light.
            Someone's created a fix, but as I'm restricted to just 3 downloads I can't really do much testing of this issue myself: https://discuss.eroscripts.com/t/a-python-script-to-fix-funscript-for-kiiroo-onyx/49593
            Is it possible to have a look at this issue and fix? If it does fix the problem it would be amazing to just run this to fix the existing online scripts and it would be worth me resubscribing again

                Forcekin hey @Forcekin - thanks for bringing this up, but I didnt think this was an issue, at least any more?

                Are you using online streaming of scripts on SLR app and haptics connect? or are you using our scripts a different way?

                What is your 'Speed booster' set at in haptics connect app?

                    RealcumberScripts I'm using the newest SLR app on a Quest 2, connected via Haptics Connect. I've tried turning the speed booster to 100% and it still happens, I've confirmed the crash definitely happens at set points in the script and it's after a pause in activity, so it does indicate the problem is a timeout/disconnection after no activity.
                    The connection drop appears to be between the Onyx+ and Haptics Connect, in order to get the connection back you have to turn the Onyx+ off and on again, then rescan for devices in Haptics Connect. It then works until the next pause/crash. It explains why other sites using FeelConnect are unaffected.

                    I've downloaded a script that crashes at a set time reasonably early on, I've run the potential fix through it and when I get a chance I'm going to sideload the script and the related video into the Quest 2 and see if it resolves the issue. I'll let you know what happens.

                    edit to add: I've confirmed that the problem is specifically when there is a lack of activity for approximately 3 seconds, and is consitently repeatable. Unfortunately the fixed version of the script didn't help, I'll need to investigate whether I messed up the fix

                    final edit to add: I've been able to confirm that it's not a lack of data points but a lack of change for 3 seconds that is causing the crash. I found a manual script editor and confirmed the script had data points at regular intervals during the pauses. I manually editted the script to add a +/-1 sawtooth to each of these pauses, playing that there was no crash at the previously reliable crash points and no change in playback. Don't know enough about python to know if that fix was trying to do the same, I suspect it would only be clever enough to add data points and not create tiny variations which is why it failed. Still, worth a look as manually fixing scripts would be time consuming

                        Forcekin really appreciated followup @Forcekin - passed this all on so hopefully can see whats going on further

                        Just confirming - same issue happens whether you are streaming or offline correct?

                            RealcumberScripts That's correct, it was exactly the same reaction at the same times using online or local copies of the non-fixed files.
                            I'm not enough of a coder to know how to do it myself, but I think it could be fixed by just running a script that did the following to an existing funscript:

                            1. Is the position of this point the same as the previous one? And is it more than 2 seconds ago?
                              If yes then adjust the point by +1 if the position is 0 or -1 if it's any other value
                            2. Go to next position

                            The only reason why this might not work is if there might be a minimum gradient of the increase/decrease to keep the activity running. If that's the case then a particularly long pause with no data points may still breaks, but it should still fix 99% of these problems and probably fixes all of them