A lot of modern phones screen length wont be fully displayed in the viewer you have, so its best to use the QI code on the viewer and let Vridge adjust the res to the viewable area, if you dont want clipping
This is a good point, I never had these issues since my phone (Nexus 6) still has a 16:9 aspect ratio. However the viewer I use doesn't have a QR code to my knowledge.
@@SuperiorSandbox Ive been playing around with riftcat for a few days, and have found - by far - the biggest issue is stopping the phone from thermal throttling and thus it's cpu downclocking. - this usually takes 5 mins of Assetto Corsa - and is evident with bench-marking a few times contentiously with the same settings. Most folk's PCs wont have any issues with the require spec, but the heat of the phone will quickly diminish the device's capabilities for VR. My phone (LG L6) is old but it has 1440p, true usb 3.0 data transfer speeds and is HEVC compatible - seemingly a great fit for riftcat. But the heat generated means it cant be pushed at all. Its best to ditch HEVC - certainly at 60 fps - and just use media foundation encoding at 17 mb/s and be content with a steady locked 30 fps, if I'm playing for any amount of time.
is the microphone supposed to work when using this? just got it working on the quest and have audio piping through from steamvr, but no one can hear me in the mic.
As far as I know, it will not stream audio input from your phone. It can stream audio output from your computer. If you want to use a mic, you need to set one up independent from Riftcat.
@@jozsefsari8324 Agreed that worked for me. You should go to protection history if you haven't done that already, your computer might have blocked an application.
Your IPD explanation is wrong. IPD = Inter-Pupillary Distance. It's basically the distance between your eyes. The knob above your VR glasses controls de focus, not the IPD.