TBM 850

@limbo696 Hi All, I wanted to let you know that I have been true to my word and applied my knowledge from the Starship to the KAS 297B. I have a solution now that functions as described in the manual, but can also still be used with native hardware bindings and the old functionality, if so desired. This means that you will be able to use the KAS 297B, as seen in SteveO's videos (as discussed in another thread on these forums), with altitude arming, vertical speed arming, vertical speed synchronizing, control-wheel steering, and pitch adjustment with an associated rocker switch. The only exception is that altitude capture will automatically arm when a climb or descent is initiated in the direction of the selected altitude. This is a core MSFS limitation, as altitude capture is set wholly on or off in the aircraft's configuration files. It's possible that I will come up with a creative solution to this too in time. I will include this change in the TBM 850, and my Baron Professional and Bonanza Professional, which will be officially announced soon. Thank you again for your discussion here, as it helps me prioritize new features, and gives me the insight to design them in a way that will not disrupt current users with my updates. Without you guys, I can't count how many features would not exist that I have become very proud of in my aircraft!

Think I may have discovered the problem on my system. It seems the flight plans take far longer to appear on the GS530 compared to some other aircraft.

Unfortunately, there is only so much that I can do within the limitations of the simulator, and most "workaround" features that I produce for my aircraft are the result of an embarrassing amount of trail and error to thread a fine needle between one rock and another hard place. What you're seeing here when sitting on the ground observing an ILS from the centerline is the result of MSFS's lack of easily accessible variables for navigation aids without querying a database. It forces me to treat many navigation aids as the same type of antenna, or directionally agnostic, for instance. For another example, the VOR's treatment close to the ground is a result of not using a terrain database and computationally expensive ray-tracing algorithms, but instead comparing the altitude of the aircraft to the receiver and applying various curves based on antenna radiation patterns and attenuation constants to arrive at a believable solution that is also light on performance. All that being said, the reason I am often so delighted to have this forum is that it allows me to add requested features and changes to a never-ending list of items to revisit during future development. Next time I am doing work near my signal degradation code (likely for the Baron and Bonanza Professional), I will see if I can come up with some more clever tricks to improve signal integrity while operating on the airfield's surface for you. As is so often the case, I may already have some ideas of what can be done after looking at the code again while writing this.

@Ridux Can't say anything about the first question other than I believe it is unofficially compatible. It works 99% for me. Some 3rd party liveries don't work, some do. I had some issues with the registration not displaying correctly on the exterior. However, this has gotten better in the SU1 beta. You can set the registration before starting your flight and it will display appropriately most of the time. You need to drag and drop the TBM 930 from MSFS 2020 into your MSFS 2024 community folder in order to get the sounds. I just flew it today and had a great flight with no bugs.

@sg_aviation OK, so this indicator uses a change in the white arc to indicate Vs since there is no green arc like on many airspeed gauges where the end of the green arc is Vs. Thanks, Al

@lucasrmdm Good to hear!

@Raller said in Oil temperature scale: You can use my repaint. I have already fixed the bug (the texture) there. N851TB I know, and thank you! It was me who suggested you to update your livery in the first place. I'm very happy for it thanks a lot! @Black-Square it would be nice to have it corrected across the board

Hi @glideslope, I appreciate your detailed reply. I will follow your tips. Wish you a joyful and safe flights.

If you want to try, I've had pretty good success with copying the TBM 850 folder over to the 2024 community folder. But you also have to copy the Asobo TBM 930 folder to it's same location in 2024. And I've seen an issue with the exterior lights, but otherwise it seems to be functional.

@Black-Square SOLVED ! found "752" inside ATC option related to TBM inside mfs menu: deleted and cleared filed, all tail numbers are properly shown as expected. I don't know when and why that field was not empty! thank you and hoping this may be useful for othes simmers.

Using Ryan's location in post 8, I found the 'asobo-aircraft-tbm930' folder and copied it into my 2024 Community folder which had the TBM850 folder in there. Now the TBM850 flies great in MSFS2024 with engine sound and the newly released TDS GTN750 Pro patch (see TDS Support forum), Thanks for your help guy's

Unfortunately I cannot reproduce it again. The day before yesterday I experienced the situation described above several times, but today it doesn't happen, or at least not to the extent described. Very confusing. I will try it again in the next few days and will get back here. Thanks.

@Raller Thanks for the heads up on that one! Haven't used that mod though.

@Black-Square said in TDS750 + GNS530= Bad option: @fabristunt If I'm reading your message correctly, are you trying to command the autopilot and CDI with the GNS 530 flight plan when the GTN750 + GNS530 avionics combination is selected? If so, unfortunately, this will not work, as the secondary GNS 530 has no control over the simulator's internal GPS variables. This is a limitation of the Working Title GNS how-swapping code. I have given them suggestions on how to add this functionality, but I'm sure their hands were full while working towards MSFS 2024, even a year ago. Not exactly: I want the 530 to follow the flight plan I inserted using the knobs. The CDI on the GPS itself is not usable, so the VOR gauge for that GPS is also useless in GPS mode. I am perfectly happy with the 750 controlling the AP, I just wanted the 530 to work on it's own. If I put a FPL in, it doesn't work. It's stuck on the first LEG and doesn't show CDI, BRG, DISTANCE and all the other info, just like Zazaboeing said. For this reason, all I can do with the secondary GPS is NEXRAD weather, Terrain and TCAS. I recently bought the Turbine Duke, I hope the secondary 650 works in there because it would be nice. Since we are on topic, what about a 650 option in the TBM? Maybe 750/650 rather than 750/530.

Nevermind, I was too quick without looking into this forum. The Solution (Thanks to Hughesj2)

Any news on this update?

So I did some experimenting, since the AP shows all the lights in 2024 (just copied and pasted the files). I removed the pms50-instrument-gtn750 folder from Community (I don't use the 750, but the Duke's GPS won't autofill the flight plan without it.) Once I removed that folder, and tested the autopilot, I got at least the HDG light. Going to try a flight later and see if I get all the lights, but looks like the PMS conflicts with the GPS in the TBM (how's that for a slew of TLA's?) Edit: Removing the PMS package fixed the problem for me. All the lights worked, and I don't need the PMS in the TBM for the flightplan. Now I just have to remember to put it back when I fly the Duke.

I'm getting this error as well: "Black square's WeatherSquare 4000 Package not found. You should not be seeing this message." It's quickly flashing on the screen. I restarted the flight and it went away, but have seen it more than once. Any idea of what addon is to blame? I have a ton of stuff in my Community folder. [image: f6dc50fa-010e-4511-953a-f7d0ce434bda.png]