Wednesday, August 23, 2017

Dev update #33 - CPU optimizations and NOLO tweaks

We're deploying few tweaks and fixes. They are already available in Gear VR beta channel and should be available for all other Android devices later today.

Latest beta versions are:
  • Gear VR: VRidge for Gear VR 1.5.0
  • Android: VRidge 1.5.3 
This is mobile side update only. You don't need to update desktop clients.


---

Tracking update rate fixed

In version 1.4 we introduced a new networking protocol but the implementation wasn't optimized too well. It resulted in many tracking frame drops every second (up to 20). If you are used to 60+ FPS gaming it probably felt terrible because the tracking update rate was hovering around 40 updates per second.

CPU optimizations

We're also changing synchronization model to put lower load on CPU. It should greatly reduce heat generation and battery drain compared to v1.4. On average, your CPU load should be reduced by ~50% compared to v1.4. In case of Pixel XL or Galaxy S6, VRidge CPU load should now stay below 20-30% (measured with Android Studio + ADB).

NOLO wireless changes

  • We're following an advice from NOLO and we're changing default tracking mode so the phone sensors are used for rotational tracking. You can still switch to NOLO IMU in mobile app settings but generally we found that phone sensors have lower tracking latency.
  • We weren't aware that NOLO hardware has recenter built-in at the firmware level. See calibration paragraph below for details.
  • We're removing nolo flip-around hotkey. It might come back in the future if many people request but currently it was causing too many problems with mixed tracking mode.

NOLO wireless calibration

  1. Put your headset on, turn on controllers and spin them around for 10-15 seconds. It can take up to 10-15 seconds for the magnetometer to become stable. It will be probably in wrong rotation when it stops drifting.
  2. Double tap system (bottom) button on both controllers. Re-center is per controller so you can recenter them individually. VRidge will also register this hotkey as "recenter" so it won't go out of sync.
  3. [Optional] Press system button on any of your NOLO controllers and go to settings in SteamVR VR dashboard. Hit "reset position in there" to make sure you are at the center of playing field.

If you feel that your height is wrong or controllers are out of sync with your head rotation, run SteamVR room setup by right-clicking on SteamVR floating window and selecting "room setup" in there. You may need to run room setup again if your relative position to the base station changes.

NOLO wireless + VRidge for Gear VR 2017

Galaxy phones plugged into Gear VR 2017 can host both Gear VR and NOLO devices which enables fully wireless experience in this scenario.
  1. Install VRidge for Gear VR 1.5 Beta (if you have installation problems, please see this article).
  2. Plug in your NOLO into Gear VR with Micro USB - USB-C cable. You need to have it connected before you start VRidge.
  3. Start VRidge for Gear VR app so it's on "Please insert your phone into Gear VR" screen.
  4. Insert your phone into Gear VR.
  5. [Just once if you select "always use this app"] You will be asked which app do you want to use with NOLO. Select VRidge for Gear VR by looking at it in VR and tapping your GVR touch pad. You can select "always use this app" to skip this step in the future. You can always reset this "always use this app" by long pressing VRidge icon to access Android app info and then clearing defaults in "set as default" subscreen. If your VRidge (Cardboard) is always launching first without an option to select GVR edition, you might need to clear its defaults in the same way.
  6. Start SteamVR as usual in desktop app.

Things that are missing

We want to finish NOLO integration by implementing following things:
  1. Vibrations.
  2. Top-down tracking mode, or at least trying to do it with mobile SDK.
  3. Throwing things. Currently controllers don't provide their acceleration / velocity in mobile SDK so throwing motion doesn't work properly in some games.
We need to work with NOLO devs to code 3&4 properly so we don't know which of these will come first. They are quite busy with their driver too so it sometimes takes a bit to get all the answers and changes we need. We can sort of do 3&4 on our own but we don't want to release it as a temporary hack without future-proofing it by working with NOLO devs directly. We want to be sure that our hacks are not broken by some future firmware update

In the meantime we're still working on a lot of things that are not related to NOLO, we should have more news in upcoming weeks.

Construct VR shutting down

Yesterday Construct VR announced that it's shutting down its platform. We are looking at other solutions to host VRidge for GearVR app but we don't have replacement ready yet.

We're very surprised to see this announcement. Construct VR team and platform was a pleasure to work with and we're really sad that their journey ends here. We wish them luck in their future endeavours. Your contribution to VR world will be remembered!

Monday, August 7, 2017

Dev update #32 - NOLO untethered



Today we are releasing version 1.5.0 to the beta channel. It comes with NOLO VR wireless support. It's not 100% finished but we wanted to start gathering some user reports to make the next version better based on your feedback.

Updates:
[1.5.2] - We're changing the way tracking status is interpreted. If you had tracking issues with 1.5.0, try again with the new version. It should be available in Google Play 7PM UTC at the latest.

Known issues:
  • Tracking may have decreased send rate, resulting in more frame skips (up to 20 dropped rotation frames per second).
  • Controller rotation and position may go out of sync in respect to head marker after recentering.


Nolo untethered

General info

In dev update 30 [http://blog.riftcat.com/2017/06/dev-update-30.html] we described reasoning behind implementing NOLO VR wireless mode. Today we are releasing first version of it to the beta channel.

There are few things that are not working correctly yet:
  • There are no vibrations yet.
  • Recentering may yield unstable results. You can turn controllers off and on again while holding them forward to make sure it resets properly.
  • Sometimes controller rotation jumps ~30 degrees to the left. We're not sure if it happens to our hardware unit only. We asked for another set from NOLO to test it further.
We plan to continue our work to fix above problems. We should have another update ready for you next week.

Connecting

You need to update both desktop and mobile app to the latest beta (1.5.0).

To use NOLO VR in wireless mode simply plug it into your Android micro USB port with USB data cable. VRidge popup will ask you for permission to use this USB device. Check "remember my answer" and then tap "allow". From now on, VRidge will automatically start the moment you plug your NOLO VR device. You can later revoke the permission by going to Android application settings if you want.

Tracking modes

When NOLO VR is plugged in, you will have another option in VRidge mobile app settings. You can toggle between NOLO VR sensors and phone sensors to handle rotational tracking. Your experience may vary from device to device. If you find the NOLO VR rotational tracking to be laggy in your case, try switching to phone sensors and see if it's smoother if you use your phone as rotational tracker.

Keep in mind that "Phone sensors" mode is still experimental as it fuses data together from two reference systems to create final 3D pose. It might yield incorrect results (controllers could be backwards, yaw might be skewed, etc.) This mode needs some extra tweaking and we might drop it completely in the future if no one uses it. Let us know if you find experience less laggy in this experimental mode.

Usage

If you started VRidge while NOLO VR was connected it will work out of the box. You don't need to install anything on your PC. We added two key combos for extra convenience. These hotkeys don't work in experimental mixed tracking mode (with phone sensors as rotational tracker).


Double tap menu buttons (upper buttons) while controllers are next to each other to recenter position and rotation

Double tap menu buttons (upper button) while controllers are apart to turn around

Rotation is still being tweaked so you might get odd results sometimes. The threshold between "next to each other" and "apart" is 10cm.

Testing sensors

If you want to see raw NOLO VR hardware data you can long press NOLO VR option in VRidge settings. This option is visible only when VRidge was started with NOLO VR connected to USB port with granted permission to read USB data. It can be useful to test if your trackers drift or have some other oddities. Rotation is displayed as quaternions which are very unreadable structure from human perspective but all you need to know about them is the fact, that those numbers shouldn't change a lot when your controllers or head marker are not being rotated.

Blurry right eye (certain Galaxy devices)

We've been tracking this bug for a while but we could never reproduce it, which made it really hard to fix. Recently few redditors suggested that it's a problem limited to Snapdragon only.
Galaxy S7 and S8 come in two variants. US edition comes with Qualcomm Snapdragon chipset and almost all other countries get Exynos edition. We checked and it seems that we have ~10 confirmations total that it's indeed a Snapdragon only problem.
Now that we know that we cannot reproduce it with our unit we took some other steps to attempt to fix it. We will soon have upgraded Gear VR renderer. We're going to send test APK to few users that are willing to test if the new version still has the problem. We are also in contact with some people at Samsung. We are trying to create minimum reproducible test case so we can ask them to help with this problem. We will keep updating you on this topic. With all the additional details and help, maybe we will be able to fix this once and for all.

Update: It seems to be fixed in updated rendering framework internally. Next Gear VR update will no longer have this problem. Many thanks to all the people who volunteered to test our debug builds!

API v3

This beta update also includes new version of API which uses Protocol Buffers as serialization layer. We needed to move from default .NET serialization because it had few things that were not very portable (byte layout, paddings, endianness, etc.). We also created Java library that is used to communicate between NOLO VR devices and VRidge. After we clean up some code and write some docs, we will add it to our VRidge API repo as another way to communicate with VRidge. Making software mods and plugins is pretty cool and can result in awesome new things being created so we want to share with you the same tools and layers that we use when connecting external tracking systems like NOLO VR.

Under Fire VR

We recently hired new programmers. They are still learning their way around VR so they created a small game as an introduction to VR world. You can check it out here:

https://play.google.com/store/apps/details?id=com.Riftcat.UnderFire

It's pretty cool so give it a try if you liked Scorched Earth back in the 90s. Our new developers now moved to other tasks that are much more related to VRidge.

More controllers option

Thanks to our new developers and expanded API we are planning to release few additional controller/tracking options. The first one to come will be based on Xbox controller. It will allow you to move in roomscale game and emulate controller rotation and position with controller analog sticks. It's not very immersive but it may find its use if you are developing VR game without motion control hardware. It's also quite viable option to play some atmospheric experiences where you want to explore areas but lack necessary hardware to trigger some gameplay things.
More advanced tracking options are coming too but it's too early to share details about it.

Other changes and fixes

  • We fixed a bug that prevented VRidge from working on Android O. It's working without any problems now on our Pixel XL with latest Android O (8.0, compilation id: OPP4.170623.014).
  • Connection screen will now turn upside down properly if phone is held upside down.
  • Settings screen will no longer freeze when SteamVR settings file is not writeable.
  • Mobile tracking will now properly switch off when VRidge receives full pose matrix or rotation quaternion through VRidge API (GitHub #12)

What's next?

  • We need to finish tweaking nolo wireless mode. This should be done in a week or two.
  • We're still reworking majority of the codebase for VRidge 2.0 revamp.
  • Our new developers are working on new tracking options.
  • Once 2.0 is out we will focus on optimizng latency and smoothness, jitter reduction and iOS version.

Tuesday, July 4, 2017

Dev update #31 - sound streaming and networking protocol changes




Version 1.4 is an update of both mobile app and desktop app. It's not backwards compatible so you need to update both apps. It's currently available in beta channel.

This update includes two major features - sound streaming (off by default, see paragraph below) and networking protocol changes (designed to decrease visual artifacting).

Keep in mind that it’s a first iteration of those features so you might encounter game-breaking bugs and might need to rollback to stable. You might notice few more minor bugfixing updates on weekly basis in July while we fix reported problems.

There's no Gear VR version yet so keep using stable channel if you are Gear VR user.

Update (11 July): Gear VR beta version is now available here.

Known issues:
  • Higher bitrates may introduce higher than usual latency.
  • Streams may partially freeze (rotational tracking stops working) after few minutes. - Fixed in Android 1.4.1 / PC 1.4.3

---

Sound streaming

We've been delaying it for a while for multiple reasons. We wanted it work with the widest set of devices possible and it took some time to tune all parameters and codec settings to work on all of our test devices. It's first public release so it's highly likely that it won't work anyway on some phones that we didn't test so please send your feedback and bug reports to support@riftcat.com. If you have problems with audio on your Android device, please follow the steps below:
  1. Go to Android app Settings -> Diagnostics and check "Enable diagnostics" in there.
  2. Reproduce the problem by streaming (or trying to stream) with sound for at least 20-30 seconds. Try few times, you can restart mobile app between tries.
  3. Go to Android app Settings -> Diagnostics again and tap "Send bug report". Enter your e-mail address so we can contact you and maybe ask some more questions that could help us fix it.
Currently sound streaming is disabled by default. In this state, it doesn't use any extra resources on mobile or PC side. If you want to enable sound streaming you need to go to PC app settings, expand "Other settings" and check "Sound streaming" box. It's currently buried this deep because it's first public release of this feature so we expect many problems and device specific issues. Once we polish it and fix reported problems, we're going to move it somewhere else in UI. We're changing this screen in 2.0 anyway so we might figure out a better layout for the settings.

Network protocol changes

This is major protocol change and a part of 2.0 changes that should make things better (maybe not initially, but once we tweak it properly). Generally, it should make streaming more stable (in terms of artifacting). This unfortunately breaks compatibility with older versions of VRidge so 1.4 versions of mobile app will require 1.4 versions of desktop app (and vice versa). We know that 1.3 mobile app doesn't work properly on some older devices so stick to stable version if you are using one of those: Galaxy Grand Prime, Galaxy S5 Mini, Blue Advance 5.0. We should have one of those devices at the office soon so we can check out what's wrong with 1.3 and GPU used by those devices.

If you don't want to be bored by tech details, you can skip rest of this section and read last paragraph only.

Until now we were using UDP datagrams to stream video data and tracking data. Adding sound streaming forced us to change our architecture so we can fit more channels (video and sound). Currently new networking layers is set to work in RUDP mode - which means that it will retransmit lost network data. This should mean that artifacts should be reduced by a great lot. Let us explain why.

Video stream is transmitted as a mix of keyframes (I-frames) and predicted frames (P-frames). Predicted frames mostly store differential information (e.g. "the bullet from previous frame moved 5 pixels to the right"). This uses much less data because only movement needs to be transmitted, not the full picture again. This has one major drawback though. If one frame is lost, all following frames that refer to it, will have some sort of artifacts because all next frames are based (at least partially) on information that wasn't received. It's even worse when an important I-frame is lost because it's followed by movement of things that do not exist yet in your stream. It may look like this:

Source: https://www.reddit.com/r/glitch_art/comments/1xgkcy/flip_and_swtich/
It usually fixes itself in a second or two because new I-frame (keyframe) is received and it clears out all visual artifacts that accumulated since the missing frame. Digging down deeper, it's even more complicated because one picture frame usually consists of multiple (sometimes even a hundred) of network frames. If any of these frames gets lost, you get partially broken picture. This manifests itself with floating pixels and frames falling apart.

This is why we want to test how RUDP works out in this scenario. We're starting with RUDP enabled for all packets. Based on user feedback we're going to tweak it. There are few configurations we can use - we can use RUDP on per-packet basis so we can, for example, only mark keyframes as "critically important" or use RUDP for audio channel only.

Once we receive some feedback we're going to set some decent defaults and possibly make rest of it configurable. Some people prefer raw frames arriving ASAP even if one is broken every now and then. Some would prefer a 5 ms lag spike once every few seconds to get rid of all artifacting. We need your feedback to get answers to some questions: How does the new streaming protocol work for you? Does it make things better?

Let's find out - we're listening at support@riftcat.com.

What's next?

  • We are working to update our API to v3 which uses Protocol Buffers instead of default .NET serialization which is kind of bad for cross-platform & language compatibility.
  • We continue our work on NOLO wireless mode. This should be out this July. It should exclude all potential lag and CPU spikes that could be caused by NOLO-SteamVR-VRidge interaction.
  • We recently got hold of Galaxy S8 so we want to test if the right-blurry-eye problem that some users report with S7 is reproducible with S8. Maybe we'll be able to fix it. 
  • 2.0 rework is still in progress but 1.4 protocol changes is one of the things that will play a major role in 2.0 so we want to test it properly with this beta update.
  • We need to figure out a way of deploying beta updates to Gear VR apps (we would like to have the same structure of stable/beta channels with Gear VR app too).

Friday, June 23, 2017

Dev update #30


In this blog post you can read about our recent developments in area of NOLO VR integration. We also talk about 1.3 which enabled everyone to integrate 3rd party trackers and included some SteamVR driver improvements.

We also try to explain problems that caused sound streaming (now scheduled to be released in beta channel on July 4th) and other updates to be delayed.

---

NOLO performance and wireless mode

There are two ways NOLO VR can work with VRidge. Currently only one is avaialble.

1. PC-based.

NOLO VR tracker is connected to the PC USB. It communicates with NOLO VR driver and runtime software. The NOLO VR software then communicates with RiftCat or SteamVR directly to provide absolute tracking data of headset and controllers.

2. Android-based.

NOLO VR tracker is connected to the Android USB OTG. In this scenario Android device is the host and it can communicate with tracker hardware to get tracking data of head marker and controllers.

Currently only #1 is implemented which is a bit limiting. The biggest downside is that you need to be cable-connected to your PC. We also don't control the software part of the process, we rely on NOLO VR software to tell us everything and we directly forward all the data into VR runtime. This is also limiting in terms of latency optimization because we don't communicate with the hardware directly. We also can't optimize CPU usage. We basically can't do anything other than listening to tracking data provided by NOLO VR runtime. Is has an ability to fully control rotational and positional tracking of HMD and controllers.

With #2 option we will be able to ask hardware directly for its sensor data and process it on our own. It should be lower latency and (depending on their hardware) very light on Android CPU usage. We haven't started working on it but we want to explore this scenario to find "the best" NOLO VR experience with RiftCat. This has a one downside though. The tracker will be connected to Android, making it fully wireless solution, but you lose ability to USB tether the stream connection.

We might try to re-implement #1 with a more direct approach (where our software queries their hardware directly instead of leaving all the comms to NOLO). It has a potential to be better in terms of latency and resource usage but wireless mode comes first.

Version 1.3 known issues

First days of 1.3 indicated that everything was going well. Shortly after we've started getting reports that some phones can't stream at all. It turns out that Galaxy S5 Mini, Samsung Galaxy Grand Prime, BLU Advance 5.0 (and some other phones using Mali 400 MP4 GPU) don't interpret video stream properly.

Those are not mainstream phones anymore but we had to start investigating the problem anyway because we don't want to leave people behind with each update. We still haven't pinpointed the problem and we'll probably defer the further debugging to 2.0. Version 2.0 will include many changes that include altered stream configs so we don't want to spend much time on this problem now because this will delay 2.0 which may fix it anyway. Version 1.0 of Android app is still compatible with latest desktop client (stable channel) so if your phone is affected - you may download and install it manually to keep using VRidge.

We also found that with 1.3 we broke our Android crash reporting & analytics. We use Google Play Services and its linked services to gather crash reports and related usage data. We rely on these reports to find out if changes we make work properly on all devices. With 1.3 we made crash reports mostly useless because of faulty configs. We tried to fix it and we now released 1.3.3 with Firebase reporting (also a Google service) that should be more reliable for crash tracking.

Virtual driver mode

As a minor change in 1.3 we changed our default SteamVR driver to use virtual display mode. It should have made the experience a bit more smoother. According to user feedback it indeed works better in this mode so we made it the new default. Your RiftCat config automatically switched to virtual display driver in 1.3 update. During the development we found another reason to add gamma slider so we'll most likely include gamma slider in 2.0 update. This will help users with screens that have less than ideal whiteness balance.

Beta & Stable

All of our updates are in stable channel now. This will give us more freedom in testing sound streaming, moonlight mode (and other 2.0 changes). If we break something in beta channel, users will still be able to revert to stable which contains everything we released so far.

VRidge API changes

We are making some changes to VRidge API for next API release.
Serialization will use Protocol Buffers. Reasons for this change are discussed here.
Remote API connections will work. Currently they are bugged (see here for a workaround).

Development status

We recently heard few opinions that we publish so many facebook posts without an actual updates on our side. Social media, support and development is handled by different people. If we stopped the social media activity it wouldn't change anything in terms of development. All the social media posts are our attempt to reach out to a wider audience. Maybe it results in an extra vridge license purchase a day, maybe it doesn't. We are not sure because measuring marketing is hard and we're still learning how to do those things without a huge budget. Coding (and this dev blog) is done by developers, social media is handled by other people. You can easily spot the difference in writing style.

Nonetheless, we still don't release as many updates as we would like to. We often get distracted from our main tasks by things that we cannot control. We rely on many components that often change outside of our control. Each Windows, SteamVr, GPU driver, Android OS (the list goes on) update we study the changes to make sure we will be ready once the update reaches user PCs. We are usually always ready to adapt to new changes but sometimes we need to drop everything and work on some emergency patches.

It's not always bad things that come from outside source. Sometimes a new game comes out that many user really want to try. We then try to make sure it's gonna work nicely not only with premium $600+ headsets but with our little tool too. We sometimes e-mail the developers to ask about their game, learn how its VR mode is implemented. Our goal is to not put any extra workload on the game developers (because they have their own goals - they gotta create the games we all love :). That's why it takes time to sometimes find creative ways to trick the game that "render please, we're totally Vive!".

Anyway, the problem with those things is that each time we drop current tasks to handle the "external event" (good or bad), it delays our plans a bit. Hours add up to days, days add up to weeks. It's also mentally distracting because we sometimes need to work on several totally different things in the same day. You don't need to be a developer to know the feeling that comes when you need to drop whatever you are currently doing to handle some outside interruption. It sometimes takes time time to get into creative zone again, to focus again after spending few hours on something totally unrelated to your original task.

We decided that we should try working with extra devs. We still don't know how well it will work out. We can't afford to transfer a senior developer with 20 years of experience @ Samsung or any other "big" company. They will be new to the system it's gonna take some time to teach them VRidge codebase and the ideas behind it. Nonetheless it's an investment that we want to try because VR is still rapidly changing and the more keyboards we can man, the more updates we'll be able to push. We already started getting our new friends familiar with VR, showing how VR experiences are made and what makes them work the best. We'll have more news in this area soon.

2.0 version will include Moonlight mode, HDMI output and will generally be more stable than currently released version. We'll keep updating you on its progress once we get back to work on it. As we promised earlier - "2.0" version name is only indicative of major codebase rework, you won't need to buy anything else - it will be a free update.

We're far from excited to write a blog post without any actual downloadable feature update but we hope that you can bear with us a little bit longer. Sound streaming is already merged into the main codebase and should be out it less than 2 weeks. After it's published, one developer comes back to 2.0 rework full-time and the other one focuses on wireless NOLO + some extra API changes to accommodate other controller types that are going to work with VRidge.

Friday, April 21, 2017

Dev update #29 - an update on our progress



This is text update only, we want to explain what we are doing and why we think it's a best way to do currently. 
---

VRidge core improvements 

Moonlight, stability & launch flow improvements, fake VR groundwork

Reasons

VRidge was first designed as Oculus proxy interceptor that acted like Oculus DK2. Its work flow was quite simple because VR was simple back then. There were no controllers, no always-on services, no Oculus Home / SteamVR dashboard like environments. You started a game by running its executable and VRidge process lifetime was limited to game process lifetime.

We added SteamVR support exactly year ago, on 21th April 2016. It was first SteamVR-mobile HMD bridge back then and it helped us grew a lot. Then we continued adding more and more features and changes like UI slider for supersampling (which was later added by SteamVR itself), better support for controllers, FreeTrack, 1440p, Intel and Software encoders, Gear VR, partial Daydream support and lately - VRidge Tracking API.

The shape of VR has changed from headsets being simple 3D glasses to full room scale systems running multiple services in OS background. The problem is that the core of the VRidge remained mostly the same and if you ever worked on a big project, you know that when goals and requirements shift, the project maintainability suffers. The VRidge was designed with pre-release Oculus headsets in mind when there were no controllers or room scale lighthouse systems. And those legacy foundations slow us down a lot.

Core rework

That's why we are currently doing major rewrite of the VRidge core. It's actually going pretty good and we already made a lot of progress. In our development version VRidge was decoupled from SteamVR launch flow. We dropped that annoying chain of dependencies that required restarting all components (mobile, SteamVR, VRidge, Riftcat) when any of the mentioned components ran into some sort of problem. We can start and stop SteamVR/VRidge at any time and in any order - they will connect without problems. 

Another thing that rework enables is modular architecture. We can now substitute capture, encoding and output components during runtime. When we detect SteamVR connection being dropped, the stream automatically switches off to screen duplication stream. While it's not very useful at this moment (because VRidge doesn't have any Remote Desktop functions) it lays a solid foundation for future Fake VR. It can capture any window with very little overhead (<1% CPU usage, sub-frame latency, duplication tech stack very similar to Virtual Desktop, Bigscreen or OBS).

Another great thing that we already have working is a plug and play Moonlight support. It works as easy as possible. We have special VridgeView.exe that can be added to GameStream library in GeForce Experience panel. Then we simply start the VridgeView through Moonlight and it automatically connects to VRidge runtime and switches VRidge to fullscreen SBS output that is handled by Moonlight. And it works quite amazingly since as we said before - we think that NVIDIA GameStream + Moonlight pair is a "relationship goal" for any streaming software.

This also allows HDMI (or any video signal cable) output. You can use the VRidgeView.exe which will find its way to your chosen display and show VR on your device's display with no added latency. This is great thing for DIY fans that enjoy building their own HMDs.

We also want to unify Android rendering. Currently Gear VR and Android use completely different rendering engines. This makes it complicated because Daydream's immersive mode requires another VR renderer. We have a way to combine them all into one which would finally allow proper implementation of Daydream's immersive mode. We didn't want to write separate renderer for Daydream only because writing three things for three platforms that do essentially the same thing is a hell to maintain. With unified renderer, it should be a much less bumpy road.

We are also moving all settings to desktop app since adjusting some settings on the mobile makes absolutely no sense. Trying to adjust FOV with your headset off is an annoying guessing game.

Let's not forget iOS and possibly other mobile clients. This modular rework will remove a lot of spaghetti netcode which will then make it easier to port the mobile app over to iOS.

To sum things up, here's our current progress of the most important components:

☑ SteamVR driver connectivity rework (plug and play startup).
☑ Moonlight streaming support.
☑ HDMI output.
☑ High performance desktop capture engine for the future.
☑ Encoder quality settings adjustable on the fly.
☑ Encoder migration: NVENC.
☐ Encoder migration: MF (including AMD, Intel QS, Software).
☑ Network output
☐ Android network connectivity.
☑ Android decoder (not changed). 
☐ Android unified renderer. 
☐ Android background mode (for Moonlight mode tracking).

Scope of the work above is enough to call the reworked release VRidge 2.0 but those are only numbers without any other meaning than a label (no price changes or anything, everyone will get this update).

Since it's a major rework we cannot provide a testable version because Android connectivity wasn't migrated yet. Nonetheless we hope that this will allow us smoother development after most of legacy code is cleaned. During last year VR matured with a release of SteamVR and Oculus CVs. Controller interfaces are pretty well documented. VR environment APIs are pretty stable. With a more solid set of VR standards we are confident that we won't repeat the story pictured below:
by: Manu Comet

Sound progress

We planned to release it faster but we ran into some problems during testing on other machines. As it turns out - different sound chips use different audio formats so we are still testing and adapting to new motherboards/sound cards that we can find. After it's released to beta channel we will probably find some more bugs with exotic sound devices but that's what the beta channel is for.

SideloadVR & ConstructVR

Apparently SideloadVR is still online so we are going to update our Gear VR app on SideloadVR to match ConstructVR's latest version. It should be updated soon.

VRidge API changes

We are making some changes to VRidge API for next API release.
1. API call to re-center view.
2. Haptic feedback response for controllers.
3. A way to mark HMD trackers state as "out of tracking range".

Those changes were requested by 3rd party device manufacturers. The changes will be reflected in next week's API release on VRidge API GitHub.

Update release schedule

  • VRidge API will be updated by the end of next week.
  • Soon everything in current beta channel will move to stable channel. We want our stable version to be compatible with NOLO VR hardware when Kickstarter backers receive their units. 
  • Sound and protocol changes will be deployed to beta as soon as they are release-ready. Most likely it will be released in early May.
  • Core rework is estimated to be released to beta by the end of Q2, hopefully. It's our biggest change since release, but for a good reason.

Monday, March 27, 2017

Dev update #28 - VRidge tracking API


Vridge API is out in beta. Networking and audio changes are nearly done. More exciting features coming in next months.

---

VRidge API out in beta channel

VRidge API is a way to interact with VRidge tracking internals. This is the first step in making our platform more compatible with third party software and hardware solutions. We start with two endpoints that will allow you to take full control of head tracking system and controllers.

You can check out the example implementation and desktop app sample on our github here:


API is versioned so your plugins and drivers should work even after we alter the protocol. Perfect backwards compatibility is something we cannot promise for sure but we designed the API in a way that should allow easy iterations - we have several ways to keep both new and old versions of API channels running side by side. Backwards compatibility will be our priority when we make changes to the API.

We start with two endpoints that can be used separately:

Controller endpoint allows you to send VR motion controller state without writing a full OpenVR driver. This allows a more stable experience since only one driver is loaded in SteamVR. You can send multiple controller states, move them around, press and touch buttons and interact with touchpad. You can also use any language of your choice to send driver states as long as you send properly formatted packets.

Head tracking endpoint allows you to control head tracking in a variety of modes. You can use it to provide positional, rotational or combined data. You can also read mobile sensor data and provide an offset. If you find it necessary, you can modify phone tracking data in real time before it's used for rendering in VR.

We already have plans to expand API further to create a way to expose compressed or raw video output. Ultimate goal is to have everything pluggable/modifiable. VR hardware and software world is very fragmented now without a clear standard that has to be followed*. That's why we want to make parts of VRidge modifiable by controller and HMD manufacturers.

*OpenXR by Khronos is a good attempt to bring it all together. We hope that it succeeeds because with OpenVR, Oculus VR, OSVR and all the bridges in between them - the current state of VR SDK is somehow chaotic.

In the future we will also start moving more and more of our comm protocols into the open API because it allows creating 3rd party apps. We want to keep improving our Android app and eventually release an iOS app but if someone wants to create an alternative app specifically crafted for their purposes - we want to support it. There are multiple reasons to do so. Maybe you need a branded app for your company. Maybe you want to demo your architectural designs with some extra options. Or maybe you want to try to hack a way to run VR on TI-84 (after seeing Quake on oscilloscope or Symmetra being played with a microwave we believe that everything is possible).

While hacking and modding is fun this is our ultimate but not immediate goal. Our next plans are another round of performance/user experience improvements.

What's next?

Protocol, audio streaming, stable channel update (April)

There isn't much to say about it. The work on audio and protocol changes was suspended while we were trying to finish the API. It will be probably our next release since it's mostly complete and just needs some testing. Next blog post will be most likely focused on those changes with audio & protocol update being available in beta channel. We will probably push current beta to stable channel then too.

Smoothness, performance, latency - Moonlight & HDMI (Q2)

We tried to tackle it several times and there's still unresearched option of time warp providing significant improvements here. Trying to create the greatest VR streaming experience would be easier if we had something to compare to. That's why before we start working on time warp (which can improve the experience but we don't know it for sure) we want to create something that should have been added a long time ago.

NVIDIA Gamestream combined with open source Moonlight project is a great streaming solution. Probably the best one we've seen. We want to support it with VRidge app acting as a background tracker connected to VRidge runtime on the desktop which translates mobile tracking data into HMD tracking data and HMD frames into Moonlight & Gamestream compatible data. We want it to serve as a point of comparision of our own streaming.

Once we have Gamestream & Moonlight as a reference of perfect streaming, we want to improve our own streaming and tweak it for VR.

AMD users - don't worry, our streaming will still be available and improved in the future. We just want to take an advantage of pre-build solution because Team Green is large majority of our userbase. And the streaming is already there, we just need to hook into it.

While we are reworking rendering output we want to add rendering to HDMI connected displays* too. We already have render-to-screen working internally because we use it for development (finding bugs is easier when you can use your 2nd screen instead of phone). We just need to wrap it up in nice GUI switches and add some stability to it.

*You can substitute HDMI with DisplayPort/D-SUB/DVI. It will also have an option to simply render to window.

Less restarts, more stability

We all hate the "Your PC is going to restart in 5 minutes and there's nothing you can do." messages. Especially when you're in the middle of ranked match and you don't want your teammates to lose and your MMR to drop. This kind of experience ruins the fun and we want to address it in VRidge too. Current runtime flow requires restarting nearly everything (mobile app, SteamVR & game, VRidge, sometimes RiftCat dekstop app) every time even the smallest thing go wrong.
  • Connection interrupted? Sometimes you won't be able to reconnect. Gotta restart everything.
  • You want to change bitrate? Restart VRidge, SteamVR, game, mobile app.
  • USB cable disconnected? You need to restart everything. Oh, and Riftcat dekstop app crashes too.
Combine this with fragmented settings (some options needs to be configured on the mobile side, some are configured in the desktop app) and questionable design decisions (changing IPD & scale requires taking the phone outside the viewer).

We want to fix as many of these. Our goal is for VRidge to run always and connect with mobile app and SteamVR in a hot-pluggable way. Some settings would still require restarts but we want to limit those to situations when it absolutely needs to happen. We also want to move all settings to desktop app.

Minor tweaks and other features

We will have smaller tweaks and some new motion control options available in the meantime too. Moonlight, HDMI and anti-restart updates might take a while to be released (late Q2 is the most likely possibility). That's why we will try to squeeze in some extra side options that were prototyped as side projects but we're not ready to talk about them yet.

Fake VR is still on the table but performance has higher priority since over 50% of our feedback survey requests can be answered by having Moonlight as an option. iOS app will have to wait until we complete moving our protocol into open API.

Friday, February 24, 2017

Cloudflare security incident statement

Few hours ago Cloudflare informed the world that they discovered a security problem that could result in sensitive data being leaked. You can read it all over the news.

Cloudflare is used by over 4 million websites across the Internet, including Medium, YCombinator, Bitpay, Patreon, TransferWise, Coinbase, Authy, Okcupid, Zendesk, Curse network, Discord, among many other big websites. You can download compressed list of all potentially vulnerable websites here.

RiftCat also uses Cloudflare but we received an e-mail from Cloudflare informing us that they didn't find any of our data leaked:

Fortunately, your domain is not one of the domains where we have discovered exposed data in any third party caches. 

The leak isn't RiftCat specific. Any* of the users visiting any of the 4M websites could have seen part of someone's else data in website source. For example, while visiting riftcat.com there was an astronomically small chance of someone's Uber/Fitbit/Okcupid** password being hidden in page source (and the other way around).

Chances of your sensitive data being leaked from the affected sites are very, very small. According to Cloudflare one out of 3 million requests (0.00003%) contained hidden parts of someone's else request[1]. Those hidden parts were probably some sort of generic web traffic because most web traffic is just people browsing pages and not entering their passwords. It was also random and hidden by nature of the problem so it's unlikely that someone could use this as an attack on any of the services listed.

An analogy of this event in real world scenario would be a 0.00003% chance of finding totally random item from someone's else house under your door rug. If you haven't looked under the mat during this unlikely event, it was gone (unless it landed under bot's door rug which is also quite rare)

Most of publicly cached mixed pages are already removed. Cloudflare found 150 page requests publicly available in web caches.


RiftCat data was not found in any of the publicly leaked data. 

Nonetheless you might want to change your passwords around the Internet if you want to minimize your chances of being compromised. It's highly recommended that you don't ever use the same password twice. Stay secure.

*It might be limited to users using Cloudflare scrape shield only but it's not confirmed.
** According to TechCrunch they were confirmed as affected. See [3]

Further reading: