Search

MTBS3D We interviewed Steve Venuti, VP of Marketing for @KeyssaTech. They've developed a solid state connector that is cha… https://t.co/081Ie1799L
MTBS3D Jim Malcolm, Chief Marketing Officer for @HumanEyesTech demonstrated their latest combination 360 degree plus 180… https://t.co/dfnwLmc1Os
MTBS3D .@Dlink spoke to us last week at #CES2020 about their latest Wifi 6 mesh router and what it means for end users.… https://t.co/n2HXCcufMX
MTBS3D RT @tifcagroup: Our Client-to-Cloud Revolution Portal is LIVE! Computing is heading towards a world of any place, any device user experienc…
MTBS3D RT @IFCSummit: .@thekhronosgroup President @neilt3d talks open standards and client-to-cloud at #IFCSummit. #CloudComputing https://t.co/T
MTBS3D Please help @tifcagroup by completing their survey by December 16th! https://t.co/nInslvJ1HM
MTBS3D RT @IFCSummit: #IFCSummit Visionaries Panel with @IntelSoftware @intel @AMD and @jonpeddie talks Client-to-Cloud. #CloudComputing #FutureCo
MTBS3D RT @IFCSummit: The Futurists Panel moderated by @deantak of @VentureBeat is online. #IFCSummit #CloudComputing #FutureComputing #Futurists
MTBS3D RT @IFCSummit: Daryl Sartain is Director & Worldwide Head of #XR, Displays, and Wireless Ecosystems for @Radeon at @AMD. He is also Chair o…
MTBS3D RT @IFCSummit: Arvind Kumar is a Senior Principal Engineer for @intel @IntelSoftware. At #IFCSummit he explained the workings of the Client…
MTBS3D RT @IFCSummit: Neil Schneider’s #IFCSummit opening presentation. #CloudComputing https://t.co/CFqiNxSzPV
MTBS3D RT @IFCSummit: Our #videogames in the #clienttocloud revolution is going on now featuring @playhatchglobal @AccelByteInc @awscloud and @Sha
MTBS3D RT @IFCSummit: On stage now, the #Crypto and #Blockchain markets with Professor Bebo White @bebo and Melissa Brown, Senior Director Develop…

What Does SteamVR Consider Resolution?

SteamVR
Interesting announcement from Valve, though we are left with more questions than answers.

There are two ways to enhance the perceived image quality of your VR experience.  The first is to get your computer to deliver the native resolution of your HMD.  Depending on your platform, it currently starts at about 2160 X 1200 pixels and goes up from there.  While an increase in hardware pixels combined with an equal amount of rendered pixels is the ideal option, it's limited to the number of physical pixels on the display and your computers ability to drive them.

The second method is to use a supersampling technique whereby your computer sends extra pixels and smooths things out even though your hardware has a physical limit on what it can display.  It's expensive from a processing point of view, but it delivers a significant improvement if your graphics hardware can handle it.

Through their SteamVR platform, Valve is going to offer an automatic mechanism that will dynamically adjust the resolution of the content according to what your GPU is capable of.  The hope is that users will automatically get the best experience without needing an intimate knowledge of their hardware.

The catch is that Valve was very vague with their announcement.  They say that the resolution will not be lower than that of an Oculus Rift or an HTC Vive, but it doesn't speak to what would happen with higher resolution options like the Windows Mixed Reality headsets or the future generations of the Vive and others.  With lower-end graphics cards, will they just upscale an image like a 720P film being shown on a 1080P television, or is it 100% supersampling where the native resolution isn't changed, and they are only referring to a processing enhancement?

We reached out to Valve directly, and have yet to hear back.  We THINK this is limited to supersampling adjustments versus the native resolution of the HMD, but time will tell.  It's currently available as an option feature in the SteamVR beta.  Check it out and see what you think!

AHAH!  Speak of the devil.  Valve updated their page with more details:
  • This feature takes the setting previously known as supersampling, and automatically adjusts it on startup based on the performance of your GPU with your headset.
  • This setting does not dynamically adjust per application or during application use.
  • If your GPU can't make native resolution on Vive Pro or Windows MR headset, it will scale down and bottom out at the equivalent megapixels per second as a first generation Vive or Rift.
  • If your GPU can't make native resolution on a first generation Vive or Rift, it will not automatically be set below native resolution (and it will perform the same as it did before this update).