Scripting pitfalls

howto
1

Right now I am changing the speed of dozens of scripts down to a max speed of 400U/sec with the awesome @quickfix macros.
https://discuss.eroscripts.com/t/re-post-processing-for-ofs-mtfg-lua-script/241831/42
Its not fun being caught in a 600U/sec overstim section. Now when I am at it I mod the scripts where I see typical problems.

  • Endpoints mismatch. Not a script - delete it.
  • Millions of points, rattle nonstop. Mostly can not be corrected by simplify as endpoints will mismatch.
  • Too fast as mentioned above don’t go over 400, its fast enough.
  • Tip is involved but no 100%. I see this most of the time even with very good scripters. If the tip is barely visible go full 100%. If there is tip play then you can go 90% to 70% or if you want to script a pause like a twist where no vertical motion happens.
  • Too fast choosing the wrong side. If tip is involved or close, limit the lower points. Doggy with tip involvement even if just a bit, limit the lower points.
  • Underexaggerated. If movement goes down from 100 to 80% go down to 50% or even 60% in your script.
3 Likes
2

I understand these points, but I’d definitely consider the 400u/s speed limit a very personal opinion. It’s not always fast enough for everyone.

It’s an opinion that should be considered by scripters, but it shouldn’t be a rule for everyone and/or every situation.

Also, simplify can be used without endpoints mismatching. This is especially true if the script has distinct top and bottom points.

3 Likes
3

I don’t think I have access to this topic?

4

endpoints mismatching: I disagree, there is always a motion end and a motion start. If there is no distinct direction change you script where motion stops or gets very very slow and then you put a point where acceleration begins if possible without flatlining. Its that simple really. I also talk about mismatching within the whole script. Those scripts are garbage.

400U/sec: yes that should be a standard. I am sure there a special scenes where you can exceed 400 but overstimulation is a problem just as underexxageration is. Scripters can make faster versions but they should make a 400.

5

I was referring to this. If a script has a lot of unnecessary points but clear and well synced endpoints, it’s possible to use simplify without messing up the endpoint timings.

1 Like
6

Thisssss.

I find myself editing great scripts made by others so that I can make sure I don’t hurt myself lol.
I do think it’s 100% preference as well.

A scripting pitfall I run into when I script for myself is that I add too much detail, therefore the script can feel less intense than the activity happening. I’ve found I’ve had to add some creative flares to make it feel good based on my preference.

Also, some scripters (even AI scripts) use speeds that match the surrounding environment (i.e. a girls head during a fast blowjob) but in reality, the stroke length is much shorter so it doesn’t require that speed (motion is only covering 80-50%).
Does it match the speed of the activity in the scene? Yes. But, is it really matching the stroke length, no.
It makes scenes too intense for me sometimes.
But again, this is all preference!

I think it comes down to what the ultimate effect and preference the scripters looking to portray. Some scripters purposely create unique and original scripts that are meant to feel different. But I get it, sometimes it’s missed when scripts are made for the sake of having it scripted.

1 Like
7

Over 400 units is normal if you use a T code device like OSR and especially if you use upgraded servos

2 Likes
8

For a handy maybe, but for an OSR2 this can be fine. And worse is: there is no perfect value here as it depends on the chosen servos, and configuration.

Its nice if the scripter would make a simplified version for the handy, but if the owner only has an OSR2, then you still cant be sure if it plays back properly. And there realy is no reason for them to go back to a handy for just testing that.

Its a device limit of the handy. Going sevely beyond it usualy brings down the quality. But it does matter a lot on where you are making it exceed. If its constant up/down at full length and as fast as possible, you might want to exceed it go up to 500. Clipping then provides some randomness, which adds realism.
But in most cases, going beyond 450 is going to reduce the quality already.

However, sticking strictly to the 400 is a negative if the video intention is full speed. As this will reduce speed. Lets say we have 2 strokes, 1 at 410 and 1 at 390, first of all, the 410 stroke is performed at 400 due to limiting, it doesnt reach the final point. Next point, because it never reached the actual point, it now has to do less distance, making 390 more like 388. By ensuring the strokes all go above 400, there are enough moments where the handy can already catch up.

And then you also get the effect that stroke positions are often going to be very static and have no variety in them.

Overstimulation is a personal thing, not everyone experiences this the same. And especialy diffirent devices and sleeves can change this even more.

And a last note: some people do limit the handy stroke distance, not everone has a long enough cock. For them the increased speed does translate towards faster motion and give them the better experience.

and regarding standards there is a mandatory comic:

standards
standards500×283 22 KB

Dont bother trying to force one, you will fail.

2 Likes
9

There will always be at least 2. The first ‘official’ way, the second way done by those who refuse to use the first.

10

The practical speed limit depends on the device. With e-stim, speeds much faster than 1000 are no problem, and the amount of stimulation can be set separately from the speed by changing the current. (I use a separate “volume” axis for that)

Like this:
https://discuss.eroscripts.com/t/kenzieland-slave-for-love-closer-nin/249015

1 Like
11

I try to make mines as identical to what is happening as possible, then leave it to users to adjust to taste.

12

I use a T-code device just for the record so 600U/sec speed is not a problem. I think you guys see it the way round. Making a script bad or unusable is not preference and I think there is some scripting that can make sure your script is just not good. I can only make suggestions.

  • underexaggeration. This one is standard already. If motion goes down 20% go down 50% or more.

  • too fast, in my opinion above 400 most of the time. It can get really unpleasant. We, or better @randomus found this out in the last group event. The Clea script, a now perfect one btw 5/5 points of all judges, was unusable at 500 or above, it simply got unpleasant. IRL you would ask her to stop and ask if she is serious. So can we or should we go as fast as the device can go? I dont thinks so. Maybe if one day we can change the pressure applied speed can rise. Like current change solves this on e-stim I guess mentioned by quickfix. Going as fast as the device can go will make your script worse. Overstim will also end you faster than intended also unpleasantly. We seem to be forced to this if the device can not keep up which I think is wrong. Use the @quickfix macros to limit to 400 at least try it out.

  • the tip problem. I just corrected a script hat had a HJ almost going to the tip end and the whole script was going up to 80-90%. My suggestion is go to 100% if the tip is involved even a bit. Most nerves are just below the tip so 100% makes sure that point is passed. Going 80% when the tip is involved is underexaggerating, just upwards.
    Same problem is when people are scripting at 0-50% when it gets too fast and tip is involved. Script 100-50% and limit the bottom points with the @quickfix macros. Desirable below 400U/sec.

2 Likes
13

Most people can not use OFS. So you leave them with a overstim when too fast, underexaggerated the whole time and understim at the tip. Just everything what I dont want to produce.
In my book great example on how not to script.

14

Example for tip underexaggeration. @qweer one of the best scripters on the site maybe the best, always accurate. Tip is scripted as seen and that is understim in my personal standard.

https://discuss.eroscripts.com/t/my-stepsis-made-me-cum-so-hard-on-her-perfect-big-natural-boobs-comatozze/170709

15
  • Tip is involved but no 100%. I see this most of the time even with very good scripters. If the tip is barely visible go full 100%. If there is tip play then you can go 90% to 70% or if you want to script a pause like a twist where no vertical motion happens.
  • Too fast choosing the wrong side. If tip is involved or close, limit the lower points. Doggy with tip involvement even if just a bit, limit the lower points.
  • Underexaggerated. If movement goes down from 100 to 80% go down to 50% or even 60% in your script.

I dont understand these points, can you elaborate more please?

16

I’ve been messaged a lot about using 100% alot back then because for many people their dick is then out of their sleeve and depending on what is happening it can get awkward with their headset when it gets down again.

As many on here said people use different devices and different sleeves. I’ve been doing 500mm/s for a longer time now because of the newer devices (e.g. A10 Piston SA) and also if my Handy is well greased it’s not an issue for me when there is lots of quick actions.

In the end OG9s scripts have been my favourite ones by far (with lots of interesting and perfectly crafted details for the animations) which is why I copied some stuff for my scripts and do not exceed 500mm/s:

Stroke length is another one of those cases. Also depends on the user, device and sleeve. I’ve had commissions where I had to decrease the stroke length for tip only, because the user felt the sleeve went too much (which is something I can easily notice too).

There is too much personal preference for scripts and devices and sleeves that are used that you can only give some certain standard advice (ala do not try to ever go above 600mm/s for the Handy because that’s where the real issues start to appear, below 500mm/s is fine most of the time with a well greased device, mostly for downstrokes).

17

I cant script for people not setting up their devices correctly.
Here is a perfect example of tip and speed problem. Adding a quick edit that is mostly batch moved and quickfix macroed. Try both and you will understand what this is about.
https://discuss.eroscripts.com/t/heather-harmon-ideepthroat-blue-bikini-my-first-script-please-advise/22959/13

500 is too high in general imho.

2 Likes
18

sure, full strokes hand goes fully up sometimes only the rim. script it like this

image
image286×180 16.7 KB

Tip is involved, speed reduced on wrong side (upper points)

image
image224×169 11.5 KB

Underexaggerated if BJ 30% down.

image

19

Why would they use the scripting software to play the scripts when scriptplayer exists?

1 Like
20

What makes you think I ask them to use OFS as their player?