A few thoughts for you:
-
Where did you get your 2560x1440 number for CV1? I don’t think there’s any confirmed info about CV1’s specs yet. I doubt even Oculus knows for sure what it will be.
-
Pixel count won’t be the only difference in CV1 vs. DK2. Refresh rate may have a much bigger impact. DK2 runs at 75 FPS, but CV1 will almost definitely be either 90 FPS or 120 FPS. The Crescent Bay internal Oculus prototype is running at 90. So, whatever number of pixels you have, you’ll have to draw them 20%-60% faster, too. You might also start getting bound by your other threads, if they’re not already finishing in 8-11 ms.
-
This is just an educated guess, but if the pixel resolution is higher on CV1, you may not need to supersample as much. Of course, if the extra pixels are to widen the FOV so your pixel density doesn’t change, you’ll need to supersample the same, but if the pixel density per degree of field of view is higher, I wouldn’t think you’d need to set the SP quite so high, so that may relax your numbers just a little bit.
IMO this sort of thing is nice to do as a curiosity, but I wouldn’t spend too much time on it. Too many unknowns in the spec, CV1 is too far out still. Just throwing this out there, but if you can get your experience to run well on the Gear, though, then you really know you’ll probably be in great shape for CV1, and you’ve expanded your market.