F70 & F100 Professional

Thank you for the feedback. We have forwarded that to our artists for further investigation. Mark - Just Flight

Above issue was via EFB. Uninstalling and installing from fresh, inputting the code via the installer fixed this...

I tried to reproduce it now on sim and TO CG was approx 25 %, so more matching with 1.8, but it's not the first time and the first leg I had this issue. I'll send a ticket if it occurs again.

Thanks Mark! Loving the F100

Even more interesting! We'll continue to monitor this anyway for any trends. Mark - Just Flight

Thank you for the feedback. For any AFCAS/ATS related feedback, could I kindly ask you to raise a support ticket with Just Flight Support at the following link: https://www.justflight.com/support The F70 & F100 Professional are complex products, so in order to give our support team the best chance at offering speedy assistance, and for any potential bugs to get properly logged and addressed, could you please include any screenshots/videos of the behaviour with your ticket, as well as attaching the log file generated by the product. 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- Mark - Just Flight

Sadly, this is not something we have any control over, and it would be up to the discretion of FSDT to implement on their end. We did contact FSDT about this and several other GSX-related items before release, but we have not yet received a response. Mark - Just Flight

I also want to add my vote for this. It would be awesome to see the fokker with the winctrl MCDU.

@Mark Thanks, rgr wildo...

When creating custom SimBrief Profiles, the only control we have over altitude is a "Service Ceiling" value, which is correctly set to 35,000ft, and a "Cruise Offset" value, which is intentionally set at P0000. The former controls what the aircraft's maximum altitude is, and the latter applies a global offset to that (for example, if we set a Cruise Offset of M2000 to the current profiles, then the maximum possible cruise altitude would be 33,000ft, even on 5-hour flights). Using a combination of the default SimBrief profile for the aircraft, as well as the values in the custom SimBrief Profiles, SimBrief then calculates what it believes is the ideal cruise altitude. We have no control over what cruise altitude SimBrief generates, other than what the maximum cruise altitude can be. The OPT/MAX altitudes in the CDU will always be a more accurate indication of the aircraft's optimum and maximum cruise altitudes, and if a cruise altitude generated by SimBrief is greater than those values, the SimBrief OFP can always be regenerated after manually lowering the cruise altitude. Mark - Just Flight

STATE SAVE Was the source of my problem. I fixed my start failure issues by loading a flight and going into the Fokker100 settings in the EFB and disabling “State Saving”. Then restarted the same flight and my engines started again. I believe the issue is more related to the State Save functionality than anything else. Especially if the last flight with State Save enabled resulted in a crash, pulling engine fire levers, or engine flame out before being unable to start engines as per normal. Didn’t need to remove my mixture settings from my Flight Yoke System, just need to be sure the mixture lever is always on full rich as with any add on. This was my solution, there could be others as well. Good luck all.

Indeed, I am suffering from this bug as well, but only in MSFS2024 - in my case in every flight in MSFS 2024, also not using any addons that could interfere with the flight model. In MSFS2020 both F70 and F100 fly very accurately and there are never any issues with the autopilot being unable to follow the path as computed by FMC.

We have simulated two independent sources of external power in the F70 & F100: GPU and Jetway. Further information on both methods, as well as the indications provided on the EFB tablet, can be found on page 17 of the F70 & F100 Professional EFB Manual: https://downloads.justflight.com/products/JFF003811/F70_F100_Professional_MSFS_EFB_manual.pdf Hope that helps. Mark - Just Flight

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.