jmig

The RV 8 will be a purchase for me. I have always considered it to be the "Fighter" of the Van's RV line.

My apologies. I missed your post the first time. I tried it and it worked. Thank you for the suggestion. Also, what a diplomatic way to call my attention to your original post. 🙂

Thanks. I set it to VDXR. 2020 is working well, except for the magical fingers shooting light rays.

I tried it on two systems, including this one which has 23H2 installed. I bought a new cable, and that didn't work. The headset is now in the Land of Lost Toys, aka, the attic.

My hands are acting as controllers, also. I sorta of remember activating them as controllers when I originally set up the Quest 3. I need to go back and figure out how to turn the hands off.

That worked. Thanks! Now, if I can only get rid of the light rays coming from my fingertips.

This may be a dumb answer and show my ignorance. However, can the human eye see trees 20 miles away? From my flying days I know you can see things to the horizon, however, distinguishing tress from the background? I am not sure you can do that. Also, what you are seeing, or not seeing, may be a result of your GPU. I know with my RTX 3080, I see scenery popping up far less than 20 miles.

There is no image. I would be interested in seeing what you are using. I went on-line and found a post that claimed to fix MSFS and Quest 3. It totally broke my system. I had to reinstall the Quest files.

Thank you, guys. I mistyped in my OP. I am using the Microsoft Store version of MSFS and I’m using the Virtual Desktop. I will look into the VR Camera setting. I want to change it. I even get the white pointer lines shooting through the virtual cockpit even will the controllers not present. Rather distracting and immersion killing.

I recently purchased a Quest 3, after my HP G2 died. I love the headset in MSFS, with one exception. I can't get the mouse cursor to work while in VR. The system wants the stupid controllers. I am running MSFS via the Remote Desktop app. When I select VR it quickly goes the SteamVR then MSFS appears. Everything else works fine. Just no mouse. Since I use a cockpit with numerous switches and buttons, I can usually get around the mouse, but not always.

That didn't help. I removed everything, in steps, until all I had left was the Honeycomb Alpha. It still killed AOA.

Thanks Lorby. The only new device is a Meta Quest 3 headset. Is it possible AOA picked up the controllers and they are interfering?

After working for over a year, AOA suddenly locks up when I click on the dropdown box to add a new button binding. AOA works find with installed templets. It worked fine with axis bindings. It only freezes when clicking one of the dropdown buttons, i.e., Key down, key up, etc. I am using the latest version: v4.1 b51. I downloaded a new copy from Just Flight and installed it after removing AOA via Control Panel. Still nojoy. I cannot find a support page on Lorby's site and the Just Flight support is only for installation issues, so I am here. I can use FSUIPC or SPAD.Next to bind the buttons, however, I am trying to centralize with AOA. Thanks, John

I am new to the Meta 3. However, I use the purchased Virtual Desktop app and just load MSFS from there. It works fine.

I have not watched the gentleman in question very much. However, I have a jaundice view of anyone being paid to give advice on YouTube. It is just another form of advertisement. Advertisement is meant to promote the good points of your produce or service. Truth, veracity, or fairness are secondary.