Today I got a little bit surprised. I was flying in the CRJ and suddenly my internet connection dropped because I was downloading stuff in the background. Immediately went up from 30 to 50 FPS despite photogrammetry and scenery loaded.
Edit: Although it seems to be completely independent of the geographical bad areas. I just tried it out around LOWS and got my stutters at the same locations as usual.
Still, I think that the Online functionality may play a part as well in this never ending story. Everything seems broken.
yeah the sim data is definitely hosted on Azure. I was more thinking about Asoboâs internal IT, Dev environment, communication tools etc. But tbh I think itâs more of a coincidence
Let me rephrase it in a slightly different way:
High and top end systems users most commonly has their settings at high and ultra (I have every setting to the highest possible level).These maxed out settings prior latest update gave us 55-60 (in most cases GPU limited due to V-Sync) FPS.After the update went down to approx.1/3 of what it should be.
Low to mid end systems users most commonly leave their settings @ default (exactly where the Sim sets them upon installation,mostly @ medium) and are o.k. with them.These settings were good enough prior latest update delivering around 22-30 depending on a specific system and/or its settings and now are delivering almost the same to most of the people or maybe even slightly less somewhere around 18-25.
So in this way which ones will suffer harder from the problem and for whom is more clear there is indeed an issue?
Apart from this,the existence of stutters isnât noticeable the same for everyone.There are users who will notice it more easily than others,it depends how much someoneâs eyes are used to gaming and such kind of things or not.Yesterday evening at my friendâs place there were times I was clearly seeing stutters and pauses around 76T however my friend told me he things heâs also notice them but not so prominently.
Therefore,even maybe the system specs arenât directly related to the explanation of the problem, the way a more powerful system user is using it - even only because he/she expects only the best from it - is likely considerably more related.
You have an Intel CPU. You have problems.
I have an AMD CPU. I have only the 76T Bishop 1 frames per second bug.
As you may know the Xbox X/S uses an AMD Zen 2 custom CPU: 8 cores, 16 threads @ 3.8 GHz CPU/GPU integrated chip. The chip itself is a 360mm2 slice of silicon (significantly smaller than we speculated), that pairs customised versions of AMDâs Zen 2 CPU core with 12.155 teraflops of GPU compute power ⊠via 3328 shaders allocated to 52 compute units (from 56 in total on silicon, four disabled to increase production yield) running at a sustained, locked 1825MHz.
See Inside Xbox Series X: the full specs | Eurogamer.net
âŠo.k. but how about lower ALL other sliders down to low/med?The users of less powerful systems has usually almost ALL their settings lower,not only the LOD related ones.Maybe the combination is what it really counts in the first place here.
But as a fellow simmer said here some days ago, if I should need to adjust all of my settings in the way Asobo proposed i.e. lower LOD and so on,what I will get as a result will be way worse even than FSX,therefore whatâs the point on flying MSFS in such a bad state?
Team Red may be actually leading in benchmarks and heavy workload environment like cad or 3D animation but for real world performance, especially in games, the difference between them and their competitors is small. So its very incidental wich hardware you use as long as it is able to run the game basically.
Some parts of Austria have always been bad in the simulator. It has nothing to do with the latest updates. They just need to improve the Bing scenery over there, but like I said, itâs been an issue way back.
I have a very similar problem. For me, heavy stuttering starts when MSFS is loaded into the main menu. The map and the choice of an airport is one big stutter and lagg. And when I load an airport, the fps do not exceed 10. I have a computer dedicated to MSFS and nothing else is on it. I donât even have mods. I only have two airports, ORBX and CRJ, from Aerosoft.
I donât know if we have correlation or coincidence. We have now 1224 posts in this thread, but we have little statistics. I think we have at least two bugs:
the 76T Bishop bug âframe rate 1 second, Manipulators thread need more then 600 msâ
the 100% CPU load, 15% GPU load âsawtoothâ bug
We have reports that user have big problems, we have reports that users have only the 76T Bishop bug.
At the moment we have not enough statistics to say it is hardware related or not. Maybe the correlation is having only 8 (logical) cores in the CPU - as my CPU has - and not Intel or AMD.
Note: The Xbox X can run 8 cores at 3.8GHz or 16 cores at 3.6GHz. I assume that MSFS 2020 on Xbox uses the 8 cores setup.
We have the fact that Asobo/Microsoft are working âfull steamâ at a Xbox X/S release of MSFS 2020 and that Xbox is AMD Zen2 CPU based. I ASSUME that Asobo/Microsoft wants to keep a COMMON codebase between MS-Windows operating system (OS) and Xbox OS.
Therefore I concluded that the current miserable sitution stems from this design decision. Asobo/Microsoft stumbled over an incompatibility between MS-Windows OS and Xbox OS. I think at the moment they play the âhot potatoâ game: MS-Windows OS department says this is not our bug, Xbox OS department says the same and the MSFS 2020 department has not the knowledge and/or tools to get down to the reason of the bug. Everybody moves the hot potato to the next party and hopes that the potato will cool down.
The BIG management desicion is to say âscrew common codebaseâ, have a MS-Windows codebase - like it was up to Jan/Feb 2021 - and a separate Xbox codebase and HOPEFULLY be able to join the two codebases later. The alternative is to ignore the customers that have already paid money - us the PC owners - and work exclusively for the new customers - the Xbox X/S clientel.
For successful second strategy it is important that all these negative facts we PC users have do not scare away the potential Xbox MSFS 2020 buyers.
Well, I work 30+ years in project management. I was in this âhas not the knowledge and/or tools to get down to the reason of the bugâ situation once myself.
The good thing: That system that gave me grief is long gone, my system is still around and still is supported well.
You literally have the exact same system and internet speed as me. I have done the same as you have and still get the fram rate drops for no reason at all over certain areas. Really annoying on final!
Very close. Its called windows core OS and, as far as I know, that will be an common base for all windows based platforms in the future. At least, thats the plan.
It will probably have some advantages for AMD architecture but I see these first on the GPU side of the SOC. The cpu code itself will/must run equally and independent of the CPU supplier.
Having an frame rate limiting is not part of the os but part of the gaphics driver. Nvidia user had to wait ages for this feature.
However, I agree that the Xbox port is not only beneficial for PC users
Itâs this part, in fact any multi-platform product, that concerns me. That the way the PC version is shaped in the future may be tightly coupled to whether changes are compatible with the XBox version. We may be stuck with this console shaped millstone round our necks for the next 10 years.
