Thursday, May 19, 2016

Dev update #11

We don't have much to show this week but most of our work will carry over to future updates. We spent a lot of time trying to counter sensor drift but our algorithms are not stable and tested enough to release them. Expect more news on that next update.

Desktop client version is 0.5.4.3, mobile app version is 0.8.6.

Changes

Log me in automatically should work more reliably. Let us know if RiftCat client forgets your password again.

1440p compatibility

After last week's 1440p update we received some reports about 1440p not working with some video cards. Here's a list of compiled results and reports.

Generation

Example hardware

1440p @ 60 FPS

1440p @ 50 FPS

1080p @ 60 FPS

AMD GCN 1.2+

R9 285, R9 380, R9 Fury X, R9 390***

✓

✓

✓

NVIDIA Maxwell

GTX 750, GTX 830M-860M, GTX 930+

✓

✓

✓

Intel HD & Iris (Haswell+)

Intel Core i3-4xxx+

✓

✓

✓

NVIDIA Kepler

GTX 650+, GTX 740+

❌

✓*

✓

GCN 1.0 & 1.1 AMDs

R9 240, R9 290, HD 7700+

❌**

❌**

✓

Intel HD (Ivy Bridge)

Intel Core i3-3xxx

?

?

?

Intel HD (Sandy Bridge)

Intel Core i3-2xxx

?

?

?

* Use 60 FPS option. VRidge will try to encode at highest possible framerate.** According to AMD developer it's not possible to encode video with resolutions beyond 1080p with GCN 1.0 & 1.1 AMD.*** There are two 390 variants. One is GCN 1.1, other is GCN 1.2. Removed - 390 is GCN 1.1.

We did not test all of this ourselves. If it's wrong, please let us know so we can correct it. Please keep in mind that some laptop (-M suffix) variants use different chipsets than non-M variants.

Thanks for extensive testing. I still don't understand why there is a difference between QS and MF (they are configured with exactly the same parameters). I'm gonna need to take a look at stream structure.

Media Foundation option uses either NVENC or VCE internally (implementations are provided by NVIDIA and AMD). Quick Sync also uses Media Foundation with some special treatment for Quick Sync behavior but the config is exactly the same with MF & QS.

The config differs only in direct NVENC option because it's separate SDK (we added it because NVIDIA did not provide hardware encoder impl. for Media Foundation versions prior to Windows 10).

To reduce the heat, i have build a fan on my cardboard. In my case it is a 12v one. So i have a cable in my neck. I was scared because my mobile is getting really hot. Now it is cool. You could use a 5v one with an otg cable.

Which res do you use in elite. And which wifi speed do you have?

How is your experience with the z4 and fov. I want to buy one but have no idea how to get it through our customs in germany.

The resolution using Dangueros Elite is established SteamVr, the only thing you can change is the supersampling to improve it, I put it in 1.5x.

The BoboVr z4 are the best. The theoretical FOV is 120 °, I with my mobile 5.5 "do not see the edges, with the Z3 BoboVr if they looked. They have no distortion, and having integrated headphones can use SoundWire to send the sound from your PC to Mobile WiFi. They are very comfortable and weigh little, I recommend buying. you can find them on Amazon, I buy them in China for 29 €.

I use intel HD 530 and windows 7 64bit.First it work only tracking with no display(looping 'awaiting streaming' message).After update my intel HD driver both traking and display dosen't work.How can I solve this problem?

hey guys,Great work and loving the progress of program. Was just wondering if it is in the works that we will be able to run the games in 4k quality? As I have a Sony z5 Premium and it goes 4k. Or is this pushing it a bit too far right now? lol

Unfortunately NVENC streaming doesn't seem to work on my Win7 laptop with an NVIDIA GeForce GTX 860M GPU, phone is a Samsung Note 3 SM-N9005. I've been trying "The Night Café" demo and the desktop app just crashes after launching, then a windows tooltip says the video card has been restored due to a crash. Phone screen keeps waiting for the VR stream.

Note 3 has some issues according to our users but the VRidge desktop crash is more interesting. Could you send logs as described in https://support.riftcat.com/hc/en-us/articles/208781529-What-diagnostic-data-log-files-should-I-send-with-bug-report-