Baron Professional

Perfect thank you. No worries about it, if we all take one extra step we can walk miles from where we are now. I will reach out to them tomorrow. Pete

As a USA VATSIM flyer, when I fly the Duke with the KNS81 I like to try to use named waypoints when possible. As for which are legally allowed, the KNS81, I think, is only allowed to use Victor and Jet Airway waypoints, no T or Q airway points here. Reason being that V and J points are based on VORs while T and Q are pure GPS required points. Also, legally, you cannot fly any SID or STAR that requires GPS. They'll usually say so on the chart, or skyvector says which ones are RNAV. They'll have (RNAV) after the name whereas non-rnav sids and stars will not say RNAV after their name. One example i regularly use is the Bradley6 departure from KBDL. Let's say you want to go to VEERS. You get out little navmap and you find a VOR that overlaps KBDL and VEERS and then little navmap lets you draw a line from the VOR to VEERS that will give you a bearing and distance. You then put that in the KNS and it can setup its pseudo-VOR for you to fly to VEERS once in the air. Also, yes, according to Gemini you can use VOR/DME points and even latitude/longitude waypoints, but I like to make ATC's life easier and pick named points because I don't know if vatsim is setup for those kinds of points like IRL ATC's software is. As for equipment code. In USA, I use /I when using the KNS in Duke. It stands for "RNAV, NO GNSS, NO RVSM". /A is pure vor nav. /Z would be rnav, no gnss above FL290. (/w would be pure VOR only above FL290. I do that is the F28 when doing vor nav only)

How do I enable co-pilot visibility in the cockpit in MFS2020? I couldn't do it on my tablet—the seat was empty.

Is the B58TC already accurate as it relates to Fuel/Mixture? It seems to me that may be the case.

I found a command to enable FD. I also found a command to enable TEST, but when I press the button, the test only lasts for one second... Although in the cockpit, when I press the button, the TEST lasts for about 30 seconds. I used 1 (>L:var_AutopilotTest, bool). And I still haven't found the command for AP DN and AP UP buttons...

@Energyzer Similar answer, but that one is technically easier. Boris and I just need to arrive at an agreement for the schedule to tackle these updates.

@LeoPilot That's what I'm here for! Any time

@meh1951 said in AC in Phoenix: Is there someplace that has a description of how it works? Pages 58-63, 104, and 107

Thanks. Good thought on the high zoom level - lens effects was the issue I was running into trying to grab screen shots. I got close with pics off search engines but I think I can still do better. This is my first foray into air manager . . . . got all the avionics displays working except the KFC 150 (Glass Out isn't finding the KFC) - still have to get the buttons working on the KNS 81, KFC 150, KR87 and the radar but I'll get there. This will be on a 24" touch panel to the right of an altimeter motives Baron panel that's on the way [image: 4aaa50d0-6516-4b7b-8fdf-d83f1cf6d5cb.jpg] .

@tlvid Absolutely no apologies necessary! I only wish I had the time to research and write some article about this. It's really fascinating to see some of the spellings and names from just a little while ago.

Great to see this, especially because I've long hopes that @Black-Square would start putting modern avionics in

I also would prefer a config without the RNAV unit.

@meh1951 Wish you could see my face when I find this type of stuff IRL without the ability to go home and submit a bug report.

The two buttons increment two variables that hold the state of the chronometer. The SEL button increments L:var_yokeChronoMode_L, while CTL increments L:var_yokeTimerMode_L. You will need these variables to wrap from 0-2, which is usually achieved with a modulo operator (percent sign). If your scripts are in RPN, they will look like this: (L:var_yokeChronoMode_L, number) 1 + 3 % (>L:var_yokeChronoMode_L, number) (L:var_yokeTimerMode_L, number) 1 + 3 % (>L:var_yokeTimerMode_L, number) I hope that helps! Let me know if you have any questions.

Perhaps the smoking gun that this is on Asobo's side is the problem doesn't exist in flatscreen... Asobo made changes to object culling in SU5 and perhaps that affects mipmapping too. This was almost certainly motivated by PSVR2 on PS5 - and thus could explain the difference between flatscreen and VR. The problem with complaining to Asobo is they'll most likely kneejerk blame it on the third party aircraft and I haven't seen it in first-party aircraft so it'll just get deflected back. I have seen this exact behavior in one other aircraft: Taogs Hangar A365. One panel behaves exactly the same as what I see with the A/S indicator in the Baron; it's one or two mipmap levels lower than the rest of the cockpit, in VR only. I'm hoping they'll dig into it and find something that points a finger at something. Note: aircraft are downloaded so it's not a streaming issue, rolling cache reset - just in case, dynamic settings off, foveated rendering off, off-screen terrain caching set to ultra - just in case.

It all depends how effectively you can equalize your middle ear pressure by manually opening your Eustachian tubes. For pilots who have trained their muscles to open their Eustachian tube on command, then even 3,000 ft/min should be doable as along as you don't have a cold or a stuffy nose. However, for uninitiated passengers, the differential created by climbing or descending at 1,000 ft/min for only a few minutes can become considerably painful. I hope that answers your question This is also a great example of what draws me to aviation, because few other hobbies require knowledge of engineering, navigation, human biology, and fine motor skills, all in one place.

Could this be added/fixed in a coming update? Hope to hear an answer!

I caught that recently too. It will be fixed automatically in the next update for MSFS 2020, but I will have to get someone from Just Flight to fix it manually for 2024. Thanks.

It does!