All Activity

This is VNAV Management Issue from A320 to A380, mate. I forgot to tell you this, @iniKyle . But A380 have issue if there's 2 overlapping SPEED CONSTRAIN. Like the VNAV capability unable to prioritize which one to be use. It is chaos whenever you are descending to any airports, having STAR wtih turn or straight-in. The Energy Management is worst especially below 10,000 feet during descend. Usually there's 3 SPEED CONSTRAINT on VNAV: STANDARD Speed Limit Constraint, noticable by 250kt/10,000feet, PUBLISHED ARRIVAL Speed Constrain, usually there's speed limit for Departure and Arrival Published Speed Limit at specific waypoint, SELECTED Speed Constrain, this is inserted by pilot for flight management planning, I notice that A380 ONLY FOLLOWING Speed Limit number 1, whenever there's number 2 and/or number 3, the VNAV failed to do as programmed. And if there's speed constrain on specific W/P, the VNAV is ALWAYS targeting the speed constrain by the NEXT W/P not on the target W/P. Like the picture above, for context: DB515 having speed 210 knots, but somehow the VNAV targeting to reach 210 knot AT DB514 or DB513. and DB508 having speed 185 knot, VNAV will target specified speed either on DB507 or DB506, or even worst sometimes at DB505, WITHOUT DECEL P/WP between GIRGO to RIDEV. This is ALWAYS happening whenever you are either having turn (most cases) and/or during straight-in STAR. Like, VNAV prioritize ONLY the path without calculating the pre-selected speed requirement (somehow, only the speed 250/10000 is prioritized more than the path or any selected speed). Based on the infrastructure of FMCGS, the path calculated with Continuous Descend Operation (CDO), descend with the lowest energy available (Idle Descend) with calculating 4 factors: ANY CONSTRAIN (Speed and/or Altitude Constrain) inserted whether from arrival procedures speed limit or selected speed limit target, (yes, it calculates BOTH constrain) Idle Power Descend possible (the lowest energy available, WITHOUT having to extend speedbrake), Pre-selected Wind Condition (or zero-wind if the wind from simbrief NOT inserted), and CDO finished at IAF. I know this is loooonnngggg structure modification. But please, make a correction about this. Somehow, PMDG and TFDi having it better about this (I don't mean to compare, but this is only happens on IniBuilds except for A300/A310). And the most funniest things, A350 Prioritizing Speed Constraint but A380 Prioritizing Altitude Constrain (until you hit speed limit 250/FL100) 😆 I hope this can be corrected for the future upcoming development. Cheers!

Hello again, I've now completed the P06 fuel factor flight here: https://galerie.klusik.cz/presentation=1ec2bc09 As I mentioned before here: https://forum.inibuilds.com/topic/41833-127-fuel-flow-increased-significantly/#findComment-101842 Raw data: TNCM LKPR A350 1.2.7 FUEL FACTOR P06.zip OFP attached for comparsion. I let ChatGPT to compare the data and attach the PDF as well. It looks like the P06 is about right, so far. I know it could be changed and probably (my guess) is they (inibuilds) tuned it to SU7 and with SU7.1 patch it just went against itself, but this is must my guess :-) With P06 my divergence off plan is about 0,2 %, which is nice, I guess :-P Planned trip fuel was 53 970 kg and real was 53 866 kg :-) TNCM LKPR simbrief-ofp.pdf

Delete any MOD. As for me i uninstall WXR and VSD and everything started well

I am using the Library and still don't get the uninstall option ????

Hello iniBuilds team, I have just updated my iniBuilds A350 to the latest version 1.2.7, and I'm experiencing an issue where "RWY NAV" remains displayed in blue on the PFD, even when the aircraft is already airborne and climbing. As shown in the attached screenshot: NAV mode is active (green). RWY NAV remains armed (blue). The aircraft is climbing normally in CLB mode. The aircraft is following the programmed flight plan correctly. As far as I understand, RWY NAV should disappear after takeoff, but it remains displayed throughout the flight. This issue is still present after updating to version 1.2.7. Is this a known bug, or is there something I might be missing in the aircraft setup? Is there any workaround or fix planned for an upcoming update? Thank you for your help!

A380 v1.0.5 – Severe Runway Stuttering | RTX 4090 | MSFS 2024 Hi iniBuilds Team, I would like to add my experience regarding the severe stuttering affecting the A380 in MSFS 2024. System: NVIDIA RTX 4090 Intel Core i9 high-end KS processor NVIDIA App installed A380 v1.0.5, previously experienced on v1.0.4 Aircraft fully installed locally, not streamed Problem: During the takeoff roll, the entire simulator repeatedly freezes and jumps forward, creating a continuous stop-start-stop-start effect until the aircraft lifts off. I experience a similar effect to a lesser extent during the landing rollout, after which everything returns to normal. Taxiing around the airport is completely smooth, as is normal flight. This happens at the same airports where my other aircraft operate without issues. I own the other iniBuilds aircraft, all updated to their latest versions, and none exhibits this behaviour. It is exclusively the A380. I am aware of reports suggesting that uninstalling the NVIDIA App may resolve the problem. However, I use this application for other purposes and do not consider removing it a reasonable long-term solution to a problem affecting only one aircraft. Given that the problem is isolated to the A380, particularly during high-speed ground operations, I would appreciate further investigation into the aircraft's performance during takeoff and landing. Could you please confirm whether this issue is being addressed specifically for an upcoming A380 update? Thank you.

And all though this is a 2024 thread, I just have done my first take off in 2020 and the same issue occurred.

Don;t look in the MP for the update you need to look in "My Library" find it in there and you should have the options. Totaly agree about MP though the A380 is the first and last anything I buy from there.

Same for me. As an remark to this bug: At this airport/runway, before 1.2.7 the Takeoff calculation always gave me Flaps 1. Now it calculates Flaps 2.....

Hi again! I just wanted to follow up, because in the new 1.2.7 release I believe you guys have migrated to the same solution that has been implemented in the A380. In this case the post may be irrelevant now. Btw, I would also like to express my gratitude, the new update is huge and must have been a ton of effort. Attila

Cara membuka blokir BWS Mobile dapat dilakukan dengan menghubungi BWS Call di nomor 08131191917 / 1500-012, menggunakan fitur Lupa Password/PIN di aplikasi, atau datang langsung ke kantor cabang terdekat. E_Statement_12Mei2026_203453.pdf

Plus one. Fuel consumption has definitely been an issue in my experience as well.

Yes, it is normal. They have migrated to the terrain system that has been implemented in the A380, thus no terrain download is needed from now on.

Really well put together. I've only had one flight to try the new update, and would like to thank the developer team their work, this was a huge release and I love the plane. Unfortunatelly I also have to confirm point 17. The SimBrief calculated fuel and the actual fuel estimation/consumption were nowhere near each other. This has never happened up to 1.2.6. If we can be of any help, let us know. Thanks!

I ran into the same issue. A/BRK causes the aircraft to decelerate and prevents takeoff—it has to be disengaged to take off successfully.

I did a fresh reinstall, deleted wasm folder, the jetway system keeps braking

Same symptom I got, but I tried delete and re-install the aircraft via iniManager, then at least uncommanded auto brake while take-off is gone.

A350F early access.

Hi, After v1.0.5, I am not getting the PA during pushback for safety briefing. Am I missing something or is anyone else having this issue? I do get the welcome message after inputting zfw, but not the safety briefing. Thanks, Reza

You can see this bug on a330 drivers stream today where he flew the updated a350

Same here, through 80 knots speed starts to drop off.

On top of that, I would love to have an option to simulate hydraulic G, Y, G+Y failures like with the fuel leak scenario.

Many thanks. I have made many posts like this for the A350! Goodness knows how many hours and hours hours I have spent doing it. Hopefully one day I won't have to do them. But I am happy to do so, just want to see the aircraft improved for all users so we all can get a bit more enjoyment out of it, so happy to do my bit. There isn't much reward other than a discord ban...

Same happened here, maybe it’s not that small of a number :)