I appreciate this point. My opinion is: the alpha and beta testers told you (assumed Asobo/MS) about these issues, long before the product was released, that they were not repaired prior to release was inexcusable on the developers part. That is like releasing a car with half the car missing or broken.
That ONE DAY it will be fixed is not acceptable. I frankly don’t care if my country is in fine detail, I care that when I pick a plane, a route, create a flight plan, and fly, that the system follows that exactly as I laid it out, then once I learn that it works as advertised, I can then set about sightseeing.
I disagree with the development model, but I am just one customer, of the millions of them, my guess is at least 75% would rather have a simulator which is working 100% of the time, and wait for the fluff later on. This is my opinion, and should not be considered as public criticism to cause me to be suspended again.
FlyingCool - I owned my own PC company, and worked in Client support and was project lead on the roll out of Windows 2000 workstation in a company of 3,500 employees, had my roll out been as bad as MSFS, I would have been fired. And based on Fluff roll out which introduces more bugs than are present, logic dictates, we FIX it before we interduce more problems. This way, none of the core problems are causing the “roll out issues”, those are inherent in the version released on X day. But who am I, just normal user here. Not professional pilot, nor any pilot license holder. Plenty of those have commented on various threads how bad parts of this are, if you won’t listen to us, then listen to them.
Enough, everyone knows, just how bad parts of this sim are, we can agree to disagree all day long and still not get anyplace. If Asobo has the courage, to take a survey of all the users, my gut tells me we want the program perfect as humanly possible, before any more fluff is released, that some parts of the world have to wait, that too could be part of the survey. My gut tells me no survey, hence you will not get any meaningful feedback on what the “CUSTOMERS WANTS” versus what management wants. Since in my day and age, the customer was king, this is a poor example of how we as the purchasers are really treated and appreciated. I am done here.
I think these are different context, no? Rolling out Windows 2000 workstation to a large company can literally mean life and death. People could lose their jobs, people could lose millions of dollars worth of business when you screwed up.
MSFS is a consumer software, if there’s issues, there’s really no life and death situation, there’s no risk to people’s jobs. All it gives is a minor annoyance that doesn’t really impact anything.
I disagree that customer is always king. Because I never expected to be treated as such as a customer. There are some things that I don’t know as a customer and I’m paying to have someone’s expertise to bring me something that they think is best. We are all human too. Software may be absolute, but they’re built by humans too. If we make mistakes sometimes, then we shouldn’t expected people to make no mistakes either.
There are issues with the sim, sure.. let’s point those out, let them know and let them do their job fixing it. It’s just a minor annoyance. It doesn’t make you lose your job, it doesn’t make people die just because of bugs in a consumer software. It’s not a big deal. Let them fix it, and deliver any update that they think is best to prioritise, and if we disagree, we just keep calmly report it to them until they fix it.
The more I play, the more I realize ATC seems to have gotten even dumber since the last update. They were bad before, but they seem to have gotten worse.
altitude assignments have gotten worse
Ground control instructions sometimes only “Taxi to XXX via taxiway”, without any instructions
ATC assigning approach right after takeoff when you’re still 100+ miles from your destination
ATC assigning bad runways to land / takeoff, even though suitable runways are available for the wind direction
I think these are always been like that since launch. I find that taxi instructions are all depending on the airport. If you were taxiing in an airport that you never done before the patch, then the airport itself may have insufficient data for the ATC to use. A trend that’s common among auto-generated airport by the AI, especially small ones.
But I tried the ATC ground control on custom handcrafted airports, and they generally give correct instructions.
Altitude assignments have always been bad. Probably something to do with how the navdata and their constraints in the STAR. So incorrect altitude constraints in the STAR, the ATC will read the wrong data and give you the wrong instructions.
That’s just it. These are airports I frequently fly out of. KAPF, KOPF, KORL, KPMP, KEYW, and MYGF are all airports I’ve been flying out of almost daily for months. I’ve never heard this lack of specific taxi instructions until the last patch at any of them..
But other times, it gives me normal taxi instructions.
Can’t tell you how many times I’ve slammed into the Sierras traveling East to Reno’s 16R in bad weather…‘Please descend to FL85’…OK Wait…Wait…Wait…THUD! Now, I ignore ATC
I can say for example KSEA handcrafted isnt even close to the real thing at all..
KBFI missing the museum of flight and weird names for aircraft companies on buildings.
This week I was doing a 20 mile airport to airport training flight. (about 600’ amsl)
ATC told me to go to 5k’. I comply.
The airport is almost in sight and ATC tells me to climb to 11k.
“Please expedite your climb to 11k.”
“Please expedite your climb to 11k.”
“Please expedite your climb to 11k.”
“Please expedite your climb to 11k.”
“Please expedite your climb to 11k.”
I get a good view of the airport as I pass over it.
The training lesson I got was, ignore ATC.
IFR flight plans should have aircraft type and equipment. This would prevent ATC issuing commands beyond aircraft performance. (This would eliminate asking a C172 to climb to FL 420.)
Another one I’ve noticed since the update that I didn’t include in my list above…
ATC: "Please acknowledge" or "Did you hear my last transmission?"
Looking up the list in my ATC windows, they told me NOTHING.
This is a new issue since the last update as well. In almost 600 logged hours (likely missing a lot from the previously broken log book), I’d never had that happen before.
Now, I ignore ATC