V1.0.11 Bugs

[dectenor1]

Many thanks for all the team's continued work on the aircraft.

Here are some simple bugs and errors I encountered on a test flight. In each of these cases, the relevant screenshot will be posted below the outline of the bug.

 

 

• Pretty sure should not be in DCLB thrust mode when just powering up the aircraft. 

 

• OIS Power buttons still do not work

 

• ADS-B TRAFFIC ON ECAM MEMO when ADS-B TRAFFIC is OFF
• 

 

 

• The first constraint of the climb should be in Magenta on PFD at the top of the altitude tape,  not the FCU selected altitude in Blue -  So here it should be magenta 6000 as there is an AT Constraint at UMLAT as can be seen on MCDU Pages.

 

 

• Syncing values on TO PERF OIS page does not overwrite any pre existing values, for instance if TOW has changed.

 

• Turning TXPR on sets TCAS to TA/RA, should stay in STBY

 

• TO CONFIG TEST should be OK if everything else is set other than CABIN.... READY. It does not need the cabin to be ready to get take-off config OK.

 

• Extremely annoying repetitive 'knocking' sound when taxiing.

 

• ECAM TCAS STBY when XPDR is on and TCAS in TA/RA 

 

• There is no ECAM memo or SYS page message appearing when G/S MODE and GPWS are set to OFF are not coming.

 

• The aircraft is still loading with TRAF enabled here (it might be on ID, I can't remember as  I had turned it off. I just turned back on here to show where it shouldn't be enabled.)

 

• The FCU MACH/SPD window is just changing to MACH above FL280 and SPD below FL280. This is incorrect behaviour. It should show SPD when the aircraft is targeting a SPD and MACH when targeting a MACH. For example here, the aircraft is targeting ECON CLB of 304KT, as can be seen by the magenta bug on the PFD being at 304, which at this altitude is equal to .772 MACH. It is clearly targeting SPD and not MACH, as it can be seen on CLB PERF page, that the aircraft will target MACH when 304 KTS becomes 0.85 MACH and we are not high enough for 304 to equal .85 yet. So the FCU window should show SPD and not MACH. Basically, the correct way is that irrespective of altitude, the FCU window should show SPD when the aircraft is targeting a speed in IAS, and MACH when it is targeting a MACH. At the moment it just seems to switch to MACH above FL280 and then back to SPD when descending through FL280 on the way back down. It is bugged in the same manner during descent.

 

 

• The CHECK DEST DATA MCDU message should go away once the requisite fields are entered. Here you can see it is still being displayed even though everything is filled in.

 

• When descent is begun, (as it can be seen it has by the DES FMA on the PFD) the aircraft should display the green vertical path indicator on the altitude tape. In the current build, it is not showing until the aircraft's shallow 1000ft descent intercepts with the path. The PERF page should also change to the DES sub-page, and DES should be in green rather than CRZ.

 

• Still the Constraint logic is bugged in terms of drawing on the PFD, or the F-PLN page Altitude predictions are incorrect. Both the altitude constraints at INREV and ESKDO are shown in orange in the PFD, indicating they will not be met, but the F-PLN page shows them in Magenta, with the correct altitudes in the Altitude Prediction column, indicating the constraints will be met. You can also see that the level-off arrow does not match with the F-PLN page. The F-PLN page is showing INPIP at FL260, but the level off arrow is showing not reaching FL260 until almost at INREV. Clearly there is a bug here. 

 

• Again the F-PLN page Altitude predictions do not match with the level off arrow. The F-PLN page is showing the aircraft will be at INREV at FL200, yet the level off arrow is beyond INREV and INREV is showing with an orange circle. So either the level-off arrow is incorrect, or the F-PLN page is incorrect, therefore, it is bugged either way. 

 

• The aircraft is clearly not going to meet the SPD Constraint at ESKDO and yet the F-PLN page SPD prediction still shows 250 KT and a Magenta asterisk, indicating the constraint will be met.
• Another bug that be seen in the screenshot below is that the PFD is indicating a managed descent speed target of 250 KT but the PERF page is still showing .85 318KTS. The PERF page should show 250 KTS as this is the aircraft's managed descent target speed, (due to the Speed constraint at ESKDO), and the MACH should disappear as the aircraft is limited by a speed restriction rather than its calculated ECON DES speeds.  Note this would also be the case if there were no speed constraints but rather just the regular FL100 at 250. So, in general, from the top of descent, it should show the MACH and the Conversion IAS. But then as soon as there is a constraint on the descent, or just the regular 250 at 10000ft, the DES PERF page should just display this constraint.

 

• LDG INHIBIT ECAM is not going away after landing. 

• The aircraft door just randomly opened and the jetway connected as I was at the gate before I had even turned the engines off or anything. Could be a GSX thing, but it has never happened on any previous build or on any other aircraft.

 

• The parking brake handle sound can be heard in drone camera.

 

Obviously these are are quite a large list bugs and errors encountered om just doing a short simple flight without even scratching the service. I really would love to see this aircraft be free from these basic bugs so please do let me know if there is anything I can do to help in this regard. I have lots of spare time as the moment, and as you can see from me writing these up and previous reports, I am more than willing to spend my own free time trying to get this aircraft to be as good as possible, and up to the standard that it was marketed and priced at. It does take a lot of time to write these up and gather the correct screenshots etc, and I just wish there was something I could do that would be more useful. Clearly these basic things are somehow being missed during the development or during the testing, and I would just like to help in any way I can to make sure this is not the case.

Of course, as I already said, thank you for work on the aircraft, I really do appreciate it, and none of this is supposed to come across as a criticism at all, I simply want to help and try and get the aircraft as good as possible, as I'm sure does the iniBuilds team.

Edited May 30 by dectenor1

[IniSteve]

Thanks for the report. I will get this stuff passed on to the dev team. 

[dectenor1]

50 minutes ago, IniSteve said:

Thanks for the report. I will get this stuff passed on to the dev team. 

No problem! Thanks

[Swisspilot1986]

Thank you for this illustrated report. After each update it's difficuilt to determine whether a well-known bug is fixed or not despite of the change log. So we all stay updated and waiting for further improvements. 

[Swisspilot1986]

Can "Der Michel" add in a further list of points?

[Powie]

What a desaster.....................

 

[Matthias0412]

Since update 1.0.11, an old bug is present again, which had been solved before: Door L4 is not opening when stairs are docking. Also it cannot be opened via OIS.

[silentghostx]

Great report.

although the first point - DCLB is indeed the first displayed thrust mode.

see around 3:20 when he boots it from cold and dark. 

[Swisspilot1986]

since update 11 how far do you think this aircraft is close to a study level, 80% maybe?

[ool]

Hi,

A couple of things I would like to point out:
 

22 hours ago, dectenor1 said:

• Pretty sure should not be in DCLB thrust mode when just powering up the aircraft. 

It is normal to have DCLB as a thrust rating mode after power-up, as pointed out above. No bug here.

 

22 hours ago, dectenor1 said:

• The first constraint of the climb should be in Magenta on PFD at the top of the altitude tape,  not the FCU selected altitude in Blue -  So here it should be magenta 6000 as there is an AT Constraint at UMLAT as can be seen on MCDU Pages.

 

The magenta FCU altitude comes after take-off when the CLB mode engages and the ALT CST mode arms. It is modelled correctly now. I agree, that the constraints on ND should be in magenta.

 

22 hours ago, dectenor1 said:

ECAM TCAS STBY when XPDR is on and TCAS in TA/RA 

Your altitude reporting is OFF. That is why it is giving you the TCAS STBY memo.

 

22 hours ago, dectenor1 said:

• The aircraft is still loading with TRAF enabled here (it might be on ID, I can't remember as  I had turned it off. I just turned back on here to show where it shouldn't be enabled.)

It is normal to have TRAF button enabled automatically during power-up.

 

22 hours ago, dectenor1 said:

• The CHECK DEST DATA MCDU message should go away once the requisite fields are entered. Here you can see it is still being displayed even though everything is filled in.

This FMS message you are describing should be called ENTER DEST DATA. It seems to come up correctly now, but I agree that it should disappear once the QNH, OAT and destination wind is set.

The FMS message called CHECK DEST DATA should come up if the QNH, OAT or WIND in the APPR panel comes from a company wind uplink. The CHECK DEST DATA message asks you to check the uplink values.

[skywalker]

18 hours ago, Swisspilot1986 said:

自更新 11 以来，您认为这架飞机距离研究水平有多近，大概 80%？

Not even 50%

[skywalker]

18 hours ago, Swisspilot1986 said:

since update 11 how far do you think this aircraft is close to a study level, 80% maybe?

No even 50%.

[Tilo Wilfert]

I'm getting a "WXR/PWS Off" error mesage on ECAM since I updated to the latest version

 

[Kolo]

during approach no Airport map loading to set the BTV ?

[MD82]

Same here, all I can pull up is the departure airport map. I can't select my destination map, or any other airport.

[haza2]

18 hours ago, Kolo said:

during approach no Airport map loading to set the BTV ?

 

43 minutes ago, MD82 said:

Same here, all I can pull up is the departure airport map. I can't select my destination map, or any other airport.

Hello,

I have reported this back to the team, thanks

H 

[LineDX]

22 hours ago, Tilo Wilfert said:

I'm getting a "WXR/PWS Off" error mesage on ECAM since I updated to the latest version

 

You have to turn this on surv page. 

[CaptainAbeer]

By any chance have you faced the issue where when I try to load OANS map for any airport it shows a blank screen on the Nav display and I’m forced to use the BRK MED instead of BTV . This is happening since the last update, I’ve removed WASM folder , uninstalled and then reinstalled . Updated Msfs 2024 Navdatabase but nothing helps. Any suggestions on how to fix it if it’s just a localized issue for me only.

[Peter]

On 6/1/2025 at 5:02 AM, skywalker said:

No even 50%.

Can you give us an idea how you came to that conculsion? Are you a type rated A350 Pilot, or engineer? 

Thanks!

[nfeuchtho]

15 hours ago, Peter said:

Can you give us an idea how you came to that conculsion? Are you a type rated A350 Pilot, or engineer? 

Thanks!

Got to be way more than 50%.

The FMS is almost feature complete now, only few things like LL crossing and RTA missing, flight model has now been tweaked in .10/.11 to feel realistic in manual flight though there seems to be an issue with some hardware having a dead zone in roll (I use TCA airbus sidestick/throttle quadrant without issue), check your hardware to make sure you don't run into this issue. There should be about 200 ECAMs by now, which is quite a big percentage of the real thing. Failures are definitely not study-level yet, simply because some are missing. TCAS is now present and working for me (2024, A359). Circuit breakers / reset switches are not there (not a big thing, maybe one or two sections in FCOM require circuit breakers or reset switches).

So much for the features. Don't get me wrong, there are still bugs, but those are being ironed out. Most significant issues right now are arguably:

1. PERFORMANCE! The real aircraft is extremely complex and computerized, and simulating that to a high fidelity takes computational resources. Lots of them. Especially VRAM for texture rendering, make sure you boast at least 12GB of VRAM, else be prepared to tone down your settings, at least in 4K. I have an RX 7800XT (16GB VRAM), and run out of VRAM with textures set to High (4K, HDR). Also, due to its complexity, the plane is quite CPU heavy. Check reddit/discord for expected FPS with your specs. Performance on 2020 is also apparently way worse than 2024. Works well in SU3 Beta, though, apart from some LOD issues on load.
2. ETA for waypoints may be way off in descent. This is reproducible and being worked on by the team.
3. AP disengages on long flights. This has been traced to MSFS live-weather updates which may cause rapid attitude change, thereby disengaging AP. If you have AP protection enabled in the OIS, then AP will switch into HDG mode instead and you go off your flight plan. Annoying for people who go to sleep during long-haul cruise, I am not one of those. Have not experienced this on long-haul/ultra long-haul with time acceleration.
4. Some managed speed/VNAV issues. Specifically, sometimes the aircraft miscalculates the descent path and shows it will meet speed/alt restrictions when it will clearly not. Secondly, the anticipated speeds on climb/descent are different on PERF page and F-PLN page. This is only this low on the list because, ultimately, it is the pilot which is responsible for the aircraft and its trajectory. You should never ever fully rely on automation, but use it as an assurance to your own calculations. If you see you are too fast to meet the speed restrictions or you are high on profile, you help by e. g. applying speed brakes or setting SEL speed to increase descent rate. Even in real life, as every software engineer will know, software may and eventually will glitch, your brain, however, should not. If it does anyway, you have a PNF 🙂

Apart from that, there is still the occasional WASM crash (have not experienced any since 1.0.7), but with the Autosave feature, that is no longer a flight ender. You just reload the flight and apply the latest savestate. Done.

Objectively and on every level, fidelity has climbed tremendously from release. The reason everyone only focuses on the negatives on, say reddit, is the - sorry to say this inibuilds - horrible release. Some people gave up on the A350, but by now the aircraft is approaching / has maybe already reached the state it should have been released in.

Fly it, you will have fun now and I am sure it will get even better.

[ewozza]

On 6/5/2025 at 2:17 PM, nfeuchtho said:

Apart from that, there is still the occasional WASM crash (have not experienced any since 1.0.7), but with the Autosave feature, that is no longer a flight ender. You just reload the flight and apply the latest savestate. Done.

Would disagree with you here. Autosave may be a feature now but it is not a fix/solution or even a workaround to WASM crashes which is still highly prevalent on this Forum & Discord. Reloading an autosave after a WASM on an overnight flight that occured 4/5+ or so hours ago isn't ideal im afraid.

Edited June 7 by ewozza

[dectenor1]

A few more things.

• When repositioning the aircraft with GSX to go to the correct place for the gate you spawned at. It is disconnecting the GPU, so I am having to start the APU to even get the OIS screen on to be able to set chocks and reconnect the GPU. Then turn APU back off etc. It's cumbersome. Also seemed to bring up an error on STS & DEFRD PROC of L/G Gravity EXTN

 

• T/O CONFIG TEST is showing as OK on the C/L Menu, when you haven't actually done the T/O CONFIG Test, so there is a discrepancy between the Test on the ECAM and on the Checklist.

 

• Entries  made on FUEL&LOAD page for RTE RSV, ALTN, and FINAL, are reset when the ZFW and ZFWCG Fields are updated.

 

• Selected ILS 22L in Copenhagen and it doesn't fill LS (Identifier) and FREQ/CHAN on Select Arrival Page (could be navigraph issue, but flown here in other aircraft and it has always got the identifier and the freq without having to enter it manually on the NAV AID page.

 

 

[dectenor1]

I should add that I am now using 1.0.12, but the same applies as was only a hotfix update, and didn't address these issues, so these (including the original post) relate to v1.0.12 as well.
 

[dectenor1]

Also incorrect placement of DECEL FLAP1 and FLAP2 pseudo-waypoints

 

I mean there is a lot wrong with this.

CHLF is 5nm from the runway and the aircraft wants be at 10ft.... 

And it is not connected to the rwy on the ND.

Something odd with this approach. Again flown regularly with other aircraft and never experienced this.

 

 

 

Edited June 7 by dectenor1

[dectenor1]

@Eddie

Hi, lots of things reported as being LOGGED elsewhere, would be great if the team could confirm this list of issues, if it's going to not be looked at for a while after the next update.

Best