Dogmanbird

the app i saw being developed about 18 months ago (qpro) ran within the headset and the masking was drawn, manipulated and processed inside the headset. It was getting applied to the game being played over link cable. unfortunately i haven't heard anything of it since. Has anyone come across any news lately that is similar to this?

it took me two returns to get a good third one without any dead (black) pixels. If they were at the outer edge I wouldn't have cared but unfortunately they were just off centre. Once I saw them i couldn't unsee them

I'm currently using the q3's hand tracking with fred's htcc, but without gestures and without finger switching, instead opting for switch activation via mouse buttons / scroll wheel attached to the joystick. I find the Q3 tracking barely stable enough if the pointer is linked to the forearm (which it is in HTCC), which works fine for me but requires a fair range of movement of my arm. If linked to the palm or finger joints, i find it too shaky/noisy for precise actions. The pointer in the Q3 headset menus (big menu buttons /easy to point at) seems to be linked to the palm, rather than finger This is where the leap motion v2 has an advantage as it's pretty stable at the palm and even the first finger bone, therefore not needing to wave your arm all over the place to point. Unfortunately it's another bit of weight attached to the front of the already somewhat front-heavy Q3 headset. However, it was great on the reverb g2 which is fairly light. Although the Q3 supposedly uses colour info tracking, if you're already using infra red spotlights (to help the leap tracking) they improve the Q3 hand tracking stability also. They make a noticeable improvement overall

i also use g2, a Qpro and a Q3. If I had to pick one it would be the Q3

before I got into VR, I used a sony eyecam and it was more responsive than my basic 25/30 fps webcam. The eyecam was only about $25 on ebay and can do 60fps at 640x480, or 120 at 320x240. I only ever tried the 60fps but it was worth it over the basic webcam. The best free head tracking results i had were with a xbox360 camera and some software I can't recall the name of. It tracked the face and worked very well considering nothing needed to be worn and lighting conditions didn't affect it.

i wonder if clearing the shader cache might cure it?

At one stage I thought I could see a performance difference between the two methods, but lately there's been no performance/visual difference how I do it.

i can confirm that the av8b / f18 mfd's are just readable without leaning forward when using either openxrtoolkit resolution override at about 4000 x XXXX, or alternately, the in game PPD at 1.8 or higher (and leaving q3 resolution settings at default - auto)

ok thank you. Maybe it's only affecting particular devices such as my hubs?

but not airlink or Virtual Desktop?

thanks for the reply. Are you using cabled link to play or are you using wireless via VD / airlink and using the link cable to only charge? If you are using cabled link (not VD / Airlink) and your headset was at 5%, would it charge it to 85% while in use, since the v60 update? If you are and it does, would you mind sharing what you are using? Mine did charge reliably while in use before v60 when using cabled link, but now seems to only maintain whatever the charge was when first connected or a very slow discharge (at about 7-11 watts). Wireless Airlink appears to still allow charging at about 14 - 22 watts while in use, using the link cable only for the charge. it's a bummer if meta have done this intentionally. Maybe to prevent overheating etc?

Since the v60 headset update, is anyone here noticing a change to Q3 charging/not charging whilst in PCVR use? With cabled link, it appears to no longer allow a charge rate of anything much higher than about 10watts when in use (as shown on the cables watt meter) while the headset is within the guardian boundary.

In someone's TTL photos from a month back, unfortunately it didn't look like it would have the edge to edge clarity of the Q3 or QPro if they use the pre production lenses

The headphone socket might be software switchable to make it 5.1 chan digital/coax, if you have an amp with coax digital input

Doesn't seem to be a developer account option. In the headset, try going into the Notifications menu / Devices turn off "VR (in headset)" switch turn off "Tips" switch and I also have the "Do Not Disturb" switch on Hopefully one of those will do the trick

ok, yeah it might be an option added in the developer section. I'll take a look

I somehow managed to turn off the quest message overlay popup about "lighting too low for hand tracking" (done in headset menu). Maybe this will hide the hand controller message popups too, if that's what's happening?

Hi Andre, I've been using your soundcard addon now for a couple of years and overall it's been great, thank you. When I use alt+tab and DCS is no longer in focus, it sounds like the .wav samples no longer loop at a zero crossing and start to produce a loud clicking sound where a loop point would occur. Closing the simshaker software (which also closes your addon) and restarting them cures it until the next time I alt+tab. It affects all aircraft. These symptoms have been present since purchasing your software. I haven't seen any other reports about it and I wonder if I'm the only one experiencing it?

Not sure when that change was implemented I can't recall lasers working within the cockpit in any version of multithreading, but they were working in the ST mode in 2.8

ymmv, but it results in intermittent audio glitches when I use anything over 500. strangely, 960 does work better than 940 / 920 / 900 etc for me, but i still get the occasional glitch. I don't see enough improvement (if any) when going over 500 to put up with the audio problem however, i'm running oxrtoolkit res override at 4030 x XXXX (whatever the max is). I wonder if that's why i'm seeing little difference? maybe it's helping the compressor to interpret the image better?

yep, here's where I set it (link encode bitrate). I don't edit the resolution width anywhere

have at least 4 of these and they will charge both the pro and q3 while gaming / flying in dcs when using the battery usb-c port. a bit too big for strapping to headset at the moment they are about $22 AUD if you have ebay plus

hi, for me, cable is the best performing method so far for clarity (due to being able to set 500mbs or more) and stable fps. There's possibly some wifi stability issues with the quest 3 which may be causing jitters, as there is a long running thread on the oculus forum https://communityforums.atmeta.com/t5/Get-Help/Known-Isssue-Unstable-wifi-covarage-with-Quest-3-on-some-Router/td-p/1090698/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExRMjNOOE9VNkRWSDRXfDExMTQ1NTd8U1VCU0NSSVBUSU9OU3xoSw/page/58 mine seems to be doing better than most reports in that thread, so not sure what's going on.

@winghunter caveats; i find the headset feels heavier than the g2, even with it's short front profile need to use what ever method you desire, to increase game output resolution to achieve similar sharpness/clarity to g2 lots of fiddling with the likes of oculus debug tool etc. to get the best of it likely to need to use ASW for perfectly smooth gameplay on most maps and multiplayer need to find a way to keep it charged during long gaming sessions (it seems all cabled methods are a bit fiddly) unless you're lucky enough to have a motherboard that has 9v 2A usb C need to turn off headset overlay pop-ups as they cause a brief stutter as they appear (low battery warning, low light warning with hand tracking etc) need to use methods to keep the headset awake when removed from head (otherwise DCS may crash under certain conditions) various link methods still don't attain the full clarity potential of the display panels and it gets to about 90%-95% of the g2 centre clarity if you can live with the above, for visuals it's an improvement overall I appreciate people with lower specced PC's find it useful, but I'm not at all fazed that it lacks eye tracking. On the quest pro, by the time I gain the fps performance / clarity I like, when using dynamic fov rendering, the peripherals are a shimmery mess. I'd prefer clear peripheral vision with detail, as I'm using hand tracking throughout the cockpit and often not looking directly at the switch I'm operating.....plus it makes it easier to glance back over the shoulders to check on the door gunners in the huey

if the oculus debug tool is set to at least 500Mb/s bitrate with in-game res or other method to override the resolution to around 2600 x 3300 or more, there are no obvious visible artefacts from my experience. i'm using a TPLink AXE75 6E tri-band wireless router when playing games like half life alyx and pavlov which look great and are perfectly smooth at 6ghz (maintains about 2400mb/s 3metres from headset) . It's working perfectly with virtual desktop and airlink. Reading through the forums, so far it seems to be the most "tried and tested" reliable router that has no issues with 6gig wireless with the Q3. This router is not a modem (just an access point) and I plug it into one of my household modem's LAN ports and the gaming PC lan port. I turn off the AXE75's dhcp server and let the household modem hand out the ip addresses (passing thorough the AXE75 to the Q3) I use cabled link with DCS and MSFS as it's just a little less stuttery at the same gfx settings in demanding scenery and a tiny bit sharper