mrlip

You’re in plan mode doing 478 TAS. It will show those turns as if it was done at your current speed. How did it look once you flew the approach? Flown that approach myself twice this week in the 789 and it followed it per the charts no problem

Latest update just released which includes CPDLC functionality

They said it’s not vatsim ready yet. Looks pretty flyable on that video but I am guessing they haven’t fully implemented the Direct to waypoint and/or the hold features yet, both of which would be needed to make it vatsim ready.

Looks absolutely amazing, what a project!

On the jpg, the text at the top is under the shade of the glareshield and the text at the bottom is in direct sunlight so it will appear different?

On my 4th flight in VR now and I haven’t experienced any motion sickness so far. A couple of times I’ve felt my balance sensation move when banking in turns though! And today I momentarily got confused for a second and tried to grab the VR side stick position instead of my actual one! But so far so good, really enjoying it and just getting used to flying under the hood rather than 2D multi screen. Im working on a few quality of life tweaks to get some app windows in VR and once that is done should be all set

Forgot to include the script I am using, see below. Its using the OpenKneeBoard remote control function to set the tab to vPilot on press of Joystick button 14 in the example below. And it works great, but I would rather not use the button hold function and have it instead so the first keypress of button 14 takes me to vPilot with mouse focus and then I press button 14 again to return the focus to MSFS. I tried to add an additional KeyWait but it didn't work. Probably something simple but it is years since I have used AHK #Requires AutoHotkey v2.0 global appvPilot:="ahk_exe vPilot.exe" global mfs:="ahk_exe FlightSimulator.exe" 2Joy14:: { if not WinExist(appvPilot) return else run "C:\Program Files\OpenKneeboard\utilities\OpenKneeboard-RemoteControl-SET_TAB.exe position 4" switchApp("2Joy14",appvPilot) } switchApp(key,app) { OutX:=0 OutY:=0 OutWidth:=0 OutHeight:=0 SendInput "{Blind}!{Tab}" Sleep 100 WinActivate app WinGetClientPos &OutX, &OutY, &OutWidth, &OutHeight MouseMove OutWidth/2,OutHeight/2 KeyWait key SendInput "{Blind}!{Tab}" WinActivate mfs }

I’ve downloaded OpenKneeboard and setup 4 window capture tabs for the apps I want to bring into MSFS. I would like to use AHK as described above but rather than hold the button down, I would like to press a button to bring the window in then press the same button to return to MSFS. Do I just need an additional sendinput or can I just remove the keywait?

Yeah I’ve only had my headset 2 days and I already feel like I’m close to being fully dialled in without much further work. Speaking of which, I’ve tried some more testing with DLSS quality and even cranking up the resolution in OXRTK doesn’t get the gauges as crisp as I would like. And by the time it’s cranked high enough, the benefits of using DLSS are gone as the FPS has dropped and latency increased and may as well use DLSS with DLAA. I think TAA with between 90-100 render resolution is going to be the sweet spot. Possibly 90 but increase the CAS sharpening slightly in OXRTK. Will finish off the testing tomorrow

I will try with DLSS quality again and crank up the resolution in OXRTK on my next test.

Good point, I didn’t think of that. I’ve removed the fps limit in OXRTK and reduced the FOV to 95% Did my first flight earlier using the settings I mentioned in my last post, it was a great experience just getting a feel for VR. Found the landing quite challenging compared to 2D! Been doing some more experimenting since then and found the HEVC 10bit codec at 150 to be quite significantly better in terms of latency and didn’t notice much visual difference compared to AV1 so think I will use that for my next flight. just trying to find the right balance between smoothness and clarity. TAA at 100 or 110% has nice clear visuals but with a bit of additional latency making it not quite as smooth. DLSS quality setting is perfectly smooth 80fps but the gauge quality is really poor. Any suggestions?

I've made a few changes and got to a pretty good place now where FPS is good, latency is Ok and fairly smooth and the gauges look OK. I've reverted back to standard resolution for now so no override in OXRTK I've stuck with AV1 and 150. Other settings - Virtual Desktop Frame rate - 90FPS VR Graphics Quality - Godlike VR Frame Rate - 90 VR Bitrate - 150 Sharpening - 70% SSW - Always enabled Snapdragon game super resolution - enabled OXRTK - FPS Limit - 45 Turbo Boost - On CAS Sharpening - 40% Fixed Foveated Rendering - Quality preset Override resolution - NO MSFS - Sharpness - 0 DLSS - DLAA mode Would be good to find a bit more of a balance to try to crisp up the gauge fonts a little bit - is that all down to render resolution and potentially using TAA? On a separate note - anyone else have the starting view position in the Fenix been way too high? Its the same in 2D as well but in VR my head is nearly on the overhead panel 😀

Av1 and 150. I’ve reduced to 120 now but didn’t get chance to test it, will try it out later.

Thanks for the YT videos and Donka’s settings. I followed them but reduced resolution in OXRTK to around 4000 and enabled SSW. Sat at the gate at EGLL in the Fenix no traffic (vatsim flyer) I am getting 40-45 FPS but the latency is high. Around 40-45ms of game latency according to the virtual desktop overlay. What settings impact this type of latency?

Thank you Donka! I will go through this later today. I’m not currently using OXRTK as I know the runtime is now included in virtual desktop. Is it still worth using it for other tweaks?

😆

Received the quest 3 today 😀 Did all of the initial setup, which for someone who has never used VR at all before was quite mind blowing in itself! Picked up Virtual Desktop from the Meta Store as that seemed to be the best starting point from what I’ve read. Fired up MSFS using pretty much all default VD and FS settings in terms of VR just to check everything worked and wow my mind was fully blown! I only had chance to sit at a gate in the Fenix but even that was an incredible experience Tomorrow I plan to fine tune everything, are there some good setup guides for VD and MSFS?

https://kb.fenixsim.com/custom-camera-views

Yeah this is what I read as well when doing some research earlier this week so highly likely I will go down the Virtual Desktop route

Took the plunge and ordered a Quest 3. Should have it tomorrow. Haven’t picked up a link cable yet, will try SteamVR/VD first and see how that goes. Haven’t picked up a better head strap yet but given what people say about the included one, I will probably get one Will keep this thread updated with how I get on!

Thought so otherwise that would have been a bit of a showstopper! Last question for now I think - the quest 3 has built in speakers and mic, correct? Thanks for all your input!

If I am adjusting MSFS settings for VR use and switch back to 2D mid flight, would I need to also change settings back? Or does MSFS have completely separate settings profiles for 2D and VR?

Thanks for all your feedback! I completely forgot that Navigraph has its own in game panel, that sounds like it could be a solution for me to get that in VR. Is there anything for vPilot? I think for the other apps I run, I could manage without in VR but it would be good to have navigraph and vPilot available. Regarding connection, I guess I would try wireless virtual desktop first and if it isn’t great then I could pick up a link cable. I’ve heard OpenXR mentioned but wasn’t sure how it fits in?

I have never tried anything on VR before but I am considering giving it a go given how much people seem to like it and the immersion factor that’s possible. I have been looking at the Meta Quest 3 as I believe the G2 will no longer be supported fully in the future on W11. I’m an experienced MSFS user flying only tubeliners on a 5800X3D system with a 4080 at 4K using FG and mostly high/ultra settings. Typically will have anywhere between 60-100 FPS depending on the scenario and I’ve recently started using the dynamic LOD app to adjust lod when on the ground. I have a dual monitor setup with MSFS on 1 screen and additional apps like navigraph, vPilot, FS2Crew,STKP etc on another screen. How do you think the transition to VR might be from this type of setup? Would I need the link cable for the quest or better to use Virtual Desktop then I can get my other apps into VR as well? As I fly tubeliners, I would imagine I would likely do takeoff and climb out in VR then switch back to 2D for cruise then back to VR for arrival. Any thoughts or advice would be appreciated as it’s a new area to me!

You need to restart MSFS after the update, will resolve it