Thursday, December 7, 2017

Dev Update #35 - VRidge 2.0 Beta is here!

This is the biggest update so far. VRidge got rewritten from scratch and it has to be released in a different way than our usual update method.

Remember that this is a Beta version of VRidge 2.0 - we need your feedback to fix all potential issues that might come up (there are over 10 000 different Android devices out there - it’s hard to test them all). Please send us feedback, suggestions and bug reports to support@riftcat.com - it is crucial if we want this update to become a success.

You will be able to track the progress of the bug fixes on this public Trello board: http://go.riftcat.com/vridge-development 

What you will find in the VRidge 2.0 Update?

Completely new user interface 

New design with user experience as primary objective. Registration will no longer be required to try VRidge!

Possibility to change quality while streaming 

Need to find the perfect setup? You will no longer need to restart VRidge endlessly to find most suitable settings. Just use LIVE streaming settings to optimize your VRidge experience (advanced live settings are also available).

Much better stability 

Completely new software architecture allowed us to make VRidge software much more stable. No more full software restarts when something fails.

Integrations support (easy add-ons to VRidge) 

We now have much better tools to integrate third party solutions. More on that soon!

Moonlight support 

If you have a modern NVidia card you can use Moonlight streaming instead of VRidge. You might receive better results in terms of latency and image clarity. To learn how to use Moonlight with VRidge - read about it in the Moonlight Basic Guide. 

Multi-language support

We have implemented multi language support. We support English and Polish languages for now. Tell us which languages you would like to see. More coming soon!

Some other stuff 

We won’t spoil everything. You can discover more changes by joining the Beta :)

Minor patches

2.0.2
  • Added diagnostic mode counters (go.riftcat.com/DiagnosticMode)
  • Added native error logging
  • Added custom FPS that can be set in config mid-stream (won't persist through restart, just for testing purposes now)
  • Fixed FPS setting not changing VR FPS which caused increasing latency
  • Fixed installer freezing at 80%
  • Fixed crash loop after switching encoders
  • Fixed Riftcat not being able to stop SteamVR if SteamVR was started as an admin
2.0.1
  • Fixed Oculus SDK games crashing when running without admin.
  • Fixed FreeTrack sometimes crashing app.
  • Fixed NOLO wired (desktop driver) positional tracking.
  • Fixed trial timer sometimes ticking down incorrectly (visual error only).
  • Fixed resolution sometimes not refreshing in UI in basic mode.
  • Fixed file lock problem causing both apps to lock up if error was encounter during settings change.
  • Fixed moonlight distort not being refreshed when .cfg changed.
  • Fixed background update check crashing RiftCat client when Internet went down mid runtime.

The instructions below will help you join the VRidge 2.0 Beta program. 

RiftCat Client (Windows side) 

The client got reworked completely. That’s why you need to install separate application to join the Beta. You can find a RiftCat 2.0 Beta installer HERE or by pressing the button below:
Install the client like any other Windows program. The installer is fairly easy to use and should get you up and running fast.

VRidge App (normal Android version) 

The mobile VRidge 2.0 application is also distributed through a separate channel. Please follow this LINK or by pressing the button below:
You will be prompted to install separate VRidge 2.0 application. Google Play will install the VRidge 2.0 App on your phone after your acceptance.

You can now connect this newly installed app with RiftCat desktop Beta client - enjoy and let us know if you encounter any issues.

VRidge App (GearVR version) 

The VRidge 2.0 application for GearVR can be found on Sideload. Just follow this LINK or by pressing the button below:
The installation process is the same as in normal installation of VRidge for GearVR. To learn how to install applications from Sideload, simply read this guide: https://support.riftcat.com/hc/en-us/articles/212489169-How-to-setup-VRidge-in-GearVR

51 comments:

  1. This new pc version and the original 1.5 beta can coexist in the same pc?
    Also, this newer beta 2.0 ask excluse permision over nolo device?

    ReplyDelete
    Replies
    1. Yes, you can install both side by side.
      No, the new version doesn't support NOLO yet.

      Wired support will be probably patched back in next week and wireless maybe a bit later but it's one of our highest priorities.

      Delete
  2. Wired NOLO controls not working?

    ReplyDelete
    Replies
    1. Should be working again now with 2.0.1 update.

      Delete
  3. Hi, glad to hear that the nolo will be sopported soon.
    I have nolo and kinect 360, can it works together with riftcat to get full 360*?

    ReplyDelete
    Replies
    1. We haven't tested this scenario but external drivers have capabilities to fully override our tracking so it's up to 3rd party devs.

      Delete
  4. Can we get a link to the APK direct download to side-load? Google Play seems to think my flagship phone can't handle the beta.

    ReplyDelete
    Replies
    1. https://riftcat.blob.core.windows.net/pubfiles/apk/daydream-2.0.0.apk

      What's your phone model? We're going to check why it's excluded in G Play.

      Delete
  5. On my S8+Gear VR it gets stuck on "Trying to connect" and says "Looking for RiftCat desktop app" on the phone.

    1.5 still works. Any ideas?

    ReplyDelete
    Replies
    1. Also manually entered phone IP and didn't help.

      Delete
    2. yep, the same in my case, only cable connection works

      Delete
    3. I am pretty sure you would not make the mistake that I did. Loaded the Beta on my PC and then opened the usual vridge (not v2 beta) on my phone. Will not connect even with manual IP. Loaded the v2 beta on my phone and connects immediately.... I use S7 Edge + Non gear headset.

      Delete
  6. The line between 2 screens is not centered .

    My phone is htc U11 plus (2880x1440 resolution)
    https://i.imgur.com/oQYJbqQ.png

    ReplyDelete
    Replies
    1. The overlay is rendered by Google Daydream side of the process. Do regular Daydream games have the same problem?

      Delete
  7. Downloading Redist...80%
    @
    Error ocurred! (occurred BTW)

    Why does it happen!?

    ReplyDelete
    Replies
    1. same here. no clue why it's doing this

      Delete
    2. update: I updated windows 10 to the fall creators update and after that was able to install the 2.0 beta fine without this error, pretty sure it's because it updated .net framework to 2.7.1

      Delete
    3. Installer link was updated to fix this problem.

      Delete
  8. This comment has been removed by the author.

    ReplyDelete
    Replies
    1. WOW! I like the new UI and color scheme. Everything is working smoothly with my S8 and Gear VR 2016. Although I did have to manually inject the Oculus ID on both S8s I tried, when previously I didn't. I tested on 5G wifi, but I also bought a USB-C to Ethernet adapter, and performance is just a bit more stable.

      Is there any plan to include native tethering over USB through the Gear VR? When I set my S8's usb mode to RNDIS in developer options, I'm able to pick up the connection in my network settings and VRidge as a RNDIS network adapter, but no phone is available in Vridge. I feel like I'm so close. Could it be as simple as my firewall settings? If you were able explain what step(s) I'm missing, I would be incredibly grateful! (Unless it requires root, which I have a feeling it might)

      Better yet, if it were to "just work" through tweeks in the app, I would be even happier. I understand the technical limitations of running through the Gear VR as it requires the phone to be the host, but I'm wondering if native RNDIS on the S8 changes this limitation?

      Delete
    2. If I recall correctly, this used to work in 1.x versions. It became possible with new Gear VR 2016 because it supported USB OTG passthrough (previous Gear VR editions didn't have this capability).

      I wonder what changed that could break it. We need to order one of those USB-Ethernet adapters to include it in our tests.

      Delete
    3. Actually, my USB to Ethernet adapter works without a problem.

      It's when I go straight usb to usb that is the problem. Again, I'm unsure if it is a problem with my phone or just a windows firewall issue, as the usb to usb network does show up in windows and riftcat, but wont connect in riftcat.

      But the usb to ethernet adapter works just like my wifi connection when I route it through my router. I was just hoping to bypass the middle man and go straight into to my pc.

      Delete
    4. Oh, I misunderstood. I actually haven't checked dev options tethering settings. We're going to test it out.

      Delete
  9. S8+, Gear VR (SM-R325NZVASER)

    I have two problems with Moonlight integration

    1) I followed the Moonlight Basic Guide, but head tracking doesn't work. Games don't respond to head turns. Without Moonlight all works

    2) If I put a smartphone in the Gear VR with an open Moonlight application, Gear VR will open the standard home application

    What should I do? How to fix?

    ReplyDelete
    Replies
    1. I have exactly the same problem, I am using a Galaxy S8 with 2017 Gear VR, I followed the Moonlight Basic Guide, but head tracking doesn't work, it's like the screen is frozen in front of you, no head tracking what so ever, games don't respond to head turns at all but without Moonlight it all works fine. I have everything loaded correctly on the phone and PC and I have a fully paid up account for unlimited access,I hope you can fix this, Mark A.

      Delete
    2. Gear VR app doesn't work with Moonlight since Moonlight itself isn't native to Gear VR. In current implementation we have no way to run Gear VR app in the background (to capture its tracking sensors) and Moonlight in the foreground at the same time.

      We will be exploring option of using Gear sensors in the background with Moonlight in the foreground but this might be tricky.

      For now, you can use Moonlight mode + Daydream app (as a background tracker) or Gear VR app without Moonlight mode.

      Delete
  10. What is the status of Leap Motion support? I can't seem to get hand tracking to work using the old guide. Will this be updated?

    ReplyDelete
    Replies
    1. The old guide wasn't tested with 2.0 yet. I added it to our task board.

      Delete
  11. Yikes... I was looking forward to this but it crashed before I could even load a game (while changing settings), and now it repeatedly crashes on startup. I'll email you the logs.

    ReplyDelete
  12. Started client on PC, started client on phone. PC client crashes trying to connect to phone. Entering IP doesn't help. Windows 10 64 bits, Oneplus 3T.

    ReplyDelete
  13. There's a problem with NOLO VR, probably with tracking, the position continually wobbles

    ReplyDelete
    Replies
    1. Are you using any FreeTrack/FreePIE plugins at the same time with NOLO or is it simply NOLO + VRidge without any other 3rd party plugins?

      Delete
  14. Anybody noticed a FOV difference with the new 2.0?
    The app is a lot more reliable than before, but the FOV is completely different on my Pixel XL 2, kind of ruining the experience.
    Check the screenshots I took on the phone:
    https://imgur.com/a/O2DjY

    ReplyDelete
    Replies
    1. Yes, similar problem described here:

      https://trello.com/c/CbJQhJeH/28-investigate-proportions-being-slightly-off-with-s8-possibly-other-phones-too

      Generally, size of those viewports is defined by Daydream SDK, which takes the parameters from Daydream View or preset selected by tapping cogwheel and changing headset in there. Please try setting different preset there. For our Pixel XL (1) Google Cardboard preset fits the best for generic plastic/cardboard headsets.

      Delete
  15. have been playing around with version 2.0.
    I like the layout, that's quite nice.
    I have been getting random crashes after confirming my configuration.
    For some reason, HEVC doesn't appear to be working on my Samsung Galaxy S8 Plus. I'm just staring at a grey screen with the lines. Tracking was working up to a point, although it was terrible. Not smooth at all. And then, tracking stopped all to together which made me feel very sick when turning my head.
    This is using the Gear VR version.
    Compared to what I'm used to with the Gear VR and S8 Plus with the smooth head tracking etc. This was a bit of a come down. I know you'll get there. I can't wait.

    ReplyDelete
    Replies
    1. Which S8 Plus variant do you have - US or International?
      I'll be tracking HEVC compatibility problems here:
      https://trello.com/c/cbJQmf8s/53-hevc-compatibility

      As for the latency, our plans our here:

      https://trello.com/c/dmAohsgI/4-continuous-latency-stability-jitter-improvements

      In 2.0.2 (just released) we fixed some problems with FPS timings (that could potentially cause increasing lag) but more problems are defined here:

      https://trello.com/c/dmAohsgI/4-continuous-latency-stability-jitter-improvements

      Delete
    2. This comment has been removed by the author.

      Delete
  16. Crash on connect using 5gh wifi. using the gear vr beta client with an S7. windows 10

    ReplyDelete
  17. Daft question.
    How do you enable diagnostics in version 2?

    ReplyDelete
    Replies
    1. There are no diagnostics on the Android side currently but in 2.0.2 later today there will be similar screen on the PC side:

      https://trello.com/c/IaXxBuiE/51-starting-vridge-in-diagnostic-mode

      Delete
    2. My phone is the international variant. I believed it worked on 1.5? Will have to retest.
      Just though I'd add this.
      I have a USB C gigabit Ethernet adaptor connected to a gigabit switch which I just installed. My PC is also connected to the switch which is connected to my gigabit router.

      Delete
    3. This comment has been removed by the author.

      Delete
    4. I have a suspicion that the HEVC issue maybe related to the Oreo beta my UK S8 Plus is running. On Nougat I am pretty-sure HEVC worked fine with the 1.5 beta. Just tested 1.5 again and I get a black screen even if the Windows Firewall is disabled, If HEVC is enabled or not. So back to version 2. But as for HEVC it very well maybe Oreo beta issues. I have reported possible HEVC problems to Samsung as I am part of the UK Oreo Beta test program. The jitter is better since enabling VSync and setting texture filtering lod to Clamp. As for the rest of the jitter etc. It is present on the new black connection screen with things flying in the background. This is before streaming has started?

      Delete
  18. General update for everyone experiencing crashes:

    We have just released 2.0.2 that should solve some crash loops.

    Also, please check GPU performance options if you are using NVIDIA Optimus enabled laptops.

    See NVIDIA GPU section in the link below:
    https://support.riftcat.com/hc/en-us/articles/207877829-I-have-a-laptop-will-it-work-

    If you still experience crashes, please send logs again after reproducing your crash with v2.0.2. It has more error logging so more details will be visible.

    ReplyDelete
  19. Wow, now it works! You fixed it! This is awesome and I like the new settings. Thanks for the Update

    ReplyDelete
  20. This comment has been removed by the author.

    ReplyDelete
  21. Why I can't login with FB account? When I click FB login nothing comes up. I want to use my FB account where I purchased the original version

    ReplyDelete
  22. This comment has been removed by the author.

    ReplyDelete
  23. I have a USB C USB 3 hub/Gigabit Ethernet Adapter connected to a newly purchased Gigabit network switch. Which my PC is also connected to. The switch is then connected to my Gigabit router. The PC Ethernet is of course Gigabit too. Testing the standard 1.5 version with the adapter connected to the phone of course :) I get a network delay of 0.02ms according to Vridge. I was very happy with that. But yet I get a black screen with a line down the centre no matter what streaming settings I use. I enabled Steam VR mirror and tracking was working. When testing version 2 it streams fine. Other than the slight jitters in the Gear VR version already known about. I have disabled my Windows firewall to retest 1.5, but VRidge 1.5 isn't streaming video. Any ideas? I'm using a UK S8 Plus on the Oreo beta. Thanks.

    ReplyDelete