Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I'm using link, and you can force 120hz using adbt RIGHT NOW if you have the new update, and everything in oculus mode (not standalone, I mean oculus sdk) runs at 120hz but steamvr forces is it back to 90hz.
So its likely its not fully implemented yet.
https://www.roadtovr.com/facebook-hints-oculus-quest-2-120hz-refresh-rate/
But you can use 120hz in pc vr on games that don't use steamvr right now. It's not fully implemented on oculus pc app either, but I can use it there using adb anyways. It doesn't make a lot of sense for steamvr to specifically cap the framerate if I can use the higher frame rate everywhere else.
However the point is your complaining about an experimental feature which is not fully implemented, which could be causing your problem,
They say that the feature will eventually be enabled by default allowing apps to run at 120 if desired by developers, this would suggest that at this moment in time, not all apps are being allowed to run at 120. Which would be inline with what you are finding.
I personally would not be worrying about an experimental feature, until the feature was rolled out and the problem was still there.
I mean I could be wrong and that 120 should work with everything, if someone who knows more posts, then great, but again if I was testing something that was experimental, I would expect issues, non working features and bugs.
The problem I have is that steamvr is capping the framerate. Sure it's an experimental feature, but steamvr is capping it when I personally believe it should be uncapped or let us uncap it since it's such an open software. Just hoping this gets fixed when 120hz is fully enabled, and I can see why it's sort of irational to complain about an experimental feature, I just wanted to know if there would be a way to uncap it
If your Quest does not have 120Hz enabled in the headset: capped
If AirLink or Virtual Desktop settings are not set to 120Hz: capped
Basically, go through all settings of everything in the chain and you'll get 120Hz wireless
Im using the cable
120hz has worked on the quest 2 since it came out of beta on the oculus software almost 2 years ago. Works great lol