This site may earn affiliate commissions from the links on this page. Terms of utilise.

One of the major challenges of ramping upwardly support for the fledgling VR industry is ensuring interoperability for major VR platforms. In theory, games should expect identical on every headset, just companies that optimize for one specific platform over another may be able to wring specific advantages out of doing and so. If yous know how the Oculus Rift's lenses make content look versus the HTC Vive, for example, information technology could testify easier to optimize for those specific lenses. Sliding backwards on overall compatibility, meanwhile, isn't a goal that serves anyone's interests.

That'southward more-or-less what's happened with AMD's Radeon GPUs and a contempo Oculus Abode update, co-ordinate to Tom's Hardware. Prior to this, AMD GPUs had no trouble with Oculus Abode, merely later on, forums filled up with complaints that VR was at present useless. Initial tests didn't isolate the issue, just follow-ups confirmed that everyone with the problem was running a Radeon GPU. Interestingly, the problem isn't confined to one single Radeon model or fifty-fifty GCN variant; THG reports problems with GCN 1.0 (Tahiti) 1.1 (Hawaii) and 1.4 (Polaris). Text in the headset is beingness rendered like this:

THG-Image

Paradigm by Tom's Hardware

THG states the update to Oculus Home is the result of a trouble in the AMD driver, which I don't agree with–if your product works perfectly and then I update my software in a way that breaks your hardware, I'm clearly the person that acquired the problem. While it's always possible that the issue arose considering my software update does something your hardware didn't expect, or that triggered a latent result in the driver, the proximate crusade of the hairball is still the software update. Regardless of this semantic niggle, it'southward going to have to be AMD to fix the problem–Oculus has already said it won't push button whatever more than updates for the DK2 and that the device is no longer supported.

So far, the issue appears to exist specific to the DK2 and AMD Radeon cards, but let us know if you've had any trouble with the headset with other GPUs (or seen the same trouble on the mainstream Oculus Rift). While in that location were never many DK2 owners, they were the early on adopters that helped set the stage for the current platform–hopefully AMD can resolve this event with an update to its ain software or persuade Oculus to set information technology on their stop.

At present read: The Best Complimentary VR Games and Apps