Everybody is complaining about the pop-in issue these days, but the airliners / IFR / ATC situation is dramatic as well.

I have just tried a couple of IFR flights from Dubai OMDB to Kuwait OKBK after SU5 with the default A320 (FBW A32NX as you know causes frequent CTD and it's unusable at the moment, FBW even pulled it out of the store).

Community folder totally empty and flight plan generated in the World Map.

In the first flight I had the following issues, apart from the old ATC stuttering bug when the transcript reaches about 10 lines, still present:

1) Aircraft struggling to climb: climb rate 4-500 ft/min above FL240 up to FL340 where I requested a 4,000 ft decrease of the cruise altitude from the scheduled FL380. Payload was 50% and I didn't have icing. It's just the old A320 power issue that has never been fixed

2) At FL340 the ATC insisted that I was 700 ft below the assigned altitude and instructed to climb to FL340. Altimeter was set to STD correctly since I was above 18,000 ft. After many radio comms I set the altitude to 34,700 ft and forgot about it

3) At about 60 miles from destination ATC assigned the approach (ILS Y 15L), I set it in the MCDU and the aircraft started turning in the opposite way, chasing a non-existent waypoint with the same name as the correct one (PASEL) but 489 miles in the opposite direction. I manually set DIR (direct route) to PASEL waypoint in the MCDU and the aircraft resumed the correct route.

4) ATC (delegated to AI) requests "change" of destination to the same airport and the ATC repeats the approach instructions, this time requesting to climb at 14,000 ft (I was already at 9,000 ft). I ignore the instruction and continue descending to 3,000 ft as previously instructed.

5) I reach the following waypoint (RERAN) and the a/c starts turning 180°. This time the "DIR trick" does not work as the a/c continues chasing the imaginary waypoint with the same name but 500 miles in the opposite direction.

6) Despite the approach is correctly set in the MCDU, the ILS frequency is not reported in the radio section and I have to land the a/c manually.

On the second flight, in the same conditions, I have only issues 1, 2, 4 (the autopilot this time works on approach) but once landed, the plane remains stuck against an invisible wall on the taxiway with the airspeed indicator going up. 

https://streamable.com/877nm4

At this point I don't know if to look forward to the next update or fear it... 🙂

 

 

These problems have been there since day one. It’s the reason I stopped playing months ago. I’ve been patiently waiting for this stuff to be addressed. All that’s happened is the visuals are getting progressively worse.

The sim is really only usable as a sim for VFR but even then you need to fly in handcrafted world updated areas to get accurate elevation maps. The rest of the world is full of rounded mountains and blurry textures. And morphing terrain kills immersion. 

Edited July 31, 20214 yr by Virtual-Chris

Another thread made a suggestion maybe the servers feeding the data to us is somehow degrading what we see?

I load up MSFS and fly somewhere.  I'll marvel at the detail, sharp textures in the distance and great sharp detail on distant mountains.  The next day I'll fly in the same area and be underwhelmed with the visuals - ground textures in the middle distance blurry and mountains seemingly half the resolution.  I have seen screenshots posted to show how good the sim looks, yet from what I have experienced on my setup the screenshots look blurry.

Lod issues, data delivery, settings bug - something is not right and is leading to this visual degradation over time.

MrBits, yes that could very well also be the case as well. Since the userbase has grown because of the Xbox release, perhaps the servers are taking a hit. I hope that this is the case and that they will be able to update their servers to handle the bigger load.

8 hours ago, MrFuzzy said:

FBW A32NX as you know causes frequent CTD and it's unusable at the moment, FBW even pulled it out of the store

It's working (mostly) fine here, you were using the Dev branch version right?

The only crash I get with it is when I load it as the second aircraft of the session. If I flew something else already, I need to switch to it and restart the sim, or it will crash when starting a flight. It won't crash the next time the sim launches. 

Edited August 1, 20214 yr by Tuskin38

FBW A32NX is working on my system, but you MUST do a clean install as per instructions on the FBW website.  It is more than just deleting a folder in the Community folder and re-starting.  And I used the installer on the website to do the installation, as well, rather than downloading and placing the new folder back into the Community folder.

1 hour ago, ozzieblr said:

FBW A32NX is working on my system, but you MUST do a clean install as per instructions on the FBW website. 

I will try the dev version and install it as prescribed, thanks.

I was using the marketplace A32NX, I thought that being on the marketplace it must be the most stable one... Nothing was in the community folder indeed, I wanted it 100% clean in order to avoid interferences in testing SU5.

Bandwidth issues can be blamed for texture quality and traffic maybe... but IFR and ATC are still affected by old bugs that have nothing to do with MS remote resources.

Edited August 1, 20214 yr by MrFuzzy

3 hours ago, ozzieblr said:

FBW A32NX is working on my system, but you MUST do a clean install as per instructions on the FBW website.  It is more than just deleting a folder in the Community folder and re-starting.  And I used the installer on the website to do the installation, as well, rather than downloading and placing the new folder back into the Community folder.

I just tested the Dev version after a clean install as instructed here: https://docs.flybywiresim.com/start/installation/ - CLEAN INSTALL STEPS.

I had some of the autopilot and ATC problems described in the first post (no. 2, 3 and 4 only), plus graphics artifacts in the cockpit, light switches not working, crazy temperature spikes with engines struggling to keep up.

My personal opinion is that MSFS, in its current status, is not usable as a simulator and good for landmarks spotting only. I will not bother with IFR further and just bush fly until the next patch.

 

Edited August 1, 20214 yr by MrFuzzy