MSFS Products

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.

Hey @Black-Square do we have any updates? Seems to only happen at some airports.

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

Unfortunately, as you say, I believe this will be a limitation of using Chaseplane with some of our products. The Vulcan, and a few of our other products, rely on the core MSFS camera system to move the user to certain locations in and around the aircraft. As Chaseplane overrides the default camera system, the cameras that we trigger in the code no longer exist, so the camera will not change. It's something we have logged on our internal trackers for further investigation, and to see if there is any form of a workaround we can find for Chaseplane users. In the meantime with the Vulcan, it should be possible to create custom Chaseplane cameras inside the AEO/Navigrator compartment and then trigger those via the Chaseplane interface. Mark - Just Flight

At the time of posting, the latest version of the RJ Professional isn't available on the MSFS 2024 Xbox marketplace, so the post-SU4 fixes are not yet available. We have approved it for release, and the next two release opportunities are today (Monday 19th) or Thursday 22nd. Mark - Just Flight

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

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

Hi Mark, Apologies for not responding, Christmas & families.... Many thanks for getting back to me. Regards, Neil.

I will do. Thank you, Derek.

It is logged on our internal feature request tracker, but it's not something we are currently working on. It is something we will be considering for future updates and/or upgrades to our PA-28 fleet. Mark - Just Flight