Im not being aggresive. I want them to shoot straight with us about what will work on day 1 of the kickstarter with those early backer units. I dont need to be agressive, the industry itself is very agressive.
If they are not as clear as possible about what the headset can do on day 1, kickstarter backers will spit out their bones.
I dont say this to be harsh, but because I want to see this company be a success.
I was in bigscreen the other day in fact promoting this HMD and their kickstarter campaign for almost 2 hours, telling people to come and back the Kixkstarter, and now the company is deciding to tell us right before the KS goes live that it suports 1440p out the gate?
They tell people a min spec of 980? Nobody who wants to back this hmd is doing it for a so so VR product. People want it because its high end, or alleges that it is.
You keep avoiding the question: why doesnât the âregularâ 8k version support native input 4k ? Why are you talking about 2x DP connectors when 1 DP is all you need ? The âregularâ 8k version has all the hardware to support 24k90hz input, what am I missing here ?
You have to input âhalfâ 8K in any case (8Kx4K), IMO they have just verified that only 1 DP 1.4 can not handle that because of problem with Display Stream Compression (DSC) or just simply because this special format drop the frequency because of limited bandwidth. Hence they need 2 DP.
@deletedpimaxrep1 when you say âversionâ do you mean new piplay software or new headset hardware will be needed to enable full 4k input?
If the kickstarter unit has displayport 1.4 it should only need 1 cable, unless you are doing like Dell and using two earlier displayport 1.2 cables with an adapter?
They donât have to half anything. Just send 4k resolution at double the framerate to the headset. DP 1.4 supports 4k up to 240 hz. Thatâs enough to send 4k at 180 hz. Then divide it among the 2 panels. First frame for the left eye, 2nd for the right etc.
One DP isnât sufficient for 2x4K 90Hz uncompressed. They havenât got compression working. Whether thatâs a limitation of their receivers, GPUs, drivers or firmware hasnât been indicated. The specs for the ordinary 8K version remain one DP, with the full rate version using dual DP for dual panels. Whatâs disappointing is itâs taken this long before a straight answer of what it actually does use; 1440p. It beats the Vive and Rift by using more subpixels, higher fill ratio, wider field of view. But trying to sell the 4K panels when thereâs no way to drive that resolution is plainly deceptive. That said, weâre talking 22.1 million subpixels compared to the Rift/Vive at 5.18. Even with the huge FOV upgrade, thatâs an improvement. But at this point, it sounds to me like thereâs no real reason to have the 8K model; only 5K and 8K X.
If you check the forum, a lot of the theory behind this has been discussed - interesting stuff. Thereâs a lot of great info on it buried in post, just have to find it.
DP 1.4 comes with compression ! It supports DSC compression out of the box. all the 1070/1080 cards that have DP1.4 have DSC. But thinking of it ⌠The 4k supports DSC compression but there is a possibility though that their new panels donât support DSC compression. That could be the reason âŚ
Well if problems with the DSC decoding are the reason for 2QHD input only, then it should be still possible to provide 24K@60Hz without DSC. Maybe not high enough framerate for every game, but enough for a virtual desktop, enough for watching movies, enough for slower games.
There is no reason to not allow 4k 60 on this hmd.
The frame buffer in steam vr at 1.5 is already just below 4k resolution, so I dont see any good reason to start it with 1440p per eye.
I wanted this HMD for a legitimate resolution improvement, not just for less SDE.
I want virtual desktop to look close to 720p definition. The SDE in the rift doesnt bug me. Its that all the content looks 480p in headset that bugs me. Lol
Hehehe you keep going on about foveated rendering. Games do NOT support it and most likely will not in 2018. And even if they do support it, it does NOT reduce bandwith at all.
Well there might not be one that does all the things needed. The latency might be to high or the input resolution might be to exotic. Such a decoder might support 8K@60Hz and 4K@120Hz but it might not support 2*4K@90Hz or 4K@180Hz because it is a asic with fixed function.
A custom design therefore would have to use either an fpga which is expensive and inefficient or a custom asic which requires a minimum production count of about 1 million units just to start the production.
Shaders, thatâs game rendering. The only thing that can be supported without the game supporting it is the distortion rendering. But again, it has nothing to do with bandwith.