I thought this question might get some enlightening answers.
I’ll start … What would i do different ? basically NOTHING.
I would #1 do what my contractor (Microsoft) told me to do - they are the ones paying and employing me.
I would set up ZenDesk and strictly control any time consuming and unnecessary dealings I had directly with the consumer.
I would work to fix issues (and add content) that Microsoft told me to address as a priority, and then next, what my department managers recommend.
I would not waste time and effort trying to deal with of a mass of seemingly random complaints and reports, that are both conflicting, do not have nearly enough technical information for me to act on, come for (let be nice) DUBIOUS sources.
I would be feeling the enormous pressure of this “Once in a lifetime” opportunity for my company, and do everything I could do to keep Microsoft “Happy”.
— It would seem that this is more than reasonable, and appear to be what they are doing … so
"GO ASOBO" You get my full support (because if this fails, we might NEVER see another Consumer Flight Simulator any better than this)
I would fixes the bugs crashes since day one not keep adding content that does not work I have submitted tons of bug reports all I get is install this or that yet no other game needs this constant installing which means games broke from day 1 yet as they said " bug fixes not important right now" December maybe and not even looking in to the fixes to stop crashing This is how companies go under My opinion no one spends 130 bucks on a game and not for it to work after 4 patches and infinite loop for a update which I have right now and 2nd time
In an ideal world, YES, that’s what I would like to do as well … I agree.
So you may then wonder why that does not appear to be happening, or happening as quick as many may like.
The anwser to that is probably very complex , and not something that most would understand, or be given the opportunity to both know about, or directly affect.
Maybe, the Bottom line, is in fact the “Bottom line”, and it is all at the end of the day about tye almighty DOLLAR.
I like to think it wouldn’t be the case, but I totally get your point. If Microsoft can’t find a way to make money out of this after doing it for 40 years, then the odds another company could do it are infinitesimally small.
So I guess I’ll live with what it is for now, even with the flaws, cause the alternative is so much worse.
HEH! You can see what they are trying to achieve grass-wise. Shame about the tree, wish that was the only issue I am seeing
Still on the plus side, streaming that vid has helped to finally push my update over the finish line after 45mins stuck on the last KB.
We fly! (maybe) now.
I’ll come back to the thread with thoughts on the original question when I’ve had a look around…
We just have to give them time, MSFS2020 is a very complex game. The only thing I don’t like is the autopilot which doesn’t work well on most aircraft but on the BeechCraft 350i it works fine except for the autothrottle. It is functional enough to fly on VATSIM, just like the CJ4. You just have to be patient for them to fix the autopilot.
It’s true that the game feels Beta-ish but that’s not something that bothers me. Everyone is working hard to make this amazing simulation better and better.
If I was Asobo I would commit seppuku for such a public display of ineptitude or malfeasance. The “or” is because it isn’t clear which one it is yet.
More seriously though, I’ve laid out what they should be doing differently many times.
Step 1 - STOP making things worse. Take a break. Think of it as a safety stop. They need to sit down at their virtual conference room table made of threatened Amazonian big-leaf mahogany and rethink their strategy.
Step 2 - Formally acknowledge, not in code, not in indirect or implied meanings derived from Q&A sessions - but directly and in writing, the many failings of the title at launch time, and the subsequent debacles known collectively as “patches” to include that the game was not ready for release.
Step 3 - Publish a DETAILED development roadmap for the next 12 to 24 months that includes specific, achievable software development milestones. I really don’t care when their next tea time or office party is - stuff like that can be left off. Milestones should be included for marketed features that only appear currently in the marketing.
Step 4 - Establish an internal process for both automated and manual software testing prior to advancing alpha builds to beta. Establish in Microsoft lingo, an insider program for further testing those beta builds.
Step 5 - Release high-quality, well-tested builds to the general public and profit with software that they can be proud of, and that generates good PR.
