CJ1045

Perhaps the mod that puts real liveries on ai planes. Just a guess as dont use it but the custom liveries broke with the main update.

Took off from Schipol and landed at Heathrow, both hand modelled airports and massive, no issues

OK, so I have no problems with flying the A320 and spend most of the flight on autopilot. With the A320 I set the managed altitude to 12,000ft, say, and the ascent rate to 2000ft/min and it climbs to that altitude fine. I normally have managed speed selected so it climbs at 250knots up to 10,000ft and then over 300knots after that all good. So when I then want to go to cruise at 18,000ft from a stable 12,000ft then I change the managed altitude to 18,000 an reapply an ascent rate of 2000ft and all is fine. Now with the 787 the situation seems different. You don't seem to be able to select managed speed (inop) but it is not too difficult to set a speed, fine. I also had no problem getting to 12,000ft similarly to the A320. However, at that altitude if I wanted to change to 18,000 then I select 18,000 as the managed altitude and 2000ft/min as climb rate BUT NOTHING HAPPENS. If I BRIEFLY turn on vnav then the plane starts to climb at a massive rate, I turn off VNAV but then I can engage managed altitude and climb rate again and the plane then ascends at the managed rates to the manged altitude. But WHY?? The same is true in reverse. I seem to need an on/off of VNAV for the managed descent to kick in. I am missing something here? Thanks CJ

Let us hope it works well as I too am currently amazed how good things are. FBW have fixed the A320 mod and it is lovely to fly and I have just landed at Heathrow at night. Here is the approach, the lighting is stunning:

Being a bit lazy - is the 747 reversed livery on one side of the plane cured yet? CJ

When you posted this the Flybywire mod was back up and running near perfectly - you just had to download the dev release which I think is what most people are running anyway as it is so stable. CJ

My liveries are working fine. Before loading any patch I always start with an empty Community folder and then add back in content one by one and check all is OK. If you are going to use non-standard items, that is, Community folder content, then you should expect to have to do this. Not for items in the Marketplace though. EDIT - take that back. Liveries don't crash sim and can be selected but don't appear on the plane, default livery still there CJ

From the patch release notes: WORLD Motion blur has been added New temporal anti-aliasing (TAA) has been implemented The temporal upsampling has been fixed (when TAA is active with the render scale below 100%) Night lighting has been improved Water night reflections have been added Huge hole in Brazil has been fixed

Because the game now uses TAA which it didn't before

Use the installer and choose the dev version - scroll down on the link below until you see the Installer download and use that. https://github.com/flybywiresim/a32nx

Never had Travel To work correctly on any plane - I always just change sim speed

Moria15 is referring to the video of the DEVs - he did not understand what you meant.

Wrong DEV update - it is the weekly Thursday update they were talking about.

There are other threads on here that explain the status - pretty much all fixed in the dev master build CJ

I am loving the update. Only flown during daytime so far so cannot comment on night flight. A definite stepup in the graphics. Seem to be seeing more trees when approaching London than before. Also seemed to be smoother as I approached Heathrow. I have PremDeluxe version so Heathrow is enhanced so did cause poor frame rates before but seems better now. I am running on high which is a stretch foe my gpu but I prefer the visuals over the smoothness.

Current status from the Known Issues issues section for the new patch on the Flybywire discord: Issues with the current update: - MCDU not working [Fixed, but not merged] - PFD not working [Fixed, but not merged] - upper ECAM [Fixed, but not merged] - switches animation missing (same with the default A320) - Radio Panel [Fixed, but not merged] - ADIRS [Fixed, but not merged] - APU [Fixed, but not merged] - Cannot engage selected heading (AP issues) - MSFS crashes to desktop at 85% (not mod related)

The Garmin database in RXP is sourced from Jeppesen as is the Navigraph database that we use with MSFS. If you use the Navigraph data load into MSFS then you will be using data sourced from Jeppesen in the World Map and all the plane NAV systems in MSFS. This applies to all the default plane NAV systems and the current modded systems.

To balance things out a bit my MS Store Prem Deluxe Edition is working perfectly. Going add a few add-ons now. CJ

Yes, me too. no problems here. CJ

But it is not

For someone that has posted on here a lot you don't seem to know much about the way sims work, Here is MSFS World Map with the default 172 selected and no mods for it: and here is the G1000 in that 172 sitting on the end of the runway before take-off: The approaches that can be selected are NOTHING TO DO WITH THE NAV COMPUTER you use. They are entirely determined by the NAV DATA that is used by the sim. I have to confess what you are missing entirely is that both CWBurnett and I were both using Navigraph Airac 2011 nav data in MSFS. 😄 CJ

Or as we say in England, maths CJ

Google: Imaginesim: Not looking too bad at all. CJ

I pretty much exclusively use the A320 in game at the moment with the Navigraph beta install. I don't have the issue you describe. What do you mean by 'when I disable the Navigraph data cycle'. There is not an option to disable it - either you uninstall it with the beta app or it is installed. Further, have you checked the Navigraph data is installed using the checks described in the beta forum for release 14? CJ