Oculus Go to Offer Fixed Foveated Rendering and Up to 72Hz Refresh Rate

Oculus has revealed that the standalone, entry-level mobile VR headset Oculus Go will support refresh rates up to 72Hz and will make use of fixed foveated rendering.

At GDC 2018 Oculus’s dedicated hour long session was a treasure trove of new and updated information (If you missed it you can re-cap via our live blog coverage right here). One of the many snippets of news was more detail on how the company’s  upcoming mobile, standalone VR headset Oculus Go handles rendering and on its display.

First up is Oculus Go’s display. We know from the device’s launch that the headset sports a “fast fill” (low latency / persistence) single LCD panel at a resolution of 2560 x 1440. What we didn’t know and was revealed today is that display can bump its refresh rate up to 72Hz is the application calls for it. Whilst it seems likely that this will be the gold standard for titles running on Go, given the low-cost, lower power on-board chipset inside the Go, we do wonder how many titles will be sacrifice visual fidelity for responsiveness but if developers do, there’s a bonus in it for them. Chris Pruett (Head of Development Engineering) says if 72Hz mode is engaged that it’ll make the display look “perceptibly brighter” and “improves colors” concluding that “If you can accommodate 72Hz it’ll look really good!”

Image courtesy Oculus

Next up is rendering techniques for developers looking to squeeze every ounce of performance out of the Oculus Go hardware. If you’ve been a reader of Road to VR for a while, you’ll know that Foveated Rendering is one of the techniques many believe will allow VR rendering to reach the levels of detail and fidelity necessary to completely fool the human eye into accepting virtual reality as reality.

.IRPP_kangoo , .IRPP_kangoo .postImageUrl , .IRPP_kangoo .imgUrl , .IRPP_kangoo .centered-text-area { min-height: 100px; position: relative; } .IRPP_kangoo , .IRPP_kangoo:hover , .IRPP_kangoo:visited , .IRPP_kangoo:active { border:0!important; } .IRPP_kangoo { display: block; transition: background-color 250ms; webkit-transition: background-color 250ms; width: 100%; opacity: 1; transition: opacity 250ms; webkit-transition: opacity 250ms; background-color: #eaeaea; box-shadow: 0 1px 2px rgba(0, 0, 0, 0.17); -moz-box-shadow: 0 1px 2px rgba(0, 0, 0, 0.17); -o-box-shadow: 0 1px 2px rgba(0, 0, 0, 0.17); -webkit-box-shadow: 0 1px 2px rgba(0, 0, 0, 0.17); } .IRPP_kangoo:active , .IRPP_kangoo:hover { opacity: 1; transition: opacity 250ms; webkit-transition: opacity 250ms; background-color: #e6e6e6; } .IRPP_kangoo .postImageUrl , .IRPP_kangoo .imgUrl { background-position: center; background-size: cover; float: left; margin: 0; padding: 0; } .IRPP_kangoo .postImageUrl { width: 30%; } .IRPP_kangoo .imgUrl { width: 100%; } .IRPP_kangoo .centered-text-area { float: right; width: 70%; padding:0; margin:0; } .IRPP_kangoo .centered-text { display: table; height: 100px; left: 0; top: 0; padding:0; margin:0; } .IRPP_kangoo .IRPP_kangoo-content { display: table-cell; margin: 0; padding: 0 10px 0 10px; position: relative; vertical-align: middle; width: 100%; } .IRPP_kangoo .ctaText { border-bottom: 0 solid #fff; color: #1ABC9C; font-size: 13px; font-weight: bold; letter-spacing: .125em; margin: 0; padding: 0; text-decoration: underline; } .IRPP_kangoo .postTitle { color: #34495E; font-size: 16px; font-weight: 600; margin: 0; padding: 0; } .IRPP_kangoo .ctaButton { background-color: #e6e6e6; margin-left: 10px; position: absolute; right: 0; top: 0; } .IRPP_kangoo:hover .imgUrl { -webkit-transform: scale(1.2); -moz-transform: scale(1.2); -o-transform: scale(1.2); -ms-transform: scale(1.2); transform: scale(1.2); } .IRPP_kangoo .imgUrl { -webkit-transition: -webkit-transform 0.4s ease-in-out; -moz-transition: -moz-transform 0.4s ease-in-out; -o-transition: -o-transform 0.4s ease-in-out; -ms-transition: -ms-transform 0.4s ease-in-out; transition: transform 0.4s ease-in-out; } .IRPP_kangoo:after { content: “”; display: block; clear: both; }

SEE ALSO
Google Shares New Research into Foveated Rendering Techniques

In a nutshell, full foveated rendering detects where your eye is looking and instructs the application to only render a portion of the display (the portion your vision is centered on) in full detail, with less detail rendered the further you move from the centre of your gaze. When done right, it can be imperceptible to the player and in the process, save significant clock cycles as far less detail is rendered per frame. However, Oculus Go doesn’t sport any form of eye tracking, so how can the headset benefit?

Chris Pruett says that they’re recommending the use of Fixed Foveated rendering which tales the same principle but from an assumed central point of gaze. Pruett says “One of the problems phones have had for years is that filling pixels is expensive,” continuing, “What we’ve done up to now is Rendering to a lower resolution eye buffer. But if you increase the eye buffer resolution, quality goes way up. We built something into Oculus Go called Fixed Foveated Rendering.”

Photo: Road to VR

Again, the central part of the image contains the most fine detail with less and less detail evident the further you move from the central point of the users assumed gaze (where vision is sharpest). Pruett also mentioned the Oculus team worked closely with Qualcomm, the providers of the Go’s onboard chipset (based on the company’s Snapdragon 821), to get the Fixed Foveated using a tile based renderer, working optimally.

The post Oculus Go to Offer Fixed Foveated Rendering and Up to 72Hz Refresh Rate appeared first on Road to VR.

Be the first to comment

Leave a comment

Your email address will not be published.


*