My Quick Guide to Preparing your DK2 app for Oculus CV1

Thanks for sharing.

If i follow the logic, you start increasing the resolution because the cv1 has a higher resolution, then you suggest to lower it back as a quick workaround when an application cannot afford it :)

I am not working on to be retail VR application but if i would, then first thing i implement is real time dynamic resolution scaling. No need to sacrifice pixel density for 100% of the game when only 15-20% of it may not achieve it ! It also often happen on very short moment, like a big smoke explosion or whatever, to lower the resolution in that case is unlikely to be visible.

When DX12 will be standard and available properly to the Oculus SDK, memory aliasing is possible, keep an history of frame duration, and when you are close to failure, alias to a smaller resolution until you detect a lighter situation.

For Dx11, memory aliasing is not possible and allocating a lot of different resolution is out of the way, so the only option is to render into a sub viewport in the render target, and extra care for existing post process to rescale UVs when sampling and prevent reading from outside the valid region.

Yep. Increase the resolution to simulate the amount of pixels/second you need to render. It does ignore some possible bottlenecks like rendering latency, but it's one way of testing.

You can already dynamically adjust render target resolution, at least in Unity.

You set a larger render scale, and simply reduce it when you start a compute-intensive scene. When you reduce the render scale, Unity culls the viewport and renders a smaller frame. You can then jump back to the larger resolution at any time.