All Activity

Anyone know why this is showing up for FS24. Obviously, we all know the story, so not sure where an FS2024 version came from.

Hi! I am experiencing a number of “gamebreaking” bugs in the A350 on Xbox. A350 1.1.8 (according to library - however in the OIS it says 1.1.4 (Xbox) • Navdata doesn’t update properly - Leading to issues with F-PLN and “airport not in database” etc. • Terrain doesn’t show on display after downloading it, and restarting flight from main menu. • No engine animations. - Engines are animated as idle when spooling up, on, and in the air. • Printer prints unreadable sized textures • Fully broken displays • Fuselage is transparent on exterior model, when looking through hatches and windows. Apart from the broken displays, all the other bugs are persistent 100% of the time. The broken displays were persistent 100% of the time, before I downloaded the A350 instead of streaming it, then deleted it, and had it streamed again. it seems fine for now!

The landing distance seems just a bit off. The real A350 would probably need a few meters more even if autobrakes are set to medium. Maybe you could have a look at this as well.

Just performing my first flight with the A350 since the recent sound overhaul. One thing im noticing is that the sound of the engines in the cockpit isn't getting quieter with altitude. Just reached 40,000 feet, and the engines sound just as clear as they did at 10,000 feet. The effect of the engines getting quieter at altitude was far clearer in the previous version. Same with wind noise. If it's more realistic this way, I stand corrected. Im using FS2020.

There is obviously an error in the flight plan. You are flying from DUGDA to CALVY, then backwards to SILTO and finally to ONTOK. 🤪Of course, the plane is making circles in that case. Two 180 degree turns on short notice - this won't work. You can see the colors in your plan, STAR and APPROACH are overlapping. Maybe you have chosen a wrong transition?

Thank you for your reply, now I know I was heard.

Hi guys, with the latest update v1.0.18 and latest navigraph data, noticing something weird planning/flying approaches into CYYZ. RVAN Z 23 LPV, ILS 23, and RNAV Z 24L. The FMC creates weird turns on final approach path as seen on the attached screenshots. Selecting the correct arrivals and approaches. Example: RAGID6 ARR all the way to CAVLY then using RNAV 23 Z SILTO to CYYZ . Something is not right here, please have a look at it @Eddie Regards

Never gonna work in these two birds. Touch screen v LSK key presses. FCU and EFIS do work in the 350 tho. Ini doesn’t make a 380 (yet). Blue skies, -A

v1.0.2 of iniBuilds Manchester (EGCC) for MSFS 2024 has been released. This update realigns Taxiways E and D with updated markings and lighting, while correcting object placement, airline codes, and various visual bugs. This update can be downloaded via the iniManager. v1.0.2 - Taxiways E & D shifted as appropriate to allow additional parallel spacing - All markings, connections and lighting adjusted to suit - Changed layout of D/E connection at NC - Some taxi sign adjustments - Moved blast wall to correct diagonal position. - Moved GSE per above - Added missing airline parking codes - Fixed z-fighting T1/3 - Fixed floating approach light 23R - Fixed mast light colouring - Fixed bugged exclusion on default street lights

I had actually feedbacked this and my post is disregarded. I had also prove of video showing it. But anyway, I will repost it again: The -900 variant is different from the -1000 in terms of flaps retraction and deployment timing. -900 is usually faster in deployment and retraction than the -1000. For your product, the -900 version is as slow as -1000. I can't make a video at sim but I can roughly provide the timing of -900. Inbuild A350-900 Flaps 0 to Flaps 1+F = About 20 to 22 seconds Real life A350-900 Flaps 0 to Flaps 1+F = About 10 to 13 seconds https://youtu.be/E80qj1C3rDM?t=272 Inbuild A350-900 Flaps 1+F Full 0 0 = About 20 to 22 seconds Real life A350-900 Flaps 1+F Full 0 = About 8 to 10 seconds https://youtu.be/E80qj1C3rDM?t=1001 Inbuild A350-900 Flaps Full to Flaps 0 = About 31 to 33 seconds Real life A350-900 Flaps Full to Flaps 0 = About 19 to 21 seconds https://youtu.be/KtKqg1tOjYo?t=754 Is just that the -900 variant need adjustments. The -1000 variant is pretty fine.

All of a sudden both Winwing fcu and efis and mcdu do not work in inbuilds A340, but in all other planes it works ( A350 - fenix A320 - FBW A380 ) however mcdu does not work in A350 and A380. I have tried everything - uninstalling all planes and simapp pro and completely new installation of msfs 2024 ver. 4 There are no lights at all in fcu and efis and no buttons work. PLEASE HELP ME .......

I confirm the same problem. At moment I identified as possible mod conflict (empty community folder seems solve the problem), but still not able to understand with mod is incmpatible.

Yeah it's pretty frustrating. They know it's an issue so I'm very surprised they haven't sorted a solution this. It is spoiling the immersion on their "Compatible" range. This was Dubrovnik. Eddie - Do you have any updates from when your raised this with the team?

Yes, both the stability of the simulation rate and the fuel consumption performance are very good on 350 and 340-300, because their EFB has a built-in simulation rate option, which I guess is related to this. Another important issue is that the fuel consumption of all default Airbus aircraft cannot be adjusted according to the simulation rate. This problem was mentioned by many people a year ago, but it has not changed so far. Currently, only Airbus has this problem among all 2024 default aircraft. I hope to pay attention to this issue, because not every player has time to complete long-distance flights in real time. Currently, only a small amount of fuel can be added and unlimited fuel can be turned on to solve this problem, otherwise they will face overweight landing. Such an experience always has regrets. I even saw in the wish list on the MS forum that many players hope to launch the 330pro, and many people love this aircraft and are willing to pay upgrade fees for it, because many issues have been greatly improved and enhanced on the 340-300!

I have MSFS 2020 on Xbox Series X, when I load simbrief flight plan into A320 Neo V2 there is always an additional waypoint that is in FMC that is 3000NM from my intended route. this only happens at EGSS. Anyone help.

I really wish Inibuilds would at least acknowledge the bugs I report. I’m not a beta tester, and it’s annoying to get zero feedback.

Hi, I'm just wondering if Inibuilds has any suggestions for this issue? I am experiencing the same thing. The aircraft performs well aside from this bug. Thanks!

I had this WASM crash on climb when passing over waypoint HULKK. Cannot reproduce the crash because I was not interacting with the airplane at the time. Information Aircraft: A350-900 (1.1.8) Simulator: MSFS24 Navdata Method: NAVIGRAPH OFP: Attached SimBrief OFP Specs: Intel i7-13700K, Nvidia RTX 4070ti, 32GB RAM Autosave: Attached latest .BIN file before crash WASM: Error during EFIS_gauge_update execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty 1765439430.bin KIADEDDM_PDF_1765433258.pdf

Hi, I use PSXT with RT for the insertion of realistic traffic into MSFS2024. At EGCC, the RT follows the new taxiways very well, generally, except for the new taxiways E and D. The taxiways E and D between LINK 4 and LINK 2 are placed too far SW compared to the real world; this results in real traffic aircraft taxiing off the scenery taxiways (see screenshots). The scenery needs to be redrawn with the correct placement of these taxiways (I will stress again that all other taxiways seem to be correctly placed for the real world). Peter

After loading an AutoSave file the top three MFD panels have incomplete displays... Is there a fix for this ? Running SU4 with latest A350 version... Thanks

2024.

Hello inibuilds, Have you fixed this bug in SU4? Regards

A35K. Exactly the same occurred to me. Pitched up, yet uncontrollable and then crashed. Have uploaded to latest SU4. WASM files deleted etc and the 350 is a mess. Multiple load up issues where screens not showing correct data and twice scrubbed flights due to ‘red screens of death.’ Had occasional WASM crashes, although now much worse since update. This is beyond a poor substandard product inibuilds even though purchased at lower cost.

Just start from the gate dark mode and there is no crash each time

我要下载这个软件