All Activity

This issue is still present and does not appear to have been resolved. Issue Summary The aircraft will not maintain a constant manual bank angle. When hand-flying, the bank angle slowly but continuously increases in the direction of the turn without any control input. Steps to Reproduce Disable the autopilot. Establish a manual bank angle between approximately 20–30 degrees. Release all control input and attempt to maintain that bank through a 180° or 360° turn. Repeat the test under the following conditions: Flaps up Flaps down Climbing turns Descending turns Observed Behavior The bank angle steadily increases in the direction of the turn (left turn increases left bank, right turn increases right bank). The aileron on the raised wing can be seen deflecting downward slightly during the turn, which appears to be driving the increasing bank. The aircraft cannot hold a steady manual bank angle without continuous opposite control input. Expected Behavior With neutral control input, the aircraft should maintain a steady bank angle once established, consistent with normal A350 roll stability and control laws (please see attached image). Additional Notes There are no keyboard or controller binding conflicts. This behavior only occurs with the iniBuilds A350 and does not affect other aircraft. The issue is consistently reproducible.

I also have the same issue, any updates on figuring out what mod is in conflict?

Just to add for prosperity down here is that the retard callout should not abruptly cut off before it ends if you idle the the thrust during it if it calls repeatedly, this is not the case for any airbus.

Just to add for prosperity down here is that the retard callout should not abruptly cut off before it ends if you idle the the thrust during it if it calls repeatedly, this is not the case for any airbus.

As detailed in my other a340 post this is prevalent in the a350 as well. The a350 is correct in terms of 20 retard, however on autoland it still calls out retard at 20 feet, this is incorrect as seen in this video, no clue if still applies https://youtu.be/c44dToFnGzs?si=ATDhhlT6CPBEugBV&t=961 Furthermore, the a350 also will overlap other callouts however this is also not the case, it must override and take priority over RA callouts, once the thrust is set to idle retard will no longer occur and the aircraft can callout the five callout as an example. Also, the retard callout will still occur one time if the thrust is set to idle before the callout as seen here you can see the A/T light extinguish before 20 feet: https://www.youtube.com/watch?v=8JjuksTvMRg&t=214s Hope this gets fixed soon for both the a350 and the a340, heck even the default airbus aircraft in msfs2024 as this is a VERY basic oversight that shouldn't have been overlooked and something basic that should have been on release and something that the pilots that test your aircraft should have spotted, but maybe they simply don't care...

This affects all inibuilds airbuses, however retard atleast in the a340 should not be instant as soon as 20FT however it is after 20 in the a350 which it is changed in the a340 for some reason, it should be right after the callout of 20FT. It should also still call even if the thrust is set to idle beforehand, furthermore it should also override any RA callouts, not overlap over them. This is also the case with all ini airbuses. I have not done an autoland at all but I assume it wouldn't do retard at 10FT either.

Hi guys, I am trying to help you out with the WASM stuff going on. I am really enjoying the aircraft and would like to enjoy it further without a worry of these crashes. I completed a flight from CYYZ-TNCM and everything went perfect. Once on the ground and deboarded the pax at the gate I figured I would mess around with the MCDU to see if I can trigger a crash. I played around with it while on the ground at the gate TNCM by manually entering a transatlantic route from CYYZ-EHAM which requires manually entering LAT/LONG positions. I entered 3 of them with no issue. After about 2 mins of looking away from the MCDU the crash happened. I also tried selecting random points to go DIR TO as I know that is also a possible trigger. Here is my report below: Aircraft: A340 EIS 1 Passenger Simulator: MSFS2024 Navdata Method: Navigraph ( up to date with the current AIRAC ) OFP: Not included or imported into EFB. Was just manually entering a flight plan into MCDU. WASM Error: Didnt a chance to copy it in the same but I have a picture included. CPU: 12th Gen Intel(R) Core(TM) i7-12700K (3.60 GHz), GPU AMD 7900 XTX 24BG VRAM, RAM: 32BG Autosave: Was disabled. I hope any info helps. Cant wait for this to be resolved....I am loving the product!

Not the same tone and sound completely different to the rest of the callouts. A youtube video that the sounds team can probably rip it from: Very loud and high quality just needs some noise isolation

Same issue for me. This has been happening in 1.1.9 when adjusting the QNH in XBOX. I hope inibuilds team can fix this.

I'm MSFS2020 too. It can use before. Other message say because navdata version. I don't know how to fix it

I have seen on other forum pages that inibuilds is working on making the Winwing MCDU fully compatible so I know this issue is being worked on. However, that being said if anyone else is experiencing this issue I figured id pass along what I have noticed that triggers it. If you fly on the F-PLN page during cruise while passing your imputed waypoints the F-PLN page has a little glitch and causes the Winwing screen to freeze. The small work around is to just cruise with a different page open on the MCDU either FUEL PRED or the PROG page. Hope this helps to anyone having the issue.

Hi @iniBuilds, I noticed, that when setting up the plane from cold&dark, and the IRS is already aligned, then during QNH afjustments the sim is freezing. It doesn't happen to me being on the ground before IRS is aligned or when setting up plane before decent being airborne (when it's set to STD). I've checked that on 1.1.9 version (MSFS 2024 / XBOX Series X)

I have a problem starting the Airbus A310-300. There are two states... Either i click on ready to fly button after selecting my route using the Airbus A310-300 Every button that contains text shows it. (Like in the attached picture) Like most are turned to off... Well the Battery and the external Power Supply is off too... the Power supply shows Avail. However if i turn it on i can turn on everything else too but nothing happens. Also the Engines are Spinning despite being turned off. If i turn on the fuel pumps (and other pups) everything still shows LO PR. The Parking brake also doesn't have any animation anymore. The Screens stay black aswell and the yellow Master Caution is on and can't be turned off. Or the second state is... Everything is off (shows no text like usual) despite the external Power Supply. It shows Avail. If i turn it on still nothing happens. Everything stays black. I can't turn on battery or anything else... Well atleast the Engines are truely turned off. not spinning like in state one. i don't know what to do. Maybe you can help me with this?

All developers analyse feasibility for the next aircraft they make, Aerosoft and Toliss will be far out of inibuilds league and highly worth it. Aerosoft isn't handling anything systems wise. I disagree with trusting inibuilds, they still don't have a good release criteria for their aircraft, hope that changes.

Hi @iniBuilds, I could see that this bug supposed to be fixed in 1.1.8 update, however it's still present in my case when you're in external view and will zoom in the front of a plane. Pink textures around wipers is there. I've updated aircraft recently to 1.2.0 version (MSFS 2024 / XBOX Series X)

I was in a 7 hour flight and exactly the same thing happened to me as well. Nothing I could do to fix it other than end my flight. Agree with you about it being frustrating. Have you logged a ticket direct with inibuild? This is obviously a continuing issue.

Hello I just installed the A350 yesterday. Everything is up to date. I use Navigraph Navdata. The UTC times looks really weird. And it happened midflight. I think it was around Munich at the waypoint KUNOD but I'm not really sure, I just noticed it around this point. Looks like the problem is present for a long time. I found a thread from March of this year. Anyone knows a workaround? Thanks all! Patrick EDFHHEGN_PDF_1767118671.pdf

@richboy2307 Hi I just have the same problem. The UTC changed midflight. I installed the Airplane yesterday so i might have the newest version. I use Navigraph Navdata, also latest version. I think it changed around Munich, Waypoint KUNOD, somewhere around that. Thank you! Patrick Edit: MSFS 2024 EDFHHEGN_PDF_1767118671.pdf

The runway is very bumpy, and the cockpit camera is all over the screen when taking off. Are there any fixes?

For some reason taxi lights are not working.

Has happened to me only in Flaps 2 or 3 config (dont ask why i was in a flaps 3 config takeoff ;)) First time I thought nothing of it, but second time I noticed it.

Try logging in again to Navigraph.

Hi, the issue is known and we've put it on the roadmap for future update as it will require some model refinement.

Same thing happened to me after a couple of hours

That doesn't necessarily mean inibuilds would or could make their own version of it. And given their current track record of how their planes are doing despite some of the issues that they try to fix with both their payware and msfs default products, I much rather trust inibuilds on making a good -600 (and -200 and -500 for that matter) atm than aerosoft x toliss (not to talk them down, every dev is entitled to make their products how they wish)