I’m really tired of topics “Asobo, stop doing this, do that”, like if those people know better than the MSFS team how to make a Flight Sim.
We vote on the wishlist forum what we want, and Asobo takes those lists, check the votes, how much time would it take to do it, if there are sinergies with other task, etc etc, and they do the scheduling.
Maybe they are not doing it the best way posible, but we can’t know if there is a better way to do it.
If you are tired only because of those kind of topic, then how tire must be those many facing bug after bug? I think they have more reasons to be upset than you.
Despite I support your message don´t forget we are customers and we have the right to complain. A different thing is that complaints are not addressed in a civilized way or that people insist too much on well known issues, but I think nobody should stop to rise new topics if things are not working and till they are fixed.
This is internet, true, but we are also mature enough to apply some filtering ourselves and get the message behind the complaint rather than the way the complaint itself is written. I personally use the helpdesk and I try to be constructive, as this is proven to work well. But remember the forum is a way to talk to developers too, and they also get the messages and the customer feeling. That also make things change.
Hello Fellow Simmers. After doing a some research into what it takes to create even the most basic Aircraft Livery or Ground Object for MFS 2020, i’m offering my sincere apologies to Asobo Staff for comments Posted by me.
The complex process’s involved in building our MFS 2020 virtual world is beyond my comprehension but after doing a little research i now have a ‘Layman’s’ insight into what’s involved.
In my irate post reference was also made to the Founder of Microsoft to whom no Apology is given.
Thank’s Asobo and Kind Regards from Thom in the Sad Old Dis United Kingdom.
All - Just as frustrated as the rest of you. But, I really feel, part of the problem as I see it is there is not a standard fixed data gathering process in the Zendesk system. I will try to outline something here. Oh, yes, I perfectly understand in today’s economy, many of us possibly are not able to go out and get or build the hottest machine so we can fly this simulator in full form. So some of us are “making do”, my gut supposition is, many of those folks hardware just cannot run it properly. So the bug reports provided by folks, do not take into account what lies under the hood so to speak. Will that have a bearing on if the simulator can complete a flight, open a door, setup an ILS properly, engage the AP system, yes, and the more complex the simulator becomes, with more places to start/end at, the problem becomes more pronounced.
The bug gathering system, should either take a snapshot of the hardware used or specific hardware items should be required to be entered into the report. Are all the problems hardware related, NOOOOO, they are not, but my guess is some of them are. If I need to move 5 tons of rock, yes, I can do it one rock at a time, or use a wheelbarrow, or get me a small tractor with a loader, or a track hoe with a huge bucket, which would make it go faster still. What explained is, various ways, but problems will occur using any of the referenced tools above, the larger the tool, the less physical problems I am going to have. If the pipe is big enough, I can drain the panama canal.
Yes, there are bugs in some of the planes and processes, but, as stated above, some of those “supposed bugs” might be an inability of the machine to process the code well enough to make it run properly.