Btw seems like my problem above is because MSFS is not showing the correct local time, trying to figure that out now. EDIT: local time was completely wonky and wrong (like 3 hours and 4 minutes from where it should be). Just in case anyone has the same problem and ends up here, with apologies that it's not relevant specifically to the caravan, the solution was to clear the rolling cache.

Thanks i hear it now. I wasn't slow enough.

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.

@Black-Square thank you for the quick response and clarification.

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

@Black-Square Yea no problem, your welcome, great work with v1.2 !

@Black-Square @BorisAudio Caravan v1.2 is awesome, thank you, love the sounds, way better than v1.1

Not flight model rated - works perfectly here. Identical turn rate and aileron deflection to both sides. Probably a joystick calibration problem.

Yes, there will be good to make it possible with lvars

L:var_trueAirspeedRing, number should really do the trick. The position of the ring is directly tied to that variable. I will double check it myself later.

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

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.