Baron Professional

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!

Are we ever going to get paint kits for this trio?

@alanfernandes this question is not specifically related to the Baron Professional, but rather to the general operation of the GNS430/530 GPS units. You may find a good tutorial in the following video https://www.youtube.com/watch?v=T0dqGVgQlsM

Could I kindly ask you to open a ticket with Just Flight Support via the following link, and our support team will be able to assist with this: https://www.justflight.com/support Mark - Just Flight

I suspect you were facing into a stiff wind? Asobo changed something about propeller dynamics after I released the Duke that sometimes results in spinning propellers when facing into the wind. I think this should be much improved after some unreleased improvements I've been making to my engine physics simulation. However, 29" MP is correct for the shutdown right engine, as ~29" is ambient pressure.

@RealPax Thanks for your response. You certainly pointed me in the right direction. In case you (or anyone else) might be interested here is what I used: LEFT selector (clockwise: OFF → ON → X FEED) OFF: 0 (>K:FUEL_SELECTOR_SET) ON (MAIN): 19 (>K:FUEL_SELECTOR_SET) X FEED (ALL): 20 (>K:FUEL_SELECTOR_SET) RIGHT selector (anti clockwise: OFF → ON → X FEED) OFF: 0 (>K:FUEL_SELECTOR_2_SET) ON (MAIN): 20 (>K:FUEL_SELECTOR_2_SET) X FEED (ALL): 19 (>K:FUEL_SELECTOR_2_SET) Thanks again for your help. David

@djw4250 I'm glad it worked. I've probably spent hours in these sections of the BS manuals. I still feel lost half the time lol