Awesome, your tool is getting better and better. Can not imagine scripting without it anymore.
Doesn’t work yet for me, you take a fixed limit I guess 500, I use 600 so still pink parts. I guess you will have to read out the value if thats possible?
The default is 600, but you can change that yourself. The speed shown in OFS can be a little different due to rounding errors. (The “pos” is rounded to an integer value when they are committed back into OFS after lua processing in the extension). If this is a problem, you can try to “max speed” to 590 or so.
Just changed “main.lua” to ensure roundoff always leads to lower than max speed, so you should not see the pink lines now.
1 Like
Ah OK thought 500 was default. Can only test tomorrow.
Tested and ermagherd this is so cool, 2 clicks SelectPeaks Bottom and Lim and its done and as perfect as it can be in a second. Without this it takes 10+ Minutes or you may end up just moving all points up until the speed fits which is never optimal. Also the points are just at the edge. Move a low point down by one and the speed gets too fast purple. Its perfect, this macro rocks!
Could you write down what each of your macros does in the first post? I know the ones I always use but I forgot already what Norm.7 does for example. In OFS there is no way to show is there? Like mouseover for x seconds or so?
AFAIK there is no mouseover option in the lua gui. I am considering to add a “help” option to show a few lines of explanation after clicking a button.
That would be cool. Is button colors possible in the options or the lua itself to set single buttons to different color? Idea came to me when I had the “wheres the button” last time. I would color te buttons I use most the minmax, invert, Lim and repeat 1 those are just following an MTFG run. If it was me they could go into a category.
Found another macro accidentally in the twist thread that would be great to have. If I or other scripters flatline pauses, which is bad, it can be a pain to change them all manually so an unflat macro would be great. Meaning if you discover a not too long flat line, to exclude real pauses, then add 10% to the next point into the direction the third point is. Is that possible?
to this
if it works you could one-click unflat this script
https://discuss.eroscripts.com/t/aletta-ocean-best-handjob-ever/151131/6
So for rotation the idea would be to macro generate a R0 twist from this, which is the twist in L0
to this
The rotation is generally longer but it’s a start that would really spare a lot of time.
Repeat 1 seems obsolete as you could do a minmax before using repeat 2 would be the same it seems?
it is not exactly the same. “repeat 2” keeps the top and bottom points, and fills in the falling and rising parts with the falling and rising parts of the pattern (time and positions are all scaled). “repeat 2” removes the bottom point and fills the space in between with the pattern, where only the time is scaled to fit.
1 Like
About the R0 rotation macro. Talked to Slibowitz and it is unsure if it works well but would be great to try. You did so much already to make scripting faster so I almost dont dare to ask for it.
What would you consider the shortest “real pause” that should be kept flat by the script?
The longest I saw in my actual script is 230ms so I guess 250ms should be max. I think this is to be tested if old scripts are converted if there is to many false positives or some not recognized by the macro. This macro could be super useful or fully useless I am quite unsure but definitely worth a try if its not too much work for you.
- <250ms
- at top or bottom of curve
- 0-30% difference between top/bottom and next point
- twist speed in R0 ??
Edit found twist pauses that are 20%
@quickfix I have another idea that could work fine by calculation and would spare us alot of time.
I just left out a pause but due to is speed its quite clear that there is a pause. So you could ask the user if lower or upper pause or make two buttons for it. Can you put a point 10% higher or lower so the speed matches the next line? The point you set there to match up and down speed will fit for 99% of the cases I think.
So after you set the endpoints you could just click a upper or lower autopause.