Ive been trying to make custom thumbnails for my videos and the method in the user guide isnt working am i missing something and or is there a more direct way like uploading an image from a directory
found an error, will be shipped with the vibrator fix in some minutes
(beta build - pixeldrain)
1 Like
thumbnail and vibrator fix
please test and report 
1 Like
Can Confirm Thumbnail is working your the best 
Vibrator works now, thanks for the fast fix.
It’s connected to my Lovense Gush 2 via Intiface. The test connection on FLM is successful. However, funscripts do not properly play. It seems it just turns on the vibration and that’s it. I was hoping to be able to remote from my phone, but I can’t even get the scripts to play properly on desktop.
I’ve subscribed to your Patreon. I would appreciate any input that might help my situation.
The software doesn’t seem to support single-file multi-axis funscripts. I saw in the logs:
“[INFO] PlayerWindow: Device: Script loaded (L0); [INFO] TCodeBackend: Playback started at 13870 ms, axes: [‘L0’]”,
but the file actually contains axes for L0, R0, R1, and R2. How can this be resolved, or is there batch conversion software available to split the files?
so it is just a vibrate at the same speed?
FLM support the single-file scripts used on eroscripts, if you have a file that is not the same structure it could be that there would be a problem.
Please send a file i can test with.
Also a diagnostic bundle wouuld be helpful.
(BlobCG)Anis.funscript (35.5 KB)
2026-04-27 01:37:09,460 [WARNING] qt: QWidgetWindow(0x1dbbb39a450, name=“LibraryWidgetClassWindow”) must be a top level window.
2026-04-27 01:37:11,331 [INFO] PlayerWindow: Device: Connecting…
2026-04-27 01:37:11,563 [INFO] PlayerWindow: Auto-connecting to device…
2026-04-27 01:37:11,565 [INFO] PlayerWindow: Using persistent backend | backend=tcode | script=Z:\video\funscript\E站(BlobCG) Anis - MultiAxis(BlobCG)Anis.funscript
2026-04-27 01:37:11,569 [INFO] TCodeBackend: Loaded 546 actions for L0 (546 after processing)
2026-04-27 01:37:11,570 [INFO] TCodeBackend: Stroke range: 18-94
2026-04-27 01:37:11,571 [INFO] TCodeBackend: Sync offset set to 200 ms
2026-04-27 01:37:11,579 [INFO] PlayerWindow: Device: Script loaded (L0)
2026-04-27 01:37:14,584 [INFO] TCodeBackend: Playback started at 31622 ms, axes: [‘L0’]
2026-04-27 01:37:14,584 [INFO] PlayerWindow: Device: Sync active
2026-04-27 01:37:20,986 [INFO] PlayerWindow: Stopping device sync before close (non-blocking)…
2026-04-27 01:37:20,987 [INFO] TCodeBackend: Playback ended: sent 29 commands, failed 0
found it, fix will be uploaded in some minutes
Thank you so much, this is the best program and developer I’ve ever supported.
the buttplug implementation of “Lovense Gush 2” supports vibrattion only.
We notify buttplug with an translation of the intensity pattern into vibration speed.
There is a factor involved which could lead to situations where it is running at max speed in “low action scenarios”, i will add a config setting to lover the factor, you can lower it then and see it that makes a difference.
1 Like
Thank you for your responsiveness. I’m still having the same issue despite going in and playing around with the Intiface Central settings on FLM. I’ve tried Raw vs. Smooth processing, tried all device modes, and have tested the intensity ramp from 1-10. Like I said, the device connects and it does vibrate; it just seems to struggle with translating to vibration (as opposed to something like ScriptPlayer).
I really do like what I see with FLM though, so I am looking forward to seeing everything in working order.
If there is any information that I could give that might help, please let me know.
sorry, i forgot to mention:
did you run a deep scan against the video again?
The file needs to be rescanned to get the correct data out of the funscript.
Just right click and then deep scan from the kontext menu.
need to inverstigate that, unfortunately i have to do it “blind” as i have no vibrator device
i will keep you posted.
I’ve been meaning to ask if FLM could allow for two backends to operate at the same time? Then the vibration toys can run via intiface and the striker device could run via FLM. Because currently I need to send signals to three devices at once. Currently I can use either just the stroker with FLM, or all three devices if I play with VLC connected to (intiface + multifunplayer)
will check if that would be easy to implement
1 Like