What Problem Does This Solve?
Different VR headsets have different performance limits:- Quest 2 has thermal/power constraints
- Quest 3/Pro can handle higher quality
- PCVR depends on GPU capabilities
When to Use This
Use device overrides when:- Supporting multiple Quest devices
- Targeting both standalone VR and PCVR
- Users report performance issues
- Optimizing for specific platforms
- Want automatic quality adjustment
Supported Devices
Quest 2 Optimization
Quest 2 has thermal and power constraints that limit encoding performance.Recommended Quest 2 Settings
Apply Quest 2 Overrides
Why These Limits?
Thermal management:- Quest 2 SoC (Snapdragon XR2 Gen 1) generates heat under load
- Extended recording → thermal throttling → frame drops
- Conservative settings prevent overheating
- 10 Mbps @ 30fps = ~1.2 GB per hour
- 20 Mbps @ 60fps = ~5.4 GB per hour (too much for casual recording)
- Higher quality = faster battery drain
- 30fps encoding uses ~30% less power than 60fps
Quest 3 / Quest Pro Optimization
Quest 3 and Quest Pro have better cooling and more powerful hardware.Recommended Quest 3/Pro Settings
Apply Quest 3 Overrides
Automatic Device Detection
Detect the device at runtime and apply appropriate settings:Custom Override Configuration
Using Config Files
Create platform-specific config files: Config/Android_Quest2/DefaultGame.ini:Runtime Configuration System
Performance Monitoring
Monitor encoding performance to validate your overrides:Thermal Management (Android)
On Android, monitor thermal state to prevent throttling:User-Selectable Performance Presets
Let users choose their own balance:Best Practices
1. Test on Target Devices
- Quest 2 has different thermal characteristics than Quest 3
- PCVR performance depends heavily on GPU
- Test with your game’s most demanding scenes
- Monitor frame times during extended recordings
2. Provide User Options
3. Document Device Support
Clearly communicate what works best: In-game tooltips:Key Takeaways
Quest 2: HD @ 30fps max — thermal/power limits
Quest 3/Pro: Up to 4K @ 60fps — better cooling and hardware
Auto-detect device — apply appropriate overrides at runtime
Monitor performance — track frame times during recording
Watch thermal state (Android) — reduce quality if overheating
Offer user presets — Quality, Balanced, Performance
Test on target devices — editor performance ≠ device performance
Related
- Best Practices — General optimization tips
- Enums Reference — ELCKVideoQuality enum values
- Types Reference — FLCKRecordingProfile struct
- Architecture — How platform detection works