You make an interesting point. To me it seems to confirm the issues are related to individual PC builds and installs. Miceosoft will test new updates against standard builds and specs.
As a reired IT manager of 35 years experience I am not at all surprised that suddenly, an update or change interacts differently with some setups.
People then assume that the update code is faulty. It isnt. But it has uncovered an interaction problem with some hardware previously unknown.
infact this is why one is always told to use latest drivers. Same principle.
My main point was that the Microsoft bashing I often see in this forum just isnt justified. The problem will be located and a fix will be made available. To make software thats always totally compatible with all machines is virtually impossible OR the software will be very uninteresting.
“The problem will be located and a fix will be made available.”
Well, they dont acknoledge that there is a problem, really. Just look at the response to the live weather, it is “user error”, case closed.
I don’t think that is their current line. They’ve accepted its happening, I think, they just can’t replicate it. I think they had to go to someone’s home to actually see the fault.
This is a load of BS. Companies have to make money and cash flow is critical. The issue here is overconfidence in the project team to commit to deliver something they can’t deliver. The so called suits have every right to show up one day and ask where the money is.
I see this over and over again in the gaming world. They let programmers decide the project timeline who have zero clue how long it will actually take. In real software development for commercial markets, you go out of business for delivering bad product or not hitting dates. No one in the gaming software development space is held accountable for ruining business, forcing layoffs, and wrecking companies.
MS approached Asobo and asked if the can deliver MSFS20 by such and such a date. They have obviously cut corners to get stuff out. Someone should get fired, but they won’t. In my business, I would get fired, or I would fire someone if this was happening. But its the gaming world and accountability is nowhere to be seen.
Do you really not think they’re trying their very best to do just that?
Sure, they do! Read it again.
I’m sure I read that some cause had already been identified, and would make it into WU4.
Judging by past fixes and pace of releases and subsequent new problems it remains to be proven that they are trying their ‘very best’
Today I flew from Lakeland Linder Rgnl as you suggested. Cessna 172. Settings: High: Real Weather.
Flew a triangle. Flew over to Midway Lake round to Plant City from there back to KLAL.
No issues, no problems. Smooth flight. I have an Nvidia graphics card and a Ryzen processor.
Software should be mostly agnostic about being totally compatible with all machines. What I mean is that MSFS doesn’t care if the CPU is Intel or AMD, if the GPU is NVIDIA OR AMD, who the manufacturer of the motherboard, memory, disk drives, or peripherals. Of course there are minimum hardware requirements that must be followed. Compatibility is done by Windows, other operating systems, and drivers. Programs that ran on MSDOS HAD to be hardware compatible. As a matter of fact, when MS first sold Flight Simulator, it was very hardware dependent. Many clone PCs could not run Flight Simulator because some clone hardware specs did not match PC specs. In a strange way history is sort of repeating itself.
yes of course.
This is a commercial company having a problem with one of their commercial products.
You have obviously NO idea the kind of pressure, monitoring and reporting this causes for
the Team internally. Accurately locating and then fixing the problem is a huge undertaking. Specially as some people do not seem to have a problem (expect 76T that simply is totally broken for some additional reason) and others do. So locating the precise issue is not easy.
So yes, they are doing their best to track down the reason (this may involve examining drivers for certain graphic cards for example, so it can be a very wide net they need to throw to pin point the precise reason.
Nice, but we dont live in that particular world.
Someone, some where said, Asbo are in over their heads. I truly believe this.
Lucky you, for me it stutters and dips down to 20FPS then jumps back to 40 and smooth in the surrounding areas. Graphic settings or online status doesn’t make a difference.
Since this is not only about FPS and stuttering, but a lot about strange errors, which seem to come out of side effects (why should suddenly one thrust lever be shorter than the others?), the problem seems more to be in the overall software architecture and maybe the (corresponding) organisation of the development team.
In the end, you cannot “test the quality into the software”, first you have to build it in upfront.
I don’t know anything about the architecture of this, so I cannot judge anything, I can just read the signs.
This software is very complex and at the same time has “near real time” requirements. There is probably certain reference architectures how you would do this.
If the architecture of a software is flawed, testing will be no cure - you have to refactor.
Nope, check out yesterday’s livestream on the official MSFS channel. Pieter had a slideshow that got worse and worse just at the time of the final landing. It was in the Fjords of Norway, far away from any bigger complexity like landmarks pr PG.
And at the same time the view was switched to other participants which were running smooth as silk.
It’s just pretty random and except for the one Manipulators (that one is reproducible but happens all over the world) issue is not location specific.
what nonsense.
out of interest, what is your CPU GPU combination?
I tend to agree that the problem seems to be with a fundamental change that has taken place. It seems to revolve around the way scenery is delivered to the PC. Clearly something has changed that only the most powerful machines can handle.
Its not random in my case. I can reproduce in exact pixel location every single time. In my case it is very much location specific.