All Activity

I guess so, but I don't know it is coming from Aerosoft or A380 itself, I hope there's fix soon enough from Aerosoft or IniBuilds regarding this. Cheers

Thanks - that worked! But how do I get Blender to paint only on a selected tile?

See the Down Arrow showing the FCU Target Altitude at the RUNNN point, it strict between FL170 to FL140. That is why the FL160 on Altimeter doesn't showing Magenta because FMCS calculates that you will reach FL160 approaching RUNNN Point which WILL NOT PASSED BEFORE FL170 or AFTER FL140. Unless you have changed one of the constrain after RUNNN (like SYMON or IRNMN) to AT FL165 OR ABOVE, then you will have Magenta on Altimeter. Cheers HaveASafeFlight!

Does anyone read before posting? Kyle already acknowldeged the issues half a day ago and that a fix is in the works. So there is no point in further reporting that your terrain radar is not working. They know it is not working.

Btw no weather radar neither on my side. No terrain and no WX.

I get that it’s probably for LOD purposes but the tail keeps on popping in when you go to external view and the same happens for the cockpit. You come back to the cockpit and it has warning lights on and the tray pops in too. It is an eyesore and the cockpit lights are the worst. Please check if it can be fixed. 🫡🙏

Just starting flight #2 and it is reproducible. Engines not started, external power connected, APU starting, select ENG page and the pump goes off - turn it back on, select any other page, same outcome, the pump goes off. EDIT: Even selecting T/O CONFIG turns the pump off, basically any button on that panel will turn the pump off. Mouse clicks on any other location seem to work fine.

I was flying at cruise, FL400, when unexpectedly the ECAM CAB PRESS EXCESS CAB ALT alert was triggered. I’m not exactly sure what caused the cabin altitude warning, but when I switched to the external view, I noticed two openings/holes in the fuselage where the landing gear could be seen. I’ve attached screenshots showing the ECAM warning and the exterior model.

Like the title states the "100 above" and "minimum" callout overlap with GPWS altitude callouts. In the irl. aircraft this is obviously not the case, with the callouts being played in close sequence if applicable. Sadly this is a bug that was already present (and reported) on the A350 as well as other ini Airbus aircraft and still has found its way onto the A380.

same issue here too

I can confirm,i have the same issue as well but i can't upload the image for some reason there is a mod where the texture are very chart but it doesnt use the navigraph https://fr.flightsim.to/addon/115176/free-oans-anf-btv-for-msfs2020-and-msfs2024

Hello, when in managed mode ; DES, shouldnt the FL160 be in the magenta color as it's a constraint (and same thing for the ALT in the FMA?) ? i think i notice the same thing during climb in managed mode

HEllo, i've noticed that i always landed below the planned Simbrief flight plan EFOB even with fuel offset of +10% I dont know if the Ini 380 consume for fuel than irl or if the simbref profile is not accurate seems that i need to add an offset of +20%

Hello, i've noticed since the A350 that the BTV apply too much pressure on the Brakes as it will reach 20kt way before the planned exit in this case you can see that i selected the Exit before the Dry marker : V exit at KLAX 24R and it still managed to reach below 20kt before the exit, i had to take over. In a AF A350 video, the FO is quite new on the A350 and the captain explain a bit about the BTV and to trust it as it will make sure to suddenly Apply a bit more brake pressure in order to exit around 20kt on the video below, you can see there are able to vacate with still the BTV on around 20kt and the plane was earlier still around 40kt just before vacating Currently, if you keep the BTV on, it will stop on the runway hundred of feets before being abeam of the planned exit quite frustrating currently as the BTV is abit useless especially on vatsim where you may need to vacate quick when there is a lot of traffic and always ended up to manual brake because i know it will stop me way too far away from the planned exit

I doubt it's a keybind as I am only using mouse clicks, not keys or buttons. I'll see how it goes with flight number 2...

This is resolved. The issue was the arrival. I tried a different approach and it worked perfectly.

Okay, I loaded a new flight directly on the runway, and I'm not getting ground spoilers. Here's my control settings, the cockpit spoilers and flap levers positions, and what I'm getting on the wing. For what it's worth, when I tried to install the plane it gave an error and I had to restart msfs to get it to install. Also when I first installed the plane I hadn't seen the"first launch" procedure on this forum, so once I saw it I uninstalled the plane, re downloaded it, then had to restart msfs because of the same error again to install it, then followed the procedure correctly.

Oh, and here's another clue: I went and listened to all the Airbus warning sounds, and from what I can tell so far, the buzzer scream I heard is most likely part of the autopilot error warning — but the sound wasn't complete. If that's the case, then in a way it does match what we ran into: AP1 failure. I'm not sure if that's where the problem lies, or whether the A380 even simulated this particular warning sound when it was made. But I hope it can serve as a useful clue. Thank you very much.

You won't get individual tiles in the save menu. Saving the Fuse_Main image will automatically create files for each tile, numbered in line with the UDIM. So you'd get: Fuse_Main_1001.PNG Fuse_Main_1002.PNG Fuse_Main_1003.PNG and so on. Just recreated it do demonstrate:

No confirmation yet, but stay tuned to our usual social channels for more info! Thanks for your patience!

I've been having the same issue, mostly at larger airports. Has happened to me at both Inbuilds JFK and LAX on multiple occasions. All in game graphic settings are set to low, with both ground air traffic disabled. It doesn't happen consistently, but when it does happen it becomes much more frequent. Restarting or starring a different flight doesn't help. Only way I've found to reduce the occurrence is to completely restart the Xbox. I did LAX-LHR last night and had a memory error while in walk around mode at LAX. After restarting the consol and the flight, I felt like I had to be extremely careful while taxiing or panning the camera because I was afraid any rapid movements during an instance of lag would cause a memory issue. I turned off RAAS and didn't have any charts up on the EFB and felt like that helped a little.

Hi all! Please delete this or ignore me if I violate any rules with my question. But, in the MSFS2024 dev stream, it was mentioned that they wish to release the A380 on PS5 sometime next week. While I understand this might be subject to delay, is there any way we can get a confirmation that it’s at least coming to the PS5? Cheers, Thomas

Hi, This has been logged by the team and fixed in v1.0.1 Thanks!

Hello, Please flag this as it is urgent. The thrust reversers do not work in their purpose to decelerate the aircraft. Users would not notice this as usually autobrake, BTV, brakes with aerodynamic braking would help slow it down on normal landing. I tested it and asked others to test. If you try to activate reversers, sounds and animations work but it does nothing to the plane in idle or max reverse. Thanks in advance.

Hi Dave, Thanks for the detailed report. I'll check with the team and report back. Thanks for your patience.