@chert1024VR Probably right mate. Interesting that Oculus seems to be restricting our graphics setting, taking out the previous top slider settings on both Q1/2. Maybe this is to help improve stability for those that do not have powerful pc's.
I also just noticed that on the dashboard settings/graphics that neither AA or panel rendering does anything. I usually only use the panel rendering because it seems to make all the home panels look nicer and does not cost much performance. Now they look a little less sharp. If you run task manager you'll see no change in %gpu with them on or off. Again, maybe this is meant to improve stability for the masses.
Likewise, the reduction in usb3 data rates in v27 could be related to stability but I'm not sure how? Maybe to stop people using too high ODT bitrates.
I gotta say that Link runs a lot smoother now and the graphics in apps still looks pretty good. Maybe Oculus is just dragging us all down the the lowest common denominator, lol!
Don't forget to let the drivers update!
What do you mean exactly? Shouldn't this be done automatically? I never saw a prompt asking me if I will allow the drivers to update. You mention "to let" which implies we have a choice also "not to let" them update. Or did you mean giving the Oculus software the chance/time to update its drivers automatically? I have read somewhere that the drivers had stayed the same for a long time, but that they were updated for v27. Please explain, because I would really like to get back to 90 Hz! Thanks!
There is a difference between Q1 and Q2 Link-rendering...
- Q1 = Downscaling on device
- Q2 = Downscaling on PC
And as described before... I'm using a Q2 and didn't have problems with refresh rates.
(didn't have any problem - beside the stuttering/high CPU-usage in Q2-Home, but not with Link/App Home)
I got PTC v126.96.36.199.469 now. 72hz bug was solved. But Link got new problems. lol
- Dynamic bitrate of debug tool (new feature) is strange. Even if I set 1000Mbps in it, the image has many encode noises like fixed 200Mbps. So it's just useless. And what's the meaning of "default" of dynamic bitrate? It has "default", "disabled" & "enabled". We need "default"?
- Sometimes horizontal line appear in the screen. The image above the line is good, but below is very whity & noisy.
- The edge of screen (bottom) is cut off, and I can see a strange pattern. It's very noticeable & annoying.
This problem is happened on encode resolution bigger than 3664.
Distortion Curvature "Default" & "High" is the same in PTC v28.
"Default" & "Low" was the same in previous versions. Always strange. What are you doing?
And Encode Resolution Width has a bug, too.
3664 on debug tool, actual encode resolution is 3680.
4000 on debug tool, actual encode resolution is 4000.
4010 -> 4032
4030 -> 4032
4033 -> 4032
Higher than 4034 -> not work
Bug1: Input value & actual value don't match unlike previous versions.
Bug2: Max encode resolution width is lower than previous version. Previous versions were 4080.
Still no fix for the Rift S post-Ver.25 USB/Controller/Crashing issues. I realize it's not officially supported, but they managed to screw it up completely right before they quit supporting it, as in 2 updates before that? I think all of us who bought one in the last yr or so deserve to at least have working hardware, mines only 5mo old !!!