Farlis

I am having trouble when trying to setup a flight from BKPR (Pristina). Whether I try to import a company flightplan or enter the airportcode manually into the init page, the FMS stays blank and doesn't even let me start build a route. I can fly into Pristina just fine, but flying out of there is currently not possible due to this behaviour. With the default Navdata this is working.

No it's not. He has made dozens of reports about stuff that is buggy or a deviation from the behaviour of the real thing. Quite a valuable contribution, but I get that it can get tiresome if update after update the most glaring ones are still not fixed. On the other hand there have been improvements that were a direct reaction to his feedback. So not all is lost.

When entering a frequency into the standby box of COM 3, which I prefer to do to remember departure before actually being told by ATC I get a repeatable WASM crash. It happens everytime I do it.

I have not tested this myself, because I always start at the gate in turnaround state. I just assume that you should be able to request the flightplan on the secondary flightplan tab.

That goes for ALL airbus aircraft. With the engines running the flightplan download will populate the secondary Flightplan not the primary.

Then fly the thing manually, like every pilot does on landing and only do an autoland when conditions demand it. 😜

Can confirm this behaviour. This is new. Wasn't the case in the previous build.

I had this one as well, on a very long flight from Osaka to Munich across the date line. Didn't figure out how to fix it. Will try your approach if it comes up again.

With every post you make it solidifies my opinion more and more that this product was absolutely rushed to release. If you want PMDG prices you have to deliver PMDG quality in systems modeling. The amount of discrepancies and bugs you find give me the feeling that the release should have been postponed for at least 9 months.

I notice that the aircraft consumes way less fuel than the simbrief profile calculates. Just as an example of the current flight I'm doing: I'm just about to reach Janjo after about 5:50hrs of flight time and simbrief says I should have 16.4 tons of fuel left on board. However I currently have 20.5 tons left. That's 40% more than I should have. And I see this all the time. Just for reference: Fl400 Mach .85 gives me a FF of 2580 to 2600. Does this sound right to you? And if the consumption of the aircraft is correct, then why is the official simbrief profile so far off?

That one I noticed from release. The FBWA380 does it correctly, but I assumed because the A350 is so much lighter the differences in turnaround time are perhaps neglible. Seems as though my initial feeling that it is a big was correct, though.

I have an issue with the sound from the radions dropping out on the A300. I'm flying the PW freighter variant with the IDC enabled. When I use the radio the voices are transmited with intermittend dropouts. I tested this with both BeyondATC and SayIntentions and both come back all chopped up. It's so bad that I miss vital information when listening and only the text box of both programs can fill me in what the transmissions really said.

How about you being more specific? You mention stuff not being fixed but you don't say what isn't fixed despite it being said to be fixed in the changelog.

Personally I'd like them to include all the failures that trigger ECAM actions first and then think about adding service based failures instead of random ones.

In which position is the spoiler leve in the flightdeck? If it it is down you probably have a rogue axis binding somewhere. This happens to me as well when I switch through my presets. It's not an bug.

Correct Airbus logic. You need to push the button twice.

All of it.

You can't if you are not in the SU2 Beta. That's what the original poster forgot to mention. 😉

Because the engines use oil. Simple. That is not tied to failures it's simple wear and tear that you have to keep track of. I assume not being able to start them after having tried to start them without oil is a simulation of having damaged them.

They have Pablo on the team. He flies the A350 in real life. You should trust he knows what should be audible and what isn't. As aspected there has been ongoing discussion on what you hear of the flaps movement. A lot of armchair pilots with no experience sitting in the A350 flightdeck questioning whether you can really just hear the slats motor. Now the same about the hydraulic pump of the cargo doors.

Which is it? In the title you say SID in the post you say STAR.

Simply delete the keybindings. They are aircraft specific anyway. So if you don't need them, get rid of them on the A350.

I don't see this behaviour at all. Just round up what simbrief gives you. If your minimum takeoff fuel is 85660, take 85800. Make sure you enter all the correct values for alternate and reserve fuel as calculated in the OFP and don't forget to import the winds. If the flight computer still predicts you have not enough, be sure you have entered the planned stepclimbs. And don't expect a perfect calculation from the computer. The computational logic of the fuel page is always a bit overcautious while you are still on the ground. At least it is this way in the narrowbodies, like the A320.

Same problem again at FMEE. ILS is correctly autotuned in the Navpage. But LS shows no reception. Had to switch to the RNP (AR) approach to RW14Y instead. That one also comes with faulty Navdata by the way because it is programming the RNP12Y approach instead. That is a Navigraph problem though, I assume.

The same amount of time you wait on the 900. About 7-12 seconds.