Funscript troubleshooting

The device is late or early

Cause. Every setup has some delay between the picture and the device: the network and Autoblow's cloud for the Ultra, the PC and Bluetooth for Intiface devices. A script made for a different cut of the video is also shifted throughout.

Fix. Change Offset. It runs from -5000 to +5000 ms in 50 ms steps. Raise it if the device feels late; lower it if it feels early. The app saves the value for each video (up to 200 videos) and restores it when you open that video again; a video with no saved value keeps the last Offset you used. There is one Offset for every device, not one per device.

What happens during playback differs by path:

• Autoblow AI Ultra. The app starts the device at the video time plus half the measured round trip, then checks the device's clock every 1.5 to 5 seconds. Drift of 80–350 ms is trimmed gradually; over 350 ms it restarts the device at the video position. If the Ultra drifts anyway, pause and play again to re-anchor it.
• Intiface devices. There is no latency measurement or drift correction. The script runs on the PC's clock from each play or seek, shifted by Offset. If the video stalls or buffers, the device carries on; pause and play, or seek, to line it up again.

If only one section is off while the rest is right, the script is at fault there, not the sync: select the span on the timeline and use Shift ±20 ms.

The Autoblow AI Ultra will not connect

Cause. The app reaches the Ultra only through Autoblow's cloud, never directly over your local network. If the cloud has no live session for your device token, the Ultra is offline, or the token is wrong.

Fix.

1. Check that both the PC and the Ultra have internet access. Both need it the whole time the device plays.
2. Put the Ultra online: hold its button for about 3 seconds, release it when the LEDs blink white rapidly, then wait for them to turn light blue. Light blue is the online state.
3. Check the device token you pasted into the app. It comes from Autoblow's online setup page; if the LEDs are light blue and it still fails, verify the token at fun.autoblow.com.
4. Connect again, then press Send Script to Device before playing. Without it, the app falls back to coarse position commands and shows "Streaming positions (fallback mode)".

If starting playback or a move fails after a successful connect, the app shows it is reconnecting, retries every 5 seconds and re-anchors the device to the video when it comes back. If the Ultra switches to a built-in pattern or oscillate mode, the app says so; send the script again to return to sync. The Autoblow AI Ultra page covers setup in full. It is the one device we have tested on real hardware.

An Intiface device is not found

Cause. The app talks to devices through a Buttplug server at ws://127.0.0.1:12345. If nothing is listening there, it starts its own bundled Intiface engine (version 1.4.8), so you do not need Intiface Central. On connect it scans for up to 12 seconds. A device that is off, out of Bluetooth range, or newer than the bundled engine will not appear.

Fix.

• Turn Bluetooth on in Windows, switch the device on, and keep it close to the PC while it scans. Connect again if it was not ready within the 12 seconds.
• The Handy works only over Bluetooth through Intiface. Its Wi-Fi connection-key mode is not supported, so set it to Bluetooth.
• If you run Intiface Central yourself, the app uses it instead of its own engine. We have not checked the app with Intiface Central v3; if a device is found in Central but not by the app, close Central and let the app start its bundled engine.
• Devices released after the bundled engine (November 2023) may be unknown to it.

We have tested the Intiface path against mock servers and a simulated device on the real engine, not on real Bluetooth toys. The Intiface page has the detail, and The Handy page covers that device.

A script will not load, or plays upside down

Cause. The file is not valid JSON, has no actions list, or was saved in an encoding the released app cannot read. Version 2.121.1 reads UTF-8 only, so a file saved with a byte-order mark or as UTF-16 by some Windows tools is refused. It also ignores the inverted flag, so a script marked inverted plays upside down.

Fix. Drop the file on the funscript validator. It names the problem and, for sorting, duplicate times and out-of-range positions, gives you a repaired copy. For an encoding problem, open the file in a text editor and save it again as plain UTF-8. The next update (2.121.2) reads byte-order marks and UTF-16, applies inverted correctly, and explains in plain words why a file cannot be used.

Also check the name: to load automatically, the script must have the same base name as the video and sit in the same folder. Otherwise use Load Funscript…. The format reference lists every repair the app makes on loading.

Movement is too fast, or strokes are cut short

Cause. Before the app sends a script to the Autoblow AI Ultra, it fits a copy to a speed profile for the device. Points closer together than the device can handle are merged, and a stroke that would need more speed than the profile allows keeps its timing but loses size. On a fast scene that shows up as shorter strokes on the device than on the timeline. The saved .funscript is never changed.

The profiles use published manufacturer figures less about 10%, not our own measurements. The Autoblow's 400 units per second is a deliberately cautious default, because Autoblow publishes no speed figure.

Fix.

• Check Device model. The profile chosen there replaces the Ultra's own, so a different model left selected gives the wrong limits.
• If one section is simply too frantic, select it on the timeline and use Soften, or Smooth, and send the script again.
• Edits and stroke-setting changes reach the Ultra only when you press Send Script to Device again, because it plays the copy it was sent.

In the released app, strokers on Intiface are sent the script without this fitting; the next update applies the same fitting and your stroke settings to Intiface devices too. To check a file against a speed limit of your choosing, use the validator's speed check.

Strokes are too small on fast scenes

Cause. This is a known weakness of the generator, not a fault on your PC. The main analysis never looks at every frame: on 30 fps video it samples 7.5, 10 or 15 times a second on Fast, Balanced and High. When motion is fast, sampling that sparsely misses the tops and bottoms of strokes, and in the developer's tests against hand-made scripts, generated strokes came out much too small on fast scenes.

Fix.

• Select the fast span on the timeline and choose Re-analyze. It rescans exactly that span at full frame rate and splices the result in.
• Or select it and use Amplify, which makes every stroke in the span 15% bigger. Repeat for more.
• Generate on High, which samples every 2nd frame instead of every 3rd. It takes longer.

Saving an edited generated script teaches the app your preferred stroke size for each scene type, which it applies on later videos.

The device keeps moving when nothing is happening

Cause. A known limitation. The generator holds opening titles and closing credits at rest and flattens windows that are nearly still, but inside the video it can go on producing strokes through spans where a person scripting by hand would have stopped.

Fix. Edit it out. On the timeline, Shift+drag across the idle span and choose Delete. With the points gone, the device glides slowly from the point before the span to the point after it; for a full stop, Ctrl+click to add a point at each end of the span at the same height. Then save, and send the script to the device again if you use the Ultra. If the analysis keeps following the wrong thing through a whole video, draw the region to track with Set Motion Region… and generate again.

Where the video has almost no motion at all, the app refuses to invent a script and tells you the video looks static.

Generation is slow

Cause. The AI models (pose and depth) are accelerated only on an NVIDIA graphics card through CUDA. On AMD or Intel graphics, or when the NVIDIA card cannot be used, they run on the processor, which works but is much slower. The app does not hide this: it reports the provider actually in use. Optical flow always runs on the processor.

Fix.

• Press Check GPU (also View → Check GPU…). It reports whether PyTorch and ONNX Runtime can use the graphics card and, with a pose model installed, which provider pose runs on and a speed self-test in milliseconds per frame.
• Set Hardware to Auto or GPU (CUDA). Auto uses CUDA when it is available.
• Use Balanced rather than High; in the developer's own measurements on a few test films, High took about 1.5 times as long for about the same result. Fast is quicker still but reads noticeably fewer strokes.
• Regenerating the same video with the same analysis settings in one session reuses the analysis already done, so it is nearly instant; the app keeps the last 3 videos in memory until you close it.

The app closes at start with no message

Cause. Most likely VLC is missing. The app plays video through an installed 64-bit VLC. The installer checks for it and, if it finds none, downloads VLC from videolan.org and installs it silently. If that download failed, for example because the PC was offline during installation, VLC is skipped, and the app then closes at launch without showing any message; the explanation goes only to its log file.

Fix. Install 64-bit VLC, or run the AutoScript Sync installer again with the PC online so it can fetch VLC itself. Then start the app again. Your settings, models and taught AI are kept in %USERPROFILE%\.autoscript_sync and survive a reinstall.

The trial will not start

Cause. The trial does not start by itself on first launch, and it cannot start offline. The licence server records the trial for each PC, so it needs to be reached once.

Fix. Connect to the internet, open the app, and in the activation window click Start free 1-day trial. Every feature is unlocked for the day. Reinstalling does not restart a trial that has already run on that PC. When it ends, enter a licence key in the same window (Help → License / Activation…); keys look like ASYN-XXXX-XXXX-XXXX. The download page has the installer, and the store sells a licence for £14.99 once.

Read next

• The app guidesInstall, activation, device setup and the quality report, step by step.
• Autoblow AI Ultra setup and syncConnecting, what the lights mean and how drift correction works.
• Device compatibilityWhat each device family supports and how far it has been tested.
• How the app reads script filesEvery repair it makes to a file from another tool.
• The learn hubAll four reference pages.