All Activity

I believe you have to uninstall the Navigraph AIRACs. Note that Default MSFS AIRRACs do update, so should be no difference

I have to twist my head to read any printed message, which makes this otherwise nice feature hard to use. Why not position it somewhere better, like the pedestal?

Just had another bad one: VEBIT4N from Zurich, runway 32. After reaching OBEDU we went around in a big circle until we were cleared direct to GERSA.

There is another severe issue with GSX: after pushback is complete and the brakes are set, the plane will gradually slide across the ground until it hits an obstacle. I've observed this twice now at MK Studios LSZH.

Then, after clicking "Instant load payload", viola, they instantly load and the Live number updates

Once all passengers are on board, the payload level still shows 0. I have to manually choose "Instant Load Payload" to update the number from 0 to whatever it needs to be. For instance: 0 passengers in PLD field for the LIVE category, even though I was just told they were all on board.

-

Just tried another flight right now - after choosing "import all from Simbrief" and then "Load with GSX", the fuel truck never comes, so the plane just sits there at the default 8000 kg, doing nothing. Passengers can be heard boarding, but they are greeted with the default US English boarding calls from the flight attendant (I'm using one of the SWR liveries from the ini Manager app, so they should be using a German accent), and the payload value remains at 0 as well. 'm

The speeds were fine, there is no way takes 15 nautical miles to take a turn at 200 knots, as a matter of fact the lower speeds i set the worse the zig zags and huge turns god The problem isn't really the fact it does these, i know it's not easy to code, but compared to any PMDG, I never had this issue ever there and I flew a lot with the 777, the ini A340 cant fly. I literally can not make a full flight without these zig zag lines and 40 minutes of deleting waypoints in the middle to help the route straighten out

Now don't take my word for it but have you checked your speeds at waypoints when that happens. I know that even the PMDG does this when the speed is too high for the waypoint.

Done!

Exactly, I keep getting this and as a matter of fact the instant 360 turn departure happend at Zurich today.

I have seen similar behavior on the GIP28 arrival into LSZH - between ZH449 and ZH457, it created a similar set of bizarre S-turns.

and had one again. it is so frustrating if halve of the longhaul flights end in a crash ruining my flight and ruining my landing statistics in the va (had now twice landigns logged at 50000 feet per minute pulling the averages to ridiculous numbers

If you were to buy it on Marketplace, transfer it to the IniManager and then follow this bit it should work, I see no reason why it wouldn't since the Airport would be activated under your account once the transfer is finalized

Here is a list of bugs in MSFS 2020: Either flaps not producing enough lift or pitch/lift issue. Cannot approach below 120 kts without having at least 10 deg nose up. Totally unrealistic. Turboprop of this kind should be approaching much slower with a nose down tendency This aircraft doesn't represent a specific Fokker 27, it's a mix breed between the -100 and the -200 (engine power, weights, etc.). Stick with one, even if it's not requested by Microsoft Pitot heaters lights are always ON when switched ON, should be the opposite (Lights ON when OFF) In cold and dark, both spill valves should be OPEN, first one NORMAL after engine start, the second one NORMAL after passing 3000 to 5000 ft Same for EXTRA COCKPIT HEATER, should be OFF in cold and dark TOTAL POWER indicators should show indication only when anti-icing switched ON, should not show anything when OFF Propeller animations are really ugly, should show a disk, not rotating blades FUEL FILTER HEATERS should be red only if filter getting iced up / clogged, not all the time when flying Weather radar never show anything anytime (people reported working, not on my side) Main passengers stairs/door doesn't fully deploy, remain almost horizontal ITT is always too low Power reduction after takeoff should be 14200 rpm not 400lb. F27 is flown at 14200rpm max, never at max rpm Hope you'll fix those quick...

HI, I have a question here for the community and devs, Is it normal/realistic to have the LNAV do squiggly zig zag lines, double turns and etc., and extremely tight physically impossible turns right after takeoff? (I'm pretty sure not..) Also after it draws and plans idiotic tight turns, it fails to follow them and turns 360 degrees, goes back to the previous waypoint and keeps missing the turn and circling. Attached is an image of what I saw, these stuff happen all the time and modifying speed constraints sometimes fixes it, but yet there are un-explaned random turns like at SDV, why does it point out a bit between SDV and XIBUS? that turn can easily be taken. And again, what is the zig zag on final? why can't it just draw a straight line and with what calculations does it get to this result? if I set speed 200 knots at TOMOS the lines get straight, but if i set 200 knots at LALTO too the zig zags come back, With another VIA, which was right at the blue 10 marker on the screenshot, it would go from LALTO to "10" and then back to TOMOS in such a stupid curve that it wanted to do a 15 mile wide turn followed by a stand still 290 degree turn and then back to TOMOS for a misaligned path, literally makes zero sense and it's just god f***g awful to release an aircraft like this and not fix these base type of stuff after a year, complete disappointment.

I might be having this issue as well, though I've never seen it in person. Im having issues where on long haul flights my TOD is pushed back so much and i lose so much fuel. At the photo icon was when I last checked on my flight and everything was looking good, TOD time was correct, was predicted to be landing with 8.6 tonnes of fuel left. In fact, my tod time was actually earlier than the predicted time upon departure. But when I came back to my TOD it had been pushed back by 3 HOURS, and dest efob had dropped down to 1.4 tonnes! A member of the community pointed out that my issue could be related to this Thread. Perhaps it may have happened when i was flying over the north pole / arctic? Route: OTHH/34R TULU3E TULUB B457 NARMI N697 PASIT T503 OVANO L768 SOKAN DCT FIRAS DCT NISAP UM861 BUK UL621 ODERO L746 LUGEB DCT DIRAL DCT LAPKA DCT ETEPA DCT KEKED DCT KELEL DCT SUDOL DCT ADVAB DCT KOLOB DCT SABAK DCT ULMUG DCT ISVIG DCT 67N010W DCT 70N020W DCT 72N040W DCT 72N060W DCT NADMA DCT 7030N07000W DCT 68N080W DCT 6330N09000W DCT YEK DCT 56N100W DCT DURUR DCT BIL DCT TCH DCT WINEN Q73 HAKMN ANJLL4 KLAX/CRCUS.I24R Plane: Qatar Airways A350-1000 Specs: GPU: 9070XT CPU: 9800X3D RAM: 64GB DDR5 My specs are quite good and they pointed out it could be performance related. But i doubt thats the case.

I do not yet have A350 but thought I’d share the same experience I recently had with FlightFx Citation X. Hitting Esc key and going right back to the flight restored it.

Hey guys, Now flown two flights with 1.0.7 and the aircraft seems to be unable to capture the glideslope properly now. Pushing the ILS button while the aircraft is physically below GS now shows GS captured immediately (rather than armed/captured), and the aircraft starts descending before the GS diamond is centered - meaning that it's descending below path for the entire approach. Disengaging ILS and recapturing results in the same issue. This wasn't an issue pre-update although I do remember that the aircraft used to climb to capture GS before 1.0.7 (which was marked as fixed), so I'm thinking it could possibly be a logic issue with that fix? That is obviously unless I'm missing something/doing something wrong. I usually capture LOC in LOC mode before arming G/S through the ILS mode. Not sure what's going on. If needed for the team, I can record a video on my next flight to demonstrate the issue. Thank you!

Ok, I'll give it a shot. How do you do it? Just change the source in the EFB? I don't want to uninstall Navigraph AIRACs in general...

Any update on this?

Frankly I get tired of the constant begging for yet another European airport when there are other massive areas of the globe that have seen far less attention, most notably, South America.

Thanks! All good now with the LVARs.

Again to add an update, at least to the STAR WASM crash; Been flying quite a lot recently on default MSFS Airacs, some shorter hauls, some longer hauls. Adding STAR and changing them has not been an issue after uninstalling Navigraph Airacs. While not a fix, it seems to be a temporary solution. For those that still struggles and want to fly this aircraft, I suggest trying this.