



To learn how to join beta testing, see the article



Of course we are still in the testing phase of features added with 2.2 patch as well. You can read about them



Deployment status:

Viveport: awaiting approval

Oculus Home: awaiting approval

Google Play: in beta @ 2.2.5 ( We have additional Beta patch release that addresses the issues reported with the Beta version. This version is a release candidate so if there are no major issues it will go live to everyone in a short time.To learn how to join beta testing, see the article here Of course we are still in the testing phase of features added with 2.2 patch as well. You can read about them here Viveport: awaiting approvalOculus Home: awaiting approvalGoogle Play: in beta @ 2.2.5 ( join





New distribution method for Gear VR and Oculus Go

We are awaiting approval at Oculus Home - please use normal Sideload method for now Installing Gear VR and Oculus Go version was really troublesome. That’s why we intend to finally make VRidge available on Oculus Home store. Before we do that, we need a way to easily install Beta releases for this devices - Beta versions cannot be live on the store as it’s opt-in only.



That’s why we went for code distribution method. Every RiftCat user will be able to generate special key code which will install VRidge Beta after entering it in Oculus Home store. To learn how it works - simply read our tutorial here

New languages available

Thanks to your great translation effort via CrowdIn we were able to update previously added languages and deploy six new ones. These languages are:

Hungarian

Indonesian

Italian

Korean

Lithuanian

Bulgarian

There might still be mistakes in translations but we believe that with each review phase at CrowdIn our community will be able to make them perfect.





You guys are awesome and are doing tremendous job. We strongly believe that we have the best VR community there is - we can always count on you, that’s why we will do our best to never let you down!

Enhancements

Multiple Android optimizations

CPU usage should be lower across all Android devices.

On average, you should see 15-20% system CPU load instead of 50-60%

This also means that heat generation should be significantly lower resulting in less "device too hot to run VR" errors.

In extremely rare cases this may lower VRidge performance. See this explanation to disable those optimizations.

This should be quite noticeable at 1440p resolution as unintentional downscaling and filtering was in effect until now.





It should improve image quality, especially on headsets with asymmetric FoV.





Instead of displaying message (in one eye only due to very old bug) it will go back to lobby with localized notification message.





This will be expanded upon as we apply to Oculus and Daydream storefronts.

Fixes

Fixed Nolo wireless mode coords going out of sync after recentering. Wired mode didn't have this problem.

Fixed Oculus Go / Gear VR touchpad jumping to top-left corner for a split second after taking the finger off the touchpad.

You will no longer be able to switch encoder when HEVC is enabled. This doesn't hot-switch on mobile side and it was freezing VRidge.

VRidge logo no longer will be upside down on startup on some devices.

Fixed a crash on startup that could happen when FreeTrack was enabled.

Reduced error spam in RiftCat.log related to DialogHost errors

VRidge's recenter hotkey will be disabled when mobile device is driving positional tracking. This fixes system going out of sync when positional tracking was in effect and user pressed recenter hotkey. In this case, the device should use its own recenter. With Vive Focus, for example, taking the headset off and on will reset its coords system.

steamvr.vrsettings read-only flag will now be automatically switched off. If the file still remains locked, error message will be displayed instead of crashing. Generally other software should never lock this file but certain drivers aren't always interop-friendly.

VRidge and SteamVR should now automatically start on dedicated GPU, if available. This should fix a crash on Nvidia Optimus laptops.

VRidge.log will now contain information which GPU drives VRidge.

Hotfixes

[August 2nd] Fixed driver crash on Windows 7.

[August 3rd] Fixed invalid projection (incorrect vertical FOV) on certain Daydream headsets (Daydream View being one of those).

[August 6th] Revert: VRidge's recenter hotkey will be disabled when mobile device is driving positional tracking.

Closing notes

This update brings us very close to final 2.2 version release. We don’t expect any major issues with this version but if anything will show up, let us know - it is very important to make this version error free. Soon every VRidge user with Vive SDK, Daydream SDK and Oculus SDK compatible device will be able to have fun with jitterless VRidge!





Thank you for all your work during tests. We hope that you will have a pleasant experience during this last testing phase.