Skip to content

Expanding audience to non-MixedVR users, added install/uninstall scripts, reduced prerequisites by 50%
Compare
Choose a tag to compare
@monstermac77 monstermac77 released this 09 Feb 05:45
· 13 commits to main since this release
v1.4
869c051

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.

Assets 2
Loading