Tag: Google

Google-IO-2016-Logo
News

Google I/O 2016 Opening Keynote begins at 10am PST. Watch it live right here!

Like always Google will be live broadcasting the opening keynote speech for this year’s Google I/O conference. And just like we do each year, we will be sure to have all the live streams from the entire conference available here for viewing for those of you who can’t make it to the actual event. This year’s Google I/O should be pretty interesting, especially with what we already know is going to be making their debut.

Google-CardBoard-IO-2016
News

Google may finally be releasing an Android-powered VR headset at Google I/O 2016

In other VR news today, word on the virtual street is that Google may be gearing up to release an Android-powered Virtual Reality headset of their own at next week’s Google I/O 2016. This wouldn’t be a massive surprise or anything if it actually came to pass, since this is the next logical step from Google Cardboard in the world of VR headset evolution. This is especially true with yesterday’s news that there is over a million active Gear VR users.

RiftCat-VRidge-Android-App
News

RiftCat updates their VRidge Android application with SteamVR / OpenVR support

RiftCat has an application called VRidge for Android which allows users of Android-based VR headsets, such as Google Cardboard, to play PC Virtual Reality games on those non-PC VR headsets. Today’s announcement is a big one, which is an update to VRidge that adds SteamVR and OpenVR support. This essentially means that if you own a Google Cardboard VR headset you can play most, if not all, SteamVR games without needing to pay $799 to own an HTC Vive.

Vulkan-Android-Support
News

Khronos launches their Vulkan 1.0 APIs today for developers to snap up and start using them

You may or may not remember back in August of last year when we reported on Google making the official announcement that they would be using Khronos’ Vulkan platform for Android developers to use its low-overhead graphical APIs. In a nutshell this is supposed to improve performance by providing developers more direct access to the GPU itself. Developers can manage memory and multiple threads on their own instead of leaving it up to the driver.