Baron Professional

Lmao yeah, I was just being grumpy

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.

Unless there is something going on locally, as ploodovic suggestions, I'm reasonably sure the variable is not changing value, so I'm inclined to believe that you're just looking at the parallax effect of the 3D gauge. They can be surprisingly deep in the real aircraft! I actually tend to underrepresent the depth in my aircraft for fear of complaints about excessive parallax.

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?

@Derek could you please assist me sir, and remove the broken link image in my post above? I tried to edit it but I passed the time window for that. I placed the updated image on the permalink of the AVNX website itself. That way users don't end up at broken links or media. Appreciate your help. Pete

@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

Hey, just wanted to bring this up- as you said it looks good so far on the Commander.. have you already worked on a solution?

@iflygary Well I do not find it difficult but need to admit that I switched from the in-sim bindings to Axis-and-Ohs a long time ago (several years). This way I can avoid the flaws of the sim with the addition benefit of being able to control much more than the ingame binding allows you. Most important in this case would be to use input repetition for the switch, otherwise it will snap back. I can provide you all the scripts you might need for controlling the Baron in case you would like to go this route. Just to give you a few examples, I can control the sunshades, every air ventil, and most of the other knobs and switches with hardware. It was a game changer for me switching to an external tool to control everything. No more lost bindings, no more missing bindings. Easy switching out hardware. Initial setup takes a bit longer sometimes but this is more due to find the right variables than to bind them. Sorry that I cannot supply more support within the Std.

@Tadeus72 Do not get me started on this. It is a mess and not only with BSQ Planes. It is a Sim issue in my mind. The only way I get this somehow consistently working is the following: Spawn at your departure location Restart the flight before you move the plane. When I do spawn cold & dark I usually hop into the plane and do the restart from inside. After shutdown on the destination airport I do restart the flight, in case of C&D I hop into the plane and push than “end flight”. If I follow these steps it does more or less consistently save the flight in the logbook and also does the state save.