hypnoticSwitch
patreon
Version 1.1.Beta1
🕑 Added 2019-02-22 11:00:08 +0000 UTCAlpha supporters reported next to none bugs. I was still busy and fixed a few things that needed fixing and updating.
Changes from 1.1.Alpha1:
- little improvements to hub scene and menu
- fixed file format to be readable by older versions
- fixed bugs in audio file parsing
New to v1.1:
Improved Session Info Screen with more infos
I had a bit of trouble with this one. I think it turned out okay, but since I realized I want to give the whole GUI a complete visual overhaul, I feel a bit unhappy with the GUI as it is now in general. The new screen lets you know the exact length of the session and which features it uses. I probably forgot something, so please let me know, ok?
Pose (Lying, Sitting, in-between) can now be changed in Hub Settings (only relevant for VR)
A long-requested features, being able to comfortably use MMM while on a bad or a reclining chair. In the Settings you can now adjust the position, there are three presets and you can finetune it as well. I hope you like it!
Re-enabled spiral switching in in-session menu
The feature is back. You were right, it is nice to be able to change the spiral from sometimes.
removed several buttons from 2D mode that are only relevant in VR mode
There were quite a few buttons that were totally useless when MMM was run in 2D. Like for example locking the spiral to your head. They now are only available in VR mode. No more trying to click buttons that have no effect.
So, let's test the hell out of it, ok? And let me know of your thoughts you have on everything!
Downloads
Windows (contains shortcuts / batch files for 2D, OpenVR, Oculus)
Android 7.0+ (supports 2D / Cardboard / Daydream)
Android 4.4+ (supports 2D / Cardboard)
Oculus Mobile (Samsung GearVR / Oculus Go)
Comments
Had an issue in the Windows version after deleting an MMM session that I loaded. The MMM file was an older file I'd created. When I deleted it, I was left with a screen with no buttons to allow me to go back to the main menu. This issue has happened before in a previous version, the bug must have crept back in.
