All Activity

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 :)

Great post. ini are lucky to have people like you spend this time to help them like this. I hope they listen.

Hi, mate Sorry for the late reply, I just checked the LFMN RNP-A RW04L. I believe you are seeing this: ON the ND => (Pic 01) On the MCDU => (Pic 02) And I believe you are asking why the runway of LFMN04L is exist in MCDU, isn't it, @spottersim ? Let's have a look at the charts: (Chart 1, 12-3 RNP-A RW04L/R) The Procedures are there, after MN04A W/P, it goes to MN504 W/P under the dashed line depicting a Go-Around Route to NERAS. And you are wondering why LFMN04L is there on the MCDU (as depicted on the pict 02)?! But here's a thing, RNP-A/B/C on the procedures IS A DIFFERENT Procedures comparing with RNP-X/Y/Z. RNP-A/B/C is a COMBINED RNP Approach and Circling (Visual Approach), so it is goes visual approaches to the runway. And MN504 is the MAP (Missed Approach Point, a point to be made as a Decision Placement to decide wheter to continue to land or Go-Around). So, After MN504, if you want to continue approach, please refer to Chart 12-3A that contains Visual Guidance Approach after MN504 W/P: This Chart => (Chart 2, 12-3A VPT RW04L/R) See how there's a box contains explanation with thick word that refering us to charts 1. Also on the Chart 1, see the on the Top-Right Box, there's Reference Box to 12-3A. So Chart 12-3 and 12-3A are correlated to each other. So the Charts 12-3A is visual description/prescription of Visual Portion of the RNP-A procedures. Based on that, it is normal to have Runway on MCDU, you can compare it with LDA-X/Y/Z RJTT/HND Runway 22, it is almost identical between each other. I hope it's help to understand the MCDU Plan for Approach. Cheers!

same here

I have also just had this happen to me, turning off the autobrake returned to normal performance immediately

Hello guys, Just a quick check, is there any one having pixelate Terrain Display like this since V1.0.5? Is it me having texture problem since SU7 or everyone who also experience this? Cheers!!

Many thanks to the team for another update. A few things after a couple of test flights, it's a bit of a mixed bag really. Some things appear to have been fixed, quite a few bugs remain, and also new ones have been added. So these are a few obvious things still wrong without going into deep systems depth and specifically testing and looking for bugs. SOUND (1) There is still no sound when when the Park Brake handle is turned on and off using dedicated hardware, in my case the Thrustmaster TCA. The sound of the handle moving, however, is present when clicking it with the mouse. (2) There is still no sound going into the throttle detents from a lower thrust setting. For example, going from halfway between IDLE and the CLB detent, there is no sound when the levers go into CLB, but reducing the throttle from halfway been MCT FLEX and CLB, there is a sound when the throttle levers go into the CLB detent. VISUALS (3) The various display screens (including the OIS screens) still have different levels of brightness when on the same brightness setting. This means you can't use the display master brightness dial to set the brightness you want for all the screens. (4) Really horrible windshield reflections. See below. (Though it may not come out clearly in the screenshot, they looked really bad, and don't remember this from previous versions.) SYSTEMS (5) Loading PAX with GSX still results in an incorrect (lower) number of PAX shown as having boarded on the OIS Loadsheet Screen compared to the number indicated as boarded in the GSX menu, which is always correct with number on simbrief but the OIS Loadsheet does not match. (6) The Preliminary Loadsheet received by the aircraft still has identical MACTOW and MACZFW. This value is always wildly different from the values for these on the Final Loadsheet. (These Final Loadsheet values, are also slightly different from each other, which is correct, unlike their values on the Preliminary Loadsheet.) (7) Altitudes on the F-PLN page are not in the correct format (Altitude v Flight Level) with respect to the Transition Altitude on the PERF pages. Below you can see the Transition Altitude is 13000ft, however, there are altitudes shown as FL070, FL090, FL120 etc., when these are below the Transition Altitude and so should be in 1000s of feet. (8) The flight plan distance is not shown until the weights are entered on the FUEL and LOAD INIT Page. This is incorrect, the distance should be shown but just not the estimated time and fuel on board (these two correctly appear once the weights are entered, but the distance should be there without the weights.) You can see this in the photo above showing the issue with Altitude Format. (9) The autobrake is coming on during the Takeoff roll which basically makes the aircraft unflyable as you can't take off. (10) Shortly after Takeoff I always seem to be getting this CHECK IRS/AIRPORT POS message on the MCDU. Shown below. (11) When setting up BTV, one cannot change the runway condition or braking action, it is completely stuck on 5. (12) The Level-Off arrow and the indication of the FCU selected altitude below the altitude tape on the PFD logic is incorrect. In the shot below you can see that 7000 is the selected altitude on the FCU, and the level off arrow is showing where the aircraft calculates it will reach this altitude in cyan on the ND, and FL70 is displayed on the PFD, again in cyan. This is incorrect though because there is an upcoming altitude constraint of AT FL130 at HAZEL. The aircraft is in managed descent and so this constraint should be taken into consideration. FL130 should be in Magenta below the altitude tape on the PFD, and the level-off arrow should be in Magenta and showing where the aircraft will reach FL130 for this constraint. The FCU selected altitude only takes priority in managed descent if it is set to an altitude higher than the the constraint in descent, and obviously in reverse if lower than a restriction during the climb phase. (13) The FCU Selected altitude should not change subsequent Altitude Predictions on the F-PLN page. In the shot below you can see that the FCU Selected Altitude is FL70, but for some reason the aircraft is then predicting that it will never descend beyond FL070 and kept FL070 as the predicted altitude at all waypoints right up to the runway waypoint. (14) Likewise, entering a manual speed restriction forces the aircraft to predict this same speed at all subsequent waypoints. This is shown below. I entered 220 at DITON, to help with the turn, and the aircraft has just put the current speed as the prediction for all subsequent waypoints, ignoring any deceleration. A speed constraint should make any subsequent waypoints not have a higher speed constraint/predicted speed, but it should not affect any subsequent waypoints that should have a lower speed. (15) Altitude predictions at waypoints are still incorrect. Below you can see the aircraft is predicting it will be at MC604 at 1450ft, but the aircraft is already at 2850ft.... But at least the Amber asterisk on the F-PLN page and the circle around the waypoint on the ND are consistent with the prediction, it is just the prediction that is totally wrong. (16) The aircraft really didn't follow the Lateral path at all well here. Yes there is quite a bit of wind, but I would have thought that it would be able to account for that. You can see below it totally messed up the turn at D074L. (17) I have also noticed that the Fuel Prediction seems to be quiet off, the aircraft is using a lot more than simbrief suggests it will, and the amount of Fuel On Board at arrival does not match with the EFOB given on the F-PLN and other fuel prediction pages. FLIGHT MODEL (18) The aircraft still seems to lift off the runway at very shallow pitch, the nose is barely a few degrees up and the VS really starts increasing dramatically, the aircraft in real life shouldn't really start to unstick from the runway until much closer to 10 degrees nose up pitch. Again, thanks for the update, maybe some of this stuff is planned for V2, but I thought it useful to have a little stock take of where we are at the moment. These things are not exhaustive, but just obvious things noticed on a couple of short flights, it is a little disappointing that there are LNAV and VNAV related things here when they were supposed to be big focusses of this update, but there we are... As always do get in touch if you require more info. Hope it is useful and best wishes.

Good evening :) I just made a new clean install, launched the sim, started the engines immediatly without preparing the flight... and It worked normally ! I then started a normal flight, prepared the flight... and I got the exact same issue as described above... I tried @SeanDarren method to recycle Engine bleed master, and it worked for ENG 1 , but impossible to do the same for ENG 2 While ENG 1 was running, APU bleed & Engine mode sel NORM, I noticed that PACK 1 was in the fault mode. The start sequence is really really strange, to get the N1 climb up to 10%, you have to make a combinaison with the engine mode selector and the engine master But without the method (that work "only "for eng 1), impossible to start the engines Clean install done at 1830z, If you did any updates before :) Good luck resolving this

Hello, I've wanted to ask about Inibuilds A350 V2 airliner possibly coming out on Ps5. Could it be possible to happen sometime?

After updating to V1.2.7, Cabin seats are missing, performance mode is off. As per the screenshot the cabin is there, but no seats. Thanks.

Hiya all am new to the forum and new to the Inibuilds a380 I hope I can get some help weird thing happened to me . During cruise the aircraft started over-speeding and the altitude dropped , the autopilot came off. I did use simbrief to do my flight plan and put everything in right in the fmc. Would anyone know what could have happened or what I may of done wrong . Would appreciate anyone help please. Picture below before everything went wrong.

Hiya guys am new to the forum and new to the Inibuilds a380 I hope I can get some help weird thing happened to me . During cruise the aircraft started over-speeding and the altitude dropped , the autopilot came off. Would anyone know what could of happened or what I did wrong . Would appreciate anyone help please.

I have just updated to V1.0.5 and confirm the stuttering is now back on take off roll

Hello, I am encountering this issue as well after the new update. Engines failed to start and N2 froze at 3%. I recycled Engine bleed master for engine #1 and it started randomly, but I couldn’t replicate that after. I am on 2020 as well and no luck with the default livery

Hey, I just finished the second flight with 1.2.7 and fuel factor is like 6 %, yes :-) https://galerie.klusik.cz/gallery/game-screens/flight-simulators/a350/from-prague-to-princess-juliana-international-airport-lkpr-tncm/?lang=cs&presentation=1&autoplay=1&presentation_fullscreen=1&presentation_music=1&presentation_interval=medium&presentation_transition=slow&presentation_exclusive=0 You can download my simbrief there and crosscheck it with my measured data: LKPR TNCM A350 1.2.7.zip I made a script which saves my flight data during the flight, maybe it could be helpful to anybody :-) A350_1.2.7_LKPR_TNCM_fuel_comparison.csv iniBuilds_A350_1.2.7_LKPR-TNCM_Fuel_Analysis_EN.pdf

After the update, there is no cabin visible when you open the cockpit door.

Same!

Before take-off I verify that in the PERF CLB tab in the FMS, I have THR set to AUTO-DERATE as usual. Upon take-off, at some point, this switches to CLB. This has happened two flights in a row. I looked into this in the FCOM and apparently there's a way to get to CLB from AUTO-DERATE (yellow is my emphasis): I will test a bit more, but perhaps this is what is happening. I'm not quite sure how it should work, since passing from CL to MCT happens when I push the throttles for a normal flex TO, and the levers go back to CL normally too. All I can say is that this did not happen in previous versions of the plane. Okay, after testing: moving the throttle CL->MCT->CL doesn't make the aircraft to switch to CLB so that's not what's going on (and maybe that functionality should be added).