Liamr685

I have the same issue, mentioned here ive found if you update the core / default sim database via Navigraph hub to the latest cycle, then select the default sim database in the a350 ois, as opposed to Navigraph, it works correctly with all appropriate points and airways with the current cycle.

As for the altitude constraints, could that also be tied into my nav data issue mentioned here?

Had the same issue myself the other day. Happens to me before I engage AP, but has on one occasion happened just after I engage the AP, similar to your video.

All, There seems to be an issue with the Navigraph data that is downloaded through the OIS. Firstly: When entering route LEMG/13 BLN5H BLN N865 VTB N867 BLV P87 BELEN DCT DIDIG UP87 MOKOR UN873 OLEBA DCT ROGPU DCT DIKRO UM185 TELTU TELT1N EGGW/25. The route uses incorrect waypoints and draws a crazy flight path. As you can see below; However, the flight path is supposed to look like the below. Whilst fault finding this, I changed the nav data source from Navigraph, back to sim default Which, as updated via Navigraph hub, is also the same cycle (2505r1) After changing the nav data source, and entering the above route, it draws the correct route, with the correct waypoints. As shown in both cockpit images, you can see that I have swapped between Navigraph, and sim default, with both being cycle 2505r1. To further test this, i entered the exact same route in the iFly 737 MAX, which is updated directly from Navigraph Hub, to the aircraft, and doesnt utilise the sim default cycle. As predicted, it drew the correct routing. This leaves me to beleive there is an issue with the way Navigraph data is implemented within the A350 via the OIS. This would also explain the inability to enter flight data or request routes from simbrief, that I, and others have been experiencing in this thread; Because, when I load the aircraft, and i am unable to enter the data, if i switch back to sim default in the ois...it then allows me to enter the data that was previously vanishing. I have mentioned this a couple of comments down on the navigraph forum here; https://forum.navigraph.com/t/2505-blv-sim-freeze/19803 Who directed me to post here, as this issue is an inibuilds problem with the way the A350 draws data from Navigraph, and not themselves.

Just having a quick play around, if i switch back to sim default on the ois (which should also be 2505r1 as i have updated the sim base pack via navigraph hub) i am able to enter data again. There seems to be an issue with the navigraph integration with this addon Updating your sims base package via navigraph hub, and switching back to sim default in the OIS from Navigraph, seems to fix the issue for now. What im not sure is, if you switch back to sim default, will you loose airport maps on the ND, and charts in the OIS? Im not sure if these are specific to selecting Navigraph in the OIS, or they're just with a subscription, regardless of selecting Sim Default or Navigraph for nav data in the ois. Some of this issue im discussing here https://forum.navigraph.com/t/2505-blv-sim-freeze/19803?u=liamr685

Issue still exists in 1.0.11

Team, Couple of flights into 1.0.11 now, and on rotation, the new dynamics feel ok, but at certain points, the aircraft randomly, and sharply pitches up, letting the speed decay rapidly into alpha floor protection. This happens when manual flying, prior to any AP engagement. I have to push my joystick fully nose down to prevent a stall, before I can engage AP.

Joining in with this topic, Flood & Dome lights don't work in the cockpit with the dials on the centre pedestal. (1.0.11)

Hi all, As per the title, and an issue that started in 1.0.10 for me, that when I enter reverse thrust, I only get max reverse or nothing, it will not follow the throttle position between idle and max rev. It’s the same when using the key bindings, max rev or none, the throttle doesn’t follow the blue dot target.

Macco Sim is working on a V2 of their scenery for MAN, so will likely include all the recent development with the second pier .

7 hours into MAN-LAS, check the sim, all looks good, check Volanta and my jets turned 90 degrees from the flight plan and is heading south. Back in the sim, disconnect AP, entire cockpit freezes. Had years of no issues in P3D, went off simming for a while, returned to the hobby and dealing with this with the ini a350. This can’t be system specific, as it’s evident across the board. Hope one day we get a final fix for this, because this is disheartening to say the least.

As you can see below, despite navigraph selected in OIS, the FMS has no database, which is why it isnt letting me enter data, I have to restart the sim for it to work correctly. Come on INI, whats going on?

Sounds similar to the issues I’m having here; I can’t import the flight plan / load it in, and trying to enter the departure & arrival airports in the fms is 50/50 whether it works, or not.

Glad I’m not the only one experiencing this. ive stopped flying the 350 at the moment due to the hit or miss ability to enter to departure & arrival airport into the FMS. Even after clearing the WASM. gets frustrating having to reboot the sim a couple of times before the aircraft allows me to enter the data. no issues with other addons.