Dogmanbird

i'm amazed at what meta has achieved with the q3 for it's price when compared to the other headsets. I'd even be happy with a 'display port only' version of a Q3 packed into the reverb g2 housing, for q3 price.

someone mentioned on reddit that the base crystal light is about 700grams. If accurate, it's quite heavy for a pcvr only headset

Thanks for sharing the workaround info. v64 PC app broke it again for me and renaming was the fix

Till now, Oculus link has given me the best results too on q pro and q3 however, my q3 headset finally updated to v64 yesterday/today and I've lost a small amount of fps via link, plus my link cables no longer reliably connect as USB 3 and I now need to flip the usb connectors on all my link cables to connect as USB 3 (very strange). edit- v64 appears be affecting our business headsets in the same way. I think they've tweaked the power settings again. i have a spare PC still on v63 pc app which has the same symptoms as above with the v64 headsets, so might be the headset software causing it edit edit - attempting to sideload v63 (which didn't work) seems to have triggered a later v64 update and I've regained the fps. Unfortunately the USB-C cables still need to be inserted in reverse (several cables tested which worked as usb 3 prior to v64 update) for the connection to be seen as USB 3.

Thanks Qcumber, if it's still the same method as months back, it was scaling down the crosshair as well as the hands. Does that happen for you? does turning off the headset beta updates option allow you to roll back to v63 to see if that helps? I don't recall ever experiencing that. if you are using it cabled, when in oculus link, does the pinch gesture for turning on menu bar or recentering headset follow your hands correctly? (oculus logo in circle that follows hands)

you can use the hand offset settings in the DCS options and see if that helps. I'm using the htcc app which doesn't require pointing with the finger (like shooting a laser beam from tip of finger towards button), instead it requires moving my arm/hand all around the cockpit area like I'm drawing on a giant tablet The hands gets in the way of my vision, so I offset the left hand so it sits slightly to the right of the crosshair, and do the opposite with the right hand (which I rarely use) to keep them out of the way. All I'm concerned about is being able to see the crosshair over the button I need to operate. I wish there was a way to adjust the opacity of the hands (or does it already exist?)

oh? I don't think my system / headset has updated to it yet. edit - still on v63 for both

my htcc settings nullnull

Hi, this is what I have. I've disabled the bottom one as it causes msfs2020 to crash for some reason when entering VR and I'm not sure how it got installed. null

I'll check once I'm home and let you know, but i guess no harm in temporarily re ordering them to see what happens maybe try disabling quadviews and oxtoolkit within the stack just to test. if you can't re order them, i think fred has a utility for changing the stack

any chance it's been disabled in the Open XR api layer stack? (can get to it via steam VR's settings/open xr/manage open xr layers) I've found that the order of the stack can affect things too

^ It's a very nice looking button ring . I'm not aiming to rain on the parade - just wanting to share my learnings after experimenting a little bit a while back with a similar ring setup (much more crude) and what I got from it; - as small as it was, it was still getting in the way - harder to place pointer finger on collective buttons / accidentally bumping buttons when grabbing throttle or grip on the collective. Using a regular throttle was ok for most things. - for speed and accuracy, it needed a "scroll wheel" and a "shift" button to increase the scroll rate when needed. I tried with buttons only but was too slow. - scrolling and pointing on the same hand with precision is very tricky Trying to keep it simple, I set it up as game device, with buttons mapped as mouse buttons in game and with a rotary encoder. However, under certain conditions in some DCS aircrafts, the buttons sometimes wouldn't behave as mouse clicks, where the buttons on the real mouse would still work correctly. I also couldn't find a convenient way to activate the shift and scroll from one hand, to speed up the rate. I ultimately ended up mounting a similar thing (modded version of Firefox's finger mouse) on the joystick which allows me to use multiple fingers for scroll and button presses simultaneously. I glued an extra button onto it, wired down to an arduino on the floor as keyboard emulation for the "shift" button. I point at everything with left hand and button/scroll with the right hand. With the quest 3 and HTCC, with quite good stability, I can get right around the full cockpit with just my left arm even if the switch is in my peripheral vision, provided I use IR spotlights over the cockpit area. Without the IR spotlights, it can get a little jittery for stiches behind the seat if I can't turn my head all the way around to fully look at the switch/dial I don't need it to be wireless, but just need it light weight and easily detachable when switching between joysticks

Qcumber - i completely forgot about bringing home a qpro over easter.

i posted some stuff here about using one a while back

its a $15 finger mouse modified to fit on the stick. operates with middle and ring finger

If not for flipping switches, then what do you use it for? For pointing at the switch i want to operate and use mouse buttons/wheel on my stick to do the flicking and turning. it always works and it's quick

.. can we have a nam map next ...... please : )

i guess the bug has given an indication of how many use just a meta headset alone

I think one of the two "Textures" options, set to low, medium or high, made the difference to the cockpit labels.

glad you got it working anyway

did you stop the oculus service prior to copying, then restart service prior to starting the oculus app?

the link to the two folders shared pages back might cover everyone till things settle down. Pretty easy to do

the last part of my version and runtime end with 045 and 360 which are different to yoyo's. it might be the same for the pc app and it doesn't show it i think we could be getting slightly different versions which might make it hard to pinpoint

unfortunately i don't have a qpro here at the moment, otherwise i would check and test in dcs. tomorrow ill see if i can take one to try

version 63.0.0.400.363 runtime 63.0.0.397.363 which has been the same for at least a week been flying for last hour with no issues