@Derek - curious stuff! I found that with resource heavy aircraft there was a marked difference in performance between MSFS2020 and MSFS2024 with regards to the Series S, less noticeably so with the Series X. I am very aware though that that’s very much anecdotal, while you guys will have access to telemetry with hard numbers. Hopefully something works out some time, and thanks for being so engaging, it’s really appreciated

Thanks, this answer a lot of questions for me.

I have same post on reddit about lack of glass cockpit options in MSFS in general. Seems like it requires a lot of work from developers so I doubt that we see anything in near future. However one dude said that he is working on Aspen avionics as an addon and provided couple of screenshots.

Thank you for your feedback. There are no plans to add support for sound packages from other aircraft into the product at this time; however, FS Traffic does already include a large selection of custom sound packages for the included models, including the A320NEO. The included custom sound packages are specifically designed for us with AI aircraft. Mark - Just Flight

That sounds like a failure may have occurred (as part of the Maintenance simulation in the PA-38 Tomahawk), and the state saving is causing it to be recalled on future flights. In MSFS 2024 specifically, there is some instability with state-saving logic in the core simulator that could be causing this, but it may also be caused by how a flight is ended in the simulator. We would always recommend exiting a flight via '[ESC] > Main Menu', rather than forcing the simulator to close with a shortcut such as '[ALT]+[F4]'. If the same failures continue to be present at the start of every flight after ending a flight via the above method, I would recommend deleting the WearStates.ini file from the relevant file directory below, and it'll then regenerate the next time a flight is loaded with the Tomahawk's default wear state, with no active failures: MSFS 2020 - MS Store: C:\UsersUSERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe LocalState\packages\justflight-aircraft-pa38\work\Wear MSFS 2020 - Steam: C:\UsersUSERNAME\AppData\Roaming\Microsoft Flight Simulator\Packages\justflight-aircraft-pa38\work\Wear MSFS 2024 - MS Store: C:\Users\USERNAME\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\justflight-aircraft-pa38\work\Wear MSFS 2024 - Steam: C:\UsersUSERNAME\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\justflightaircraft-pa38\work\Wear Hope that helps. Mark - Just Flight

All of my keyboard flap keys are disabled and only respond to trim button on yoke and flap axis handle on TM quadrant. Never seen flap responses from B key. Thanks though for the info.

It is possible for the state saving to get confused between updates, especially after large product updates which have a lot of changes, as the aircraft may be attempting to load a state that was only possible in a previous version of the product. One thing I'd recommend trying is deleting the StateSave.ini file from the relevant file directory, and it'll then regenerate the next time a flight is loaded with the RJ with the correct state saving options available. MSFS 2020 - MS Store: C:\UsersUSERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe LocalState\packages\justflight-aircraft-rj\work\PanelSave MSFS 2020 - Steam: C:\UsersUSERNAME\AppData\Roaming\Microsoft Flight Simulator\Packages\justflight-aircraft-rj work\PanelSave MSFS 2024 - MS Store: C:\Users\USERNAME\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\justflight-aircraft-rj\work\PanelSave MSFS 2024 - Steam: C:\UsersUSERNAME\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\justflightaircraft-rj\work\PanelSave Hopefully, that should resolve any issues you may be having with state saving. If you continue to experience any of the behaviour you have listed, could I kindly ask you to raise a ticket with Just Flight Support via the following link: https://www.justflight.com/support In the ticket, if you are able to provide any screenshots/videos that are relevant to what you are experiencing, as well as any steps on how the behaviour can be reproduced, then our support team will be in the best position to be able to further assist with this. Mark - Just Flight

With the NAV LIGHT switch in the FLASH position, the nav lights and beacon lights will be illuminated. This is the position that is required as part of the takeoff callout conditions. Mark - Just Flight

Great to know. Thanks! Love this aircraft!

OK. My bad then. Thanks for info on that I just have not worked on or seen any of those, having worked on plenty different PT6 powered Aircraft. Probably explained by the few installations and mostly for Float planes it seems.

@Buzz thanks for posting that, the Command 114, 685 and 690B look interesting, especially the 690B. Hoping the King Air is next to release.

@SchnauzerMan Hello, I am here, always working on my airplanes I don't really know. Just not enough posts to warrant it, I guess. Just Flight manages the forums. I just develop the aircraft. Have you updated your TDS installation lately? Those all sound like issues inherent to the Working Title G3X and TDS GTNxi interconnectivity, not the aircraft specifically. I haven't heard any other reports like this, despite the aircraft being update about a year ago with these new features, and being tested by the TDS developer himself, so hopefully it's just an outdated installation. It would also be helpful to know if you're using MSFS 2020 or 2024, in case we need to provide more information for him to investigate.

Alright, I need that livery.

Thanks, I'll do another engine run and check this for the second start. Can you think what would possibly repeatedly cause this on both engines? I have the MAG1 START / MAG2 START bindings to my HC Alpha, tied in with a required switch activation to allow for EITHER the left or right engine to be started independently. Because the start switch is not a spring switch, it's possible (I guess) that I left the starter on after the engine started, for a short period - how long would the starter need to be engaged to overheat and pop the circuit breaker?

Love it! Thank you! And good catch- you are correct that I did pull that quote from the G1000 Caravan POH! It did confirm what I remembered about my Caravan experience, which was unfortunately well before G1000s even existed. Just one more confirmation that I'm getting old!

I've found the volume of navaid audio tones to be very, very low in both MSFS 2020 and 2024, often to the point of being inaudible. I've only managed to just barely hear them a couple times, both times with headphones. I've never attempted in the Vulcan, but maybe if you turn engine and environmental volumes down it'd be easier to hear them, since it's generally a loud aircraft. Just an idea. I don't even try to listen for these tones any more because they're so hard for me to hear in any plane.

@django1489 annnnd there it is! https://flightsim.to/addon/107332/blacksquare-caravan-pro-greenranger-aviation

Thank you for your reply. I'm familiar with AAO, but unfortunately, it doesn't recognize my hardware, at least not the panels. That's okay, though, so I'm using Spadnext instead Exactly, I found similar variables, but when I set them to 19, 20, or 0, naturally for each page, nothing happens. My guess is that perhaps a "sent" command or some other instruction is missing. As I said, this is purely speculative. Maybe someone else has an idea, or perhaps the team does? Best regards and many thanks, Dennis

@AndrewCoolidge said in Baron is my favorite airplane: reviving the old feeling of exploration This is really music to my ears. Thank you so much for sharing