F28 Professional

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.

It's not currently possible to change the pilot voices in any of our aircraft; however, we do have it logged as feature requests that will be considered ahead of future updates to each product. Mark - Just Flight

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

Hello Mark, Thank you so much for your reply.Actually I meant,that the space between the main landing gear leg fairing and the tire on the corresponding side is too low,when the aircraft has all the weight on wheels. Its perfect in flight when the landing gear are down before landing.You can see it when observing the real aircraft pictures when parked or on ground.I have almost all of your aircrafts on Msfs2020 and they also excellent. Again its such a minor details I will provide pics if possible.I have logged a lot of hours into the F28 and it is so well made by your team and so immersive with the realistic sounds and everything that sometimes i forgot its actually a simulator,and i am a airline pilot. Thank you for caring and for the excellent customer service. Best regards.

That helps tremendously, thank you!

The lack of brightness of aircraft lighting during the day is a limitation of how MSFS 2024 handles aircraft lighting. The lighting in all of our MSFS 2024 aircraft has been fine-tuned to have realistic brightness levels at night, which does mean that certain lights can look dim or not lit during the day. If we were to increase the brightness of the lights to make them visible during the day, then that would have the side effect of making the lights extremely bright at night. There are various bug reports logged for this on the offical MSFS Forum. For example: https://forums.flightsimulator.com/t/aircraft-external-lights-barely-visible-during-daytime/671317 We remain hopeful that this may be something that will be improved in future MSFS Sim Updates. The low-res textures in your screenshot, we can't confidently say the cause of with the limited information in the post. As a first step, we would recommend checking the Texture Resolution settings in MSFS 2024. The higher this is set, the higher resolution the textures will be, but at the expense of FPS/performance. If you have a PC with a GPU featuring 12GB of VRAM or more, we have an optional 8K cockpit textures available for download here: https://support.justflight.com/en/support/solutions/articles/17000134893-f28-professional-8k-cockpit-textures There are also automatic performance-saving measures built into MSFS 2024 that will automatically downscale a texture sheet's resolution when the sim thinks most of the texture sheet is off the screen. Depending on where the camera was placed when the screenshot was taken, the sim may be automatically downscaling those textures. Mark - Just Flight

Thanks for your reply Mark, I look forward to it!

@Mark W Wonderful glad to hear Mark

That is intended logic. The GPW "GS MODE" switch will inhibit glideslope warnings, and the GPW "LG/FLAPS" switch will inhibit flap warnings if landing with a flap setting that is less than 42°. These are both independent of terrain/sink rate GPWS alerts, which can only be inhibited by pulling a circuit breaker (which aren't simulated). Mark - Just Flight

@MPilotD Awesome, glad you got it sorted -- happy flying!

Thank you Mark...

The above screenshot was taken in 2024. If you do end up picking up the F28, the following website has the LADE 1981 and 2005 timetables: https://www.timetableimages.com/ttimages/ld.htm Best of luck Mark - Just Flight

It is worth considering that the F28 is an aircraft that was designed and built in the 1960s. It doesn't have an autothrottle, and the autopilot is very rudimentary (often with only on/off modes). I recall during testing that I did experience similar oscillations, but after discussing them with our flight model developer and F28 experts, we came to the conclusion that they were mostly always caused by me trying to fly the F28 like a modern airliner with a sophisticated autopilot. I'll post some tips below that have helped me fly the F28 more realistically: Avoid making large, sudden changes to the vertical speed. With V/S mode enabled, the F28s autopilot will command whatever vertical speed is selected on the altitude preselect controller. If the V/S is instantly increased from 0 to 2000ft/min, the aircraft is going to pitch up at its maximum rate and will likely overshoot the vertical speed target and will take a few osciallatiosn to settle on it. It is good practice in any aircraft, especially older ones, to slowly increase/decrease the vertical speed for passenger comfort. For this, try increasing/decreasing the vertical speed knob in the range of 1-3 notches per second, and see if that improves the osciallations. Ensure the selected V/S matches the aircraft's current V/S before enagaging V/S mode. For similar reasons as above, if the aircraft is in level flight and V/S mode is selected with the V/S knob already set to 2000ft/min, the aircraft is going to pitch up at its maximum rate and overshoot the vertical speed target. The best procedure for using V/S mode is to first set the V/S knob to match the aircraft's current vertical speed, then engage V/S mode, then slowly increase/decrease the V/S knob to the desired V/S speed. Preempt altitude capture in a descent by increasing engine power. In a modern airliner, the autothrottle systems will most likely increase engine power as the aircraft levels off in a descent. This ensures the aircraft's airspeed remains the same throughout the altitude capture phase, and the aircraft will maintain similar momentum. As the F28 doesn't have an autothrottle, this power increase must be done manually. As the aircraft enters the altitude capture phase, you'll want to slowly increase engine power to maintain the same airspeed as you were at in the descent. All three points above will come more naturally as you start to fly the aircraft more. Just like the real pilots, you'll start to understand the aircraft's quirks, and you'll find the techniques that work best for you. See how you get on with the above tips. If you do still experience oscillations on future flights, could I kindly ask you to raise a ticket with Just Flight Support at the following link: https://www.justflight.com/support In the ticket, if you could provide specific examples of when the oscillations occur (i.e. provide steps for how our support team can reproduce the behaviour), and if possible, send us a video of the behaviour, then we will be in the best position to be able to assist with further troubleshooting, or we'll have enough information to pass onto our development team for further investigation. Mark - Just Flight

Yep it is another JF masterpiece for sure.

I just created a support ticket for this issue, it's still broken in 0.2.2