New to the forums? Click here to read the "How To" Guide.
Developer? Click here to go to the Developer Forums.
Developer? Click here to go to the Developer Forums.
1000k triangles per frame: Quest or Quest 2? What is the difference? Why the update from 100k?
aRchMaGe333
Posts: 6 NerveGear
The official documentation page "Testing and Performance Analysis" has been updated to state that the recommended "load" for tris count is 750-1000k.
This used to be 100k. A professional who constantly works with Oculus Quest VR in a major firm recently quoted this for me, then I found out it has been changed (not sure how recent the change is).
My questions are:
1) Where does this change come from?
... and more importantly... :
2) What is the difference between Quest and Quest2 when it comes to this recommendation (triangles per frame)?
Can we have separate recommendations for Quest and Quest2, with numbers and everything? Surely it's not the same number?
This used to be 100k. A professional who constantly works with Oculus Quest VR in a major firm recently quoted this for me, then I found out it has been changed (not sure how recent the change is).
My questions are:
1) Where does this change come from?
... and more importantly... :
2) What is the difference between Quest and Quest2 when it comes to this recommendation (triangles per frame)?
Can we have separate recommendations for Quest and Quest2, with numbers and everything? Surely it's not the same number?
Tagged:
0
Comments
You're spam-trolling.
Someone please actually answer my post?
Yes the quest 2 has much more power gpu wise with the xr2 chip ang 6 gig ram.
So the increase in triangles is very possible with AI and video upscaling. The danger is over developing for the xr2 chip.
What i mean is you have quest 1 users that would be out of luck if developers aggressively developed for the xr2 then the 835. Because the truth is the xr2 is capable of 120 hz, oculus made the decision to cap at 90 to be fair to quest 1 users.
So developers are given limits to what should be done. There is ample headroom for the xr2, but they still need to design primarily for the 835, and patch for quest 2.
Yup, but Oculus said XR2 is only 35% faster than Snapdragon 835, they had to cripple it to save battery power. And the higher res and forcing 90 fps easily eat up all the extra power - but more ram is great for textures.
Compared to new gpus from Nvidia and AMD the Quest 2 XR2 is nothing but the worst low-end garbage. It's just a new generation of phoneVR/GearVR with Touch.
The great thing about Quest 2 is of course that you can use it with a RTX 3080 to experience real VR.
"Ask not what VR can do for you – ask what you can do for VR"
"Ask not what VR can do for you – ask what you can do for VR"
About the "No info" part I was hoping some official statements could be given on this unclarified official page info, apart from the page being "fixed" so that it's clear what it's saying. Nevertheless, thank you for the feedback, Nekto2.
We're all here to help each other by reading the posts and replying to what we read, not spam-trolling with whatever random string of words we divine out of nowhere. How does anyone even have time for this much redundant nonsense?
I (wrongly) assumed Oculus employees were watching these threads. This pertains to the official webpage and the quality of info that people are able to get out of it. It's my free QA for the platform we're all using and what I got in return? A random string of blah-blah that's going to hide the actual answer. People need to get over their inflated self-worth and actually practice what they preach, which is be of service to the many. No one should give a damn about being nice to someone who entered the thread as an a-hole, being of disservice to us all.
SSDs: Intel 660p M.2 2TB, Samsung 860 Evo 1TB, 850 Evo 1TB, 840 Evo 1TB | Startech 4 controller PCIe USB 3.0