In my case, it was because an old version of the SimConnect client was installed when I installed the Leonardo MD82 Anniversary. This SimConnect version is still from FSX and has repeatedly caused problems in both MSFS 2020 and MSFS 2024. Since I uninstalled it, FSTraffic has been working smoothly again.

Thank you for clarifying that mention in the manual. I really didn't notice that detail!

@Black-Square I get issues from time to time with the native navdata and navigraph where some addon airports delete all the navigraph procedures. I talked to Matt from working title about it and he said it's a known issue and doesn't know if it can be fixed, but in the meantime most of my Canadian payware airports do not work with the starship or working title avionics because of this... So an external system where you can download the navdata from navigraph hub like with the TDS 750 would be nice... In the meantime, probably more work than it's worth.

Nope, tried again, that wasn't it. I'll keep pecking away until I find out what makes it work and let you know what strange new way I found to break something I went through every page of the FMC and there were no boxes showing data needed and no discons in the route, and my manifest.json is showing version 0.1.5. This is procedure I followed for the FMC if it helps : Pos Init lsk last position to set ird pos route enter origin and dest (LSZH/EBBR) dep/arr departures select runway then sid (28 - VEBI1X no trans) route enter airways / waypoints to last waypoint VEBIT T51 LASUN T14 LUMEL T10 TORPA DCT EDOPI DCT GIVOR DCT SORAL DCT IBERA N853 DIK Y37 BATTY act / exec dep/arr enter arrival if known (star baty6a trans flo appr ilsY25R) exec *** try to save flight plan here enter flight number on route page (JF1234) perf init enter zfw in while tonnes (what you put in the efb)(30) enter reserves and crs alt (0.9,26000/260) enter crs wind (270/3) and Trans Alt exec *** try to save flight plan here 1st edit - to make sure we were on the same page about directories I created a new plan in simbrief and downloaded it, and moved the .RTE file to the directory mentioned in the FMC manual (fs2024 steam). Then I reloaded the RJ100 and tried loading that from the company route field - great, did exactly what it says on the tin. Exited back to the main menu. Then I created a different plan in simbrief, loaded up the RJ70 in case it was just an RJ100 problem, imported that flightplan from simbrief, and tried to save it. Poo, wasn't that. But when I looked in the saved flights, the one I downloaded as a .FLT file was there and available. I've run out of time for tonight but I'll keep picking away at it as time permi ..... perm ..... per ... back in a minute ! Bother. I had a thought it might be a permissions thing so I cut Steam out of the loop and directly launched the MSFS2024 exe file as an administrator. Still couldn't save anything. Really have run out of time now, will try again tomorrow. 2nd edit - I wondered if it could be a mod conflict so I tried again with the community folder completely empty except the RJ. Still couldn't save. So I uninstalled (through windows settings) the RJ and downloaded a new copy and installed that - still can't save. I even moved the camera right down to the FMC level so I could confirm the LSK was actually getting pressed. 3rd edit - Out of curiosity I loaded up the F28, imported a simbrief flightplan, and saved it. Then I cleared the flight plan and loaded the saved one. Everything just worked. So I did the same thing with the 146, and again it just worked. So it's something about the RJ. Hmmmmmmm ... 4th edit - I manually created the %appdata% directory structure for an MS store install in case it was trying to use that, nope. Then I made sure there were no procedures in the route and I was only saving the origin, destination, and en-route waypoints. Absolutely nothing obstinately continues to happen when I click the 'save' button ... I might fake the directory structure for MSFS2020 in case there's anything buried in the registry pointing it there. 5th edit - created the directory structures for both Steam and MS FS2020 installs, still can't save flight plans. This is weird !

Thanks Mark. Do you want to just close this thread and I'll "roll" it into the other one?

Great ideas, also missing the option to refill oil in pistons. Given the crazy detail level in so many other complicated areas, this would seem almost easy to implement I would also love an additional EFB page for future Black Square planes that would cover everything around gear and flaps. Strut health, tire health and pressure, brake health and temperature, flap health (after overspeeding). Obviously, one can dream. Although we already have brake temperature in the Starship, so might be a sign of things to come

No worries...appart from this issue its a damn solid Product that just keeps getting better over time. Cheers guys.

If this behaviour persists, we would recommend opening a ticket with Just Flight Support via the following link, and one of our support team will be best suited to assist with troubleshooting: https://www.justflight.com/support Mark - Just Flight

FS Traffic uses IATA aircraft type designators. A list of those can be found here: https://en.wikipedia.org/wiki/List_of_aircraft_type_designators Mark - Just Flight

But also, in case you didn't see it, there's another thread further down about this issue. Might be a related cause, or might not. https://community.justflight.com/topic/9140/king-air-have-grey-displays-in-2024

Perfect!! That worked

I love the cockpit lighting, it's excellent.

Are you starting from the full rich position on the mixture before you start the procedure on the edm? If you've pre leaned before you start the lean procedure on the EDM you won't ever see the cylinder temps.

FLC always commands nose to level first, before raising it to capture the selected IAS. This is a bug that's been there since v1.0

Will 690B include the option for 5-blade MT props?