I got linked here from the mira page. But yeah for the handy. Takes quite some time to start playing scripts for me.
Hi, thanks for the software. Gave me hours of fun! I have a question though: I have some games on my computer and some of them use a different version of EDI from each other, do you reckon its a good idea to update the EDI on each game, or should I use the version that came with the game? How’s the compatability. Thank you
has anyone been able to run this software with WINE ?
Please add upper and lower stroke length limits for Edi. Edi can connect to many devices through Intiface Central, but Intiface Central cannot control the stroke length of the output script. Some devices do not have the ability to adjust their stroke length and can only move according to the received data. We hope to add a stroke length limit function on the Edi side. It would be great if we could add the stroke length limit settings in the EdiConfig.json without even needing a UI. Thank you!
It will come in an upcoming release along with a new endpoint to set the “intensity” from the game.
es, it’s because these RPGs have many hours of script, more than 5 hours. That’s why the bundle with all the galleries takes so many minutes to upload, as it’s actually loading many hours of scripts.
This is what allows everything to run smoothly within the game since everything is preloaded onto the device.
I have a functionality in development that allows splitting the scripts into different bundles so that smaller portions are loaded and swapped as the game progresses. However, it still needs a bit more refinement.
OSR Multi-Axis!! Big thanks to @to4st for your many contributions and integrations to the project!
i made a fix in the handy loop offset. loops should work better now
Had the same issue where EDI would crash on launch, spent a while debugging it and figured out the culprit was the “Intel(R) Graphics Command Center Service”
As soon as I stop the service (in services.msc), EDI launches with no issue.
Btw I am using a desktop with iGPU disabled, might have something to do with it (installed graphics command center when I enabled iGPU multi-monitor for a bit)
I finally got an OSR2. I cannot get it to move with EDI. It seems to connect (e.g. I can select COM5 when I have it plugged in), but the servos don’t move. (I have the g90ak version if that makes any difference lol). The OSR2+ works with FunscripterPlayer so I’m not sure if its on my side or the software.
Guessing there’s no usage with the Ai Autoblow Ultra?
All games works with autoblow if you update to the last version of EDI and put your device key in the device key texbox
I tried that but I don’t see an option for the Autoblow Ai. Can I go somewhere to watch a video or a step by-step?
Wishful thinking, but is it possible to compile this to work on OSX/Mac?
I recently talked to to4st about how to better convert funscript to the algorithm of rotating devices. The algorithm of the latest version of funscriptplayer1.4.2 has been integrated. Is it possible to integrate the corresponding conversion algorithm in the latest version of EDI? Thank you @to4st
Is it possible to make this work with the FunSR1 2.0?
It’s a device similar to OSR2(+) and OSR6, connecting via serial connection and using TCode protocol. But it only has L0 (stroke) and R0 (twist) axes.
I tried with the version currently in the Mega, and I can select the COM port and it detects the device as “tcode_0.3” with the variant “detailed”. It shows up both in the UI and in the API demo webpage when doing the GetDevices GET request.
However, it does not play the patterns from a connected app on the device, instead it seems like it keeps disconnecting and connecting, the device constantly resetting itself. The device works just fine with MultiFunPlayer, so it’s working correctly.
If there is any debug version I can run to provide you with logs I’ll happily supply those logs.
sorry for the inconvenience. I hope to solve this in the new version of EDI, especially the logging part. I am particularly interested in making the funSr devices work.
Great news
Take your time, glad to hear it’s on your to-do list. Thank you for adapting the tool to new toys