devices:oculus_quest_2
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| devices:oculus_quest_2 [2025/05/04 08:25] – Sean Rhone | devices:oculus_quest_2 [2025/09/11 06:43] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 13: | Line 13: | ||
| ===== Versions ===== | ===== Versions ===== | ||
| + | |||
| + | * 2025/05/04 | ||
| ==== System Version ==== | ==== System Version ==== | ||
| Line 111: | Line 113: | ||
| ====== Notes ====== | ====== Notes ====== | ||
| - | * :!: Developer mode needs manually re-enabled from Oculus app on mobile after Factory Reset ((any issues with pairing will prevent enabling Dev mode; [[https:// | + | * :!: Developer mode needs manually re-enabled from Oculus/Meta app (mobile |
| * Hold PWR + Vol- to access bootloader menu to perform Factory Reset on-device | * Hold PWR + Vol- to access bootloader menu to perform Factory Reset on-device | ||
| * '' | * '' | ||
| Line 233: | Line 235: | ||
| * Last updated: 2022/07/11 | * Last updated: 2022/07/11 | ||
| - | * :!: TODO | ||
| - | * Latency at H.264 is 4ms at 1080p@144, 6ms at 1440p@144, and 10ms at 4K@30 ((HEVC tests didn't run on 22.5.2)) | + | * Latency at H.264 is 4ms at 1080p@144, 6ms at 1440p@144, and 10ms at 4K@30 |
| * It looks ideal to either use 120Hz, or limit encode resolution for lower refresh rates to ~2560 in order to avoid the 4ms spike | * It looks ideal to either use 120Hz, or limit encode resolution for lower refresh rates to ~2560 in order to avoid the 4ms spike | ||
/usr/local/www/wiki/data/attic/devices/oculus_quest_2.1746361547.txt.gz · Last modified: by Sean Rhone