dectenor1

The level off-arrow is pretty badly bugged in many cases and different scenarios. Here is one example: The aircraft is in managed speed and managed descent mode, so the level-off arrow on the ND in this case should show the point at which the aircraft predicts it will reach the FCU selected altitude as shown in Cyan under the Altitude tape on the PFD as there are no 'at or above' constraints higher than this selected altitude. Here you can see that the level-off arrow is showing the aircraft will be at FL180 just before TERSA. However, on the F-PLN page, you can see that the aircraft is predicting it will be at FL200 at TERSA. Therefore, either the level-off arrow is incorrect, or the F-PLN page altitude predictions are incorrect. Based on experience with the level-off arrow being incorrect in numerous cases, it is likely the F-PLN page is correct and the aircraft will be at FL200 at TERSA, and it is the level-off arrow that is incorrect. It is possible that the level-off arrow is being calculated based on current speed and VS, whereas, in managed mode, it should be calculated based on the predicted calculated path of the aircraft, as shown on the F-PLN page. There are other issues with the level-off arrow in other scenarios, and I will post these here as i come across them again.

Sorry, feel free to delete to clean up forums. As an aside, I think the starting fuel of 24000KGs is way too much. Something like the amount the aircraft would have landed with like 8000KGs or something might be more realistic. Many thanks for the teams continued work on the a350!

You can see here the MORA displayed on the ND and on the VSD do not match up.

The MANAGED SPD targets such as green dot, S, F, econ climb etc, are bugged and keeping jumping and changing.

The T.O CONFIG TEST on the Checklist goes green when all the conditions for the TO CONFIG TEST have been bet, but the ECAM one stays blue and does not go green until the CONGIF TEST has actually been performed, thus you get this discrepancy.

It would be great if the Loadsheet Screen on the OIS displayed the current ZFW GW FOB etc of the aircraft. At the moment, if you load and fuel the aircraft via GSX rather than directly instantly importing the payload and fuel straight in from Simbrief, there is no way to see on the EFB what the various weights are.

Yes also seeing this, the first waypoint of GA is still in Green for me here, and also showing a -3.0 path.

The TRAF button on the EFIS panel is on by default at start-up, and keeps turning itself back on even if you turn it off.

No matter what rwy exit you select when using BVT, the aircraft always displays the same ROT and Turn Around Time. Obviously in realty the closer the exit to the touchdown zone, the lower the the ROT and the greater the Turn Around Time.

You can see the inconsistency here, on the SURV page it shows the ADS-B TRAFFIC OFF, but on the ECAM it shows it as ON

Very occasionally the parking brake handle makes a sound, but the vast majority of the time it is completely silent. It is a really nice immersion feel when the switches in the aircraft make a little sound.

When you refuel with GSX it resets the FOB to 500KGS no matter how much fuel is currently on board. This is annoying because it A) adds extra time to refuelling and B) is unrealistic, fuel doesn't just disappear when you start to add more.

Here are quite a lot of bugs noticed on just a simple short flight without delving too much into in-depth systems, just basic stuff. Many thanks for all the team's hard work and on the continued updates. A350 v1.0.4 Bugs.txt

This is also an issue yes, but if you look at the ZFW given in simbrief and the one in the EFB, they also do not match. the OEW of the aircraft in the simbrief profile is incorrect. You can check this my removing all fuel and payload and look at the weight, it doesn't match the OEW in the official simbrief profile. At least not in the Freighter version.

I will put in this thread the issues with VNAV during flights. Here you can see there is an AT 10000ft restriction at FM860. I am at 10000ft yet as can be seen the aircraft is telling me I am 5000ft too low. Clearly this is incorrect. Route: EGLL/27R DET2F DET L6 DVR UL9 KONAN UL607 KOK DCT LIRSU DCT LALMI DCT ABTAL DCT RIDAR DCT GOMIG DCT GOTAR DCT BABIT DCT ESIRI DCT ETIDA T390 RILEX RILEX2B LTFM/17L

The official simbrief profiles are incorrect as they have the wrong OEW. So if using the official profile you need to edit that value.

OK awesome, I am not sure, that's why I put a question mark! So there is no way to turn off the integral panel lights on the FCU panel unlike all the other integral panel lights in the flight deck?

The sound balancing is still incorrect in v1.0.3 When engine noise decreases due to reducing thrust, the system (as it is called in the EFB settings) sounds actually increase, (I think it is the air con/packs sound) This should not happen, one may hear more of the system sound, but this is due to the sound level of the thrust reducing, not the system sounds increasing. I.e. the system sounds in the mix may get louder, but only because the thrust sound is reduced, not because the system sounds themselves get louder. I hope that makes sense

At the moment the knob immediately below the AP panel is dimming both the windows on the AP panel for speed, altitude, heading etc., and the integral lights on that same panel. So there currently is no way to turn off the integral lights without turning the windows off and therefore not being able to see what is selected. Is there another knob that should be dimming the AP panel integral lights? I notice the light controls knob on the pedestal has one dial for PED & PNL, and one dial for OVHD, is it possible this knob should also be dimming the AP panel and this is what the PNL stands for, whereas at the moment it is only dimming the pedestal? Thanks