SMI to Unveil Eye-Tracking and Foveated Rendering for Gear VR at MWC


Having demonstrated their impressive eye-tracking and foveated rendering technology to us at CES last month on a modified Oculus Rift DK2, the company have now unveiled they’ve applied the same principals and technology to Samsung’s mobile VR headset, the Gear VR.

SMI demo’d their eye-tracking technology to us at CES last month and along with our first glimpse at foveated rendering, all on a heavily modified Oculus Rift DK2. The demonstration proved not only that SMI’s gaze detection systems were worked, they were quick enough to allow the implementation of foveated rendering almost imperceptibly.

What we weren’t allowed to talk about though, was that SMI had plans beyond the desktop VR hardware space. At CES I got my hands and eyes on a modified Zeiss VRone headset, powered by an Android smartphone. The headset included a retrofitted version of SMI’s eye-tracking assembly and an early integration of their software. The mobile VR demo included a near identical version of the ‘exploding box’ demo seen in the demo series below. With the exception of a noticeable increase in eye-tracking latency (and therefore overall timing accuracy) it was an impressive demonstration of the company’s portability and commitment to getting this system right for multiple VR platforms.

Now, SMI are ready to show more about their mobile VR eye-tracking plans, and they’ve revealed that they’ve now managed to ‘upgrade’ Samsung’s Oculus engineered Gear VR headset with eye-tracking and are ready to demonstrate foveated rendering for mobile VR.

See Also: Hands On: SMI Proves that Foveated Rendering is Here and it Really Works
See Also: Hands On: SMI Proves that Foveated Rendering is Here and it Really Works

We asked SMI’s Executive of OEM Solutions Christian Villwock, to give us a summary of progress since CES. “At CES, I’ve shown you an early prototype based on the Zeiss VRone which is a Google Cardboard design using the Cardboard SDK and running on Android – Cardboard is not really optimized for running on Android with low latency,” Villwock says. “Our focus in the last weeks was on adding eye tracking to the Gear VR – the Gear VR with its software is much more optimized and tweaked for VR under Android, especially for latency. Our eye tracking platform is generally available for integration with all mobile VR headset but our reference design that we’re launching at MWC now is based on the Gear VR.”

Quest 3 Teardown Shows Just How Slim the Headset Really Is

Foveated rendering is a rendering technique that takes advantage of the fact that your eye perceives high levels of detail only within a small area of focus at any one time. This means that, an image can be rendered at increasingly lower levels of detail, potentially imperceptibly, the further from that area of focus you go. Less pixels to push means less clock cycles, means less power used means higher frame rates. At least that’s the theory.

SMI-DK2-Eye-tracked (3)

Arguably, the benefits that foveated rendering might bring to the mobile VR space are greater than that in the current desktop arena. The ability to decrease load drastically on comparatively lowly mobile silicon will become more and more important as the expectations of consumers grow in the Mobile VR space.

SMI will unveil their Gear VR eye-tracking hardware and foveated rendering demo’s at the Mobile World Congress in Barcelona from the 22nd February. Road to VR will be there to go hands on with SMI’s latest push into eye-tracking applications.

This article may contain affiliate links. If you click an affiliate link and buy a product we may receive a small commission which helps support the publication. See here for more information.

  • Bryan Ischo

    Pet peeve time: pixels and clock cycles are countable entities so you should write “fewer pixels means fewer clock cycles”. “Less” is for uncountable entities like detail and quality, such as “less detail means less quality”.

    • Falcon195
      • Bryan Ischo

        So that’s a disputed wikipedia article describing why incorrect use of fewer and less has become normal practice to the point that someone wants to call them “correct according to conventional usage”. Ho-hum.

        • Falcon195

          I was backing you up. My mistake.

          • Bryan Ischo

            Well, appreciated, I guess? But a little more context than a wikipedia link could help avoid confusion. The article you linked to seems to me to be contrary to my position anyway, although maybe I didn’t read it closely enough.

  • DonGateley

    It will be nice when one can actually get this. It is what will make 4k, 8k and above screen resolutions possible without correspondingly huge increases in compute power.

    OTOH it another great arena for fragmentation and incompatablity.