Thanks for looking into it. Has to be incredibly frustrating for you! At least in this case there's an easy workaround for now - turn em off lol.

@Black-Square thankyou. I can see the changes added in v1.2: Sounds for all exterior interactions, like opening and closing doors, are now audible during walkarounds.

@Black-Square I don't see anything related to this in the change log for 1.2, should I still expect it to look funny in 2024?

Hi. Thank you for the detailed reply. Totally understand it must be more frustrating for you than me. This issue certainly has legs. I inadvertently misled you re. MS placing blame on the developer. What I was trying to say was that any issue with a third party module gets instantly moved to a section of their forum which is little better than a dustbin: https://forums.flightsimulator.com/t/dynamic-registration-issues-with-3rd-party-a-c/758875/4 So when I say it’s a developer issue, I’m saying that whatever you raise regarding a third-party module on the MSFS forum, it’s instantly moved away from the issues section where people can usefully vote if they have the same issue to a section that is essentially ignored. It baffles me how MSFS don’t appear interested in how their beta changes are negatively affecting third party ads-ons. I don’t really use any of the stock aircraft (quite like the Asobo 152 & 172 - plus some others), but without my A2A, BlackSquare, PMDG, Just Flight, FSR and FSW addons I don’t think I’d be interested in MSFS currently. The sounds and visuals alone of the Piston Duke climbing out, for example, is still incredible every time I see/hear it. It’s particularly frustrating on the MSFS forum as I can remember the issue with dynamic registrations first appearing (after they been working perfectly on Xbox). I raised the issue at the time on the MSFS forum hoping that it would invoke a near-instant reversal of whatever change they’d just made in whichever beta it was. But instead I got a “talk to the developer” and now we’ve had this issue baked in for a ridiculous length of time. I don’t use a PC at home, so posting and searching threads is all done on my phone (so apologies for my writing style), so not easy at times….but imagine this issue has been present for over 18months now. Could be a lot longer - time flies! Thanks again. Like so many on here I can only express my gratitude for you being such an open and engaging developer. Not to mention creating all of those amazing modules which greatly help me relax after a hard week. Regards, Mike. PS: I’m biting my tongue not to add to the requesters about Simbrief integration into the tablet. One step at a time :).

@Heclak I just saw that documentation for the IFD series was posted recently. When I saw no mention of hot-swapping configuration, I looked elsewhere, and found a post from someone at Working Title saying that they will not not support hot-swapping with the IFD series. That's too bad, because it would obviously require substantially changing the architecture of all my aircraft to support one new piece of avionics. In order to add the IFD's, and maintain all the existing hot-swappable configurations, some of my aircraft would end up with 32 variations in the aircraft selection menu. I consider hot-swapping to be a major feature of my aircraft, so I'm obviously disappointed to hear this, but I feel worse that it artificially limits the options that I am able to supply to my users.

A BlackSquare Twin Otter would be amazing. It would fit right into the BlackSquare portfolio and is something different from the existing aircraft.

I’m sure that it’s 1.1a because your support sent me this file month ago with the idea in mind that this would be the solution for the problem.

Confirming that pms50 fixed this from release 2.2.60 of GTN 750.

The issue persisted across all turboprop aircraft that have a condition lever. Re-installing Flight Simulator 2024 resolved the issue. I can only assume it was a faulty package upon installing SU5.

@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.

Okay, so I had a few minutes to test a couple things out. Primarily, the issue I noted earlier with not being able to get close enough to the pitot covers to remove, IS a VR issue. The issue is not there in 2D mode. The same applies with the menu and tablet size changes. These two are not really issues, as they don't negatively effect their use. I didn't test the instrument lighting, but should be able to later this evening.

@Black-Square said in KingAir 350 - brightness of the AP panel: If so, then have you tried adjusting the "ANN BRT" knob on the radio panel (right of the altitude selector)? I didn't know about that "ANN BRT" knob! Everything's fine work now.

That's correct. Data logging from the ETM is not implemented, mainly do to the limitations of JavaScript in MSFS. The button is connected to the unit in software for future use, but it has no functionality.

Can you share a screenshot, please? All the main instruments occupy the same amount of texture space, so there shouldn't be any noticeable difference between them.

Glad I finally tested this. I had forgotten that the indicated airspeed must be below 145kts for the warning horn to activate. That should do the trick