All Activity

A quick workaround for those struggling with this. I have found I can fix the issue by selecting the ON APU panel state in the EFB. Starting the APU from the regular cold and dark default setting doesn't light the performance screen. Although, I powered down the aircraft after using the APU panel state to see if the performance screenl would work again. I found the APU will not start on battery power and needed the GPU to be connected and on the bus before the APU would restart... So concisely, the screen is dead unless using the APU panel state in the EFB. The APU will not restart after shutdown in this mode unless the GPU is connected and providing power, despite batteries being on. EDIT: On GPU panel state also fixes the performance screen, although not if you do this manually from the cold and dark boot. Its looking like a variable isn't being set somewhere, that gets forced to on when loading a panel state from the EFB but remains off otherwise for the performance screen. Cold and Dark panel state load from the EFB leaves the performance screen dead and unpowered when using EXT or APU power to boot the aircraft. Jane

same here

Indeed. I even did not ask for the promised main displays as used by the UPS freighters. It is sad, because the A300 was the first INI Aircraft.....

Seeing exactly the same issue here. The EFB version number has also reverted to 1.0.1 (I was at patch 2) All was fine on my last flight earlier in the week. This is streaming via the Microsoft store, EDIT: Deleting the WASM folder forced a reinstall to 1.0.3 however, the performance screen is still dead. Jane

How did you resolve this, as I am having the same issue?

I always meet this problem when I spawn on a runway but not on apron.

The official GSX profile has no marshallers at the cargo ramps. Tested with Ramp 615.

I’m pretty sure there’s no responses from the team as they’re at FsimUK. No other threads from anywhere in the forum have been replied to since Thursday. We just have to be patient I guess, hopefully we will get a response today or tomorrow.

It’s been happening to me, its just there! Nothing can be done, I’ve done multiple disabling and re enabling, since 1.0.3 came up, I can’t even get the WASM crash report up. And this is where it’s needed

Has anyone else had issues with a low initial altitude followed by a large STEP climb? On a flight out of EGLL, with an initial altitude of FL230 followed by a STEP to FL350 after DVR. The aircraft climbed OK to FL230 but then ignored the remainder of the STEPs. I retried the flight with an initial altitude of FL330 and it appears to be climbing ok. EGLL/27L N0419F230 DET2G DET L6 DVR/N0489F350 UL9 KONAN UL607 KOK DCT MATUG DCT BOMBI DCT TENLO DCT DEXIT DCT BEGLA DCT DEGET DCT SOKRU/N0490F370 DCT LUGEB DCT UDROS UM859 KARDE UL851 TBN UM11 REBLO P130 MAMED B449 RANAH/N0484F390 L750 MERUN G452 LKN R460 CEA L507 IGONI DCT WILLA WILA2C VTBS/19 FL STEPS EGLL/0230/DVR/0350/SOKRU/0370/RANAH/0390

Hi , currently i cant calculate the aircraft take-off performance as the screen is dead, note this was working ok until a couple of days ago.

Hi Kyle Many thanks for the great update. After 1.03 the issue seems to be sort of resolved but still there seems to be some weird minor issues. Sometimes still the PA does not play, or of I switch to exterior view while the announcement is going on, I wont hear it when I switch back to cockpit view. Just wanted to share. Otherwise, I must say this is an amazing aircraft. Thanks, Reza

I think the A-380 is a fantastic aircraft and has a lot of potential the further refined it gets. I am having issues with the brakes not releasing. I own the Thrustmaster Rudder Pedals. I have verified there are not conflicting binding and have tried everything in the control settings to find a fix and have loaded up my IniBuilds a-350 to see what rudder profile it uses that works and then used that profile in the A-380 but it does not work. I have discovered that when I brake with the R&L rudder pedals the A-380 will move forward but once I release the 930 stops. I have gone into the settings and reverse the axis and when I do that the 380 wont move with released brakes. I have also created a new profile What am I doing wrong? I spent most of my day trying to troubleshoot this with no luck. I am verifying that the Parking Brake is off. Help! This aircraft is not able to taxi to the runway. BTV, How do we get this to park on the BTV setting on the AutoBrk selector knob. My knob only parks on Disarm and LOW never on BTV. Thanks in advance for whatever advise/direction you can point me to.

The A380 (without brake fans) is notorious for hot brakes during ground operations. Very common to get the hot brakes ECAM after engine shut down. For departure Limit brake applications as much as possible and plan your taxi. A 20kts-10kts technique is often used at heavy weights. The Ini A380 is however very conservative in terms of brake temps compared to the real aircraft. 300 degree C is the limit for takeoff. Pushing from the gate with temps in access of 150C will most likely result in Hot Brakes ECAM during taxi, unless a very short taxi. If the Hot Brakes ECAM should arise after takeoff thrust is set, it is acceptable to continue the takeoff, but leave the gear down until temps are around 260-270 degrees before raising the gear due to residual heat build up.

The trailer....the screenshots, absolutely insane! I don't know how to thank you guys enough! Hopefully we get the Global before GTA 6 😉

For at least a year, some livery images in the iniBuilds Manager have failed to load, while others look identical. It’s difficult to tell them apart without searching for the registration number on Google. It would be helpful to have clearer previewa that highlight the differences between liveries, or a short description next to each image. Improving these previews would make choosing the right livery much easier. As an example I will add the lufthansa staralliance versions, where you see how they look exactly the same. Thankyou for your time!

When flying through convective activity the green track is same color as the weather depiction. Result is loss of visual FMS track routing through the convective activity. Perhaps related to the display brightness setting.

With the October dev update specifically mentioning LNAV being updated on the A350, I would respectfully request that that effort can also be copied to the A340. Unfortunately, lateral navigation is not a strong side of the A340. At the start of this year I created a detailed bug report with multiple specific and repeatable cases where the LNAV completely failed. Unfortunately, this has not been improved in any of the updates since and it has been many months since the last update. With the effort being made for the A350, I hope this side of the A340 will also soon improve!

Where is this feature located? I am getting hot brakes during taxi out and in.

With airports like Addis Ababa and Nairobi, Inibuilds has an impressive track record of doing honor to the hidden gem airports that are often overlooked. I’ve recently flown in to CGK and it struck me what a special airport it is. It’s slightly chaotic, but relaxed at the same time and the international terminal is beautiful. In MSFS, an Inibuilds-level scenery of this airport would open up a huge array of new sectors for simmers. Not only internationally (CGK-SIN is one of the busiest routes in the world), but also the very vast domestic Indonesian network would get the gateway it deserves. In my opinion, a worthy candidate to make its way on to the airport planning. What are your thoughts?

Any news at all on the future of the A340?

Different System, but same issue as OP on departures: 9900X3D 7900XTX 64GB RAM

Small minor detailed I just noticed. When CPDLC connection established and/or ADS-C connection indicated in The Mailbox, The FMS, ATC COM box is not indicating the connected ADS-C Station. Picture for correct illustration. The Mailbox connected ADS-C ground Station should be listed under ADS-C Connected Ground Stations on the FMS Com page. Minor detail.

Yep, yet another shiny new plane has been announced, so older planes like the A300 get pushed further down the list while they still have unresolved issues (add the terrible ground handling to the list above). Not happy.