Leaderboard

@Cameron That was it ! I confused it with the 1.31 installer apparently. Running like a charm now - wonderful aircraft by the way ! Thank you guys and kind regards, vlartisan

Hi jojo, thanks for the report...I thought we had fixed this, maybe it crept back in with exporting the cockpit object. Funny enough the yellow bug starts out at the first line, but then you can never push it back all the way up. I also want the checklist to be "flush" against the yoke - we only flipped it up to read it, then would pop it back in. It bothers me that it is out all the time :-) Cheers, Jan

Hallo Jan, updated to AviTab-0.3.21 and it is there again,many thanks Viele Grüße, Jürgen

@Litjan the error you experienced was a component mismatch error, meaning the download file size was wrong. The above shots show a file not found error, which can only be one of two things: 1. Running an older installer than what's on the server. For every update you need to re-download the latest installer from your account. This is the most likely issue right now. 2. Firewall The error means it is not even finding a file to download on the server. You should double check that the file you're running is in fact the 1.32 installer.

Perfect explanation. No idea why I was using it. Will test it later and see if that relates to my C of G question also.

Hi Iain, this explained it. The PLAN line "overwrites" the measure fuel quantity for planning purpose. Imagine you sit at the gate and wonder if you can make an altitude restriction on the SID or how much fuel you would have when you arrive at the destination... you put in your ZFW, but the fuel truck did not refuel the aircraft, so the GW calculated by the FMS (ZFW + measured fuel quantity) is not what you will actually have when you take off (too light). Another use for this field is entering the actual fuel value when the fuel summation unit messes up and the measured fuel quantity in the FMS is wrong. It would lead to all sorts of wrong calculations, so you can overwrite (hardlock) the value here. So you can enter this PLAN FUEL and this will effectively overwrite your "measured fuel". Until you eraze it. Cheers, Jan

Having done far too many 2000nm+ flights in this aircraft, I can also say I have never seen a drift of the line in LNAV, so I doubt it's to do with the route length.

All you had to do was search the word "Catalina" to get results.

The 2D rendering pipeline in X-Plane 11.50b15 was broken for us, we have worked with LR on a fix that should be rolled out within the next few days.

I enjoy this airport, fun place to land, at night and during day light. Usually quite breezy. This flight was a cargo flight from East Midlands. https://youtu.be/OoUdlkRlJpE

Before this turns into another FS vs XP thread, I'll say we've got the FS2020 SDK, and we know what is going into it. And that's where our information will stop. All I want to say about this is that FS2020 is a flight sim. X-Plane is a flight sim. Both have lived and grown alongside each other for the better part of 2-3 decades. MSFS development has stopped once or twice in those 20-30 years, but it has never had an effect on X-Plane to the extent of "Laminar will go out of business." Use whatever you want to use. It's up to Laminar and the X-Plane developers to keep people interested in X-Plane to the point where the community will show enough interest in it to keep using it. We all have our own, individual preferences. And rightly so. Let the products speak for themselves.