Small QOL changes
Several people suggested to hide the vertical white bar because it was visible in the viewport. It will now automatically hide after 10 seconds. Settings button will now automatically dim by 70% too.
If you want to align your cardboard to the screen, tap anywhere to show the vertical bar again (it will disappear after 30 seconds after manual toggle).
![]()
We also added "Never ask me again" option for bluetooth prompt so it won't annoy you anymore. We're leaving a small note at the bottom if it's online.
There were some other changes, optimizations mostly but nothing worth writing about. Some bytes were spared. Some bytes move a little faster.
If you want to align your cardboard to the screen, tap anywhere to show the vertical bar again (it will disappear after 30 seconds after manual toggle).
We also added "Never ask me again" option for bluetooth prompt so it won't annoy you anymore. We're leaving a small note at the bottom if it's online.
There were some other changes, optimizations mostly but nothing worth writing about. Some bytes were spared. Some bytes move a little faster.
SteamVR driver progress
As some of you noticed you had to reinstall our SteamVR driver after yesterday's Steam update. Next version of our driver will be properly registered with Steam API and won't require reinstallation anymore. Actually it won't even require manual installation, it will be done automatically.
We are not entirely sure but after some changes in our pipeline it seems that SteamVR latency is even lower now. It's hard to measure but it all seems more fluent.
New version will also allow better context switching between VR apps. More on this when it's out.
The ongoing battle with artifacts - frame loss / latency @ decoder
This is very annoying problem because whenever we finally think "Okay, that was it, fixed" something new comes up. This is the issue that can be identified by tapping top-left part of the streaming screen and seeing high (above 0.1 ms) decoder latency and constantly raising Frames lost @ decoder counter.
We had ~30 reports of this happening and we can now share some data - this is top 8 of reported problems.
We had ~30 reports of this happening and we can now share some data - this is top 8 of reported problems.
| Phone name | Reported cases | Install count | % | Chip |
| Asus Zenfone 2 | 5 | 89 | 5.62% | Intel® Atom™ Quad Core Z3580 |
| Galaxy S4 | 5 | 84 | 5.95% | Exynos 5410 | Snapdragon 600 |
| Galaxy S7 | 2 | 125 | 1.60% | Exynos 8890 | Snapdragon 820 |
| Galaxy S7 Edge | 2 | 339 | 0.59% | Exynos 8890 | Snapdragon 820 |
| Redmi Note 2 | 2 | 60 | 3.33% | MediaTek Helio X10 |
| Nexus 6 | 1 | 110 | 0.91% | Snapdragon 805 |
| HUAWEI Honor 6 | 1 | 8 | 12.50% | Hisilicon Kirin 910 Octa Core |
| Xperia Z C6603 | 1 | 28 | 3.57% | Snapdragon S4 |
Galaxy S4 has the most problems. There were 2 users reporting hard device crashes.
Zenfone 2 also has constant artifacting. No crashes were reported but it is still unusable if it's turning into blocky pixel mess after several seconds.
Galaxy S7/Edge seems to have something special about its decoder too.
These numbers are high because when we look at top 10 most popular devices of our users (S6 & OnePlus One leading the pack) there are 2000+ installs shared between them and 0.1% error report rate. Also, the reported errors are probably caused by something else because there were more issues than artifacting there.
One thing I would like to know. Is there anyone that got VRidge to work successfuly with bolded phones in the table?
Please let us know if you got it to work. I know about one Zenfone 2 user that fixed it by changing CPU governor to interactive but the same didn't work for other phones. Send us an e-mail, PM @ reddit or use any other contact channel listed at the right column, at the top of the page.