MSFS Products

Running RJ in MS2024 and copilot is not showing. Noticed the same thing in the 146 MS2024 version. The copilot is enabled for both planes. Not sure if I need to set something within MSFS. Any suggestions? Thank you.

Thanks for the summary. Have you make sure the TDS GTNxi is up-to-date, the PMS50 GTN is either not present or up-to-date, and the KLN-90B is the MSFS 2024 version and up-to-date? I know I've asked about everything except the GNS 530, but that's how this can be sometimes. Other GPS units might be interfering with the GNS in unpredictable ways. Glad you're enjoyed the airplane, but I will be a lot happier when we can ensure you have a working GNS 530!

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

Interesting the patch notes say it required the F28 to work; I don't have it and it worked for me.

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

@Mark said in POH Charts: What am I doing wrong?: I'm not personally aware of us having an alternative version of the ODM with different charts; however, I'll ask the question to the team in the morning and get back to you. Mark - Just Flight Thanks Mark! There was only ever the one version, and it was updated not long after I made this topic those few years ago. However, like I said, I just overwrote my copy with one downloaded direct from the support page since you guys don't package them with the aircraft anymore, and it looks like that version is missing the engine power chart (or maybe it's that ancient version, I know you guys were having caching problems on the website a week or two ago).

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