RJ Professional

This helped me a lot. I have to manually click the AP disconnect on the yoke to reset the AP alarm. Thanks, @GJDober!

Thanks for the feedback. Could we kindly ask you to forward that feedback to Just Flight Support via the following link: https://www.justflight.com/support Our support team will then be best suited to assist with troubleshooting and/or ensuring that any valid bugs are properly logged. However, just to note that point 1 is intentional logic, as each RJ livery is fitted with accurate equipment configurations by default. Point 2 sounds like expected logic if the engine parameters are on the limit of rounding up/down to the nearest whole number. This will likely vary on every flight as the engines will idle at different speeds/temperatures depending on weather conditions. Mark - Just Flight

The first thing I typically recommend is setting the MSFS Turbulence settings to LOW or MEDIUM. This is based on feedback from pilots on our various testing teams that state that the REALISTIC option produces much more aggressive winds than they would encounter in the real world. This setting is located at: MSFS Options > Assistance > Piloting If that behaviour persists, we would recommend raising a ticket with Just Flight Support via the following link, and our support team will be able to further assist: https://www.justflight.com/support Mark - Just Flight

My initial impression is that TOW is quite heavy for EGLC, and flap 18 is quite a low flap setting. I just set up a basic EGLC-LSZH flight plan on Simbrief with the RJ100, and opened the Takeoff Performance calculator. For EGLC, it has given me a maximum runway weight of 40,100kg and a Flap 30 takeoff at that weight. That is also with TOGA MAX selected on the TRP. For reference, some airlines would actually takeoff from EGLC with Flap 33 selected! Quite the unique quirk of the RJ. Mark - Just Flight

@AlphaEcho You're more than welcome to join the server anyway. You don't have to be an RJ maniac. The topics will stay focused on the 146/RJ though.

Hi Mark... Uninstalling and reinstalling worked... no message about out of date nav data... thanks, Rob

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

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?

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.

That's not a behaviour I recall seeing reported before, and it shouldn't be possible to deploy the lift spoilers in flight, so it sounds like something that could be caused by a controller conflict. The first thing I would recommend checking is if you have any "SPOILERS" control assignments being inadvertently triggered by your external hardware (TOGGLE SPOILERS, SPOILERS AXIS, EXTEND SPOILERS, etc.). For reference, the conditions for automatic lift spoiler deployment are listed on pages 79-80 of the RJ Professional Operations Manual: https://downloads.justflight.com/products/JFF003765/RJ_Professional_MSFS_Operations_Manual_MSFS2024.pdf Mark - Just Flight

This isn't something I recall seeing reported previously, but if this happens again, 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 could provide further details on when this behaviour is observed, then we can begin to log any further instances of this to see if a trend starts to emerge. Mark - Just Flight

OK solved it.

Thank you for the kind words. For future reference, you may be interested to know that there are tools within MSFS Developer Mode that can help you find LVARs for any control in any aircraft. With Developer Mode enabled, if you move your mouse to the menu bar at the top of the screen, and navigate to: Windows > Behaviours > Local Variables. Entering instrument names or abbreviations into the ‘Filter’ field will vastly speed up the process of finding LVARs. For example, if you are trying to find the LVARs used for the transponder, you can search for ‘XPDR' and you will find the following LVARs: "PED_AFT_XPDR_MODE". With the Behaviour debug menu open, it is also possible to automatically populate the "Filter" field with the LVAR name of a specific control. With the Behaviour debug menu open, move your cursor over any control in the cockpit and then press [CTRL]+[G], to populate the "Filter" field with the LVAR name. Hope that can be of some use. Mark - Just Flight