I find it funny when people set the encoder resolution to a higher value and they think it makes a different when its actually bogged. I hope a fix comes soon because while compression is virtually non existant, the resolution is really bad.
I wonder it it's tied to the bitrate you choose? Also, maybe super sampling? Who knows? Until we get a clear explanation for Oculus it's impossible to say for sure imho. In the meantime I've rolled back to v21 I'm just going to stick with it for now since it seems to be working fine with my Q2 with encode res = 3664 and Global SS = 1.20, ASW = auto.
i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 32Gb 6400 ram, 2x2TB SSD, 1000W PSU, Win 11, QPro, Q3, w/Link and Air Link, Vive Pro1 with 2x2.0 base stations, Etsy lens mod and Index Controllers
Wow, you guys are really underselling this update. It's absolutely incredible how good the link works now after setting bitrate to 500 mps. And this is on my quest 1 which I thought was limited to 150 mps. Too bad that there is still foveated rendering but you can't have it all I guess. Will the foveated rendering be the same on quest 2?
UploadVR stated that there's a bug in the encode resolution option Quote:
However, there seems to be a bug in this release preventing custom encode resolutions. The OVRMetrics debug tool indicates the delivered resolution simply defaults back to 2064. Interestingly, setting it to 0 (default) results in a new higher default of 2352.
I checked with OVRMetrics- and it's true, but it's "random" that it's staying on 2352 - don't know how to force it, even mit encode res set to "0"
Just tested this, and I'm getting 2064 regardless of what setting I use in the Debug tool. After opting out of the PTC and rolling back to v21, setting it to 3664 still gives me 2064, as does setting it to 0.
UploadVR stated that there's a bug in the encode resolution option Quote:
However, there seems to be a bug in this release preventing custom encode resolutions. The OVRMetrics debug tool indicates the delivered resolution simply defaults back to 2064. Interestingly, setting it to 0 (default) results in a new higher default of 2352.
I checked with OVRMetrics- and it's true, but it's "random" that it's staying on 2352 - don't know how to force it, even mit encode res set to "0"
Just tested this, and I'm getting 2064 regardless of what setting I use in the Debug tool. After opting out of the PTC and rolling back to v21, setting it to 3664 still gives me 2064, as does setting it to 0.
Can confirm, that this was a "outlier" - I can't reproduce that, but I swear I saw it in the OVRMetrics and it was so much cleaner.... Already did a reinstall, to get the same results - but I don't know what I've done to force this... Essentially I only followed UploadVRs tip...
If it is truly an improvement, you should be able to see a difference. If you need to go to special tools to measure it, then it is not worth harping on about. VR is about perception, immersion and feeling. You shouldn't need to "confirm" numbers.
If it is truly an improvement, you should be able to see a difference. If you need to go to special tools to measure it, then it is not worth harping on about. VR is about perception, immersion and feeling. You shouldn't need to "confirm" numbers.
The thing is that you do see a difference, I noticed the low resolution when compared to virtual desktop which runs I think at native res. But measurements is to know exactly what the resolution is. Regarding compression the difference is really noticiable especially in games with fog, shadow places or many effectsTomCgcmfc said:
I find it funny when people set the encoder resolution to a higher value and they think it makes a different when its actually bogged. I hope a fix comes soon because while compression is virtually non existant, the resolution is really bad.
I wonder it it's tied to the bitrate you choose? Also, maybe super sampling? Who knows? Until we get a clear explanation for Oculus it's impossible to say for sure imho. In the meantime I've rolled back to v21 I'm just going to stick with it for now since it seems to be working fine with my Q2 with encode res = 3664 and Global SS = 1.20, ASW = auto.
I remember an oculus update for the quest1 that also broke the encoder resolution, If I had to guess its just a bug
If it is truly an improvement, you should be able to see a difference. If you need to go to special tools to measure it, then it is not worth harping on about. VR is about perception, immersion and feeling. You shouldn't need to "confirm" numbers.
I agree with you, but we shouldn't ignore that very funny phenomenon called "placebo effect". It's so easy to feel like something changed when actually it's nothing different. Measuring the numbers is always important to counter that effect. Imagine if you think "oh wow, the resolution is so much better now!" and when you measure it you realize the changes didn't actually work and the res' is the exact same as before, lol.
On the contrary, if you feel like nothing changed, but when you measure it the res' did change, then it could be a bug worth noting. But if we assume it's not a bug, then you're right that the changes are nothing to brag about. In every case, it's always interesting to look at the numbers, at least to check that the changes did happen!
I have tried the new bitrate feature in fallout vr on my quest 1. The difference is absolutely massive. From bushes and mountains being compressed blurry blobs to look saweeet. Played with it for around an hour comparing 0 mps to 100 150 300 and 500. Stowing away my cv1 now finally.
