I got this today and as usual a great addon by Justflight, only small little issue I have is that no matter the curve I add, the wheel brakes feel very sensitive.

Overall very happy that I have a JF regional Alliance and Virign flights to do between airports along the East Coast of Australia.

What I like about JF is they make their cockpits look less cartoonish and more realistic, Fenix is another master at that.

3 hours ago, AJZip2 said:

Ignore the above!! It wasn't anything to do with the mouse configuration at all... There were some leftover default commands still in my Honeycomb Yoke and also Throttle blocks that related to APU!!

I know that I cleared ALL supplied Honeycomb commands when I first got the controllers a few years ago - but the little tinkers clearly snuck these two back in!! Those spurious commands are now removed and all of a sudden my Legacy mouse settings worked a dream! 😊

I think this was the reason on my first attempt today that I couldn’t get the engines started!!! All cleared for next attempt tomorrow morning as I ran out of time.

18 hours ago, JYW said:

Well, yes and no.

His issue is that the INIT B page is unavailable to him, because he starts the flight with the engines running. But that is a realistic representation of the FMS. INIT B concerns fuel-related pre-flight calculations, so if the engines are started and fuel begins to be burned, the INIT B page is inaccessible as it can no long compute everything that it needs to.

Again, this is real-world behaviour and the Airbus A320 works exactly the same.

This is a high-end addon, systems-wise, so I guess it's just a case that if you want to use the systems to their full breadth, starting the flight with the engines running is going to prevent some aspects of being able to do that.

If JF had built it so that INIT B was still available with the engines running, some people would have complained that this was not realistic 😉

Having said all of that, I'm not fully convinced that not populating the INIT B page will actually prevent Profile (VNAV) mode from working. I've only made 2 flights in this bird so will need to dig deeper. As I never start a flight with the engines running, I was able to populate INIT B, Profile mode worked fine, and I didn't see any issues.

Well in the PMDG 737's I would have to fill in the blanks in the Perf section of the FMS such as gross weight, cruising altitude, cost index, reserves, V1, V2, Vr in order to get a VNAV to work and I could do this with the engines running at start. That's why I suspect that I might need to fill in blanks on the next 2 pages of the INIT section of the F70/F100. Is there a default VNAV profile where I shouldn't have to enter performance characteristics and only my cruising altitude in the FMS for the autopilot follow standard VNAV profile for the F70/100 so I can start with engines running and use VNAV for the autopilot. You say that you are not convinced that the auto pilot will not follow VNAV from climb to descent without access to the next page of the INIT of the FMS to enter the data into the blanks like when I'm starting with the engines running? In other aircraft in FS2024 and X-Plane 12 I would have to add certain data besides cruising altitude for the VNAV to work, especially in the Perf section of the PMDG's. So there should be a standard VNAV profile in the F70/F100 that the autopilot can follow without needing to enter the data into 2nd page and following pages of the INIT?

Edited 4 minutes ago4 min by SpeedPilot