Yes
I have a Mouse4 Press action (not Click as press is faster) for -5 max L0, Mouse5 for +5, and another button for set to =80
This is annoying (ik I can workaround but I fail sometimes)
2025-01-18 04:21:07.7233|ERROR|Stylet.BootstrapperBase|Unhandled exception|System.IndexOutOfRangeException: Index was outside the bounds of the array.
at MultiFunPlayer.UI.Controls.KeyframesHeatmap.UpdateRange(Span`1 buckets)
at MultiFunPlayer.UI.Controls.KeyframesHeatmap.Refresh()
at MultiFunPlayer.Common.ObservableConcurrentDictionary`2.<>c__DisplayClass12_0.<NotifyObserversOfChange>b__0(Object _)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
2025-01-18 04:21:07.7233|FATAL|MultiFunPlayer|System.IndexOutOfRangeException: Index was outside the bounds of the array.
at MultiFunPlayer.UI.Controls.KeyframesHeatmap.UpdateRange(Span`1 buckets)
at MultiFunPlayer.UI.Controls.KeyframesHeatmap.Refresh()
at MultiFunPlayer.Common.ObservableConcurrentDictionary`2.<>c__DisplayClass12_0.<NotifyObserversOfChange>b__0(Object _)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
Caused by negative keyframes or whatever
Could you please crash when I try to enter the invalid state by pushing bad keyframe or whatever
Thank you! this app has lots of nice features, i just have to ply around with it some more. Got it working. Thanks again 
I’m having an issue where MFP won’t connect properly to Intiface using a Lovense Edge.
When I search for devices in Intiface to check, it finds the Edge no problem. Since I read in some thread that searching within Intiface and MFP clashes, I close everything, restart the toy, replug the Bluetooth dongle.
When I start Intiface again and start the engine, the light on the dongle becomes static. Next I start MFP. I managed to add V0 and V1 axes by cloning the TCode 0.2 device. When I connect to the Buttplug output, the light on the toy goes to static, so it does connect somehow. However, no output from the toy and after ~20-30 seconds the Buttplug output in MFP disconnects.
Intiface log attached:
One thought is it might be worth updating your Intiface, they’re up to 2.6.5 now so you’re quite a few versions behind.
That was fixed in v1.31.3 or later, it was a bug in the library used for connecting to buttplug
So in other words, without paying for MFP, Intiface/Buttplug support is not existent?
Paywalling features is standard practice, but bugfixes?
Thanks, but I mainly use it to connect to Handy via BT when their servers are acting up and there’s a thread somewhere around that advises against updating.
If you want to call it that then sure, the updates will be released on github eventually. Bugfixes still take time to implement, bugs probably take more time than features.
And I would not call buttplug support not existent, the bug is caused by one of the messages sent from intiface, and it is pretty rare. I could not reproduce this message on my PC, it should be sent mainly on android.
If you really want you can recompile MFP with the updated library, or maybe download latest Buttplug.NET dll and try replacing it, but not sure if MFP will start.
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.