Bonanza Professional

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.

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 anyone explain exactly what needs to be typed to get the Fuel Selector to work? I saw Nick's reply, but the spaces, commas, and "enum" command don't seem to work. I'm struggling with this hardware controller stuff.

Would be really cool to start seeing the new GPS (garmin alternatives) coming into the BKSQ fleet

Following up to report that my hobbs meter does appear to be accumulating / persisting. B36T MSFS 2024.

You're saying the GTN turns on when you turn off the lights? I'm not sure what to make of that, since the circuit power uses the underlying electrical simulation, which does not account for voltage drop. Are you draining the battery an enormous amount before starting, and then leaving the engine at idle RPM? Perhaps a video would be helpful to diagnose this one.

Thanks again for this! I went through the new file, and everything looks perfect. It's those SetSimVarValue calls that really seem to affect performance when in great number, so the simple conditional is usually better. I will include this in my next updates, and I've already updated the manuals with the new variables. You're more than welcome to share the profile! Usually I worry about conflicts later down the line when a mod is made incorrectly, but in this instance, since you will be overwriting only the one file, and with the exact same code that will be in the next update, I think it's mostly safe. You're welcome to make your own package, or wait a month or two until my usual round of summer updates for all my aircraft. There are lots of little new features for all of them, so this will be a nice addition too! Thanks again.

Empty Wt: 2355 Fuel: 50-100 gals: 335 - 670 lbs Baggage: 50 lbs Occupants: Pilot + 3 (170lbs ea): 680 TOW (not factoring taxi fuel consumption): 3420 - 3755 lbs (within CG envelope per EFB) Earlier flights in the list were at 50 gals fuel, later flights were longer (100 gals).

Figured that was still the case. Landing lights workaround is fine until they do. From your comment it sounds like SU5 did not tackle this, maybe SU6.

@Dingle Sorry for the delay. I was traveling to record audio for the Twin Commanders and King Air. I have not seen this reported in any of my aircraft recently, so I suspect it is something on your side. Make sure the TDS software is up-to-date, and you might have luck contacting TDS support, or Just Flight Support, since they provide advice on many more aircraft than just mine alone.

Honestly, it's one of the features A2A has that yours do not. Would sure be nice to enjoy.

@RealPax Yeah, that's a good idea. I currently do not have that much time to fly, so I usually stick with familiar terrain to avoid having to prepare the flights for too long