Bonanza Professional

@SadBucket I'm positive he will. Very much looking forward to the updates.

I succeeded too but I had to search, because there's plenty of malware/false download links...

Excellent - I was nervous to adjust it too far. I tried .7 at first and that wasn't quite enough, .5 seemed to do it but I think .25 would be even better.

FYI - I tried reaching out to you through the justflight support ticket system - ticket #95631 - Dan said he sent you a message but it was back while you were finalizing the Caravan so may have gotten buried.

I would say I prefer discord, but this site is super well made.

Oh sorry, the beginning of the sentence is identical... but the end is not...

Just did a short flight with the A36. As you can see the Hobbs did move. @Kaaplink Would be interessting to find out what the difference is, why does it work for me and not for you. Strange.... [image: b706d3f5-7a5c-437f-8c4d-3479e0a1adca.png]

For your information, I turned Raymarched Reflections to OFF (Graphic settings > Custom) and it did the trick. No more reflections in the glass of the cockpit. Of course the effect is also removed in other areas but I have not noticed in my usage.

Ok figured it out. In my specific view the selector was hidden. I see the valve now

I was able to get it working. It was one of the following: activating VLOC before swapping the ILS frequency, or arming APR before the LOC needle started moving I have gotten used to how the PMS50 GTN behaves, which is not completeliy aligned to the actual Garmin GTN 750. I'm moving to the TDS because the PilotWorkshops GTN training uses it, and I can understand why ... as pilots in training in real life need to learn exactly how the real device operates.

Nick, tried to mail you. Can we still hope for this to come out? Thanks for a short reply.

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 :).

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.