Farlis

The steps he described in this thread clearly point that this is not a matter of where he puts the aircraft. Something in the sim, I suspect a setting in the Developer Mode, is preventing the compilation of the WASM data that is necessary to run this aircraft. If his initial load after installation is done after 30 seconds than something went wrong. It should take at least 15 minutes the first time.

There are no refunds for digital products. Some companies offer them regardless, Inibuilds does not. And on top of that a refund policy for a faulty products only applies if a product is really faulty. In this case it is not, it is the system of the end user that is faulty because it is not compiling the software as it should.

Depending on your system up to 20 Minutes.

No it isn't. Actually I just tried it again in the A350 and it is now working. It was probably a bug in the Navigraph Data and since there has been a new Airac Cycle since my report it seems to have been fixed since then.

Yeah that's one of those things: I noticed these issues back in MS2020 with the rolling cache and therefore never used it. When they announced that the rolling cache would be mandatory for MS2024 I foolishly assumed they had ironed out those issues because you now can't escape using it. Turns out they did not. So be sure to do this regularly, as counterintuitive as it may seem.

This one I'm not so sure of Michel. Visual differences can often come down to different software suites in the aircraft modeled. I would be hard pressed to believe that the artists at IniBuilds would not be able to draw a dashed line when their reference material tells them to do so. So I assume that the aircraft they based that appearance on is using a different version of the software and is drawing these differently than the ones you work on.

In the OIN under 3rd Party. Du schaust auf die Option für den Kartenprovider nicht auf die für die Navigationsdatenbank.

This is a complete misunderstanding. In the A350 you can chose which data you want to use. Default or Navigraph. Even default navdata gets their monthly airac update, albeit sometimes they can be a week or two behind in the update.

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.