F70 & F100 Professional

The liveries included with the Livery Manager app have their livery_config.ini files stored within the main package, so it is expected that they won't appear in the \LocalState\Work folder location. If you haven't already, could I kindly ask you to raise a support ticket for this with Just Flight Support at the following link: https://www.justflight.com/support Our support team is best positioned to provide further assistance or log any bugs in our internal trackers if needed. Mark - Just Flight

Thanks for the feedback. We have this logged on our internal trackers to address in the next update. Mark - Just Flight

Also hoping for a dark blue British Midland Livery, dont forget about us in 2020 still!

Thanks, that's exactly what I'm experiencing too, and in the descent it WILL overspeed..

I don't think this is a limitation of the non-GPS architecture of this aircraft. DME/DME and IRS should not deviate that much during short flights (and I doubt they have simulated degradation either). The plane is artificially not following the track, so it's up to JF to fix it.

Thanks for the feedback. We've logged this on our internal tracker for our development team to look into further. Mark - Just Flight

Thank you for the feedback. We'll log this feedback for our development team to look into for a future update to the F70 & F100 Professional. Mark - Just Flight

The EFIS warning on the LH MFDU typically indicates that one of the EFIS displays has its brightness set to the lower position (OFF). I would recommend double-checking that the PFD/ND knobs on both EFIS Control Panels are all rotated above their minimum positions. Mark - Just Flight

Hi Mark...doh..yes contrails, my apologies. I must be flying in every warm area known to man lol not seen a single contrail yet and have been upto 34,000ft. Will continue to watch for them and thank you for the kind response. Tony

@SimRaceFly Typically, a cockpit control being held in one position is caused by a controller conflict. I would recommend checking if you have any controls assigned to the APU OFF or APU STARTER control assignments. Mark - Just Flight

@Genista So from the manuals, NA (Noise abatement) button activates this mode called NAP, noise abatement profile, that essentially is a vertical mode activated. And in fact it does limit the engine power in orde to reduce noise, by: Inhibiting Flex EPR, and changing it to NEPR (Noise EPR) Activates NA on the Flight mode anunciator, that comands the Flight Director to initiate during the takeoff a rotation of 3deg/sec until it achieves a pitch of 22deg or a speed of V2+10kt, wichever comes first. At 400ft (lower than any possible selected THR RED) by manual selection of CLB THR reduces pitch and power even further to achieve lower noise leves. At ACCEL ALT selection of PROF or LVLCH reverts to a normal acceleration (250kt) and continues normal climb. [image: 91f25876-8b4e-4a00-bec3-2044bf530ff5.png]

Thanks for the feedback. We've logged this with our development team to look into further. Mark - Just Flight

Thank you for the feedback. I have passed this on to the development team to look into further. Mark - Just Flight

I am unable to replicate any issues with the takeoff speed export on my side. After calculating the takeoff performance on the EFB Performance Calculator app and pressing the "EXPORT TO SPEEDS" button, the speeds are being exported into the FMS and displayed on the PFD as expected. It may be worth noting that any changes to the weights entered in the FMS will invalidate the takeoff speeds, and they must be reentered (for example, if the "EXPORT TO SPEEDS" button was pressed followed by the "EXPORT WEIGHTS" button, that would invalidate the takeoff speeds and they would need to be reentered). I believe the speeds are also invalidated if the departure runway or SID is changed. Hope that helps. Mark - Just Flight