News for hackers. Stuff that matters.
Re:Google Earth VR by mdrzn on Wednesday November 16, 2016 @11:28AM (#12968526)
Why only on HTC Vive? Does this require huge computing power, or is it because of the controllers? I hope it'll become available on the Google Daydream phones.
Re:Google Earth VR by dag11 on Wednesday November 16, 2016 @01:29PM (#12969859)
They had to do a crazy amount of optimization just to the Earth engine to make it work in 90fps VR.

Here's a talk one of the devs gave at SIGGRAPH a few months ago about how they made it work: https://vimeo.com/177549565

Re:Google Earth VR by andybak on Thursday November 17, 2016 @07:22AM (#12976787)
Weird because once you get it running via the hack it runs perfectly fine. I'm running it on a DK2 and the only issue is controller emulation.
Re:Google Earth VR by artofcode on Wednesday November 16, 2016 @11:45AM (#12968733)
My bet would be the controllers, which would mean a Rift compatible release would be imminent when the Touch controllers are officially released in a month.
Re:Google Earth VR by wolrah on Wednesday November 16, 2016 @04:14PM (#12971588)
Most OpenVR/SteamVR titles more or less "just work" with Rift + Touch. Obviously the different controllers mean input mappings might be weird or lacking an equivalent and the in-game representation of the controller might be wrong, but the basics work as well as you could reasonably expect.
Re:Google Earth VR by RossM on Wednesday November 16, 2016 @11:59AM (#12968905)
Same with Daydream - odd that they didn't keep earth for the release.
Re:Google Earth VR by andybak on Wednesday November 16, 2016 @01:03PM (#12969585)
I've been using DK2 + Leap Motion to play some of the simpler Vive only titles. I'll try it and report back.
Re:Google Earth VR by gefh on Wednesday November 16, 2016 @01:54PM (#12970108)
Please do! I'd like to avoid cluttering my desk with too many more gadgets.
Re:Google Earth VR by andybak on Thursday November 17, 2016 @08:39AM (#12977280)
It works on my DK2 when I used this workaround. https://github.com/Shockfire/FakeVive

It's pretty tough to use with the Leap Motion. However - you can run the tours via the mouse on the desktop. (Also - in another comment I mentioned you can edit the tours in a text editor so that might be enough to keep people happy.

Re:Google Earth VR by thebiglebrewski on Wednesday November 16, 2016 @04:49PM (#12971905)
I agree! I don't understand these two separate arms of Google VR. Couldn't they do the processing power on the server side if you have a fiber connection?
Re:Google Earth VR by elaus on Thursday November 17, 2016 @01:26AM (#12974896)
VR needs 90fps with only a few milliseconds of latency between moving your head and seeing the movement in your headset. Both can't be achieved by streaming from a remote server…
Re:Google Earth VR by shostack on Thursday November 17, 2016 @02:01AM (#12975048)
Yet... And once you can leverage the power of the cloud for rendering that makes VR a much more portable proposition.
Re:Google Earth VR by daeken on Thursday November 17, 2016 @04:26AM (#12975840)
This isn't really a "yet" case -- it's just physics. Even if you assume that this is all light speed and that congestion, routing latency, etc aren't a factor -- it's still impossible. You need to send your input (sensory and otherwise) to a server, then get a response, 90 times a second. That's 11ms round trip for the entire transaction. Light can only travel 2050mi in that time, meaning a maximum distance of 1025mi each way. And that's the easy part of this -- not to speak of the massive latency that video compression would add (at least 50ms), the transfer time of the data (if you go with a conservative 12Mbps bitrate and a perfect 50Mbit connection, that's another ~3ms there), etc.

This would be possible if everyone had a VR render cluster nearby (<100mi) and no network congestion ever happened. Otherwise, not a chance.

Re:Google Earth VR by dahauns on Thursday November 17, 2016 @08:53AM (#12977408)
Video compression shouldn't introduce that kind of latency (I get <10ms with Steam in-home streaming), but other than that you're correct, of course.
Re:Google Earth VR by chronial on Thursday November 17, 2016 @04:34AM (#12975883)
90fps gives you 11ms per frame. I have a 20 ms ping to the closest internet servers to me.
Re:Google Earth VR by johansch on Wednesday November 16, 2016 @05:22PM (#12972159)
The roomscale VR that let's you walk around in cities as a giant is really the killer feature of this tech demo.
Re:Google Earth VR by baobrain on Wednesday November 16, 2016 @01:19PM (#12969736)
I'm confused about this as well - this could be a great application for "casual" vr like daydream.
Re:Google Earth VR by alexqgb on Wednesday November 16, 2016 @02:10PM (#12970314)
As a title, sure, but that's about it. As a product, it would be a fundamentally different thing. That's inevitable when one system offers full position tracking and 300 watts of power while the other tracks rotational motion only and runs on 3 watts.