Hello to all Whirligig users So I've been working on an OpenXR release for a long time. Trying to get all the controllers working, testing with multiple setups, WMR, Oculus and Vive headsets and multiple controllers, Quest, Quest2, Rift, Index, WMR and Vive original. After a few weeks of testing, community feedback and bug fixes this is that OpenXR default build release. [h3]Overview of release[/h3] This is a major update to the core of Whirligig with a switch over to the OpenXR sdk. I really don't want to break anyones enjoyment of Whirligig but for me to continue support and add new features this is something that needs to be done. To reduce the chance of disruption I'm not removing the old builds from the beta list. If you have issues you can change back to the default build. I've also included a new version that uses SteamVR instead of OpenXR incase some headsets have issues with the OpenXR SDK. Here is a summary of those builds with a guide to changing to other beta versions. [h3]How to change to other beta versions[/h3] Steam's beta program is very easy to use and you can switch between versions in seconds. Here are a couple of guides. [img]{STEAM_CLAN_IMAGE}/12189003/11776107d7fb9c4eb03ea6fc6c4f4db26c705518.png[/img] I've also created a tutorial on Youtube: https://youtu.be/z9pv-cgn4IE [h4]Beta version - None[/h4] None means that you'll use the default build. The default build is the version that'll you'll automatically download when purchasing Whirligig. Updates will happen to this build but will go through a much more rigorous testing process before release. [h4]Beta version - whirligig_early_access_v.4.881[/h4] This version was the previous default build released 2021. If this major update causes problems and you wish to return to the previous version choose this one. This version will not be removed and once you've chosen it any updates to the main build will not automatically update your version. [h4]Beta version - whirligig_openxr_early_access_v.4.9841_steamvr[/h4] The latest build uses OpenXR as it's core SDK. This version has been created with the SteamVR SDK. This version has been provided to support headsets that aren't fully operational with OpenXR. If you have performance issues that could be related to OpenXR try this version. Although this version is based on the latest build it won't be updated unless requested. [h4]OpenXR Update[/h4] [h3]Core SDK is now OpenXR[/h3] So if you follow any VR news you'll know that OpenXR is a big deal and will help to ease development for porting, new headsets being compatible out of the box and overall improving the VR experience. Whirligig up until now has had two SDK implementations, Oculus and SteamVR. I've removed these and replaced them with the OpenXR system. [b]Advantages of OpenXR[/b] OpenXR is in constant development with improvements that will carry down to all headsets. You will be able to use your headset with the VR front you desire. OpenXR is fully compatible with SteamVR, Oculus Store and Windows Mixed Reality Portal. This means when using Whirligig from Steam you are not forced to use SteamVR. With direct support from each platform any performance improvements those platforms use will be filtered down into Whirligig. OpenXR implementation has meant I've removed the input options for both Oculus and Steam replacing it with a universal controller and some core controllers to use. You could select different controller skins when using Oculus. Now this feature is available on all setups. Quicker updates to other platforms. As all builds have been brought under one sdk I can now release the same version on different platforms with little change to the code. This will help to reduce bugs being introduced into other versions when updating and help my confidence that when I update I won't be breaking everyone's experience. I can develop for both PC and Mobile headsets at the same time. [b]Disagvantages[/b] OpenXR is new and in constant flux. For development this is both advantages and crippling as currently every update to the SDK can cause issues in multiple ways. This will improve greatly over time but currently it's making supporting some headsets (mostly mobile headsets) quite difficult. Some features aren't working. Basically the UserPresent (what happens when the headset is put on or removed) feature isn't working properly. I will be implementing this back in once it's back up and running. [h4]Feature Updates[/h4] [b]Thumbnail view in explorer[/b] [img]{STEAM_CLAN_IMAGE}/12189003/334adc26f25cd1a80de596f80f27a62b6a7f3e25.png[/img] There is now a thumbnail option within the explorer. This option allows you to view all your video or images with a thumbnail view. Loading thumbnails can take up some resources so some caching of thumbnails occurs to speed up reload times. This addition is quite complex so there might be bugs that still need looking into. If you have issues switch back to the standard explorer which is much more stable. If you have issues let me know so I can address them for the next update. [b]Presets include some standard options for easy selection[/b] [img]{STEAM_CLAN_IMAGE}/12189003/c68117949fd636fe06bb6cd904e3b20f3559905d.jpg[/img] These include Cinema in void (has a reasonable curve on it), 180 fisheye (good for fulldome content) Equirectangular (what most 360 films are in) and cinema environment (where you're actually in the cinema. [b]Surround sound support.[/b] [img]{STEAM_CLAN_IMAGE}/12189003/80f67b52e0f980747729e2b0f6d00526ff885d0c.jpg[/img] If you are playing videos, which include 5.1 audio tracks they can now be viewed with positional audio. This option also includes levels for each channel which is good if you wish to boost the voices in a film (voices are mostly in the front centre channel). For this feature to work you are required to be in either Media Foundation or RT video path. Whether you can play back the 5.1 audio depends on the compatibility the video has with Media Foundation. [b]Update to main UI[/b] [img]{STEAM_CLAN_IMAGE}/12189003/a4868aceb78897f9bcec0ab4ffc26d7101705583.jpg[/img] The main UI has been updated to include the presets menu and a mute button for the volume. There have also been some repositioning of the playback options to be similar to other media players. [b]Update to the controller UI[/b] [img]{STEAM_CLAN_IMAGE}/12189003/373d3decd70d66e416e801b149cf37b61f82cc5d.jpg[/img] In previous versions the functions on the controller have been a bit rudimentary. This has been updated entirely with all your easy access functions, play, pause, media timeline, volume, next/previous media, time (what time it is so you don't have to take your headset off to find out), audio menu and subtitle menu. This menu can be activated by simply point the laser at the other controller. It will disappear after a few seconds so not to get in the way. [b]Input control skins now available in all version with additional controller options[/b] [img]{STEAM_CLAN_IMAGE}/12189003/b87bb91a7b2a4837874ac42c270ce0e2170def0f.jpg[/img] As mentioned before a lot of work has been done on the controllers. Here are a few screenshots that illustrate some of those options. [b]NDI Support[/b] If you work in production you might of come across NDI. NDI is a way to send video over a network and be picked up by other devices. This is useful for previewing video streams from programs such as After Effects and VJ software. [b]Everything Else All At Once[/b] There have been numerous other updates including a host of bug fixes and optimisation. I can't list them all here but rest assured they have happen :) [b]And Finally[/b] So this will be a very big update to the main build and as such it worries me greatly. I have been working on this for a long time and with any luck it will improve my overall development and support for other platforms and speed up the addition of new features. For me to be confident enough to update that main build I want feedback from anyone who's giving this build a go. Bugs are the most important thing to bring to my attention and if you can explain them in a way I can recreate, I will do my best to fix them. I really apricate the support I've had from the community over the years and really want to continue to update and improve Whirligig for everyone. It's not possible to make a living on the income I get from Whirligig and it's the tightknit community with their desire to fiddle with every setting that has helped to keep Whirligig relevant for some. All the changes I've made are to help me continue to support Whirligig and continue to make it relevant for future media watchers. I thank you all and I hope to continue to improve on a product that works the best for you. Keep watching :) All the best Phil