Oculus Connect Keynote: John Carmack
Why Hacker News recommends it
HN recommends it for Carmack's detailed engineering insight into VR rendering and latency challenges.
What it is
John Carmack's keynote at Oculus Connect 2014 about the Gear VR and development stories from building it. He discusses mobile GPU optimization, latency, and display ideas like programmable interlacing.
Recommended by 2 HN commenters across 2 different months, 2014 to 2021.
What Hacker News said
Strong rec lhl · 2015-06 · on “Oculus Rift”
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: [this video] This talk was a slightly long but very informative discussion of the various challenges in reducing latency and dealing w/ PC rendering: [LINK]
Recommends nickjj · 2021-06 · on “Note that I wouldn’t pass the listed minimum requirements”
> 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: [this 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.
Cites barium · 2014-12 · on “Why movies look weird at 48fps, and games are better at 60fps”
Speaking of "frameless" rendering, I noticed during Carmack's Oculus keynote ( [this 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).
Cites pfranz · 2016-11 · on “Inside Magic Leap”
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