3 ms·
It is a big deal in VR, at 90Hz, two eyes, you have 3x the draw calls of a game running at 60Hz. There are some optimizations to reduce the per-eye overhead, b
by cma 10y ago
It is a big deal in VR, at 90Hz, two eyes, you have 3x the draw calls of a game running at 60Hz.
There are some optimizations to reduce the per-eye overhead, but it is still a lot.
Sony's headset can run at native 120Hz, increasing things more, but not too many games are using that mode.
- Retric 10y ago4k at 60fps is 498 million pixels per second, Rift @ 90FPS is 233 million pixels per second. GPU's can deal with making 2 images without meaningful CPU overhead. The real issue is stutter and latency not CPU or GPU GFLOPS.
- Arelius 10y agoPixels/second aren't a very useful metric when speaking about CPU performance. Your comparison seems to show that CPU performance might be much more important than GPU perf for VR. Also, you're correct that GPU's can play all sorts of tricks to get multiple projected views for low CPU-overhead. But that is with significant software support. Otherwise VR will have to build twice the amount of framebuffers/frame as a single view game.
- cma 10y agoWe're talking about draw calls on the CPU, not pixel fill. Still wrong about Rift vs 4K though. Due to the lens unwarping you have to render to a much larger render target to get native screen res. About 1.7x more pixels than he native res. > GPU's can deal with making 2 images without meaningful CPU overhead. I meant to say that with this "There are some optimizations to reduce the per-eye overhead, but it is still a lot." But I didn't word it well. I didn't mean per-eye overhead was a lot after the optimizations, but that the increase in CPU usage was still a lot in spite of them due to the higher update rates.
- deleted 10y ago[deleted]