Dogmanbird

some redditors have reported the official link cable will keep the q3 charged if used with a usb-c powered hub as TimberWolf has mentioned above

i just use it for pointing and use a modded mini finger mouse attached to the joystick to turn the dials/flick the switches, so every aircraft ive tried works pretty reliably

if anyone is looking for batteries that will slowly charge the q3 while gaming, these work when connected via the usb-c port (10000mah version) nullhttps://www.ebay.com.au/itm/313876486910?var=612602680292

ive raised the leap controller up about 4cm. it puts the hands within range of the slider capabilities to get the hands aligned. Everything else seems to still work and track well

just been experimenting again. in multithreaded mode I reckon you're right . Not sure if it's changed just since the 2.9 update or because it behaves differently in single threaded mode? In MT it seems to work really well for me now.

yes. you'll get it looking 90-95% of the centre sharpness that you get on the G2 (but all over the fov). you might need to read back through a few pages for suggestions. You'll probably need openxrtoolkit for turbo mode if you use multithreading (it fixes the jitters which are unrelated to gfx settings)

Whilst gaming, I've now got the q3 at least maintaining it's charge and very slowly charging via a $24 AUD ebay link cable (with ac adaptor port) , using a 23watt single usb port AC adaptor. The q3 seems to need a USB A port capable of at least 5v 2.5 amps or 9v 2.2 amps. The AC adaptor I'm using is QC and PD, which might be needed to tell the quest to work with the higher current a typical 5v 2A or 9v 2A so far has not been enough for it to hold the charge and will slowly drop while flying

do you also notice less hand lag in the VR leap mode, than the special mode?

the finger interaction distance is changing almost every flight. A few days ago, and just now, I was able to push buttons and twiddle knobs with just the very tip of my finger as I'd expect (in Special Leap mode). It's as if the finger tip touch location randomly changes based on where my hands are when I enter the cockpit, but I can't reproduce it. It almost never works for me in VR leap mode and can only point / gesture. although I love the leap pointing ability and now can't live without it, I certainly admire anyone who's using the finger switch/knob interaction and still be effective under pressure, even when it is working correctly. the only thing i can rely on it for is to press the master warning / caution buttons

you can use some white electrical tape over the sensor in combination with the displays-off timer, to keep it awake

that was being tested last year so hopefully not too far away. I don't think it's a meta app

If you've got a similar system, i get my best fps performance / visually appealing results in dcs by doing the following. I have all in-game graphics at their maximum settings except lens flares, motion blur, depth of field effects etc, which I turn off; Posted October 24 during this last week, I think i've tried just about all combinations of settings, just to get back to the performance I had with the reverb G2. system 5800x3d, 4090, 32gig ram 3600, all NVME drives in Oculus app PC software; - don't touch the oculus device resolution setting. leave it set to auto. ASW doesn't seem to engage under certain conditions if the res not at auto - set your 72 /80 / 90 hz as you wish. in OBT, don't adjust anything except; - use sliced encoding (no longer sure this is actually having an affect) - bitrate at either 500 or 960 (keeps consistent audio) - set sharpening to quality - set pixel density to whatever gives you satisfactory sharpness v performance (or leave it at 0 and do it in the game) I choose to set only the in game PD to 1.8 or higher and leave debug tool at 0 As Snuten suggested - openxr toolkit 'resolution override' now seems to offer better performance than doing it in-game in OXRTK; - turn on turbo mode if using multithreaded dcs, otherwise the game may have regular short pauses regardless of gfx settings in ODBT CLI; - set ASW to 30Hz I use the batch file mentioned a couple of pages back (may not be necessary now that openxr toolkit 'resolution override' seems to offer better performance) I prefer the multithreaded mode's DLAA anti aliasing option. It's clear and runs smoothly using the above settings over cabled link

the solution to getting turbo mode on for me - uninstall the oxrtoolkit then reinstall it, run the single threaded version of DCS and immediately turn turbo on before doing anything else, then exit DCS and run in multithreaded mode and it should be on. Open your oculus PC software app and check that oculus openXR runtime is enabled You can use these commands to force OpenXR and VR when opening DCS, though I believe using multithreaded mode uses openXR regardless —force_OpenXR —force_enable_VR

There's still no specific proximity sensor setting that I have found. Therefore I still need to place some semi opaque tape over the sensor to stop the displays going blank (but can see display backlight is still on). If they go blank or the headset fully sleeps (and turbo mode is turned on), DCS will crash. We're nearly there i wonder what happened to the proximity setting? Maybe they are worried about burn in?

my headset (and controllers) must have updated during the last 12 hours as it show as v59 and I now have the extra developer options for display timer off and detecting the link cable edit - i wonder if the proximity specific option has been re-labelled with the 'wake headset when there's movement' option? not there at all it seems edit edit - and the oculus PC software has just updated. I reckon I can see a modest fps improvement too. I can now almost run 45hz locked ASW smoothly on the Marianas map flying low in the huey with no other settings changed. The link settings are great (thank you meta) and can now take headset off, sit in on the ground for a while without fear of DCS crashing

yeah I think you are right. I've just noticed it get's a mention in tyirel's video here

apparently; - an option to automagically turn on cabled link within the headset, when the cable is plugged in - an option to turn off the proximity sensor and also adds an option to keep the headset awake permanently (or till the power button is briefly pressed, which will put the displays to sleep / wake up) a couple of steps closer to the convenience of the G2

Hi, has anyone's headset updated to v59 yet (announced a few weeks back)? I'm still on v57 and it hasn't found any updates. The update apparently has a couple of qol niceties for PCVR users

Although I experienced the occasional AI shooting guns through the very tops of trees in 2.8, it has become a regular thing since 2.9 in the Caucasus map and it's now occurring at tree trunk height. I have also seen a sam pass through the trees and I'm fairly sure the perimeter wall around the airbase, travelling a few feet from the ground to hit it's target, which I've never seen in 2.8. I'm sorry I don't have a track to share for this but will try and upload when it happens again.

An old Oculus account or a basic Meta account is still required, but you don't need a full facebook account from what I can see. I'm just using my old Oculus account.

Do you have turbo mode turned on in openxrtoolkit? I think that might be the cause, due to it preventing openxr from passing the frame timing info to/from the game / video card. Probably don't need turbo mode in ST. Ive put the leap onto the Q3. I'm finding the leap tracking is substantially better than the built in Q3 tracking. Still no lasers once in the game in MT, but at least the cross hairs are stable and work all over the cockpit. I hope meta can improve theirs as it would be great to not have to attach more weight/cables to the headset.

I think I'll need to go back to the leap 2 for laser pointing. I find the quest tracking is just too noisy / erratic when used in the same way, to be able to operate things quickly. If there was a way to base the laser on the first finger joint, rather than the tip, it might improve stability. Fred's HTCC would probably be okay with the quest if the pointer crosshairs were more easily visible. Today I haven't been able to see the laser at all in MT How is everyone else's experience so far with the quest tracking?

yeah, unfortunately it's been a lot of fiddling in the beginning

gave 'normal' another try. I think it helps the MFD text readability ever so slightly, though I still prefer the look of 'quality' overall

sometimes that's the same for me in MT. Not sure why they disappear.