Thursday, January 25, 2018

Update changelog: 2.0.3

2.0.3 is release candidate for 2.0 stable release, which will happen on Tuesday, January 30th.
Full blog update will be posted on Tuesday but we're posting a quick technical changelog today.

Both mobile app and desktop app need to be updated to 2.0.3 to work together.


Added / Changed:

  • Added IPD and Scale sliders, adjustable mid-stream.
    • You can fine-tune viewport to match your custom lenses. It works with Daydream, Cardboard and Gear VR backends.
  • Added Tracking Prediction slider.
    • Bigger prediction window results in a faster response but high values are more likely to overcorrect, resulting in a rubbery judder. Default is configured for 60ms of total motion-to-photon latency.
  • Added Streaming Mode selector.
    • Default will prioritize keyframe delivery to keep a good balance of latency vs artifacting but you can prioritize latency or artifacting countermeasures.
  • Console window was hidden.
    • You can still the same log in Logs/VRidge.log file. The console window along with extra diagnostics will still appear when started in standalone/diagnostic mode.

  • SteamVR will now report real selected FPS instead of 60. 
    • This is useful for third party VR software which relies on SteamVR-provided HMD FPS.    

  • Disabled SteamVR's async reprojection in VRidge driver. 
    • It doesn't change anything in our driver workflow but fixes crashes for some people.

  • Installer was updated to match new color set.
  • VRidge PC server will now use a bit less CPU.
  • Added splash screen during RiftCat launcher startup.
  • RiftCat launcher will now remember whether you selected WiFi or USB as a connection method.
  • Logs will now be rolled into one file instead of individual file for each session.


  • Play SteamVR button won't become disabled (unclickable) when VRidge exits incorrectly.
  • HEVC (aka H265) will now work correctly on Galaxy S6 and some other phones.
  • VRidge mobile will no longer crash on screen tap in certain cases.
  • FreeTrack tracking won't interfere with API tracking (NOLO and other custom API clients)
  • Moonlight (rooted edition) will now be properly detected as viable Moonlight app in Moonlight mode.
  • Moonlight mode will no longer crash on Maxwell NVIDIA GPUs when NVENC wasn't selected.
  • Sound streaming should no longer cause additional latency with new default Streaming Mode (which only prioritizes keyframe delivery).
  • Fixed text rendering issues with certain Xiaomi phones.
  • Fixed Windows firewall rule not being set correctly for RiftCat.exe.

This build will move to stable channel next week and replace default 1.3 installer. Both 1.3 and 1.5 versions will continue to work if you want to stick to the old version. NOLO wireless mode will be brought back in v2.1 in February/March.


  1. "NOLO wireless mode will be brought back in v2.1 in February/March."

    Nice! I'll check back in March. I would hate to miss the announcement of wireless NOLO being pushed back to June/July.

  2. Should I upgrade the firmware of Nolo to the current v. 0.11.0 or isn't that necessary for the upcoming Riftcat release? Want to use it in wireless mode in combination with GearVR btw.

  3. I have no head position tracking with NOLO with this latest Riftcat version. My controllers are far behind me and I can't really play anything. In job simulator for exemple, I'm in front of the pedestral and the controllers hand are positioned correctly behind it.

    Head tracking works fine in the NOLO Visualizer, in iVRy and even in Riftcat 1.5

  4. Can anyone tell me where i can find the latest GearVR Android version? The one on Sideload seems outdated...


    1. It's right here:

  5. I have a Huawei P7 that works great with Trinus and Moonlight, but Google Play says my phone is not compatible with vridge, is there a way to change this? Can i download the APK???

    Thank you, i really want to test your app!!

  6. I am having some trouble as soon as I get it up and running everything fine. I hit ok connects me for like 2 sec then disconnects me. any fix for that?

  7. No sliders for viewport adjusting available. VRidge 2 (unlike 1) shrinks viewports making 1 cm black frames around them.