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.

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 :)

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.

can you please upload a simple full package. Using installers on my computer is a general problem no matter what. would rather just have a full package so i can see what is going on with my connections and not rely on the 80% installer.

can you please upload a simple full package. Using installers on my computer is a general problem no matter what. would rather just have a full package so i can see what is going on with my connections and not rely on the 80% installer.

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?

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.

I was using a BT Home Hub as a wireless extender but got frustrated by random drops in quality. So I dug out my USB C to Gigabit Ethernet adapter to try that again. I was so glad I did. I can now ramp up to the Extreme setting with no issues. So I agree with Jason Beger. If your phone supports Ethernet then use it with your Gear VR (2017). My RiftCat VR has never been so good. And shows the amazing work the team has put into this amazing piece of software.

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.

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.

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

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.

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.

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.

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?

It should launch your default system browser asking you to login in there. It's working for us. If it continues to fail for you, please send files in Riftcat/logs directory to support@riftcat.com with problem description.

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.

I have a USB C Ethernet hub that has three USB 3 ports and a Gigabit Ethernet on the end. The make is Ucouso. The USB C cable end that connects to the phone is USB 3. In have confirmed when 8 plugged it into a router that the Ethernet is Gigabit.

I cant get the version 2 beta to install, i download load it, run it and withing about 2 seconds i get the error Riftcat20Installer.exe has stopped working, i don't even get chance to install it. I've tried with my virus checker turned off, turned off windows defender, tried with and without administrator privileges and it just instantly crashes. my setup is windows 10 pro x64, ryzen 7 1700 cpu(oc to 3800mhz), 16 gigs corsair vengence memory running @3200mhz, a gigbyte gtx 1070 gpu and Rog Strix X370-F Gaming MB. windows is installed on a 250gb ssd drive. i dont know what else to do.

ok, i sorted it, the problem was being caused by Display Fusion Pro. i think it was because DFP adds extra icons next to the standard minimise/full screen/close icons and because the installer doesnt use a standard window when installing DFP just caused the installer to crash. i just turned it off while installing and everything now works fine, Thanks.

I have sent logs from 1.5 standard Cardboard version because beta testers for Oreo on the S8 in the UK got an update today.I retested 1.5 which previously gave me a black screen when streaming. This now works again. I also tested HEVC which also works again! I have sent logs from 1.5 for the jitters on Samsung devices and logs showing HEVC working.I also tested the cardboard version of 2.0. I tested normal and HEVC, which also works now on version 2. I knew it was a Samsung problem.But much to my surprise with the Cardboard version of 2.0. When using HEVC the streaming was way smoother when tilting the phone etc. I didn't have a headset on. But I see a vast difference with 2.0/HEVC as apposed to non HEVC. Does this make sense? I know I didn't test the GearVR version at the moment. But what I was seeing on the screen looked buttery smooth when tilting the phone around.

Awesome!!!!! Works really well so far (but I've only tested it a little bit). No drifting :) I couldnt find a setting to adjust the tracking input (gyro, magnetometer...), but so far its super precise. I had to use magnetometer with the previous version, did you integrate gyro and magnetometer into one for this build?

Only minor bug so far is that once I start steam vr, the two images dont meet at the center, but there is a small gap between the two. When launching the app, however, both "test" images do meet in the centre. Not a big deal though, since my headset doesn't show the centre anyways.Keep up the great work!!!!!

Minor correction to my above post. I did notice a bit of drifting, but much better than the gyro method on the previous build. Is it possible to again have the option of using the responsive magnetometer setting from before? Right now there seem to be no options (unless they're hidden).

how to fix the display is too small on my Galaxy Mega 6.3 with a 233 pixel density and 1280 x 720, the side by side image doesnt fill up the entire screen, I used my custom profile, it became bigger but any other way to fix this?

I doubt it will fill up the entire screen. I have a Galaxy S8 Plus with Gear VR and that doesn't fill the entire screen. But it's perfectly fine in the headset.For Google Cardboard style headsets if you have scanned the correct QR code for your headset all should be fine.

The streamview.exe does not stay on the top of the other windows (when using Moonlight Mode). So, if i start the stream and then I open a game like Project Cars, the game window needs to be on focus because otherwise It does not receive controller inputs. When It is on focus it should be still "under" the streamview.exe program in order to not cover the "VR version" of the game.

I'm using beta 2 on both phone and computer and they connect via 5ghz wifi but no game is shown on my display. I don't wanna play SteamVR games, just wanna play some PC games with Tridef. But after starting a game via Tridef, the Gear VR only says "awaiting Steam VR stream". What can I do? Tried disabling firewall and all encoders.

Unless I have lost my mind. VRidge does not support non VR games. So it's Steam VR or nothing I'm afraid.Riftcat have talked about support for non native VR game support. But I think it's some way off.

Riftcat 2.0 dont work as good for me after 2 days of testing, riftcat 1.0 (latest version), works with HEVC and max Bitrate with USB-Tethering BUT, due to cardboard mode and no gear vr sensors i get horrible drift.I tested with others and idk why but the programm that was never working for me (stream theater) works in gear with litteraly no lag with my 2,4ghz router (moonlight).But seeing forward that these things will be fixxed.

No.Unless the game supports the HTC Vive or the Oculus Rift (with Revive) you are out of luck I'm afraid. Basically the game must have native VR support.And either way, Steam VR will be used.Whoever told you that you could stream your normal PC games was incorrect.At least for time being at least.Other than Trinus, I don't really know of any other viable solution.

When using moonlight, the app can't start Streamview (failed to start streamview.exe), tried reinstalling both (pc&app).Also causes HEVC Blackscreen on my Galaxy S7(SM-G930F), but i don't know if its even capable of it. :D

Moonlight now works, is there a workaround for using BigScreen with Moonlight? Cause the BigScreen streams the fullscreen Streamview screen which causes my steam vr to crash because if the black warp whole the restreaming creates.(And with Tridef injecting steam before starting riftcat i got an steamvr can't be loaded, if thats a thing). Ty for the support and i like version 2.0 much more.

hello so far trying beta get crashes, and that would not be much of a problem. Thing is i cant even open it anymore without reinstaling.once it does crash it keeps saying "a problem caused the program to stop working..." not much. windows 10 creators 64bit (gtx 1070, i5 4690k, ddr3 2x8 1600)

Just update both client and server for Vridge 2.0. I'm on a S7, at first the client detect the server, but as soon as I click on Start, inside my visor I see that Vridge lose the Connected status and go back searching ('Searching for Riftcat Application'). Even if I stop the server side, the client keep loocking for it. I changed various setting, but I have no luck. I can't use Vridge anymore :(

This update isn't working at all, wireless connection crashes the min I launch steam vr, and usb tethering keeps stuck at "is that your phone?" even after clicking yes please fix :( The phone I'm using is your average galaxy s7 edge.

The problem I have is that my pc recognizes my phone and it pops up the screen with "is that your phone?", but when I click yes, the screen goes away for half a second and then pops-up again, no matter how much times I press yes, it stays in that loop, the problem occurs both in wired and in wireless mode. The old version works just fine.