Farlis

You are on a roll again. I admire your tireless effort to document everything that IniBuilds gets wrong in their Airbus fleet. However given the snails pace at which they correct them and carry them over from product to product, I also admire that you still hold out the expectation that they will fix all of these.

And flying long haul alone and letting the aircraft unsupervised isn't?

Push the disconnect button on the sidestick twice.

Funny that the original poster did miss this, consindering MSF24 has been out a year and it works exactly the same in the A330 that came with it.

Since when? Rawdata approaches are only flown when all else fails. As long as you have a working FMC you fly VOR and NDB approaches through the FMC and not the Needles from the RAD/NAV page.

Any Aircraft that comes with an EFB integrated Navdata Solution, like the A350, PMDG 777, Aeorosoft CRJ and the A340 is best updated through the EFB itself and not through the Hub.

Descend management is your job as a pilot. You can't leave it to the automation alone. A330 and A340 are very slippery aircraft. You can't descend and slow down at the same time. So extend the speedbrakes, that's what they are there for.

How about being less sarcastic? Because if you are going to be like is, all I can say is: What do you need a checklist for? Just download the generic Airbus one, they are all the same.

Ah. Maybe that update did install itself in the background without me noticing and that's why the MCDU display ceased to function. Edit: Yup, that's the reason. EFB says 1.02. installed. So I assume it is up to Winwing to update SimappPro to be compatible again.

I just bought the A340, 4 days ago. I'm quite sure there was no update since then. 😉

The odd thing is that it does not work reliably. Sometimes the display comes on right when you connect SimAppPro sometimes it doesn't. And during my current flight even pushing the "Restore Default Configuration" button does not help. It did help during the last flight I had with the A340, today it doesn't and the display remains blank. Strange.

He mentions simming on XBox. I guess there have been no updates since the XBox version got released and he missed the fact that the PC version had about 12 Updates since release and all of them ended up in the XBox version.

Why not? The damage and crash detection within flightsim has always been spurious and is best set to off in all cases. Just as an example of how spurious it is, when I did a bank angle protection test with the A350 and started to pull up the nose to prevent losing altitute my sim reset, telling me that I had just overstressed the aircraft. I very much doubt that a simple 67° bank will rip the wings off the A350 in real life. 😉

That's Singapore's ULR layout. Are you sure you are choosing the correct variant in the menu and not accidently the ULR version?

Sure what do I know? You keep looking at videos, I'll be listening to A340 pilots who explained the technique. And then waste your time asking for a sofware fix instead of fixing your faulty landing technique.

That is because you are landing her wrong. You have to make a complete tripple touchdown before activating the reversers. First the back wheels, then the front wheels then the nosegear and after that you activate the reversersers, not before. If you do activate them after the first touch down with the nose gear still in the air reversers will activate, the spoilers deploy, destroy all lift and the nose gear will slam down.

That's what happens when you share code that already has incorrect logic across your add ons. You carry over the same bugs to the next product...

And the saga continues...

That's GSX. Check your profile for Heathrow.

Now I know what happened to my PMDG777 in VR. I had the same issue in VR and had no clue what was going on. Now I see this thread and all makes sense.

It's not realistic to fly long haul over 8 hours alone without a shift change. So flying sped up is the best option.

Cannot confirm. Issue is gone all works as it should now.

My experience is that it OVERestimates the fuel burn. I usually take up about 300kg more than the OFP states, which is good practice, but in the A350 that is not necessary because I end up with more than 1000kg than estimated at my destination. At least it used to be this way, maybe the updated profiles calculate the fuel burn mor precicesly.

I have the same issue. What is especially odd that after just updating to the newest version and clearing the WASM folder it worked on my first flight. But the 2nd time I fired up simulator and aircraft it is broken again and won't print F-Plan INIT and T.O. Data when it should.

Apart from the obvious typo I can confirm this behavior. The newest patch broke the Terrain Display on the FO side. Don't you love it when something that fixes one thing breaks another at the same time?