MSFS Products

We're not aware of any compatibility issues between 146 Professional v2.4a and RJ Professional v1.4. Could I kindly ask you to raise a ticket with Just Flight Support, and one of our team will be able to assist with troubleshooting this: https://www.justflight.com/support Mark - Just Flight

The KLN-90B is v2.04 (Aug 20). The TDS GTNxi is up-to-date. (Recent update) I didn’t have PMS50 GTN, so downloaded the latest and installed. The PMS50 GTN doesn’t light up heading, nav or approach either. KX 155B did light up the autopilot modes. The GNS 530 and PMS50 GTN are failing to light up but the autopilot is functioning. Thanks. The KLN-90B is the v2.04

I have just looked into this, and it doesn't look like the PRIMER control assignments are supported in the PA38. I have therefore logged this on our internal bug tracker, and we'll add support for those in the next update. Thanks for reporting this. Mark - Just Flight

We're not aware of any brake issues in Vulcan, however, if you're using MSFS 2024 there have been some changes to Parking Brake control assignments in SU3 that could be causing a conflict. See: https://forums.flightsimulator.com/t/parking-brake-cant-toggle-on-off/734585 If brake issues exist in multiple aircraft, that typically points to either a control assignment conflict. Mark - Just Flight

It is expected behaviour that the F28 should be susceptible to floating when entering the ground effect. The F28 has a low wing, much lower than most conventional aircraft due to the lack of engines, and it also has a very thick wing that is designed to generate lots of lift at low altitudes. Combine both of those factors with an approach speed which is similar to more conventional airliners, and it's likely that the aircraft will be rather susceptible to ground effect. If an approach is carried out following standard procedures, it is standard to extend the speedbrake as the aircraft crosses the runway threshold (there is a callout for this in the F28 Professional). When the speedbrake is deployed, the extra drag will slow the aircraft down to the VREF speed, thus reducing any tendency to float. Upon touchdown, the liftdumpers will automatically deploy (if armed), which are used to spoil any remaining lift that is being generated by the wings. The act of extending the speedbrake during the final approach is something unique to some of the aircraft we develop (F28/146/RJ), and does differ from the more conventional aircraft, but once you start doing it a few times, it starts becoming second nature. There are few settings in the simulator that we may recommend changing that could improve your experience with both points you raise: We recommend using linear sensitivity curves for all of our aircraft. This is what the flight models in our aircraft were developed around, and provides consistent control throughout the control range. The sensitivity curve can be adjusted in MSFS 2024 Settings > Control > then click on the cog icon next to your joystick/yoke/controller > Hardware Settings. We recommend using the "Low" turbulence setting. Based on various feedback we receive from real-world pilots on our testing teams, the "Medium" and "Realistic" turbulence settings tend to produce overly aggressive wind effects in the simulator. Therefore, reducing this setting to "Low" will provide a more realistic experience, and may reduce any wind effects/ground effect caused when low to the terrain. The turbulence setting can be found at MSFS 2024 Settings > Assistances > Turbulence. Hope that helps. Mark - Just Flight

At the moment, v2.4 is available at JustFlight.com and other third-party retailers for PC. We are currently in the process of building and uploading the builds onto the 2020 and 2024 marketplaces for both PC and Xbox. Tricky to give exact dates on when they will become available, but based on experience, I would say it will be 1-2 weeks for the PC versions to release, and 2-3 weeks for the Xbox versions to release. Lots of factors may change that, but those are our best estimates at the moment. Mark - Just Flight

There have been various improvements to this over the course of FS Traffic's updates; however, it's sadly not something that can be removed entirely without affecting the traffic generation at the destination airport. The small freeze is caused when the FS Traffic module detects that the player is within a certain radius of the destination airport, and starts to read the schedule files that are stored locally on your PC. Once it reads those schedule files, it'll start to generate the relevant traffic. The more schedules that exist at the destination airport, the longer it'll take for the FS Traffic module to read those; therefore, the size of the freeze is directly related to how busy the destination airport is. For example, if you approach a small to medium-sized airport like Manchester (EGCC), you may only notice a small stutter, but if you approach Chicago O'Hare (KORD) at rush hour, you will get a larger stutter. Mark - Just Flight

The G3X Touch used in our Hawk is one of the default GPS options included in MSFS, developed by Working Title, so we don't actually have any control over its functionality. The logic of the flight plan being removed when the GPS is turned off, I can only assume, is either accurate to the real unit or is a feature that has been implemented for MSFS compatibility. I seem to recall that in order to get a flight plan loaded in the G3X that you have to have departure and arrival airports entered in the flight plan. So if you try and create a flight plan when the aircraft is not on the ground at the departure airport, the GPS may not create the flight plan. Mark - Just Flight

Thanks so much Mark!

I agree. I would be willing to purchase an upgrade for the Turbo Arrow package.