Altair3285

Hi Kyle, thanks for the quick reply. Please correct me if I´m wrong: But this drag issue would also (at least partially) be an explanation for the to low fuel burn (my second post in this thread). If the plane has way to less drag at altitude, it needs less power to get to the desired speed hence less fuel consumption. Best Alex

One addition: in contrast to the EFOB and trip fuel calculation, the fuel burn actually is way less then what expected from simbrief, at least in 4x time acceleration (in the EFB). Roughly half way through the flight I burned already short of 15T less then I should, with a constant headwind too.

Wrong post. Sorry

Hi, as others wrote the issue seems resolved in SU7. However, I have to say for such a severe issue the suggestion "try reinstalling it" after one week is just poor. Of course we tried deinstalling, reinstalling, disabling, enabling. Restarting the sim, the console and so on. We weren't born yesterday: You can assume we try the obvious bits and pieces before posting in the forum.

Hi, I´m just doing a flight from LAX to ICN. Simbrief calculated a block fuel of 194T for a ETOW from 539T. The fuel burn seems more or less accurate / according to simbriefs calculation, so far at all waypoints the FOB was right where it should be. However, on the FUEL&LOAD Page, the aircraft calculates a Trip Fuel of 484 Tonns, which is almost twice as much as the A380 can hold in total. This gives me the DEST EFOB Ecam message. Since Korean Air does fly this route with the A380 and simbrief did calculate a managable flight plan, I wonder why the FMS has the Trip Fuel skyrocketing? Thanks.

Hey Inibuilds Team? Any update, reaction, answer whatsoever? Why are you completely silent? Not only in this thread but also to other users commentating the same issue. This is a dealbraking issue that needs to be addressed.

Unfortunately I can confirm that this is no solution (at least on Xbox): I tried uninstalling and reinstalling with the same effect of orange screens. Why is Inibuilds silent on this? This is not a small bug, annoying but bearable. This is a critical problem preventing us customers of using the product which we payed 80 Euros. The least they could do now is address the issue in the first place.

It seems to be a widespread issue among Xbox users. Which raises the question: If this is not a particular niche issue some unlucky ones are having why on gods green earth was this not detected in testing the update?

I have the same issue as well, I uninstalled / reinstalled the plane, restarted the sim etc. I highly doubt this has anything to do with the IRS. Metas AI has no clue what causes the WASM crash and it hallucinate anything which sounds like an answer but is just a bunch of probabilities piled together to a pile of nonsense

Hi Inibuilds, after the update to version 1.03 I have orange screen (WASM crashes) in every single try to start a flight in cold and dark (I tried multiple liveries at multiple airports). The plane is not usable at all right now. It went from okay performance (1.0) to bad performance (1.01 - much more memory induced black screens then before) to no performance at all. Honestly, how is this even possible to miss such a critical issue? Did you test the version not even once on a real Xbox before pushing out the update? This needs to be addressed and fixed ASAP.

Hey Kyle, my rolling cache is already at 64 GB. In addition I´m neither using real life traffic nor AI traffic nor any ground aircraft or vehicles. Its basically just the aircraft, the livery and the airport. Also, I´m using the performance mode. Yet, again, in at least 80% of flights the result is a memory induced black screen scenario before even taking off. As I said: Once it does work, it really is a great plane, and I see a lot of potential in it once stability increases (and performance on ground could be somewhat better too). Best Alex

Hey Inibuilds, the A380 is a great plane. But on Xbox it is barely usable in its current state. On handcrafted airport - not even third party, the standards ones from Asobo - I´m getting black screens 80 percent of the time. And since most A380 destinations have handcrafted airports at least at one end (Dubai, London, Paris, Munich, Sydney, LA, San Francisco, New York JFK and so on), this is a huge deal. What is the roadmap of increasing stability and performance? Thanks and have a nice weekend Alex

It´s hard to predict when it happens and when it does not. Additionally, I usually fly from the cockpit (this is why I can not tell if it was present in the release version): If I happen to see it again, I will record a short tape :)

Hi, when using the time compression in the EFB, the wings flap up and down as if it were a birds wings resulting in a weird zigzag pattern of contrails. I do not know if this issue was there prior to V1.01. In 1x gthis "flapping" is not there. Can you have a look at it? Thanks.

I can confirm that time does indeed not jump ahead correctly. I tried a flight (QFA7) from Sydney to Dallas. It should land around 1740 UTC (around 1240 (p.m) local time). But after jumping ahead to shortly before TOD I arrived in the middle of night. This is on Xbox X