Just don’t spend time on info that already exist. A lot of the basics are already in written and video guides. Spend time where the benefits are the most and maybe just refer to the other guides to begin with. If the existing guides are lacking then we can probably make updates to them instead of starting new. But it is of course up to you to decide what you want to do.
1 Like
Something that I think is really important, that I suspect gets overlooked a lot, is really feeling what works and what doesn’t and studying this by feel instead of only looking at dots on a screen. One of the things that you do so well as a scripter is that you really capture the feel of what’s happening on screen. You don’t just stick a ruler next to the dick and say, “Well two cm of movement on screen is two cm of Handy movement.”
What you could do is put out an open call for people to send you specific parts that they’re having difficulty with. Then you could talk about and show how you would script that part. Of course I’m not talking about rescripting an entire scene, just a few seconds. Then have a short split screen video, with a script, that repeats so we can both see and feel the difference between what works and what does not because a lot of times what looks right, just doesn’t feel right. So for the video both sides of the screen play the same clip in unison. Underneath the clip on the left you can see the script that needs improvement in real time, and underneath the clip on the right you can see your script also playing in real time. The clips play simultaneously, but the clip on the left or right is highlighted depending on which script is actually playing in the attached funscript file.
The benefit of displaying the scripts simultaneously side by side, is that when I feel that something feels right I would be able to see all at once the way it should be scripted and also see what it is that I’m doing wrong. I imagine this could be very enlightening for some and could really accelerate the learning process.
1 Like
Please tell me this is a script you’re releasing soon! 
1 Like
I was just looking at a script request, some Super simple to script cgi stuff. Something one could do after watching a tutorial video. Totally awesome what your doing here @Slibowitz , if I can help in some way hit me up 
1 Like
I know we already have guides for that. But I would like to make a complete guide, that covers everything. And I feel like something would be missing, if I wouldn’t have a introduction episode and show some basics.
Sounds interesting and something I would consider. It’s probably something I would do, once the tutorial videos are done. But maybe even in between. I will put these idea on the list. Thank you for the idea!
Thank you! If need help with something, I will let you know 
2 Likes
This is a great idea, hope it can help more people get into scripting. Thanks for doing it!
I like the idea of an intro episode and the ambition to cover “everything” - information is spread out in different forum posts right now.
A good topic could also be (Handy) device restrictions and how to handle too slow/too fast actions.
2 Likes
I think so too. I’d like to create a place, where users can find everything. From the start, how to set the script tool up, import a video, start scripting, export a script to all different kind of actions, that you can possible face, while scripting.
The speed topic is something I will cover in the first episode. I also think it’s very important. I often see scripts, that are just way too fast, because they don’t know about speed limits.
2 Likes
I think the OFS side is already pretty well covered in a different tutorial on here. Personally I would be more interested in scripting specific actions like mentioned in the OP.
2 Likes
While true and these guides are of course really good, I still would like to cover the basics in the first episode. There is also additional stuff I would like to talk about, that hasn’t been mentioned in these tutorials.
Is there anybody with an account on vkontakte, who could help me out and upload the first episode there, once it’s done? I would like to add to FapTap, for streaming, because I think more people would watch it, when it’s available as a stream. I will still provide a mega link for people, who want to download it.
1 Like
hi, you can send me a link, I will upload the video to VK, in the evening when I’m at home
1 Like
Thank you so much!
I will text you, onceI am done.
The first, or how I called it “Episode 0” episode would be ready.
Before making the actual thread for it, I will leave it here for reviewing.
So, if anybody has some time, I’d be very grateful if somebody can review it and check if it’s good, all the Information I provide are correct, there are no spelling mistakes, all the things are explained well enough and it’s understandable and the overall viewer experience is good.
There is some light background music I put in, but when the actual explanations are starting, I muted it. Or should the music play all the time? Thought it could be a bit annoying.
I will release the episode later today, if everything is good with it.
Thank you for your help!
2 Likes
Have seen the whole video.
Feedback:
Good:
Production value is good
You show mostly every single step for even the most basic user
Neutral:
No subtitles for everything
Not so good:
Way too long. It’s way quicker and with more explanations about the stroke speed and length in currently available written guides
Importing movies especially VR videos and setting the view is important, but it would be way more important to show how to prepare your files for easy scripting (lowering resolution and framerate)
It’s a good video, but I would rather read a guide than to watch the tutorial episode 0, but it’s a start.
1 Like
Thank very much for the detailed feedback and for your time watching the video.
Was thinking about them, but decided against it. Will take space away and I would need to find a way to generate them. I think Davinci Resolve can add them automatically now, but I am not sure. But I think the TTS voice is clean enough and everybody understands English good enough to understand the script.
17 minutes is too long? Really? It’s not really that long in my opinion. My goal was to stick under 20 minutes. And for written guides: Yeah, sure. Everybody can decide what they want to use. I prefer video guides over written guides, but that’s because I hate reading and prefer videos.
I never did that. Never changed resolution, rarely changed framerate from 60 to 30, whenever I was too lazy to script a 60 fps video. And I am not even recommending doing that. I can only teach, what I know and did.
Also, I think that is a more advanced thing, which I don’t would want to cover in an introduction episode. Maybe that’s something for later in an advanced showcase episode.
Fair enough. As I said, everybody can use what guide they want. This is just an offer and for people, who prefer video guides. If people don’t like it and prefer reading, that’s ok and then I won’t need to make a video guide. Because it’s a enormous amount of work and I can spend the time somewhere else.
You should mention that the installation you describe is for Windows only. Linux and MacOS cannot use your installation guide.
The first choice should be to try the AVX version since most modern CPU:s support the instructions provided by AVX. The non-AVX version is mainly for those that run on some odd or very old CPU.
I don’t recommend installing LAV filters unless you really need them. All codec packs tend to cause issues for many, often due to conflicts of having conflicting codecs installed. I only use the HEVC addon from Microsoft app store to get h265 support and nothing else.
I’m also uncertain about the need for VS2015 since that is Microsoft specific and OFS can be compiled for many platforms.
Could the LAV and VS C++ redist 2015 be a mixup with JFS that at least require VS C++ redist 2015. BTW, VS C++ redist 2015 has been replaced by VS C++ redist 2015-2022. The pure 2015 version might not be up to date and may contain security vulnerabilities.
OFS is not pinned in the software section, at least not for me.
When you go through the window overview, why not load a video and a script so you actually see data as an example. I believe it is difficult for a new scripter to understand what statistics, modes, chapters etc. are, hence the information provides little value this early in the video. At least that is my experience from making presentations and demos at work.
More scripters should use the metadata window so disabling it for new projects is a bad recommendation in my opinion.
You should consider to add that new scripters should probably avoid videos with blowjobs as well as avoiding obstructed or long videos as their first videos if possible.
I personally don’t step one frame back as you describe in the video. I actually do the opposite when I don’t set it on the very top. I do this because down movement in videos are often a bit faster the up movements so you might want a higher speed down. I also don’t want to feel the device start moving before I visually experience the girl to start moving down so that also motivates me not to move backwards when setting the top point. However, this is where personal preferences comes in I guess 
2 Likes
Nicely done! I think it covers most important parts and don’t think it’s too long.
You are mentioning too fast movement but I think too slow is also valid to mention, I think it is harder to handle than too fast. But this could maybe be a separate episode on how to script accurately/for pleasure.
I personally don’t step one frame back as you describe in the video. I actually do the opposite when I don’t set it on the very top. I do this because down movement in videos are often a bit faster the up movements so you might want a higher speed down. I also don’t want to feel the device start moving before I visually experience the girl to start moving down so that also motivates me not to move backwards when setting the top point. However, this is where personal preferences comes in I guess
Totally agree with this 
1 Like
Reencoding a 60fps VR videos to 30fps through Funexpander cuts down the time to script a lot. Manually scripting is way way quicker and if you use Motion Trackers the speed increases a lot too. Changing resolution is recommended for people with older machines. It’s one of the quickest ways to improve scripting speed especially for manually scripting.
As for me, a 17 minute tutorial video with slow information makes it incredible uninteresting. I changed the speed to 1.5x and it’s a lot more enjoyable and engaging imo.
1 Like
Thanks for the feedback. Based on the feedback I think it’s best to not release it and to not continue on working on this series. It seems it’s lacking too much.
Was worth a try I guess.
Just don’t give up. Making good training material takes a lot of effort. That’s why video material is hard. Editing a written guide is so much easier in comparison.
You might consider posting a manuscript to get feedback before actually do all the hard work with the video parts, much like when film makers shoot a film. They have the manuscript and make a storyboard based on that before actual shooting any scenes.
3 Likes
Definitely agree on the framerate, when i first started scripting i downloaded the Joyfunscripter and it defaulted to 30 FPS and i didn’t know that. Ended up putting out 2 total dogshit scripts because i had no idea how to fix it for 60 FPS replay. 100% not noobie friendly