Flights generated by FS Traffic will activate at the time stated in the Traffic Control Centre "Schedules Manager". They will then run through their pre-flight routines (connecting the jetway, baggage loaders, etc) before pushing back from the gate. This process can take up to 15 minutes depending on how many ground services interact with the aircraft. To speed up this process, you can go to Aircraft Manager > Ground Services > Set No Ground Services > Save Changes. This will remove all ground services from the aircraft, allowing them to push back within a few minutes of their scheduled departure time.

It is also worth considering that FS Traffic uses the in-game time when activating flights. So any changes to the in-game time after loading into an aircraft can prevent FS Traffic flights from activating flights. For example, a flight that is scheduled to depart at 10:00 will not activate if the in-game time is changed to 16:00.

For further information on how you can use the Traffic Control Centre to customise your FS Traffic experience, we would recommend having a read of the FS Traffic manual.

Hope that helps.

Mark - Just Flight

Got it thank you

@Mark , perfect. Thanks for the clarification. I know I'm well out of the norm from most users but the sims IFR ATC is awful and was one of the reasons for my limited use of the 146. I think I will replace it with the RJ now.

@Mark Thank you. I'll try it out.

@rj Thank you for the feedback. It's one of those very specific things that we could never find an answer for in the FCOMs, so we based the logic on what we have seen in other aircraft. We've logged that on our internal bugs tracker to look into.

Mark - Just Flight

Thanks, that helps!

Thank you for the feedback. With regards to the ground effect feedback, I don't believe this is something we have been fed back from the flight models in the 146 or RJ, but we will continue to monitor the forums for any other feedback. It is worth considering that a lightly loaded RJ70 will likely be more affected by ground effect than an RJ100 at maximum landing weight though.

It may also be worth experimenting with the "Turbulence" option in MSFS (located at MSFS Options > Assistance Options > User Experience). Setting this to LOW or MEDIUM can lead to more accurate wind conditions within the simulator at low altitudes (this is based on real pilot feedback from our testing teams).

Mark - Just Flight

@flightstrike

Hi. No ... as auto-throttle was on and autoland, I'd reduced them 'physically' to idle.

But heh, it was my first autoland so I need to read the manual a bit more.

And I use a 3rd Party Cardiff EGFF so I know elevation and ILS angles can be 'problematic'.

Prolly a good idea to test it on a stock airport.

Late to the party, i had a similar problem.
In my case i had to disable some additional WTT compatability mod, that was needed previously.

I had a similar problem, the rate file was saved with <src icao><dst icao>01.rte, so for KMRY to KLAS, KMRYKLAS01.rte. initially I tried to load KMRYKLAS in coroute, but that would fail, when I tried KMRYKLAS01 in coroute, that loaded the plan correctly. So maybbe cheek if this is the problem for you.

Has anyone else had problems with pressurization issues. I have tried everything to get the plane to pressurize. I have packs on, app air on. I've also tried all engine switches on and app air off, im also in auto. But I can never pressurize. Cabin air is always the same as altitude. Also outflow switch is normal, but the outflow valves are always open. As the green lights are one. Am I missing something? Thanks

Page 18 under Displays and Controls:

Row 2 indicates cabin two ambient pressure differential; I assume this is supposed to be cabin to ambient?

Quick update on my first point. The oscillation in pitch happens in both lvl change and in vs whether beginning a descent or climb. It seems like the aircraft over compensates the fpm of climb or descent and then tries to correct itself but overcorrects. Thus it begins to oscillate up and down.

During takeoff and initial climb, the flight directors should indicate the pitch required to climb at the V2+10 speed.

We did come across situations in testing where spiking in the user's throttle axis can cause the flight directors to indicate too great a pitch angle during takeoff and initial climb, but we worked around this by adding the "A/T THROTTLE LOCK" option on the EFB which disconnects the users throttles from the aircraft whenever the A/T is active (A/T green on the PFD).

Something I would recommend trying is to load into the aircraft on the runway. Ensure the "A/T THROTTLE LOCK" is enabled on the Aircraft page's Configuration Menu. Advance your physical throttles to 100% (fully forward), then trigger TOGA in the aircraft (click the hidden click spot on the bottom left screw on the captain's VHF NAV radios). Release the parking brakes and takeoff. With the A/T THROTTLE LOCK active, and your throttles in the fully forward position, this should negate any spiking in your throttles axis and allow the flight directors to display the correct pitch angle.

Hope that helps.

Mark - Just Flight

I was hoping being able to use SimBrief's Takeoff Performance calculation, however it always returns SEL TEMP = NONE.

I assume this relates to missing performance data in the aircraft profile. Is this something JustFlight could collaborate on with Navigraph?

We haven't removed any liveries from the RJ package, just added additional liveries. We've never had an Aer Lingus livery for the RJ85 (there is an Aer Lingus livery for the 146-300 which you may have seen some 146 screenshots of), and we've only got the Braathens livery for the RJ85 (not the RJ100).

We are starting to see some RJ liveries being posted on flightsim.to, so it may not be too long until a community member completes those two liveries.

Mark - Just Flight

The correct way to disengage the autopilot in the RJ is to press the red AP DISC button on one of the yokes. If the autopilot has been forced off by other means, the autopilot "cavalry charge" audio can also be silenced by pressing the AP DISC button on the yoke. This can also be triggered using the TOGGLE DISENGAGE AUTOPILOT or TOGGLE AUTOPILOT MASTER control assignments.

It may also be worth considering that the Autopilot DISENGAGE switch on the MCP is only typically used in an emergency. If this switch is activated, the autopilot cannot be reengaged until this switch is returned to the up position. it may cause the autopilot "cavalry charge" audio to play until the switch has been reset and the AP DISC button pressed.

Hope that helps.

Mark - Just Flight

@Mark Thank you very much!

The Navdata in MSFS 2024 isn't something we have investigated just yet. However, the initial compatibility updates for the 146/RJ will focus on making the 2020 versions of the products compatible with 2024, so the initial 2024 versions will retain the Navigraph requirement for updating the Navdata. Once the products are compatible with 2024, we will then investigate what 2024-specific features can be added in future updates, such as the new flight planning/Navdata features.

Mark - Just Flight