Thursday, June 30, 2016

Dev update #17

VRidge launch

Last week we started selling VRidge as premium product. We had to create some quick client and server side hotfixes to keep everything running smoothly. We added some checks for exotic PayPal error codes too. Everything is currently operating normally and we started getting back to regular development schedule.

If you can't use PayPal remember that you can send us an e-mail (support@riftcat.com) to process payment manually through TransferWise. More payment options will come after we fix bugs we promised to fix a while ago (Intel-, MediaTek- and Kirin-chipset phones, etc.).

What's next?

We want to continue with frequent updates but every change, even the slightest one, can break something. For example, we can add a lot of optimization in an update that will improve experience for 99% of our users but break stuff for the remaining 1%. It sounds good statistically but this would mean that a lot of users (the last 1%) would have problems they didn't have earlier. We of course would fix those new bugs but this takes time.

Forced updates are not the greatest user experence - that's why we decided to split updates in several branches.
  • Beta update branch will be updated few times a month (probably once a week like we used to do in beta phase). Use it if you want to be first to access new features and bug fixes.
  • Stable update branch will be updated less often, every few weeks. We don't want untested changes going live for everyone as forced update.
  • Previous stable updates will contain stable versions from the past. If somehow beta bugs make it into stable branch you will be able to switch back to previous versions and ignore updates.
This will not always work. For example, VR SDKs, graphics drivers or some other condtions can change in a way preventing backwards compatibility. We're not always in control but we will try our best to give you the most options.

Client update with branch selection should be available next week.

But what about features?

If you are signed up for Android beta releases (you can join & leave beta channel here) you will see an update 1.0.1b in few hours. We updated our app to use Google's latest VR SDK instead of Cardboard SDK. This shouldn't break anything and it brings improved tracking and native drift-correction for default tracking algorithm. Also, this is first step in Daydream's direction. We are really excited about Google's plans for VR. Check out the beta update and tell us if you notice any improvements in default tracking algorithm.

If it causes additional crashes let us know so we can fix it before pushing this update into stable channel. :)

We also started working on GearVR version. We are in early stages and we're still assessing the amount of work required to create native GearVR Vridge app. We'll keep you updated!

33 comments:

  1. Haven't had much time to test the beta yet as my battery died, however, it looks like the awful drifting on my Nexus 6P no longer happens with the new Google VR tracking :) Great stuff, keep it up!

    ReplyDelete
    Replies
    1. How's the latency/fps with the 6p? I was thinking of buying one.

      Delete
  2. Great, just joined new Beta, can you please make old video cards work, just like Trinus VR and Kino VR does ! ?

    ReplyDelete
  3. One of the best updates yet, the new tracking is MUCH improved. This give me a lot of hope that when the daydream phones come out later in the year this app will actually be quite usable (my one plus is just too blurry).

    ReplyDelete
    Replies
    1. Which OnePlus model are you using? I'm testing a lot with my One and it's working quite nicely.

      Delete
  4. Good job guys it keeps getting better. Streaming looks amazing in Leap Motion's "Blocks" (Unity)

    I have a new problem since the last update. The settings menu does not want to save my settings when I hit OK. This includes resolution, bit rate sensor use, etc. I hit OK and the window stays open so I have to hit cancel to close.

    ReplyDelete
    Replies
    1. Can you try deleting Riftcat/config/vridgeQuality.cfg? Maybe it somehow got locked into read-only mode...

      If it doesn't help please send Riftcat/logs/clientLogs.txt to support@riftcat.com. Maybe some errors are written to the log file during saving.

      Delete
  5. Also does riftcat have player height adjustment? Height seems to be different in different games. Is Vive Room setup the only way to adjust it?

    ReplyDelete
    Replies
    1. Vive room setup should set the correct camera position in all SteamVR games but game developers may modify "camera position" resulting in inconsistent height across different game.

      Lack of positional tracking also can cause odd results if game expects the player to change from crouch to standing position sometimes. (this can be solved with FreeTrack, webcam and some markers).

      Delete
  6. How long do you think it'll be before the first gear VR beta is ready? For testing purposes you could put it on the sideloadvr appstore rather than the oculus store

    ReplyDelete
    Replies
    1. No time estimates yet but yes - we'll start with sideloadvr.

      Delete
  7. We are currently exploring PS Move and Leap motion because there are already 3rd party SteamVR drivers available for them. We will test Wiimotes after we are done with PS Move and Leap. :)

    ReplyDelete
  8. Hello. I want to buy your program, but I have a Asus zenfon 2 ze551ml. I really hope that you will be able to provide a convenient work with the program, and with this smartphone. I look forward to the news. (I am from Moscow)

    ReplyDelete
  9. Is there a way we can get email updates from this blog? Thanks

    ReplyDelete
    Replies
    1. Currently we only have Atom feed:
      http://blog.riftcat.com/feeds/posts/default
      If you paste link above to any Atom/RSS reader it should work. There are services that offer Atom-to-E-mail newsletters but I haven't tried any of them so can't recommend anything solid.

      Delete
  10. Getting a blue screen of death after using this program.

    ReplyDelete
    Replies
    1. BSOD is usually driver/hardware error. We don't install any driver-level software so try updating your GPU drivers (and motherboard too if using QuickSync).

      If it doesn't help tell us what kind of error do you see on the blue screen.

      Delete
  11. Kind of stupid question....
    Is there any develop to take advantage of realtrigger tecnology?: http://www.realiteer.com/diy

    ReplyDelete
    Replies
    1. This looks interesting but it still looks to early in development to integrate. When it comes to hand control our main focus is Daydream because Daydream will be probably the most widely available tech in the future.

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

    ReplyDelete
  13. Really hope that there is a payment options that can pay via google play store.

    ReplyDelete
  14. It is posbible to add support of old (fermi) nvidia optimus laptops (like gt 630m)? Because now Intel QS not working on this laptops with win10 (steamvr run correctly and tracking work fine, but stream not working)

    ReplyDelete
    Replies
    1. Software encoding will be added eventually but I'm not sure how good it will work performance wise.

      Delete
  15. Anybody else with "Compositor" error since last SteamVR update?

    ReplyDelete
    Replies
    1. Beta or stable SteamVR channel?

      Delete
  16. Hi guys,
    the riftcat pc client isn't working for me.
    as soon as i open it it crashes.
    my specs:
    nvidia geforce gtx 960
    amd fx 8350
    8gb of ram

    ReplyDelete
    Replies
    1. Send us logs located in RiftCat folder to support@riftcat.com
      https://support.riftcat.com/hc/en-us/articles/208781529-What-diagnostic-data-log-files-should-I-send-with-bug-report-

      Delete
  17. You will want to be using Windows 10 since you are using Nvidia. If you are already, try restarting your computer a with all other startup items disabled to see if anything is conflicting.

    ReplyDelete
  18. It keeps repeating awaiting VR stream connection on my phone and it's telling me that both my computer and phone are connected but every 2 seconds into starting a game it crashes and says VRE.Vridge.Transmission has stopped working, i've tried on multiple games with the same result. Any help please?

    ReplyDelete
    Replies
    1. Pipe reading error: System.NotSupportedException: HW encoders were not found.
      at ckfpH982RRoFx$tQ8JHmFZDAzvleTNmoynCixm1mZiIPXuohW8hncKJu0$3O5DRx2w.8rLdgBdkUWeJBp$zBtSWudw()
      at ckfpH982RRoFx$tQ8JHmFZDAzvleTNmoynCixm1mZiIPXuohW8hncKJu0$3O5DRx2w..ctor(EncoderSettings settings, pHWBtLWF4r37Uz2XWZQ6JWBtBeOZbc17pSU2NZMYGBbtNGvdXS7CZxk77JjnZq8EbFusN3agVXbc$uoZq_124aw sourceDesc)
      at ?????????????????????????????????????????.?????????????????????????????????????????(EncoderSettings , FrameInfo )
      at 58w$rpqJGOQXCxWaM8N6pIeAD6JrTmi3t8CAJo_rACzwzc5nvssElybLShD8Xd7iEw.ssLwnwxeW4wJ5tvQ6$xPn84(FrameInfo )
      at SbQyGSgiT_OQ9JGh4C_lN6JDrDamvWkkeZE7zDXWYHtI.D$ymArgNwqxBvULOSxVRsD8(Packet )
      at SbQyGSgiT_OQ9JGh4C_lN6JDrDamvWkkeZE7zDXWYHtI.PsN2d1r03vqCz9JIKu_PaZQ()
      Connection monitor: timeout.

      Delete
    2. What is your video card and operating system? This error is usually thrown only on unsupported hardware.

      Delete