Liamr685

Team, Purchased EGSS in the sale, and I've toggled off the detailed interiors & animated people, yet in sim, they remain active. Any ideas as to why they wont disable?

Team, As per the title, Stand 21R has the incorrect taxiway turnoff number. Both the head of stand markings and signage are correct, showing 21R, but the turn off marking from TWY A, before A5, shows 22R

There's been issues with navdata since 1.0.8. Importing the flight plan from simbrief via company flight plan request is the current work around. Alternatively, Use Navigraph hub to update your core SIM navdata, then switch to SIM default in the OIS, that will fix issues for now, but you'll loose out on MORA and GLS. Charts and other Navigraph features will still work. https://forum.inibuilds.com/topic/30966-110-cannot-insert-airways/

A few of us have had similar, where it draws the vertical profile wrong and has you either too high, or too low on the STAR.

Further investigation / narrowing down... This issue doesn't occur when navigraph is selected in the OIS & you import the flight plan from simbrief via requesting company route in the FMS, the Airways work & the route is drawn as shown in simbrief with none of the errors mentioned above. However; This issue only occurs when Navigraph is selected in the OIS & you enter a route manually in the fms or if you edit the route manually at any stage of the flight, after importing it via requesting company route. This issue does not occur at any stage, when Sim Default is selected in the OIS.

That’s what I mean. Before, I think 1.0.8, the Navigraph functionality worked fine, after that, is when I started having issues with it, and reverting to sim default fixed it, and yeah, as expected, because I’m having to revert to sim default in order to be able to fly this addon / be able to enter a route into the fms, I don’t get the Navigraph features. Which is frustrating. This is all when entering a route manually, I haven’t yet tried to import the route directly from simbrief, whilst Navigraph is selected in the ois.

Trying a different route, and to add some visuals. EGCC SONE1Y SONEX L975 DESIG L603 LAMSO DCT EVELI DCT DOJOH DCT DODEN DCT NEGIX DCT DINKU DCT BESNI DCT GOMIG DCT GOLVA DCT OBUTI DCT LAKIK DCT TISAK DCT MAVIT DCT ARTAT UP975 ERGUN UL124 KONUK UM860 RENGI UT253 OTKEP UM688 RATVO M688 SIDAD P975 LONOS L703 HAYYA HAYA1R OTHH Trying to enter that route...the first issue is from SONEX via L975 to DESIG. With Navigraph selected After hitting Enter after typing DESIG, I get this However, if i swap back to Sim Default (which has been updated to 2506 via Navigraph Hub) It works... And I can continue to enter the whole route, with no issues. But, as mentioned above, by reverting to Sim Default...I loose the additional features you're supposed to get with an active navigraph subscription.

Did you install a ULR livery? Install one of the Singapore ULR liveries from the manager and see if it shows.

Team, As per the title, with the latest update, when using the keyboard to enter data (Pressing CTRL then using my physical board) there is input lag, that gets worse with more data being entered, occasionally not registering any input. Reverting to the keyboard on the FMS is the solution currently. Along with that, the curser on the MFDs lags too when panning across the screens.

As per the title, when the APU is on and running, the door, when open, has no colour. Colour comes back when APU is off & Door closed. Happens on most liveries, seen here on A35K G-XWBL - Latest version from inimanager.

Whilst doing a bit of fault finding; KBOS/04R CELTK7 CELTK DCT FRILL DCT WHALE N93B SUPRY/M085F390 DCT 46N050W 49N040W 51N030W 52N020W DCT LIMRI DCT XETBO DCT EVRIN DCT INFEC DCT JETZI DCT AMFUL DCT OCTIZ P2 SIRIC SIRI1H EGLL/27L That's the route im trying to insert. The first issue is WHALE N93B SUPRY When using 'Navigraph' selected in the OIS, i cannot use N93B from WHALE...Why? Because there's 3 in the world, and only 1 has N93B from it. But for some reason, the way you guys at ini draw data from Navigraph, doesn't allow you to select the correct waypoint, it assumes its another, that doesn't have access to/from N93B Now, i have used Navigraph hub, to update my core sim database...so in the OIS, i select sim default, which is fine, it also gives me access to AIRAC 2506. I am now able to enter the route correctly, with no issues surrounding the airways issue. Same issue with OCTIZ P2 SIRIC, selecting Navigraph in the OIS, I get 'Airways/Waypoint mismatch' Swap to 'sim default' in the OIS...Works perfectly. BUT, I now loose out on advertised functionality Because I now have sim default selected in order to get a route correctly input into my FMS, I no longer have (off the top of my head); MORA GLS And anything else that requires a navigraph subscription, to work in this addon. You advertise the product as having extra features when you have a navigraph subscription... But whatever method you use to implement that navigraph data via the OIS...Doesn't work...or at least hasn't since a few updates ago (I think around 1.0.8) We're no longer getting what's advertised, nor are you acknowledging the issue...Wen will you address this?

As per the title. 1.1.0, I cannot insert airways into the FMS. I'm getting 'Out of range' or 'Airway/Waypoint Mismatch' Despite them being valid for AIRAC 2506. I don't have this issue in my other, 3rd party aircraft, such as the iFly MAX. This isn't the first issue I've had with the A350 and its issues with data implementation data from Navigraph. All these issues have arose around the 1.0.8 update. Here's the link to my previous issues with your inability to implement navigraph data into the A350. The issues still exists, and is part of a growing list of issues surrounding navdata; Cant enter airways Improper route drawing Improper approach drawing

I'm having the exact issue. I literally cannot insert airways and can only do directs. whenever i set up an airway, I'm getting 'out of range' or 'waypoint airways mismatch' absolutely ridiculous

Similar thing is happening with me with the latest cycle, ELVO1M into 23R at EGCC does the same, and also doesnt have the correct vertical profile, and if followed, ploughs you into the ground 15 miles from the runway.

1.0.12 still has this issue with the latest cycle. some places it isn’t drawing the flight path on approach to airports, and giving incorrect vertical profiles on approach. For example, ELVO1M into 23R at EGCC, has a profile that will cause a CFIT around 15 mile before turning onto final and intercepting the ILS.

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.