F28 Professional

Hello, My RJ Professional went from 1.4 to 1.5. It works. Now the same with the F28. I gotta learn how to fly them. I guess I lack some patience. Thank you. Hope all is well. ️

@Mark Thank you! These conditions, plus the conditions for boarding logic, would be awesome to add to the manual in a future update! (I just realized I probably haven't combed the EFB manual exhaustively, so please excuse me if they're already in there)

In addition to the @GroverJ41's fantasitc reply above, we also have a tutorial flight from Page 153 of the F28 Professional Operations Manual that will walk you through an entire flight in the aircraft: https://downloads.justflight.com/products/JFF003039/F28_Professional_MSFS_Manual_v2.2.pdf We also have a 4-part video series on our YouTube channel that covers that tutorial flight: https://youtu.be/zZQf0yjYHtw Mark - Just Flight

@Mark It was well within crosswind limits. I don't have tiller hardware. But there was no dead zone, so I'll try adding that to see it it helps.

It's been a while since we last looked into it, but I seem to recall there being some sort of barrier that prevents us from having fully automated GSX refuelling without FSDT support. However, we've made a note to take another look ahead of the next update to the F28. Mark - Just Flight

@Martyn You're very welcome, thank you to the whole JF team for bringing the F28 to life! In a way, you're part of preserving history with recreating these vintage airplanes. One day the last F28 will fly, but they will always fly within our simulators. I am looking forward to your beautiful F70/100 with the Tay engines and your A300B4 as well. Thank you for passing that along to your sound team in case it could ever be improved!

This aircraft (RJ) should be capable of performing n LPV approach.

Thank you very much. You guys are great.

Unfortunately, it doesn't look like GSX seated passengers are supported on marketplace products due to encryption limitations. The following is from the GSX product page: "Note: Seated passengers feature requires non-encrypted aircraft. Not available for Marketplace aircraft due to encryption limitations." Mark - Just Flight

If you let Just Flight Support know about these they can look into them. https://www.justflight.com/support

The locked cockpit seats are intentional logic in the MSFS 2024 versions of the F28 to work around a simulator limitation. See point 5 in the following FAQ: https://support.justflight.com/en/support/solutions/articles/17000145497-f28-professional-msfs-2024-known-limitations Thanks for the feedback regarding noise reduction/headphone option. Although nothing is planned at the moment, we have added that to our internal feature request tracker for consideration in a future update. Mark - Just Flight

I'm waiting for the addition of a random unruly passenger to really kick up the immersion level.

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

Update 2: all is well, no issues. It could well have been user error, since the "Master Radio" switches have to be on for 60 seconds.

This is a conscious decision by the development team to make the parking brake more accessible across as many flight simulator hardware as possible. We have a feature request logged to perhaps make this logic toggleable via an option on the EFB, but we haven't looked into it as of yet. Mark - Just Flight

You should always set take-off power as 100% on the thrust indicators. Changing the thrust index changes what the indicators regard as 100% thrust, but that's the indicator you always want to hit. The lower the thrust index, the lower the LP and HP rpm indication at 100% thrust indication - you can see this if you set different thrust indexes on each engine or hold the aircraft on the brakes, set 100% on the indicators, then change the thrust index. As you noted, the information needed to do a proper FTTO (runway length vs. aircraft weight) isn't available. So what you can accurately do is a full rated thrust takeoff, setting the maximum thrust index for the given elevation and temperature. This is what the Thrust Index tables in the JF manual and on the in-cockpit paper checklists let you set, and what will be automatically set when you click the a square on the speed reference card, along with the relevant bug speeds. With a full rated thrust takeoff, if you've calculated the thrust index accurately, you should reach 100% thrust on the indicators with the throttles in the detent. In a FTTO, you would advance the throttles until you registered 100% indicated thrust, which may be before the detent is reached, because you are setting the thrust index for a temperature that's much higher than reality. The main purpose of the detent is to provide a clear throttle setting for the minimum throttle setting needing for the engines to produce rated power and the aircraft to achieve its certified performance. With the throttles in the detent and pitch matching the profile commanded by the flight director in Speed Control mode (not modelled in the JF F28), the aircraft is guaranteed to meet the requirements for obstacle avoidance etc. even on one engine. With the throttles below the detent, this isn't guaranteed, which is why the manual says you have to advance the detent OR beyond to achieve 100% thrust when you need full rated power. A Flexible TO is foregoing this guarantee when you have a lot of runway to spare, so you don't need to hit the detent. But if you had an engine failure after V1 you'd advance the throttle of the good engine to full thrust. The detent also indicates/activates other things like the automatic speed brake/lift dumper retract function, and the TTC system, but it's mostly there to indicate the max rated thrust position.

We cannot replicate any increased animation speed behaviours in MSFS 2024, and I don't recall seeing any other reports of it. The only thing I can think of that would affect the speed of the beacon lights and wipers is the sim rate. We haven't tested the F28 in the SU4 Beta though, as officially we don't support any of our products on the MSFS Sim Update betas. The Sim Update betas are beta releases, so bugs are expected, and it would be a full-time job in itself to keep all our products fully compatible with each beta update. If we can replicate this once SU4 has been fully released, we'll include any necessary fixes in the next F28 update. Mark - Just Flight

@Mark ok thanks Mark

Okay, thank you for the info, it is useful to know it's probably not intended, I will try again on SU3, and SU4 when it is out before coming back! Thanks

We do have this logged on our internal bug tracker, and we will look into it again ahead of the next update to the F28. We did intend to look into this ahead of the recent update to the F28 Professional; however, on this occasion, our systems developer wasn't available due to commitments with other products. Mark - Just Flight