Dio wrote:I had absolutely zero problems running Alyx over the link once I had a good USB3 cable. (That was more of a challenge than expected mind, I hadn't realised quite what a shitshow the USB-C cabling situation has got itself into). I saw no perceptible VR quality difference to native Quest software, and it was a vastly better experience all round than the DK2 I had mostly used VR on previously.
This was a Ryzen 1900X and 5700XT rig of course, so plenty beefy, but I suspect the point is that the limitations are not the link itself or SteamVR, but the whole system.
I give you "an instant example" and keep in mind "all LS SW heavily is based on it" .. two words "that kill the Adreno GPU" .. "ALPHA BLENDING" also dunno why even the word "POINTSPRITES" seems to have problems.
And I am not even talking about "superweird shaders" or "mega complex thing" we can really talk about "1 fragment shader, 1 vertex shader, 1 single buffer full of one primitive type to draw".
Stuff that on a PC "we can TRULY do MILLIONS of those primitives" with that same shader/etc. on the Quest "you can't do the same identical thing", the peformance goes immediately low.
Then there are "quite a number of peculiarities" I found on Quest, little things but fundamental on the shaders that "you change just a couple of what for you are minor things" ( and let's say they seem to make almost no difference whatsoever on a pc ) you can go from "good performance" to "really shit performance".
I suspect the "Raster OPs" capabilities of the Quest are NOT really that big, and you can really see it by "drawing bigger things", you draw something "up to a certain size" with certain fragment shaders, all ok, you really make polygons "a bit bigger" performance goes crap.
Not to mention the SPIRV/GLES compiler on the Quest seems to be "a bit shit", it's a fraking pain in the arse to compile/debug shaders on it becuase the tools are SHIT and the error messages are often nonsensical or "obscure" ( i.e. of the sort of "internal error 7788" except that is nowhere described what it could possibly mean , or even more obscure ).
And then you "simply" found out after MUCH ripping your hair off that "you declared something vec3 and it did NOT like it because it wanted ONLY vec4 aligned".
Also that is "more pants" because happens at SPIRV level so you can see it ONLY at runtime, the "validation" tools before tell you "it's all ok" and it is, it's in the SPIRV-to-real-gpu-shit that the stuff goes shit.
But yeah NO, YOU CAN NOT take something "that you debugged already and works nice on a PC" and assume it will work on Quest, it won't ..
On the other side is more likely that once it works fine for Quest it will work "0 effort" on a PC ..
So what I mean a PC probably has so much power that over a very good link can do better BUT , THE WHOLE POINT OF THE QUEST IS NOT BEEN TETHERED !!
Which opens .. "a very scary idea" .. WHAT IF .. they find some "superweird wireless mode" where at this point "you don't need the cable at all but you stream wirelessly".
And at the point "even one more step back" .. "you don't need any CPU/etc. at all powerful in the Quest" you are "tethered to a PC without wires" ?
But then you'd loose the "all in one VR system thing".
HUM.