kevinh

Thanks for replying. The documentation implies nothing else needs to be done after downloading the update. In the PMDG 777 the new cycle is available after it is downloaded, so it can be done. I've tried cycling electrical power (as is necessary in some real aircraft) but only a sim reload has worked for me up to now. I'll try changing pages next AIRAC cycle. The fact you've worked out this page change trick shows something has to be done in the A350, but customers shouldn't be left in the dark about it. The documentation should be updated to address this knowledge gap and a proper procedure written so customers know how to get the new AIRAC loaded in the FMGC.

No airline pilot has ever had to remove these things on a walk round check. It's completely unrealistic. It annoys me every time I load the plane. Please make them optional and removable from the OIS. It's very annoying to get halfway through a cockpit setup then find you have to get out and click them in walkround view.

I asked this last year and still no response. I have 1.2.6 installed, have downloaded the latest AIRAC in the OIS but the FMGC still will not update in the sim. You have to reload. Why can't this be done in the Navigraph Hub, would be much easier?

The chocks are the most important issue for me. OK, you can remember to remove them before you enter the cockpit, but it's ridiculous you have to leave the aircraft to set the chocks when you shutdown. It makes sense for a GA plane, but not an airliner. Can you make the engine covers default to off?

Setting thrust for takeoff didn't produce any fan noise and the sound volume didn't increase much as power increased. Very poor.

The other thing to add is that if you set the fuel up using the A321 configuration screen (the only way to control it at present), it fills the aux tanks and centre tanks first. This makes no sense. I was able to switch centre fuel tank to MANUAL which pumped the fuel into the wings but the aux tanks remained unusable. Edit: As my wing tanks got very low, ECAM low fuel cautions on, fuel started to come out of the FWD aux tank. Surely that aux fuel would be used first in cruise.

Still a problem with v1.20. There are external engine sounds but they are much quieter then flightdeck sounds. In flight I just hear a quite aero sound (not the default wind noise). All sound sliders in OIS are at maximum, headphone simulation is off).

I hadn't updated navdata for a couple of months, so I've only just come across this issue. With cycle 2509 released, I went into the OIS to update it (I already had NAVIGRAPH data selected and linked). I did this with the aircraft on external power, no engines running. I downloaded the latest revision (2509r1) and that showed up correctly in the OIS with a green success banner and an updated revision nymber. However the FMS is still on the old revision. I tried powering off the aircraft completely then reapplying battery and external power. That didn't load the new database. I had to go back to the main MSFS menu then reload the A350 to get the new revision loaded. The FAQ says downloading a new navdata revision wipes the database, but it doesn't indicate that in the OIS and the FMS still has the old data. The FAQ says switching from NAVIGRAPH to SIM DEFAULT would wipe the database, but it doesn't indicate that in the OIS and the FMS still has the old data. The FAQ doesn't mention having to reload the sim to get the new database loaded in the FMGS. So how is this supposed to work? Is a reload now a required step? If so that's not great, as it takes up a lot of time in MSFS. The PMDG 777 EFB updates the navdata loaded in the FMS so there's no need to reload the sim. So it is possible. An offline method of updating navdata would be much faster and more convenient unless this can be fixed. Managing this via the Navigraph Hub would be a way to do that. Finally, a suggestion. The sim doesn't keep a back up navdata revision (unlike the real aircraft). That would be a nice feature to implement so you could easily revert to the previous revision in the FMS in case there's a problem with the latest data. Kevin

Departing EIDW 28R, using the PESI2J SID. The A320 levelled off at FL090 after passing waypoint DW991 because the next waypoint (DW122) has a -FL090 ALT constraint. However it recommenced CLB before reaching that waypoint. A pseudo waypoint for the 250/10000 speed limit appeared between these two waypoints and I think that may have broken the CLB constraint logic. A later ALT constraint at -FL230 was correctly respected. AIRAC 2508 was still current when I flew this today but I see the FMGC says 2509 is active (from tomorrow, Sept 4). Kevin

I was flying the SUTE4L STAR to EIDW 28L. This creates several waypoints at FL070 from SORIN to DW706. After passing DW706 the A320 did not resume the descent automatically, as I expected. I had to press the ALT selector again to make it continue. AIRAC 2508 was still current when I flew this today but I see the FMGC says 2509 is active (from tomorrow, Sept 4). Kevin

Hi Vrishabh, The OFP is attached. Note, I had to regenerate the OFP for the original date and time as Simbrief had deleted the saved OFP. Best regards Kevin KMIAKSFO_PDF_1756933046.pdf

@richboy2307 I see the latest A350 version has a much improved ECS pressure controller, but the cabin is still a bit slower than it should be climbing and descending. The cabin altitude is always behind the target value. It works well enough during climb but the simulated cabin had to resort to a sudden 2000 ft/min rate of descent to catch up with the aircraft before touchdown. That would have made some ears pop. If you don't have ECAM pressurisation page selected you probably won't notice this but I did as I was checking to see if it worked properly now. Kevin

Correction, the ON/OFF switch is there in the Fenix but it defaults to ON. I've never noticed it because it's already in the ON position.

Likewise. I've never seen an ON/OFF switch on that panel before, Airbus or not. There's usually only the STBY-AUTO-ON and STBY-TA-TA/RA. TCAS still works with it OFF, displaying traffic and TA/RA mode on the ND, so one way or another something is wrong.

I realised that eventually, the problem was I didn't know what the start up state was. However, it seems possible you could be in a position where there was no external power and no fuel for the APU. I think having a way to use the OIS regardless of simulated power state would be beneficial.