Thank you very much, highly appreciated. So my guess was correct, that every user has the same problem, but not everyone seems to realize it. There seems to be something fundamentally wrong with the current update. Even when I fly offline the issue is the same.
3 Likes
You are lucky then!! I have I5 10th gen with 3060ti 16gb ddr4 and very often I get to 9, 11fps now! It is totally impossible to use!
1 Like
Had to do it. Had to to a break from this now mess of an update! I own X-Plane 11.5. Fired it up. Manā¦ do the visuals stink comparatively. But flying is smooth as glass with a rock solid 60 FPS on max settings using the Vulcan drivers. My preferred sim is FS2020. Until this update there was no comparison. The visuals of FS2020 just make the sim experience so much more realistic. I sure hope Asobo / Microsoft takes this seriously very soon and fixes this mess. Their silence on all this is disconcerting.
7 Likes
ya im lookingto buy xplane 11 as well because of this
2 Likes
Do we have confirmation that they are working on a fix?
This game is so enjoyable, but not after this update. Just roll it back, fix it, and release it when itās actually ready. Likeā¦did they play test any of this? Come onā¦
I came here because I wanted to see if other people were encountering the same issue. Glad to see Iām not the only one. Flying into KPHL last night my frames suddenly dropped pretty much below 5fps and never recovered. Couldnāt even land.
For reference, Iām running an 8700k OCād to 4.9, RTX 3080, 32GB RAM, and an NVMe SSD. This is the first flight since the new update. I also would like to report that prior to the update Iād get anywhere from 30 on the ground to 60+ at cruise, so something definitely has to be broken. Most settings are on Ultra save for Terrain LOD which is at 150.
Nothing on my system was even close to maxed out when I briefly looked. GPU utilization was under 30%, CPU was around 50%. I also flew the 172 right after in the same area and had no issues. Go figure.
This stuff is so disappointing, the sim looks incredible but the QA on the game just seems lacking. Itās like one step forward and two back with every single update.
Looks like itās back to X-Plane for now.
1 Like
Unfortunately, welcome to the club. Hopefully this issue will get fixed ASAP!
Thanks for your post itās so refreshing to see a detailed post about an issue than the temper tantrums from grown adults that act like 5 year olds.
3 Likes
well spoken 
The ticket I opened with Asobo is closed as āSOLVEDā. They are ācontinuing to monitor and investigate performance issuesā¦ā I personally donāt see that being aware of performance issues and ācontinuing to monitor and investigateā¦ā as working on a fix.
I provided them the information I collected showing the possible root cause if this āperformanceā problem. It is not a āperformanceā issue. It is broken code that causes the performance problem. It cannot be fixed adjusting or changing performance parameters or implementing optimization such as DirectX12.
Because this problem occurs at speciific locations, Iām thinking there is something wrong with the scenery or objects within a certain radius that badly breaks the MSFS code. It is somewhat like the massive scenery spikes MSFS had recently. This time there are no spikes to see, just a busted FPS.
I am extremely disappointed in Zendesk/Asobo āCustomer Serviceā. Any ticket marked āSOLVEDā should not be closed without concurrence or approval from the person opening the ticket. If the user/customer doesnāt approve closing the ticket, maybe it should be marked āIn Disputeā. But that isnāt an option.
Another issue I have with their āCustomer Serviceā is that there is no escalation path. Who can I talk to if I donāt agree with a solution or a ticket closure? Wait for a developerās update and hope they read my question? Seriously?
Finally, there is NO focus on customer/user satisfaction. Has anyone seen a survey asking about the quality of ZenDesk/Asobo support? Helpfulness? Has Zendesk/Asobo asked anybody what can be done to improve customer/user service? Customer/user satisfaction?
MS/Asobo is very close to losing a customer/user.
10 Likes
Wholly agreed. A techā support ticket reporting frame rate / jitter / lag problems is not āSOLVEDā until the simulation is fully repaired and is no longer subject to those problems. I too opened a ticket with Zendesk, reporting the same problems many weeks ago. I was also surprised to learn that my ticket had been āSOLVEDā too. Marking such report tickets as solved when they are not might make the tech support solution rates look acceptable to the MS and Asobo Teams but, alas, it is invalid information. The frame rate / jitter / lag bugs which have been earnestly reported by many hundreds of MSFS 2020 Users (who canāt ALL be wrong!) have NOT been solved. Asobo and Microsoft assure us that these performance issues are being addressed and will be rectified in up-and-coming patches. We keenly await a comprehensive fix so that we can actually complete a flight without experiencing an inevitable and catastrophic stutter and lagfest! Only at that point should these Zendesk tickets be defined as āSOLVEDā.
Interesting, I started googling this topic because of my performance at KATL. I was getting 2-8fps where I normally get 40 with a SLI-2080TI setup
For the millionth time Asobo isnāt using Zendesk internally to track bugs, merely as a way for us to report bugs to them. A ticket marked as solved simply means that they have collected all the info they feel they need and have moved the issue into their internal bug tracking database.
The main question is: What are they doing during testing.
Basically nothing.
I would actually talk to the whole QA-Team for not being able to bring out a single patch that doesnt cause a major problem on the users end, and thatĀ“s the state 8 months after release.
There must be reasons for this and these reasons have to be elimated very soon, otherwise some people seem to lose confidence in this product.
1 Like
I have a high end home build myself, youāll have to take my word for it as Iām not adding specs -BUT- Iām not shocked when this particular software drops to 7-8 FPS based on the understanding the devs and publishing house -should have- released this title as āearly accessā or under the more correct title āMSFS 2022ā.
Itās not finished and wonāt be for a while. Not fair to the customer, but itās a cold reality.
1 Like
I am not ready to throw the entire QA team under the bus. Before I single out QA I would like (and I know this is not going to happen) to know what development process does Asobo have - how many QA - what type (In house - off shore - contract). Continued issues like this do not point to one area but a failure of the entire process. For example is anyone in development stating āI am checking in this risky change are there any concerns? - are we sure we can test this adequately?ā - because if they are not then some of this is their responsibility as well. Also what kind of scheduling pressure is being put on that may be influencing their decisions.
Now-sure-unless Asobo has no QA at all then yes I would agree some of this falls on their shoulders - they are the final say and if it isnt working they should be leading the change to make it betterā¦They should be making it clear at this point that they need help - but if they dont (our arent getting what they need) there is more to this then them just āMissing Bugsā
1 Like
Zendesk is OUR bug tracking database as well. My issue is that we donāt any info about what happens after Zendesk.
There is a failure in communication.
To most people, āSOLVEDā means āFIXEDā and will be delivered with the next update because there is no feedback loop from Asobo except the occasional āWe are working on it.ā
There is a āKnown Issuesā list. This list has FOUR items. Only FOUR! Seriously?
The āFeedback Snapshotā lacks transparency. It is a list of bugs, issues, problems, and wishlist items jumbled together providing only status and release information. Does anything on the list show priority or severity? Is the impact of āDreadful Performanceā higher or lower than āIcingā, āHelicoptersā, or āSeasonsā?
I recently submitted a ticket about performance which is marked āSolvedā. Is this being worked in the āDreadful Performanceā issue? Or a different issue? Or maybe it hasnāt been assigned yet? I do not know and cannot find out. This process is a mess!
1 Like
Iāve opened another ticket but deliberately did not use the āPerformanceā category. IMHO, stuttering and trashed FPS are NOT performance problems that can be fixed by changing graphics parameters. These are code problems causing slow performance.
5 Likes
Via the Windows and MSFS User Interfaces on a wide range of PC specifications, hundreds, if not thousands of MSFS Users have collectively invested hundreds and thousands of hours trying unsuccessfully to eliminate the contaminative stutter and lag which blight this simulation. These incidences of stuttering render it pretty well impossible to complete any airport to airport flight without encountering the problem. It is somewhat challenging trying to complete a short final whilst FPS counts fluctuate anywhere between 2 and 60 in real time, even on super-high end gaming PCās!
It is therefore entirely reasonable to conclude that it is the source code which requires significant debugging or even recoding. I trust that Microsoft or Asobo will address this issue sooner rather than later in order to render the simulation, āfit for purposeā.
1 Like