This isn't something I am able to replicate on my side, so if the behaviour persists, 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're able to provide any further information about the behaviour, ideally including the flight plan, the phase of the flight where the behaviour occurred, as well as any related screenshots/videos, then our support team will be best positioned to assist with further troubleshooting, or to pass on to the development team for further investigation. Mark - Just Flight

The /FUEL value on the PERF INIT page, I don't believe, has ever been alterable in the RJ Professional, as it automatically synchronises with the aircraft's current fuel quantity. However, fuel values can be entered into the PLAN field. Mark - Just Flight

As you correctly said, the Documentation folder was removed from the RJ package with the latest build to comply with the MSFS 2024 SDK, and that includes the tutorial flight file. The purpose of the tutorial flight file was just to select the same aircraft, airport, gate, etc that is used in the tutorial flight, which can also be done by selecting the gate manually in the main menu. For the RJ tutorial flight, you'll want to choose the following in the main menu: Aircraft: RJ100 Livery: Swiss 'Zurich Shopping Paradise Livery' Departure Airport: Zurich (LSZH) Gate: H85 Time: 1000L (0800UTC) Weather: Clear Skies We'll make a note to clarify that in the manual with the next update. Apologies for the confusion. Mark - Just Flight

The weather radar is intentionally not simulated on the ND as we have modelled and simulated the separate Weather Radar unit located on the pedestal. Mark - Just Flight

Typically, behaviour such as this will be related to a control assignment conflict. An easy way to confirm if this is the case is to unplug all your external hardware (Joystick, Throttle Quadrant, etc.) and then take off using only the mouse and keyboard. If the landing gear/hydraulic issue no longer exists with just the keyboard and mouse plugged in, then it is likely a control conflict with your other hardware. If this behaviour persists, could I kindly ask you to raise a ticket with Just Flight Support via the following link and one of our support team will be able to assist with further troubleshooting: https://www.justflight.com/support Mark - Just Flight

I manged to get it working somehow reliably two times. I disabled my VPN as I've read in another forum that State Saving is actually saved onto Microsoft's servers (truly horrible choice), so I figured NordVPN might be a problem. The same post also told about the importance of choosing the same livery, as SS is tied to that also. This is not on the manual. I noticed that sometimes the livery is pre-selected, some other times it reverts back to the default one. In the first case, I've found it's good to actually select another livery, then select the previous one manually, and some of the variables are recalled: engine health, active failures, fuel on board, windowed open, cabin thermometer. The rest is always reset (including the radios).

@vanislepilot Unfortunately, I don't have those variables exposed at the moment. Tracking them with the H:Events might be a very simple solution, since they will always initialize to the same values. On the other hand, if doing some simple code edits doesn't scare you, then you can add the following lines immediately after screentimeUpdate_L(){ in PFD.js. SimVar.SetSimVarValue("L:var_DecisionHeight_L, "feet", this.decisionHeight_L); SimVar.SetSimVarValue("L:var_AlertAltitude_L, "feet", this.alertAltitude_L); That should do the trick!

Hi Martyn. I just wanted to give you a quick reply since you took the time to write this out. I have also intuitively noticed this behavior with my own software, and I did investigate what was causing it at one point. This was several years ago, but I believe there was a fuel-flow-based simplification that I made that was likely the cause. Unfortunately, I didn't see a clean way of fixing this at the time. I suspect this behavior might go away when I start using some new fuel flow calculations available in the sim (2020 & 2024) courtesy of Working Title. If it still persists, then I will revisit the cause and see if I can come up with a solution after sitting it on it for a couple years. Thanks for your thorough explanation!

And finally a good studysim float plane.

Unfortunately, double sided dynamic signs are not possible in MSFS, so I've had to do the best with what is possible within the simulator. I have tailored my new sign models to minimize thickness and any z-fighting when compared to the default models, however.

The TTN section was updated in the latest version of the manual. Could you kindly double-check that you've downloaded the latest version from here: https://support.justflight.com/support/solutions/articles/17000142841-rj-professional-msfs-manuals [image: ef406bf8-ee90-4492-b648-938c2aa89f05.png] Mark - Just Flight

@All-About-Aviation Was submitted last week, earliest it will be available is this coming Thursday but obviously no guarantee there.

They are 2 separate computers for redundancy. When I load a flight plan, both FMS2 and FMS1 have the waypoints. You will notice that, when sitting in the left seat, and selecting "FMS2" as your nav source, the nav data will appear in yellow on the navigation display to let you know that you are using a "cross side" source (conversely, in the right seat, selecting "FMS1" will show in yellow). They are 2 separate computers for redundancy. When I load a flight plan, both FMS2 and FMS1 have the waypoints. You will notice that, when sitting in the left seat, and selecting "FMS2" as your nav source, the nav data will appear in yellow on the navigation display to let you know that you are using a "cross side" source (conversely, in the right seat, selecting "FMS1" will show in yellow). Here is an example for you. Here, I have entered a simple flight plan using the FLT PLAN screen on the left CDU, origin KTIW (Tacoma Narrows) and destination KPAE (Paine Field). Here I have selected FMS1 as my nav source on the left side CDU, and FMS1 as the nav source on the right side CDU. [image: 7VbQyTc.jpeg] Note that the left side Navigation Display shows Course, Waypoint, Selected System (FMS1), Distance to go, sequencing mode, and course deviation indicator in white, and this data appears in yellow on the right side ND. Here I have selected FMS2 as my nav source on the left side CDU, and FMS2 as the nav source on the right side CDU. [image: ywYSV2y.jpeg] Now, on the left side, the navigation data is yellow, and on the right, it is in white. That is because the left side is in "cross source" mode, and the system is telling me I'm doing so. Bonus: Radio Navigation sources show in green when "same side" selected (e.g., VOR1 in the left seat, VOR2 in the right seat): [image: Bb3T0S0.jpeg] And here I have selected VOR2 in the left seat, and VOR2 in the right seat: [image: iga8Ctk.jpeg] I don't think there is an auto failover here, you would have to select the "working" system manually in the NAV SOURCE page should one of the computers bite the dust.

For those just dipping their toes into the AAO route, I'll offer my (still novice) experience. The program has some quirks that I encounter from time to time, but overall I love it and I use it for all of my planes. The "Scripts->Watch Simulator Events" can be a great help, depending on the plane. Also, MSFS dev mode toolbar "Tools->Behaviors" is indispensable when it comes to investigating what's happening when you press a button or move an axis. I started using AAO because in both MSFS 2020 and 2024 I have completely lost my controller profiles several times (once was my own fault, I did a cloud reset and didn't investigate how to save the profiles first). This was extremely frustrating for me, especially with 2024's very laggy controllers menu pre-SU3. AAO has overall been a godsend. Since getting most of the basics, the only thing that's been challenging enough for me to give up on is camera controls. Just didn't have the gumption for it, so they're all still bound in the sim. Edit: Also, thanks @HadronFlux for the video, I'll definitely be watching it to see what tips & tricks I can pick up.

thank you

Absolutely does. Thank you. I will get it handled.

Managed to get on before leaving. Did a proper reinstall still the same. Convinced it was something in my settings. Had a look around and not one of my switches wasn’t in the same position as usual. Flicked that to the normal position and bingo. It was mapped to ‘toggle engine 1 fuel value‘. Removed the binding so won’t happen again. Once again thanks for your reply. It made me do more digging.

Hi Mark, Thanks for the reply, it must be frustrating having to deal with new sim. All the best David

@Godwisper The VR issue is still present with the latest version in MSFS 2024. I'm really disapointed to be honest and I would not recommend purchase for users who like to fly in VR. The plane itself seems to be quite good, so far only VR experience is BAD. I logged a ticket but i'm pretty sure the answer will be "we already aware about the issue and working on a fix"