Here is a post from a long while back from @PimaxSWD about how to get native 4K working on the Pimax 4k, posted by Pimax themselves.
The Turing Architecture deep dive says this:
“Turing GPUs include an all-new display engine designed for the new wave of displays, supporting higher resolutions, faster refresh rates, and HDR. Turing supports DisplayPort 1.4a allowing 8K resolution at 60 Hz and includes VESA’s Display Stream Compression (DSC) 1.2 technology, providing higher compression that is visually lossless. Table 2 shows the DisplayPort support in the Turing GPUs.”
As we all know, Pimax 4K goggle support physical 4K by Interpolation menthod.
Actually, it also support native 4k resolution by using data compression technology（Qualcomm FBC 2.0 or VESA DSC 1.1）, and it works well on android platform. there is the sketch map as follows.
And question arrives, Why not open the native 4k resolution?
The cause is because the graphics card（NVIDIA or AMD）couldn’t support the Qualcomm FBC 2.0 or VESA DSC 1.1 tech. so we have not opened the native 4k resolution until now.
If u are expert on GPU or data compression, please participate in the discussion and try our best to find an valid method to resolve it. thanks.
THE SOLUTION IS HERE FOR ANYONE WITH RTX! @SweViver please alert the software engineers.
Does anyone here realize that the 4k is already the perfect HMD to utterly demolish the HP reverb if it can be utilized fully?
the 4k has 1920x2160 per eye, it has a 110 degree FOV at a PPI of 806, its cost is insanely low, and it used decent non fresnel lenses!
I realize that Pimax is busy with controllers, base stations, 8K-X, etc. but you guys have a secret weapon right under your nose.