When available, yes I’ll load a video with several scripts linked - I just don’t remember all the axis coding, just the names. L0 = plain stroke funscript, the others would be *.pitch.funscript, *.roll.funscript, *vib1.funscript, etc.
This site has a “single script” dl option, where the funscript axes are all rolled into one .funscript file - but it isn’t something that works reliably for me, so I DL each individual axis.
In MFP for the PC, I have to load the video in VLC, then load the main (stroke) script, then each script for each axis (sometimes it will locate them if I played it already) before I can run it. Whereas with XTP, I can just load the one video as it pulls everything with matching names from the folder and sets up the axes automatically, like how FP will find the script for matched video. But XTP won’t connect with Initface to run dual vibe…
Basically yeah - FP getting multi-axis support would be the high value desire, even without being able to map vibrator/initface-action scripts. That part is the cherry on top, and I can’t imagine it’s easy to code in.
Initial setup with MFP is confusing and super-detailed without much local help, have to wade through a dozen pages of a couple topics and piece together from what other people had issues with. I sat down to play a couple weeks back when I had an hour or two, and spent the whole time just setting the damn thing up and getting it synced wth VLC and Initface, then mapping out script destinations and limits/ranges. By the time I got it working as desired, my partner came home and I had to shut down to go be responsible.



