RJ Professional

It would definitely be worth trying a reinstall of the RJ Professional just to be sure the latest version has installed correctly (the latest version for MSFS 2020 is v1.4). After uninstalling your current version, we would recommend downloading a fresh version of the installer from the store you purchased the product from and running that installer through. That will ensure the latest version of the product is installed. For reference, the Navdata file directory will vary slightly between Microsoft Store and Steam versions of MSFS 2020, so it is important that the navdata is installed in the correct location for your version of the simulator: MSFS 2020 – Microsoft Store: C:\Users*USERNAME*\AppData\Local\Packages\Microsoft. FlightSimulator_8wekyb3d8bbwe\LocalState\packages\justflight-aircraft-rj\work\JustFlight\navdata MSFS 2020 – Steam: C:\Users*USERNAME*\AppData\Roaming\Microsoft Flight Simulator\Packages justflight-aircraft-rj\work\JustFlight\navdata Mark - Just Flight

Just tried it. Secret was to choose gear up option on PRESS and same button for gear down on RELEASE Anyway, sorted now

Thank you for your reply, but not what I'm looking for. I'm talking about things like RNP AR, LPV and RF-leg capability etc. The kind of info you need in order to figure out if a certain RNP approach is allowed or not. Operator approval is also a factor, but that's going to vary from airline to airline.

@Mark, Many thanks for getting back to me. The only odd thing is the entry lights. When you start the APU or connect the GPU in the dark, the cockpit is illuminated well as the panel flood (X2) and console flood are all lit - making the entry lights a bit pointless. Also, if you switch the entry lights on using either of the cockpit switches - it also turns on the entry lights in the galley - but the galley entry light switch then has no impact. If entry lights are off in the cockpit then the galley switch turns the galley entry lighting on/off as expected. Just seems a bit illogical to me, however, maybe that's how it works on the real aircraft. Regards, Neil.

Nothing further to share at the moment. It's logged on our internal trackers and our development team will investigate again ahead of the next RJ update. Mark - Just Flight

This would be amazing, I love flying the RJ and the 146 and it would be fantastic to be able to use the WinWing FMS display in them.

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?

@GJDober That's similar to autopilot behavior I see in a lot of default (and I'm pretty sure independently developed, too) GA planes -- when I use my yoke button, which I believe in most cases is bound to Autopilot Off, I have to press the button a second time in order to be able to reengage the autopilot. It makes me wonder if this is a sim bug. I don't recall experiencing it in the RJ, but I also haven't flown it since the 146 update released. Edited to Add: I should have mentioned, the GA planes I've seen this in all use that same common autopilot (or a very similar one) that ships with most of the sim default/included GA planes.

Thanks, Mark. I was able to find the ini file but no luck there. However, I found the issue was with a binding on my throttle for the autothrottle - a go around mode. Deleted that and the problem is solved. Thanks again.