Dogmanbird

Thanks Eldur. Are they photos through your lenses? If it is, it's doing a great job rendering the distant objects, even though the supersampling might be set a bit low at the moment?

i'll prophesise (though i'm probably stating the obvious) - within the next 48 hours will be another video of how vrflightsimguy has discovered a new setting that has improved things and now looks so much better, but it's still not the best yet, because there needs to be a reason to create another 10+ minute video after that........my thoughts after 1 month!........Is quest 3 still worth it in 2024?......

Id guess there's a generous amount of sharpening applied when connecting it via usb, as there is on the pro. Turning it off might help reduce the aliasing for distant objects / horizon etc

Thanks for your updates Hoirtel, I also see the slight hue and brightness change toward the edges on the q pro. I'd have thought it could be corrected by software since it's always the same region On the quest pro, I can increase the vertical fov noticeably by tilting the headset downward (raising rear strap). This also seems to improve the sharpness across the lenses. Reversing the headset rear padding helps keep it tilted down a little. I wonder if the Q3 is similar with regards to tilting and fov?

Hi, thanks for taking the time to reply and provide those details. I thought leap may be working because of this line one your page "Traditionally, VR flyers have been looking for external hardware solutions like LeapMotion or PointCTRL which solve these issues to varying degrees" n...but I've obviously misinterpreted it. I'll try copying those files should I use the vr controllers in the future. Thanks again

i'm not sure many if the reviewers are capable of seeing the difference, but if it is truly capable of 72 and 80, that's great news if someone's got a dslr or mirrorless camera and can hold it to a lens, we'll figure it out edit - could use a phone camera pointed at a lens. if you can't see any banding, or if you see a band moving very very slowly up or down, take a pic, use something like Faststone Image Viewer to check the photo exif data and the shutter speed used. will be great to know 72 and 80 really work.

with all the talk of it only supporting 90 or possibly 120, i wonder if 72 is actually running at 72?

the 512 one goes faster. meta said they'd have painted it red if they could

I'm curious too, as I saw 72 as an option mentioned by another reviewer on reddit. I'd say meta underestimated the interest the 512GB version would have, as it appears there's a shortage and delivery has been delayed for many orders

Thank you for the feedback!

I hope they do too. I've read the v2 has a little more fov coverage and an overall tracking improvement, but I've never compared them so it's hard to say just how different they are.

orsm on both accounts

I'm presently trying demo. It looks terrific in your video. I'm very happy using the DCS default lasers and hand tracking (with leap), but I wish there was a way to disable any interaction except upon a mouse press or turning the mouse scroll wheel. Is it possible to use the leap motion hand tracking with mouse buttons and scroll wheel, instead of the hand gestures, in your app? So far I've been unable to get the hand cursors to appear. The ivyvr exe is running and I can see the menu. I've included a screenshot below. I understand most of these should disappear if working correctly. Does Ivyvr require the leapmotion option to be ticked within DCS? I have tested on and off I'm running DCS with it's native OpenXR in single threaded mode. I have the VR controller option disabled. I'm running the steam version of DCS located in the path below. Am I right to be using the following as the ivyvr DCS install path? { "DCSPath": "D:\\SteamLibrary\\steamapps\\common\\DCSWorld\\" } I believe mbucchia was having issues with his toolkit hand tracking option in the latest version of DCS and using native openxr. Could the same bug be affecting ivyvr? Thank you

I'm hopeful for this one too. Not sure about the size of the sweet spot from this pic, but at least it looks a little bigger than the G2 null

you could try temporarily renaming the DCS .cfg files that have the game controller mappings in them. DCS should then make new ones when started.

ive been using my fingertip to press the two red goddamnshuddup!! buttons with no problem. I don't find it quite accurate enough for anything else, though I can sometimes press the ufc keypad. I generally use the mouse on the joystick A.F - are you using the v1 of the controller? I'm guessing my success with it is due to it being a v2? My finger/hand are very closely aligned with the laser I'm hoping the quest 3 hand tracking is at least as good.

p.s. if using MSFS2020 and OpenXRToolkit for vr controller emulation, centre your vr view 'in game' so it's as closely aligned as possible to the way you set up your WMR headset alignment mentioned above in DCS, the hand position is affected briefly with head movements. Hopefully the developers will disable that. This does not happen in MSFS and I find it a dream to use. Tilting the leap controller down as firefox has shown, helps reduce the affects of the leap lens barrel distortion, which helps to keep hands on the desired buttons when turning the head left and right. You can't really see this in DCS due to above, but it's noticeable in MSFS Finger tracking is still not perfect, even with all the above. I use a modified mouse for button and dials tweaking.

For me, best results are from below; - as Firefox has mentioned above, remove any unnecessary objects from your seating area, especially if they show as 'middle grey to light grey (or white)' in brightness within the leap controller app. Clear a one metre buffer all around you, leaving only your hotas, pedals and monitor. Alternatively, cover unused objects with a material that shows as very dark grey or black when viewed in the leap controller app - turn off the pilots body in your cockpit view. This affects hand and finger stability when on - add infra red lighting to the areas each side of your seating position. This will notably improve hand stability when they are in your peripheral vision - if using a WMR headset, clear WMR environment data and when re aligning headset ground height and direction, end the alignment process by looking directly where you would be when looking forward out your cockpit window - restart the leap controller app if experiencing tracking wierdness

possibly clearing current WMR environment data and also re pairing both controllers (in WMR) might do the trick I had a similar issue of the controllers not being seen by MSFS2020. I'm not 100% sure what cured it, but doing the above was one of the steps I took and now it works.

some interesting bits in this

its coming. was being tested around this time last year

for the price, i'm pretty sure it will become the new staple, more less what the G2 is now but with it's other improvements and features too, as a bonus. If it's hand-laser pointing tracking is as good, or better, than what I'm getting on the leap at the moment in DCS and MSFS, that alone will be awesome from my perspective. Downside - possibly video compression when using USB link, but even that may have improved. soon to find out might need to ask yourself - can you bear the thought of Mark pleasuring himself behind his desk while watching you as one of a million squares on his gigantic video wall? I wonder what Xi does while watching the pico4 users?

Looks like 512gb version is now out of stock on Amazon Australia

yeah I think that's the only one I've seen mentioned that will maintain the current charge state while in use on the pro. All the ones I've tried that don't have a second USB connection achieve about 3.5 hours during use, starting from a full charge

the quest pro might have two elements per eye, where the q3 might have one. Though it may not make much difference for fov in this case if they've used a re-designed single element per eye for the q3