Releases: monstermac77/vr
Minor instruction changes
Made it more clear what users need to do to get the MAC addresses of their lighthouses. If you want to read full release notes for recent major release, v1.4, click here: https://github.com/monstermac77/vr/releases/tag/v1.4. There is no functional differences between 1.4 and 1.4.1.
Expanding audience to non-MixedVR users, added install/uninstall scripts, reduced prerequisites by 50%
This release allows for users to easily toggle MixedVR's management of basestations and/or the HMD on/off, opening the potential audience of MixedVR Manager to non-MixedVR users:
- Index/Vive/Pimax users may want to use MixedVR Manager for more reliable management of their base stations.
- WMR users may want to use MixedVR Manager for enabling/disabling their HMD and automatic closing of Mixed Reality Home.
- Oculus users may want to expand MixedVR Manager to enable/disable their HMD, and manage Oculus home.
The less niche the audience, the more convenient the setup required. This release merges in incredible work by @timberrr (/u/defenestratedDM) in pull request #9 to reduce the setup complexity by an order of magnitude, and eliminate a nasty prerequisite we had, which was disabling UAC (an action most users felt uncomfortable with). The install script creates a task in "Windows Task Scheduler" which starts MixedVR Manager as admin whenever the user logs in. These permissions allow MixedVR Manager to enable/disable the HMD without a UAC prompt.
Other bug/quality of life fixes rolled into this: Mixed Reality Home is now being killed immediately when SteamVR is closed. This prevents users from seeing the nasty errors Mixed Reality Home shows when it can't find the HMD, which was leading some people to incorrectly think MixedVR Manager was doing more harm than good. Moreover, the uninstall script now re-enables the WMR HMD. A number of users wanted to try MixedVR Manager or disable it temporarily, but were dismayed to find their headsets "bricked" even after killing MixedVR Manager and restarting. The install script also includes a notice that encourages reading, explaining that SteamVR is expected to shutdown during the start-up process, which many were dismayed by. Finally, if the user quits SteamVR before Room Setup opens, or never opens and they quit SteamVR before 90 seconds, we now immediately initiate shutdown rather than waiting 90 seconds; this seemed to be causing users to think the shutdown procedure wasn't working, which is understandable because 90 seconds is a long time.
Hotswap configs, prevent HMD disabling, UAC whitelist deprecation
This release mainly is to address issues people are having with the HMD not disabling. This is because our whitelist approach for USBDeview simply was not working. Please see issue #7 for more information or to help get this working.
We now provide two alternatives to changing to "Never Notify". One is just clicking "yes" every time it prompts, which is obviously pretty crappy. The other one is turning off the HMD enabling/disabling in config, which was a planned feature anyway. This also includes a mod for hotswapping configs, so now you can change what's in config.bat after the program has started up, and it'll use the new values.
This is a slight risk if someone puts a ton of gibberish in the config, but we think that's unlikely and it seems no matter what they put it won't crash the script.
Production edition with lighthouse-keeper
This is the production release of v1.3 but also has a small addition allowing the configuration of the path for USBDeview, which is highly relevant to those who whitelist only USBDeview in UAC, rather than changing UAC notifications to "Never notify". Thanks very much to @timberrr for this pull request.
Introducing lighthouse-keeper: more reliable and faster lighthouse management
@rossbearman has done a phenomenal job creating lighthouse-keeper, which allows for the discovery and power state management (on/off) of both 2.0 and 1.0 lighthouses. This is a big improvement over the existing binaries that MixedVR-manager was using. Most notably to users: starting and stopping your VR sessions will take about half as long as they did before. Moreover, you'll experience a lot fewer instances when one lighthouse remains on and the other is off, requiring you to turn on/off SteamVR a couple times to get them both into the correct state.
The time for MixedVR Manager to complete all startup events (given two 2.0 basestations) is about 38 seconds (down from 60 seconds), and the time to complete all shutdown events is about 26 seconds (down from 34 seconds).
This release includes lighthouse-keeper v0.1.0
Fixed issue where 1.0 lighthouses would be stuck on "Press enter to continue..."
Thanks to TommyVR in the MixedVR discord for sticking through the debugging with us on this.
Added support for version 1.0 lighthouses
Huge thanks to @rossbearman (Tetracyclic) for doing most of the work here.
Added ability to maintain SteamVR Home and Chaperone (optional features)
Because SteamVR can often, and randomly, delete the home you painstakingly created, and also slightly, or drastically, adjust your chaperone bounds or playspace, this release allows you to save the relevant files in a userdata folder that will overwrite SteamVR's copies on every launch, preventing any such loss.
Fix for Windows Defender blocking .exe
Apparently Windows defender blocks the mixedvr-manager.exe, simply because it's an exe not a bat. Instead of having to make people allow for this and deal with that extra setup, decided it was better to just use a vbs file that silently launches the .bat file on launch. Thanks to DayApprehensive6531 on Reddit for discovering this.