As a quick follow-up on this, our IT team did find and fix the issue with the FAQ "Page 2" on Friday evening. So the FAQs should now be fully viewable: https://support.justflight.com/support/solutions/folders/17000144909 Apologies for the inconvenience. Mark - Just Flight

The F70 & F100 Professional can be activated either via the installer or via the EFB/Tablet. If it has been successfully activated in the installer, it does not need to be activated again on the EFB/Tablet. Mark - Just Flight

A fellow F70 & F100 user has posted their TCA Thrustmaster sensitivities here: https://community.justflight.com/post/51459 Hope that helps. Mark - Just Flight

We are looking into a possible incorrect path depiction on the ND on long legs: https://community.justflight.com/post/51217 Mark - Just Flight

There aren't many systems powered when only the Batteries switch is selected ON, but there should be the sound of some avionics in the background, as well as the EFIS Emergency Cooling Fan. On the overhead, the EFIS EMER COOL FAN annunciator should be illuminated, along with the ELECTRIC panel displays and the dome lights. If none of those things is happening, then that would suggest an installation/activation issue. We'd recommend unsintalling/reinstalling the F70 & F100, and ensuring that the Activation Key is entered either when running the installer, or on the EFB/tablet after loading into the aircraft. If the issue persists after a reinstall, we would kindly ask you to contact Just Flight Support for further assistance: https://www.justflight.com/support Mark - Just Flight

I've just done a quick test with the F100 at 30,000 kg, and VMA looks correct. In the following screenshot, VMA is approximately 128, and the VREF for flaps 0 is 134. [image: 567a562d-35fd-4787-bca4-353330385962.png] VMA does vary with flap position, as well as the weights entered in the FMS. Mark - Just Flight

There are no changes to the rudder sensitivity being looked into at the moment. We set the rudder effectiveness to allow it to have enough effectiveness at the aircraft's crosswind limits, so any reduction in the rudder effectiveness would negatively affect that. That's not to say there won't be changes/improvements in the future. In the meantime, there are a few things you can try: Ensure your rudder axis sensitivities are all linear (straight lines). All of our flight models are developed using linear sensitivity curves, so we would always recommend using linear curves as a starting point. It is then possible to reduce sensitivity from there based on personal preference. The "RUDDER STEERING AXIS" option on the EFB can be a useful tool to provide more realistic nose wheel steering/rudder control. With this option enabled, any rudder inputs will control nose wheel steering AND rudder, so you will have a mixture of both operating during the takeoff roll. With this option disabled, rudder inputs will only control the rudder, so you will only have rudder controls during the takeoff roll, making control less sensitive. With this option disabled, you will need a way to control nose wheel steering separately from the rudders. Hope that helps. Mark - Just Flight

@nhe03 Noticed the same thing. The hPa is off by ≈1.5. It would be nice if this could be fixed.

Thank you for your feedback. To answer each of your points: 1/2: We are working on gathering as much feedback on these behaviours as possible whilst working on improvement ahead of future updates to the product. If you have any specific examples of this, we'd be very appreciative if you could send any screenshots/videos of this behaviour, as well as a log file to Just Flight support via the following link: https://www.justflight.com/support Instructions for locating the log file can be found here: https://support.justflight.com/en/support/solutions/articles/17000152594-where-to-find-the-log-file-s- 3: After APU Start, it takes 2 minutes for APU bleed pressure to become available - this is the same logic as the real aircraft. However, if you use one of the states on the EFB, APU bleed pressure will become instantly available. 4: The "TCAS OFF" text overlapping the artificial horizon is accurate per the real aircraft. For example: https://www.jetphotos.com/photo/8247706 Mark - Just Flight

Pink/missing textures are usually caused by installation issues. Could you kindly try uninstalling/reinstalling the F70 Professional, and that should ensure all the textures are installed. Mark - Just Flight

I would love GPS RNAV as an option, especially since many of them IRL have had this retrofit.

@ScotchMist If you are using Spad Next, Ive done a snippet (17282) to fix all these issues. Here are the expressions for each of the windows that will show exactly what you see on the plane. But I agree, we shouldn't need to write this code ourselves to interpret these windows. Sharing it so everyone can enjoy flying the plane with their hardware: Altitude: Display Expression-Result Format '000' If( [LVAR:AFCAS_ALT_Window_1] == 254 && [LVAR:AFCAS_ALT_Window_2] == 254 && [LVAR:AFCAS_ALT_Window_3] == 254 && [LVAR:AFCAS_ALT_Window_4] == 254, '', ( If([LVAR:AFCAS_ALT_Window_1] == -16 || [LVAR:AFCAS_ALT_Window_1] == 254, 0, [LVAR:AFCAS_ALT_Window_1]) * 10000 + If([LVAR:AFCAS_ALT_Window_2] == -16 || [LVAR:AFCAS_ALT_Window_2] == 254, 0, [LVAR:AFCAS_ALT_Window_2]) * 1000 + If([LVAR:AFCAS_ALT_Window_3] == -16 || [LVAR:AFCAS_ALT_Window_3] == 254, 0, [LVAR:AFCAS_ALT_Window_3]) * 100 + If( [LVAR:AFCAS_ALT_Window_4] == -16 || [LVAR:AFCAS_ALT_Window_4] == 31 || [LVAR:AFCAS_ALT_Window_4] == 254, 0, [LVAR:AFCAS_ALT_Window_4] ) * 10 )) Heading: Display Expression-Result Format '000' If( [LVAR:AFCAS_HDG_Window_1] == 254 && [LVAR:AFCAS_HDG_Window_2] == 254 && [LVAR:AFCAS_HDG_Window_3] == 254, '', If( [LVAR:AFCAS_HDG_Window_1] == 255 && [LVAR:AFCAS_HDG_Window_2] == 255 && [LVAR:AFCAS_HDG_Window_3] == 255, '---', If([LVAR:AFCAS_HDG_Window_1] == -16 || [LVAR:AFCAS_HDG_Window_1] == 254, 0, [LVAR:AFCAS_HDG_Window_1]) * 100 + If([LVAR:AFCAS_HDG_Window_2] == -16 || [LVAR:AFCAS_HDG_Window_2] == 254, 0, [LVAR:AFCAS_HDG_Window_2]) * 10 + If([LVAR:AFCAS_HDG_Window_3] == -16 || [LVAR:AFCAS_HDG_Window_3] == 254, 0, [LVAR:AFCAS_HDG_Window_3]) )) Speed: If( [LVAR:AFCAS_SPD_Window_1] == 254 && [LVAR:AFCAS_SPD_Window_2] == 254 && [LVAR:AFCAS_SPD_Window_3] == 254, '', If( [LVAR:AFCAS_SPD_Window_1] == 255 && [LVAR:AFCAS_SPD_Window_2] == 255 && [LVAR:AFCAS_SPD_Window_3] == 255, '---', ( If([LVAR:AFCAS_SPD_Window_1] == -16, 0, [LVAR:AFCAS_SPD_Window_1]) * 100 + If([LVAR:AFCAS_SPD_Window_2] == -16, 0, [LVAR:AFCAS_SPD_Window_2]) * 10 + If([LVAR:AFCAS_SPD_Window_3] == -16, 0, [LVAR:AFCAS_SPD_Window_3]) ))) Vertical speed: If( [LVAR:AFCAS_VS_Window_1] == 254 && [LVAR:AFCAS_VS_Window_2] == 254 && [LVAR:AFCAS_VS_Window_3] == 254 && [LVAR:AFCAS_VS_Window_4] == 254 && [LVAR:AFCAS_VS_Window_5] == 254, '', If( [LVAR:AFCAS_VS_Window_1] == 255 && [LVAR:AFCAS_VS_Window_2] == 255 && [LVAR:AFCAS_VS_Window_3] == 255 && [LVAR:AFCAS_VS_Window_4] == 255 && [LVAR:AFCAS_VS_Window_5] == 255, '-----', If([LVAR:AFCAS_VS_Window_1] == 253, 1, -1) * ( If([LVAR:AFCAS_VS_Window_2] == -16, 0, [LVAR:AFCAS_VS_Window_2]) * 1000 + [LVAR:AFCAS_VS_Window_3] * 100 )))

@Rhinozherous We do need to stay indeed civil and respectfull, these guys worked hard on it, and that must be said! I knew from the get go that I would not fly this plane much without a failure system, but I bought it anyway to show my respect and support to the efforts that has been made by the developers. But because of that it will be a "hangar queen" most of the time.

Thank you for the feedback and for the kind words. The way the FMP/autopilot knobs are currently set up doesn't allow them to be controlled and animated at the same time, but we do have this logged on our internal trackers and intend to add support for it in future updates. Mark - Just Flight

Thanks for the feedback. Looking into your specific example, the root cause is the extra decimal place in the longitude. I.e. "/01716.51E" will generate a FORMAT ERROR scratchpad message, but "/01716.5E" will be accepted. We've logged this on our internal trackers for further investigation. Mark - Just Flight

Thanks for the feedback, everyone. I've also seen this occur at the end of a flight, but it's proved a bit of a tricky one to track down with it not occurring every flight! We do have it logged on our internal track,ers and we are actively investigating it. With regards to co-pilot callouts, the AFCAS MODE warning shouldn't have any effect on them. For reference, the triggers for all the announcements/callouts can be found here: https://support.justflight.com/en/support/solutions/articles/17000151473-pilot-callouts-and-cabin-announcements-explained Mark - Just Flight

Thank you for the feedback. I have just tested this on my side, and I am seeing the correct altitude indications on TCAS. Can you confirm that both aircraft in your example had correct altimeter settings? Mark - Just Flight

I should have said that the performance is similar to the Turbo prop bonnie. After speaking with a gentleman on the field that has an A36 with the latest and greatest from Tornado Alley, there really should not be that much difference in performance from a NA bonnie down low. Also, he remarked that even on the takeoff roll you cannot hear the turbo spool up. Just food for though. Otherwise it's an absolute joy to fly and my go to aircraft.

I believe I found the issue. On my latest flight I was paying very close attention to the F/D bar and how the autopilot follows it. Speed kept deviating from target ( like in all my flights ) and F/D bar commanded a lower pitch, however AP is very slow to react and causes the speed variation. I disconnected the AP during cruise and by following the F/D bars I no longer have speed variations like on AP.