Despite our best efforts to make LIV as lean as possible on your already overburdened systems, some of you may still experience performance issues. It could be that your PC hardware just isn't powerful enough to do VR & LIV together - However, there are a few settings that could (and should!) be tweaked, if possible.
- Turn off Auto Render Resolution in SteamVR - their supersampling algorithm doesn't account for LIV's requirements (you can view it as rendering VR twice). Set it to Custom and begin at 100%, then work your way up/down depending on your results.
- Reduce LIV's target resolution - this is the resolution you are rendering mixed reality at and has a massive impact on performance.
- Set the vrserver, vrcompositor, vrmonitor and OBS processes to high priority in Windows Task Manager → Details.
- Change the encoder in OBS from x264 to NVENC. This greatly reduces load on your CPU.
- If you're using Streamlabs OBS (SLOBS), consider switching to regular OBS. SLOBS' CPU usage is significantly higher - we have reports of it dropping from as much as 5% to around 1.4% on a Ryzen 1700.
- Make sure you use "Game Capture" to capture the LIV Output window as it is the most performant capture option. In terms of performance, the list goes: Game Capture > Window Capture >>> Display Capture.
- If you're using a Kinect as camera source, ChromaFree (our tool for background removal) has quite high CPU/GPU usage. Kinect support is still undergoing some optimization from our end.
If you have an iOS device with an A12 processor or higher you can use our app LIV Camera to record yourself with background removal and better performance.
- An unoptimized avatar, as well as storing an excessive amount of avatars (this in particular can cause long compositor loading times) will cause extra load.
- If playing Beat Saber, disable Smoke and Mirrors in the game settings.