Oculus Connect Keynote: John Carmack

While this may be true for high fidelity gaming, for moving some textured triangles around, mobile GPUs are fine. Also, they can (and do) perform much better clock-for-clock vs a PC (and especially a Mac) thanks to the ability to optimize drivers. For a fascinating discussion of the optimizations possible, Carmack's 2014 Oculus Connect keynote is well worth watching: [VIDEO] This talk was a slightly long but very informative discussion of the various challenges in reducing latency and dealing w/ PC rendering: [LINK]

> What was Carmack's development focus during Oculus? I'm not sure exactly but there's a bunch of keynotes from Carmack around Oculus Connect on YouTube. Here's one from 2014: [VIDEO] , and another one from a year later where he's live coding in a VR environment [LINK] . You'll find a bunch more if you search too. I remember skimming through them years ago not because I'm into VR development but I've been a life long fan of Carmack's work and like listening to him talk about things.

Speaking of "frameless" rendering, I noticed during Carmack's Oculus keynote ( [VIDEO] ), he talks about trying to persuade Samsung to integrate programmable interlacing into their displays in order to give dynamic per-frame control over which lines are being scanned. This would give you the same "adaptive per-pixel updating" seen in your link, though primarily to tackle the problems with HMDs (low-persistence at high frame-rates).

Found where Carmack talked about it[1]. For VR, the consensus I've seen seem to push for multi-sample AA > full-screen AA > temporal AA (I feel like I've even seen no AA is better than temporal AA). I'm not quite sure if it's performance, architecture (they really prefer forward renderers instead of deferred renderers for low latency), or aesthetics. In the little bit I've done, when just playing with knobs temporal AA looks better to me. Without AA specular highlights are way too distracting and pop too much. This reference[2] talks about the extra velocity buffer needed for temporal AA and the fact it tends to over-blur which can fuzz out fine details (low resolution is a touchy subject in VR). There's a lot of moving pieces when making decisions. In talking about interlacing, he was ideally talking about not having to create a whole image buffer before sending data to the hardware--just rendering parts (well, scanline) of the image that moved. [1] [VIDEO] [2] [LINK]

Excellent list of things to keep in mind. Of course, being The Statue is allowed, if you happen to be John Carmack, legs planted firmly on the stage like a colossus: [VIDEO]