OpenFunscripter (OFS) is fully open source over at Github
Disclaimer: You can do whatever you want with scripts created with OFS. No strings attached.
How to get started with scripting and OFS?
Be aware of the fact that scripting takes a lot of time and is a very subjective process.
Subjective as in if you like the script you made you did a good job.
The “Options”->“Keys” window is your friend it shows all possible key combinations and buttons you can press it also let’s you rebind them.
Replaced “Open project” & “Import video/script” with a generic “Open…”
When opening a video or a funscript it first checks for a .ofsp file.
If a project exists it is opened instead otherwise a new project is created.
Changes to bookmarks and chapters
The old way of creating bookmarks and bookmarks ranges was removed.
And replaced with a new UI below the video timeline.
To create/edit bookmarks/chapters you just right click and use the context menu. Hopefully it’s intuitive enough.
These bookmarks & chapters are also imported and exported from and to the .funscript files #55
This means they can be read by other applications.
New app directory
The app directory has changed again from %appdata%/OFS/OFS2_data → %appdata%/OFS/OFS3_data.
I don’t want to make this a trend but migrating is too hard and I’d rather not be responsible for lost work.
Changes to projects
Project files are now stored in a different format. It’s stored as CBOR rather than just raw binary data.
This means project files created with older versions of OFS will not work in this version anymore.
On the bright side this new format is much more robust against change and won’t break in future versions
Thank you for improving our scripting experience even more. These big updates are always very exciting ^^
The new bookmark / chapter setting is amazing! It feels very good to use. Love I can choose colors for the chapters. Next step would be that the chapters gets also saved, when you save the heatmap and the chapters are visible there.
Maybe I am blind, but where can I find this and what does it do?
Is this one already usable or currently in development?
It should be in the “Mode” window when “Frame” is selected.
Basically when you have a low FPS video it allows you to override that giving you more granular stepping. The framerate of the video obviously doesn’t change.
There’s version 1 release. I think it’s very usable. It’s just a simulator for multi axis nothing more yet.
You just enable the Websocket API (in View->Websocket API) start the simulator and it should just work.
By default this always uses port 8080. If you need to use a different one you need to start the simulator from the command line and specify a different url like this FunscriptSimulator3D.exe ws://127.0.0.1:1234/ofs.
I was blind. Thank for the explanation. That is very useful. Will try it for some 24 fps videos.
Thank you for the information. Will test if I can get it to work. I never scripted anything multi axis, but I liked using the 3d simulator for PMVs. The pitching helped me to see, if I got the beat right.
First of all, thanks a lot @gagax123. Lots of good improvements in this one, including a few of my requests (#19, #49, and, indirectly, bookmark/chapters).
Concerning the chapter UI, I haven’t used it for long but what I noticed so far:
The height of “selection box” for the chapters is really small (1 or 2 pixels high), which makes it hard to select sometimes. Could the height of the box be increased?
It’s great that we can change the colors but, right now, we are kind of required to do it because, by default, the chapter is always the same color. Could OFS rotate between a list of different colors when adding chapters? (1st chapter added: blue, 2nd: green, etc)
I’m not sure if I’m using it correctly but, if I don’t want gaps in the timeline, I have to create a “tiny” chapter, move to the start of the next one, select the previous tiny chapter, choose “set size”, add a new “tiny” chapter, … If I “set size” and forget to add a new chapter right away, it’s a bit hard to reselect the exact point at the end of the previous chapter to create the new one without a gap.
Personally, I would prefer if a new chapter would always fill the gap to the next chapter or the end of the video and that I could cut a chapter in two by selecting “create new chapter” inside an existing chapter (which doesn’t seem to be possible right now).
If needed, “Set Size” could still be used to create a gap in the timeline.
The good thing is that information is also saved inside the funscript file. Besides OFS, all tools that create heatmaps could use the information in the future (funscript.io, MFP, etc). I’m personally planning to add a feature to generate “advanced heatmaps” to FunscriptToolbox soon, probably during the Chrismas break.
Vertical. I haven’t thought about increasing the window size and, yes, it is a good workaround, but I feel that it should not be needed. It seems that the first 6 or 7 pixels on the top and bottom of the visual box don’t select the object. For example, if the height of the bars is about 15 pixels (which is large enough to read the text), we only have 1 or 2 vertical pixels for selection.
Look at this screenshot, my pointer is clearly on the bar but it’s not selected.
Ok, I see what you are doing in your video. I didn’t think that “set size” worked for the start of the chapter too. I’ll do that. I still think that splitting a chapter in two with a simple “create chapter” could be useful and, maybe, menu options “expand left” and “expand right” would be more fast & intuitive. But I’ll let you experiment. It’s a really good start, and really useful as is.
No everything that worked before should still work.
But since the app directory changed you’ll have to copy the extensions directory over into the new directory.
No sorry. Best you can do is open the old version and the new one side by side and compare.
Writing migrations for this stuff is not super easy and before having a buggy migration I’d rather not have one at all.
That’s also the reason why this is 3.0.0 and not 2.1.0 because I had to break stuff.
The next version won’t be 4.0.0
