All Activity

I also think the simbrief file is not the problem at all. The changes in the calculations are happening during the flight in the fms. See my last posts above.

Hi, Thank you for the fix, yes I tried the “Check AIRAC cycle” and updating it but it just stuck at the “Preparing” part for so long.

Noticed a bug with the A380 cabin lighting. Upon initial load, the lighting doesn't work. The tablet says the lighting is set to Deep Blue and at 100% brightness, but it remains dark. It is only when you click the colour again, does it begin to work. This is also the same when launching at a gate, it says Deep Blue but you need to cycle again. Looks like on first load the lighting or shaders are not working properly. Videos attached demonstrating the issue. https://drive.google.com/file/d/12b9eyytiUZCUuVdH8c16AqZs1MHPYOgT/view?usp=sharing https://drive.google.com/file/d/1I_Myq7xkmxbEIaXz0h8AfYAv2dHzfvvb/view?usp=sharing

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

A380, move it and it will become like this

I don't want to create a new thread about this, but here is one suggestion more: Do NOT make the TAXI button INOP as it is in the A380 now. Leave it just the way it works in the A350 v1. This is because the freeware Taxi Cam mod is a gamechanger for immersive taxiing in the A350. In the A380 you have to use a custom keybind to enable the Taxi Cam whereas in the A350 it can be engaged with the TAXI button just like in the real aircraft. Thanks!

When you have the correct RNP AR approach selected in the FMS, the APP-DES | NAV mode arms when APPR button is pressed.

Same behaviour... Unloaded nearly everything that I didn't need for that flight. I also reinstalled the plane and deleted WASM folder. I also don't see a reason why a random scenery which isn't even loaded all the time would cause a performance degradation on a single airplane. Here is after takeoff and before landing comparison again with the Main Thread loaded up.

Yes, I did the update. And you're Correct. The SU7 did fix it. Thank you, and Happy Flying... While I have your attention on this matter😁😇😊, any news from your team on scenery development for FYWH(Hosea Kutako International Airport)

Encountered this whilst flying the EA Cabin variant after TOD. See attached. But did not encountered this issue on the RR variant

Hi inibuilds team, do you have any plan to implement two or three independent fmc on airbus aircraft in future update?

Same problem in V1.0.4

I have noticed this too, as well as the effect when trying to scroll the map in this video 20261015_130231.mp4

I just realized one thing, the ground effect dynamics on Flaps 3 causing the airplane overshooting the Touchdown Zone so much. Can you also check about this and make adjustment, @iniKyle ? Many Thanks, Cheers

AND I was not flying the FMC route. I used SayIntentions ATC which gave me HDG vectors. Even with heading mode, the aircraft captured and followed the glide slope correctly, but the PFD still did not show the glide slope diamond.

Also, when I uninstall/remove the scenery, everything works fine again.

Thank you very much Kyle as always for your prompt reply. Here is a video, sorry for the background noise and poor quality. You will notice that as I click the + sign to zoom, it takes so long to zoom and adjust. Hope it helps. Reza img-5937_lYHWLqjP.mp4

Hi team, Thanks for checking. I've double-checked on my end and confirmed that I'm on the latest version of the scenery. I also re-launched the game to test it, but the same issue is still occurring. Attached is a screenshot showing what it looks like on Runway 07L. Thanks for looking into this!

Hello, After updating to A380 v1.0.3 on MSFS2024 SU7, I noticed an issue with the ILS display. When flying into KDFW runway 18R, the aircraft correctly follows the glide slope with AP1+AP2 engaged, and the system shows LAND 3 DUAL BARO. However, the glide slope diamond does not appear on the PFD, even though the aircraft is descending along the correct path. Before the 1.0.3 update, the glide slope indicator displayed normally. Now, only the backup instruments show the glide slope, while the PFD remains blank. Steps I followed: - NAV1/NAV2 tuned to 110.95, course 183° - LS button pressed - AP1 + AP2 engaged - Aircraft captures LOC and follows glide slope correctly Could you please confirm if this is a known issue, or if there is a workaround? Thank you!

No worries, Kyle! Thanks for the reply. Just one last question: as far as you know, is there any further work or testing needed from the iniBuilds team for the A380 PS5 version, or is everything on your side completed now? Thanks again!🥲

Hi, Yes, I’ve had the same problem since updating to version 1.04. Switching to a different card and zooming is extremely slow, and the flight path tracking doesn’t work either when you click on the little aeroplane icon in the top right-hand corner. It just jerks about! If you look closely, you can see that the aeroplane is situated in a small square below the map.

Thanks. Will log for the team to investigate!

I'm not entirely sure. I usually don't get those type of updates!

Thanks. I will forward this thread to the team for further clarification!

Hi Kyle! Thanks for the previous updates. Since the A380 PS5 build has been submitted to Microsoft/Asobo, do you know if it has passed final validation yet, or is it still waiting for approval? I understand you can’t provide a release date, but knowing which stage it’s at would be really helpful. Thanks again!