Troubleshooting — Loading a Script¶
Find your situation below. Each question is written the way you might actually think it — not the way a manual would phrase it.
If your question isn't here, ask the help assistant → and if it turns out to be a common one, it will show up on this page.
The file won't load — it says "file not found"¶
You might be searching for: "file not found", "funscript won't load", "can't open my file"
Use the full absolute path to the file, not a relative path or just the filename.
Windows example:
macOS/Linux example:
The fastest way to get the exact path: on Windows, hold Shift and right-click the file → Copy as path. On macOS, drag the file onto a Terminal window.
My analysis only shows one phrase (or a very small number)¶
You might be searching for: "only one phrase", "just one phrase detected", "phrases wrong", "my funscript is one big phrase"
This usually means your funscript is uniform-tempo — the same BPM throughout with no significant tempo changes. That is very common with scripts generated by automated tools.
FunscriptForge handles this. When uniform tempo is detected, it splits the script into time-based phrases automatically so you still have sections to work with.
Continue to Read your assessment — it will explain what was found and what to do next.
The chart is blank — I can't see anything¶
You might be searching for: "blank chart", "no waveform", "chart not showing", "nothing appears after loading"
The funscript file may be empty or malformed. Open it in a plain text editor (Notepad,
TextEdit, etc.) and check that it contains an actions array with entries like:
If the file is empty, or the actions array is empty or missing, there is nothing to display.
You will need a valid funscript file to proceed.
The analysis froze partway through¶
You might be searching for: "analysis stuck", "progress bar stopped", "analysis not finishing", "app frozen during analysis"
Very large files (2+ hours of content, millions of actions) can take 30–60 seconds. The progress indicator should still be moving. Wait and watch.
If it is genuinely frozen (progress indicator completely still for over 2 minutes): close the app, reopen it, and try loading the file again.
The progress shows "Phrases: 0" at the end¶
You might be searching for: "zero phrases", "no phrases found", "phrases 0"
This can happen with very short funscripts (under 10 seconds) or files with fewer than a handful of actions. FunscriptForge needs enough structure to find meaningful phrase boundaries.
Try with a longer file. If you're following this guide for the first time, the example funscript (link coming) is a good starting point.
The app loaded my file but the assessment numbers seem wrong¶
You might be searching for: "wrong BPM", "wrong phrase count", "assessment looks off", "phrases don't match my script"
Assessment results depend on the actual content of the file, not on filenames or metadata. A few things that look "wrong" but are actually correct:
- Very high phrase count — a highly varied script with frequent tempo changes produces more phrases. That is accurate.
- BPM seems too high or too low — BPM is measured at the cycle level (one up+down stroke). If your script has very short or very long strokes, the BPM will reflect that.
- One phrase covering the whole script — see "only one phrase" above.
For a full explanation of every number in the assessment panel, see Assessment deep dive.
My question isn't here¶
Type your question the way you'd naturally ask it. If it's a question others are likely to hit too, it will be added to this page. You're helping the next person by asking.