Looking forward to hearing your thoughts!
Yes, there was a shop! And so I went roughly like this:
Round 1 played fine → Handy didn’t begin playing Round 2 when it started, though the video was playing → I swapped to a lovense device to see if it would move and it didn’t → Lovense was still connected when Round 3 started and it began playing properly again → I swapped it back to Handy to see if Handy would play → It did not → I swapped it back to Lovense to see if it would keep playing → it would not
1 Like
Pushed up a potential fix for it. It sounds like a device caching issue.
Cool concept I made a challenge run with some rawsource vids if anyone wants it. Can’t wait to see updates on this and to try it out later!
2 Likes
Hell yeah! I’ll check it out tomorrow. Thanks for sharing
I’ve added it to the available journeys above 
1 Like
Don’t suppose you could reupload that on pixeldrain? That’s just slightly too large to download all in one go on Mega, given their 5 GB daily download limit.
1 Like
Here you go
1 Like
Tragedy strikes!
I should have taken smaller bites when learning the system, but I sort of got in a flow with how much I had organized. I cannot save; it thinks for a brief moment and gives a generic message in the top right. Before when I got errors, I think it was quotations in the Round names, which cleared the previous error. Now, I’m not sure if it’s maybe quotes in the storyline segments when a character is speaking, or maybe that I only used a default image when characters speak instead of on every message. Or maybe it’s just too long or has too many branching paths! Any input would be helpful, it would be a bummer to try remaking this from scratch. I’ll leave it up overnight in case anyone gets a good idea of what happened.
Much appreciation to any kind souls willing to help resuscitate this so I can finish! 
1 Like
The League of Legends one is missing, any idea when or if itll be back?
Iv got it installed, I downloaded MinUSB file, connected to intiface, ran the game, chose the file and its playing but my keon isnt doing anything. Any suggestions?
Still developing the storyboard for this one. It should be soon!
1 Like
First off, wow! Second off, sorry for your loss 
Quotes in the storyline segments are totally fine. Same with Images, you can have images on every message without issues.
Length shouldn’t be an issue… I’ll do some debugging today and see what conditions get it to fail.
If all else fails, this really signals to me that I need to implement more specific errors messages in the editor.
Hang in there! I’ll give you some suggestions in a bit.
First thing to check is if the device is connected in the options menu and if the Test button works.
Besides that I would make sure your Output Type is set to Intiface.
Let me know if the test button doesn’t work. That could be a deeper issue.
Hey, It must have been somthing to do with the unzip. I started over again and its working now!. Just about to try it!
1 Like
Alright here is a checklist of things that could be wrong (in v0.1.2):
Naming rules
- Round names and fork-path names can’t contain
\ / : * ? " < > |. - Can’t end with a space or period (Windows folder rule).
- Max 100 characters.
- Required to be non-empty.
Path-length limit
- Total destination path =
<journeys folder>/<sanitized journey name>/<round name>/<video filename>must stay under ~240 characters to keep clear of Windows’ 260-charMAX_PATH
Source File LifeCycle
- Any source file (video, funscript, image) the user drags into the editor is referenced by absolute path until Save copies it into the journey folder. If the user moves or deletes the source between drag and Save, the save fails. Editor doesn’t watch for this
Inherent journey structure rules
- Top level must have at least one round.
- Each fork must have at least 2 paths.
- Each fork path must have at least one round.
- Each round needs a name and a funscript.
The main thing I would suspect in your case are these 2:
- Round names and fork-path names can’t contain
\ / : * ? " < > |. - The journey is so deep (forks within forks) that destination paths exceed Windows MAX_PATH. Fix: move journeys folder via Options → Storage Location to a short path like
D:\J
I neglected to think about the windows path issue. I might need apply a short naming convention for folders and their contents to avoid the character limit.
Also, I am working on increasing the verbosity on the error messages and adding live-validation to the editor to catch issues like this before the save.
This makes a lot of sense! In my Round naming, I included BOTH the artist and FS author. Considering it’s above 10 Rounds, the character limit is surely having issues. I do indeed have special character in fork path names as well. I will take a look when I get the chance, thanks for the detail!
To others writing: save often lol
Absolutely this ^
Almost always the best practice when editing anything!
Also to builders, new version is available. I made some sweeping changes to how journeys are saved, added more validation, and much more useful error messages on fails. Please get the latest version before building:
Some Highlights:
- You used to be blocked from using / \ : * ? " < > | in round names or
fork-path names because they ended up in folder paths. Not anymore. Names are
now purely display strings. - Before any file is touched, the editor now walks your entire journey — top level
plus every fork path, recursively — and lists every problem it finds in one
shot. - Windows has a 260-character path limit that used to silently bite on journeys
with long names, many rounds, or videos with long filenames. The save system
now uses short, fixed-length internal folder and file names
Thank you to Ultari123 for bringing said issues to my attention!
2 Likes
The 1.2 update does fix the problem of Handy’s stopping playback on round 2.
1 Like
Thanks for reporting back! 
I know it’s probably annoying to have to redownload the app every single day but this one should be the last release this week!
Some Highlights
- A persistent device-status banner now warns you the moment your device,
Intiface server, or serial port disconnects mid-play. - The banner also catches selected-device mismatches — if your saved
preference isn’t connected but a different device is, you’ll know. - Beat Bar and Storyboard Filler settings now take effect immediately
instead of requiring a new round. - Saves now correctly transcode non-H.264 videos inside fork paths, not
just top-level rounds. (important for long journeys)