RJ Issues
-
So some further testing and I have deduced the following:
When TOGA is pushed the auto throttle goes from armed (white) to active (green) and the thrust is increased to take off power. For some reason however, once initially climbing out, the auto throttle is then changing back to armed and white, thus allowing the throttle to no longer be ignored and send their physical position data to the plan and thus a reduction in thrust.
I have no clue why this change back to the armed state is taking place, I am pressing nothing.
Anyone else seeing similar behaviour?
-
This is correct logic as per the real aircraft. After completing a takeoff with the autothrottle engaged, the autothrottle will return to a disarmed state (A/T white on the PFD) when passing 350ft AGL. This is the altitude where TO mode is automatically disengaged and the throttle freeze mode is left, allowing the pilot to manually control the throttles. At this point, there will be no vertical modes engaged so the autothrottle has to return to the armed state. Engaging any other vertical mode (LVL CHG, V/S, ALT HLD) will reengage the autothrottle (A/T green on the PFD).
Hope that helps.
Mark - Just Flight
-
Thanks @Mark - all makes total sense, are you able to offer any logic or troubleshooting around the cabin lights - still appear to have the issue with them as detailed above ?
I’ve also noted in the manual it says that moving the DU brightness controls to the compact position should give a compact display on either the ND or the AH (depending on what’s selected), but when I dim mine down to that click stop it just blanks the display and doesn’t toggle a compact version. Is this a bug?
Sorry to be a pain, if you could offer any answers I’d be grateful. I adore this fantastic plane!
-
No worries @Mark.
Sorry to confirm, do the cabin lights need to be turned on inside the virtual cabin? If not, what criteria need to be met for the auto cabin lights to kick in as my cabin seems to be in darkness on night flights, despite having auto cabin lights enabled, until I flick the in cabin switches.
-
Hi, I need a little help. I'm a passionate flyer of the RJ 100 in MSFS 24, but for the past two flights, I've been having a problem where both flight directors shut down immediately after takeoff. I'm also having trouble hearing my copilot's callouts. Does anyone have any tips for fixing this? Thanks.
-
With regards to the flight director behaviour, that's a tricky one to diagnose without a video of the behaviour occurring. However, as a first step, I would recommend double-checking for any conflicting control assignments that could be triggering the flight director switches.
An easy way of confirming any control assignment conflicts is to unplug any external hardware (joystick, throttle quadrant, etc.) and then perform a takeoff with only the mouse and keyboard plugged in. If the flight directors remain engaged, then that would confirm that there is likely a control assignment conflict on the external hardware.
The copilot callouts have a specific set of triggers that must be met in order for the callouts to play. An FAQ covering the callout triggers is available at the following link: https://support.justflight.com/en/support/solutions/articles/17000142836-pilot-callouts-and-cabin-announcements-explained
If the above recommendations do not have any effect, could I kindly ask you to raise a ticket with Just Flight Support at the following link, our support team will be able to assist with further troubleshooting: https://www.justflight.com/support
Mark - Just Flight
-
@Mark Hello, thanks for the quick reply. I actually only had the landing lights set to taxi. After I turned the landing lights on properly, the copilot made the announcements. I also deleted some control commands on my Bravo throttle. I probably had some assignments on it after SU2. So far, the flight director has stayed on after takeoff from the ground. I'll test it further in the next few days. Thanks for the tip.
