@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

@Ausgorilla245 You are not contradicting me. I said I could not find any information on the fleet in Australia. I actually figured that if the upgrade was done on any of the operational fleet it would have been Alliance. I just gave up searching that. Also, if you notice my avatar, I am a Marine and have no feelings to hurt or contradict. I had my feelings removed with my wisdom teeth at boot camp. Having no feelings means I rarely get mad or butt hurt.

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.

Thank you for the kind words, and it's great to hear you're enjoying the products! I have logged both of the feature requests on our internal trackers, and although we can't guarantee all requests will be added to the product, they will certainly be looked into by our development team when planning future updates. Mark - Just Flight

Thank you for the feedback. I have passed this feedback on to our livery artist for consideration. The livery organisation in the simulator is sadly a limitation of the simulator when using MSFS 2024 native (but not modular) packages. It is something I'd love to have improved too, but sadly we haven't found an easy way to do that at the moment. Mark - Just Flight

Yes, we do plan to bring the latest livery_config.ini logic across to the RJ in the next update. Mark - Just Flight

Thank you for reporting this. I have logged this on our internal tracker. Mark - Just Flight

Thanks for the feedback. We have logged that on our internal trackers to investigate. Mark - Just Flight

The actual fuel and payload that is loaded into the aircraft, or the predicted fuel and payload from a SimBrief OFP, can be exported into the FMS in any aircraft state. That can be done via the "Export Weight" button on the EFB Performance Calculator app. When importing a SimBrief OFP on FMS INIT A page, this will only import the flight plan. Hope that helps. Mark - Just Flight