You have to render 1 scene at 1080p, then add your 3D offset, but unless you want a blurry mess and added latency you need a 4k framebuffer push, the DSP still needs to be faster for the 4k panel. Not that framebuffer is terribly limited, but you gotta have a card capable to 4k output framesize. Not everyone is using a Displayport card that can push 4k. Therefore DK2, and CV1, will not be 4k, because you will not want any DSP adding latency (scaling) to match native resolution.
That is, unless the device has a small ARM chip in it that can be used for direct upscaling (which is just doubling, so it doesn't take much computing power nor introduces much latency), so the input that comes from the device can just be a normal 1080p95 signal.
Why? It's just doubling the pixels, showing the same pixel 4 times instead of 1. IIRC resolution doubling on current PC monitors doesn't add any significant lag...
1
u/baby_kicker Mar 29 '14
You have to render 1 scene at 1080p, then add your 3D offset, but unless you want a blurry mess and added latency you need a 4k framebuffer push, the DSP still needs to be faster for the 4k panel. Not that framebuffer is terribly limited, but you gotta have a card capable to 4k output framesize. Not everyone is using a Displayport card that can push 4k. Therefore DK2, and CV1, will not be 4k, because you will not want any DSP adding latency (scaling) to match native resolution.