Being a SW developer myself I tend to agree. However, since a bugfix already exists, merging it into the free branch should be easy.
I’ll try what you suggested or just use an older version of MFP to see whether that works.
By the way, how does the Polled Update work?
And how many hertz does it generally make?
It only updates on each script action, so it depends on the script. Polled update only supports speed limit and auto home, everything else does not work with it.
Its used for devices that cant handle a lot of data, so instead of sampling at 100hz+ with Fixed Update and sending small moves, Polled Update only sends longer moves on each script action.
If you are creating a script in real time and adding a new point at 100hz then Polled Update does not make sense to use as it will behave like Fixed Update.
kk i try:
This is fixed update:
This is polled update:
Fixed update is spammy and tells the device to move every tiny interval. Polled update only does it once where there’s a point in the script.
I have no idea why PolledUpdate behaves funny with your mod. It makes everything smoother but shortens the stroke length.
Ahh, does fixed update feel sawtoothlike at times with tempest devices?
Why? You add 10% scale then or so?
Not really? You also get to choose pchip interpolation with FixedUpdate which makes it smooth around the corner, which isn’t available for PolledUpdate.
This is in reference to another topic that you don’t have context of…
K so which is best setting in your opinion for those who dont want to fully get technical?
What funscript axis-like postfixes can I use for SLR funscript format? (the {axes:{actions:[]}} one)
Hmm, I’m looking at the code and it seems like it looks for <filename>.*funscript
Does that mean I can name a sctipt my-animation.ors2.funsctipt and it’ll match?
Technically any, but it makes sense to only use <video>.funscript
No, you would have to add osr2 to funscript names in device settings in MFP.