Marc Collins

This actually has already been addressed on the sim side in SU13 for MSFS 2020. An option for volumetric fuel flow was added in engines.cfg, and developers can enable it to prevent the old behavior where fuel flow *increases* when leaning the mixture at altitude. Very few developers have taken advantage of the new option, but it's there. Asobo has been wisely implementing changes like this on an opt-in basis (developers need to explicitly enable them in the cfg files). That way, the changes won't break any existing code which developers have written to work around old bugs.

I just hopped in the Turbine Duke for the first time since the update yesterday and enjoyed it once I got up in the air. Getting set up for the flight reminded me of why I sometimes get tired of Black Square products, though: the checklist is so mind-numbingly long. Especially for a multi-leg flight (e.g., land, shut down, walk to the FBO for lunch, then start up again and fly somewhere else), I suspect that it wouldn't be realistic to run through the entire list of pre-takeoff checks for every single leg of the flight. What would be a realistic way to handle this which is true to life? I know there are checklists out there on flightsim.to which label the essential items for just getting going, but are there any that give guidance on how often each systems check should be done?

In my opinion, yes. It has everything I like to see in a quality add-on: 1. Excellent flight model 2. Excellent sound pack (Boris Audio Works did the sounds) 3. Systems depth for normal operations (custom engine and checklist pages in the G1000 and custom engine and systems simulation) It doesn't have a tablet with every conceivable failure point like Black Square. But for normal operations, it is outstanding. And it has improved significantly since release. A flight model update within the first few months of release took it from good to exceptional. This is a plane that requires rudder trim for takeoff, and rudder trim adjustments are smooth and controlled in a way I haven't seen in most other GA aircraft in the sim. I should clarify that I've only flown it in MSFS 2020 so far. I'm going to transfer it over to 2024 soon.

Oh, excellent information! Thanks for sharing this. It's great to know there is a way to access the contents of the virtual file system while the sim is running and view any content that is unencrypted.

In the September Dev Stream, Jorg was non-committal about allowing config files to be edited for stock aircraft in MSFS 2024. He said that "spiritually" Microsoft would like to allow it, but it's hard to know how to do it when aircraft are streamed rather than stored locally. Here's a YouTube link to the exact question and answer:

One thing which can cause this problem is keyboard input on an EFB (or something similar. It also happens with keyboard input on the WT G1000NXi). I've had it happen with the EFB in the FBW A32NX. If I use the keyboard to input data on the EFB, the EFB is programmed to block normal key assignments from triggering sim events while typing. But for whatever reason, ALL inputs are blocked during that time, including throttle and yoke controller inputs.

I only have the SWS version, but I personally think it's quite enjoyable. It certainly flies very differently than most other addons in MSFS (even high-quality addons like the Blackbird 310R). I assume the type of controller hardware makes a difference on how enjoyable it is. I have a long-travel Fulcrum Yoke and Thrustmaster TPR pedals. I'm sure the experience would be quite different with a twist stick. With my hardware (and using linear control profiles), the SWS PC-12 requires MUCH more aggressive control inputs than most planes in MSFS, especially at low speeds on approach. I can't claim to have any real-world experience in a PC-12, but this strikes me as realistic from the cockpit videos I've seen of pilots moving the yoke quite a lot on final approach. The corollary of all this is that the SWS PC-12 feels extremely stable. In my experience, it is the exact opposite of twitchy. When I think "twitchy", I think of an airplane that responds too much to small control inputs, making it difficult to finesse the controls and point the nose where I want it without overshooting and overcorrecting. The SWS PC-12 is the opposite of that. It's really quite refreshing to fly a relatively small airplane in MSFS that doesn't feel like it's getting thrown all over the place by small control inputs. The main drawback is the yaw behavior. It has been discussed extensively on SWS's discord. I get the sense that the current behavior is a compromise that has some advantages and drawbacks. The behavior of the turn coordinator ball certainly seems odd and counterintuitive. At first, I was distracted by it. When I realized that it wouldn't be quickly fixed and that SWS evidently intentionally chose the configuration they did to capture other aspects of the way the real airplane behaves, I started focusing less on the turn coordinator and more on looking outside. When I do that, I am less bothered by the yaw behavior. I do think it needs improvement in that regard, and I'm glad to hear the new update will be addressing the yaw behavior. Anyway, I enjoy the plane. Hopefully those additional details will help you decide if you'd enjoy it. It's definitely unique and handles unlike almost any other plane I own for MSFS.

The only thing I've noticed is the G3X does not display visual approaches when they are activated on the PMS GTN750. The G3X will show a magenta line going straight to the destination airport, rather than showing the STRAIGHT and FINAL waypoints. But that's pretty minor in the grand scheme of things. As long as I'm using the GTN for flight planning and map, it works just fine.

I also agree that the current combination of G3X and stock Asobo GNS430 is a deal-breaker and I will not be buying it for now. I understand the choice to use the G3X -- it's very common in real-world RV-10 builds. And I can understand the complexity of trying to support TDS and PMS options when PC and Xbox versions are involved. But there are a wealth of airplanes with similar capabilities to the RV-10 in the sim, and many of them have superior avionics: The Carenado V35B Bonanza currently is flyable with the WT GNS530 (with a few bugs in the altitude preselector and the HSI not depicting RNAV glidepath). I suspect this will be patched soon, as Carenado has been patching all of their planes to work with the WT GNS units. The G36 improvement mod features the G1000NXi The stock Cirrus SR22 also has the G1000NXi Carenado's other high-performance single-engine offerings (Mooney M20R, Cessna 182T) have already been patched to work with the WT GNS, and they also work with both the TDS and PMS GTN 750 units. The Just Flight Arrow and Turbo Arrow work with the GTN 750. As Bert mentioned earlier in this thread, the RV-14 from Simworks can be modded to accept the TDS GTN750, and I've also successfully modded my own copy to accept the WTT mode in the PMS50 GTN750. The G3X doesn't perfectly match the flight plan I program in the GTN (although it is actually close), but if I use the G3X as a flight instrument and the GTN as the sole source of navigation, it works just fine. I will be sticking with the RV-14 for now.