fix: declare supported Quest devices

This commit is contained in:
XxJSONDeruloxX committed 2026-10-15 21:18:50 -04:00
1 parent e9a199285e
commit 16e083545b
2 files changed
+8

No files matched your search

+1
View File
@@ -38,6 +38,7 @@
android:isGame="true">
<meta-data android:name="android.game_mode_config" android:resource="@xml/game_mode_config" />
<meta-data android:name="com.oculus.supportedDevices" android:value="quest2|quest3|quest3s" />
<activity android:name=".QuestXrActivity" android:exported="true" android:launchMode="singleTask"
android:permission="android.permission.DUMP"
android:resizeableActivity="false" android:screenOrientation="landscape"
+7
View File
@@ -180,6 +180,13 @@ performance for the running OpenXR session. These are runtime-managed hints;
device power and thermal policies remain authoritative. Unsupported or rejected
requests do not prevent startup. This does not change render resolution.
The manifest declares the supported Quest models using Meta's standard
`com.oculus.supportedDevices` metadata. Without it, Quest 3 used compatibility
mode and its refresh-rate API returned an empty capability list. With the
declaration, the test runtime reported 72/80/90/120 Hz; a fresh normal launch
used 72 Hz in both OpenXR telemetry and SteamVR's HMD property. DroidDeck leaves
the refresh choice to the runtime. No forced refresh override is included.
### Experimental flat games in SteamVR
Start SteamVR first, then add `droiddeck-steamvr-game %command%` to a flat