Yep, since the last update everyone has to turn now TLOD because it’s hammering the main thread. An update should not make people use lower settings. It’s a downgrade.
Add to this, the FPS loss on flights you now also get where frames go down by a half during a flight it’s just unacceptable.
What about nVidia DLDSR? I seem to have gotten a nice quality improvement with 2.25, although I’m not sure how it interacts with the MSFS Render Scaling setting …
you know… in this forum are a lot of developers and I’am sure all of these know, that adding a month of testing will change nothing. There are to many situations, scenarios, combinations which no test-team in the world can find. You allways get in real-world then the bugs which you never ever seen in test-environment.
Thus, for me is these “adding more test” absoltly useless.
What we need is a ! permantent ! beta branch. More exact two of them, like a stable-beta and a experimental-beta. The users can choose in which they join, or whehter they only want use the stable release branch. Users can get in this way much earlier bugfixes, optimizations, new features,… Also new DLCs which work only “since version x” and so also the developers of Mods have time to can test it within the beta.
New “content” ( for which so many users in forum simple not asked ) can be delivered each 3…6 months. If these new content needed changes in code-base, it goes first trough the beta.
For the stable release is a delivery-cylce of two months realistic.
There are so many “games” where users join into the beta only, because they not want to wait. And the concept works. The users also know ( at least most of them ) that they are then within a beta and all the hating posts will be a bit more constructive.
Of course.. it is not so easy, in special to sync new-features in beta with the stable release ( where this not exist ) , and lots more difficulties. But a beta branch , where we not need to reinstall each time 130g, is simple state of the art
Agree with this. We need options to choose what version to use in the meantime they fix the new version with more features or even completely overhauled features. It will create less stress on the devs.
And this is why I don’t participate in the betas any more. It’s become evident that their release schedule rules all, and no matter what we report as completely broken isn’t worked on as long as the build is shoved out the door on the announced date with game-crashing hotfixes to follow 2-3 weeks later. The open betas appear useless from a “did we fix this really” testing medium from my perspective.
Let me tell you a story from yesterday (Friday, June 3rd 2022).
The company I work for as a software developer (german Sim-Racing Hardware) released 2 major updates yesterday. One for the driver, one for our control software with telemetry support from the simulations.
Driver was ok, no bigger issues.
The control software had an issue. It simply crashed for one user during startup.
The affected customer was so smart to send us the event logs.
5 minutes later we have known the cause and how the customer could fix this. We also knew that the crash would not occur for any user.
Another 5 minutes later we got the confirmation from the customer that the workaround worked for him.
And another 15 minutes later I had a new executable with the issue fixed.
Less than 30 minutes for a fix.
And then there is a company which let’s us wait 2 weeks for a “hotfix”?
I think they could perform better.
Imagine if Asobo flipped the schedule. Sim improvements and bugfixes arrived every few weeks and World Updates were released only 2-3 times a year. I think that would take the sim to a much better place.
Not really.
The smart guys responsible for the [C / C++ / C# / HTML / … ] code have other things to do than the smart guys responsible for putting new data into a database which we can see graphically in the sim when looking out of the cockpit window.
Asobo is a mid-range software company founded in 2002.
They have about 220 employees working for the company.
The company is France and based in Bordeaux.
Microsoft is the client and Asobo the developer.
I think that most of the workforce of Asobo is now working on other new games and surely not only on MSFS 2020. When a game is on the market bug fixing and development of new parts are slowing down.
When Microsoft want’s quicker and more development force then they have to pay for it.
The thing about your story, is that your company wrote the software in the first place. With MSFS they’re working with code that was coded by different companies over the years, then they had to put their own fixes and adaptations to it to make it work like they wanted it to.
IMHO the sim needs to be re-written from the ground up, no using old code and what not…
You are absolutely right!
IMHO the first design failure was to use the 12(?) year old FS-X code as a base and trying to develop from this base.
Sometimes it is better to throw everything you have in the bin and start from scratch again.
WIndows got a lot of fancy, useful and necesarry updates in the code since the old Win-NT days.
It’s a lot more than just eye-candy stuff!
And, windows did not break core features with every update.
And, when Microsoft decides to do some thing different in the future, all devs for “3rd-party-software” worldwide know about it 6 months in advance and have the documentation about it 6 months in advancer as well.
Agreed, but like our beloved sim here, which has also gotten some great upgrades/new functionality, it is built upon something old.
This obvious works for Microsoft.
I also wonder if MS was really unsure if this revival of the FS “franchise” was going to be successful. I bet in hindsight they wished they’d started from scratch.