mrlip

Use DIFRIPS in the airbus. Data, Init A, Fplan,Init B, Perf, Sec if using simbrief, can have the MCDU programmed in under 5 minutes no worries Also, not always the best idea to delete discontinuities if it’s for a vector or manual, especially if flying online, you will likely get in trouble from ATC. Wait till you’re cleared to the next waypoint then use direct to instead

Without evidence 😂😂😂 Good grief, take those glasses off for a minute

SOP is to disengage BTV at 70 knots by pressing the autothrottle disarm button on the side of the levers

Enjoyed this preview. Looks great!

Do you wear glasses?

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.