MultiFunPlayer v1.16.0
Added 2021-10-13 22:08:38 +0000 UTCDownload: https://github.com/Yoooi0/MultiFunPlayer/releases/tag/1.16.0
- Add ability to seek, by clicking on the heatmap, and play/pause video, by clicking on the play/pause button (#24)
- Add ability to customize actions (#21)
- Reduced the number of actions from 900+ to 100+
- Allows custom settings "profiles" by having different values per keybind
- Action settings can be accessed via the wrench button
- Add heatmap stroke visualzation, accesed via right clicking on the heatmap (#22)
- Also allows modifying heatmap quality for different effect
- Add ability to set the window to be always on top, accessed via application settings on the window title bar (#23)
- Fix buttplug.io vibes not stopping under certain situations (#20)
- Small ui tweaks
Breaking changes:
- All previously configured actions will be reset
Comments
Anything that acts as a xbox 360 controller should work, you can also use x360ce to map other controllers to a virtual xbox one. Using VR controllers would be nice to add tho. To control the actual axis value use "Axis::Value::Offset/Set/Drive", the serial range settings only limit the output. The actual axis values, that are always between 0-1, will be mapped to the range slider values, you use those sliders for example to set top/bottom position that works best for you.
Yoooi
2021-10-19 20:58:36 +0000 UTCOh i see now. So could I assign maybe Oculus controller thumbstick to the pitch/yaw axis's then? That might be good as manual control while L0 is scripted. Will have to look into that. Not sure how i tell it what controller to use. Seems to be only "Range" options in serial though - how do you do an absolute "set" type value, and have that driven by a thumbstick?
geo_gan
2021-10-14 16:22:36 +0000 UTCYea I know it can be a little confusing at first, it was tricky to figure out how to generate the configuration UI with as little code as possible when registering the action. So there is no real feedback and the UI cant be anything complex, its just a list of "description-value" fields. All of the "::Drive" actions have to be used with "axis" type gestures, for example mouse X/Y axis, or controller thumbs/triggers. Basically the value will follow the mouse/thumb/trigger position. I'm planning on adding type filtering so "::Drive" actions would only be visible when editing axis type gesture.
Yoooi
2021-10-14 10:17:47 +0000 UTCGreat. Thanks. Just remapped keyboard commands to the Serial axises again using new system. Was a bit confusing to figure out but intuitive enough to figure out in a few minutes. i can confirm the new system still working now using Stream Deck keyboard commands. I am using the Offset function mapped to buttons to change max/min and position of LO and range of R0. One question - what does the new Drive function do?
geo_gan
2021-10-13 23:46:06 +0000 UTC
