I wrote weeks ago that the “spiked terrain” issue might be much more serious than we first thought. In order to fix that they not only need to debug their coding, but may also take lengthy time to reconstruct terrain for the whole world. This can explain why they delayed this bug fix for so long until World Update 3.
If indeed so, telling us truth would have only made us more understanding and patient, and in the long run help the development team more (people will prefer slow but robust updates to quick fixes, thus buy devs more time).
You are right about nobody can force transparency here. But at least I should be honest about my opinions as a paid customer. Expressing discontent here instead of writing a negative review on Steam Games or so is more constructive, don’t you agree?
Honestly we’ve waited for quite a while for the next world update. Waiting a few more days won’t kill us. I suspect they tried to deliver this on 11th until the very last moment but it just didn’t work out. Cut them some slack people, Asobo is made up of humans and things don’t always work out the way we’d like.
Nice sarcasm, suits you well. But they aren’t spikes, those rock forms are hundreds of metres across. A spike is typically one outlier point with the current smoothing algorithm bring further points (ground) up around it.
Yes, I’ve had almost 50 years practice at sarcasm. Really starting to get the hang of it now.
But anyway, the point stands that application of a filter to flatten out spikes isn’t going to be an easy fix, as without some major coding it’d flatten out spikes that aren’t spikes. Plus it’d just be a band aid, much better to find the root cause in the first place.
The problem of your argument is: you Asobo defenders are no different than those Adobo criticizers (or even conspiracy theorists) in that you both know absolutely nothing about what really happened.
Without even the slightest knowledge about what’s going on, how can you expect others to agree with you? What if the truth behind delayed bug fixes and planned update was not at all what you speculated?
You may wonder why we care about transparencies about MSFS issues or delays at all? The answer is simple: first these things impact us, second we need such information to validate our future MSFS investments (like a new VR headset or PC upgrade).
Yes it’s not a simple fix, but it does like a mesh data problem which calls for a data science solution which will remove the majority outliers from the data with no adverse effects (I’m a software engineer/data scientist by trade and this is my bread and butter).
Thank you for taking the time to post your response. Due to some technical difficulties with the forum on the day in question I was not able to see the announcement made by Angernerve shortly after the discord post. When I returned the announcement was very much buried in a sea of posts. I therefore eat crow in the face of my own incompetency as there was no delay in the announcement. So I’m retracting what I have said and leave with these words. I need a beer.
If I tell you that my first experience of flight simulators coincided with the release of the BBC microcomputer in the 1980’s then you might also believe that I have a limited knowledge of these programs. I can honestly say that no other flight simulator team have made anywhere near the same attempt at communication and customer response than this Asobo MSFS group has. This very comprehensive website is proof of that. While I have been very critical of Microsoft software updates in the past, as have most users of Windows operating systems, I feel we need to cut this team some slack. I was looking forward with great enthusiasm to this update, but it won’t hurt me to wait a little longer. I think we should temper our disappointment at the delay, and bear in mind the difficult current working environment. None of the other systems I have operated have attempted to provide such comprehensive and regular no-cost scenery updates, so let’s chill out for a little longer. I am sure that any future delays, as there will be inevitably, will be communicated more successfully.
I know that river, but didn’t know the name of it. I love driving through the Goodwood estate to nearby Midhurst. Hope they get this right, I fly exclusively now in VR in the simulator.
To me it’s a sin not willing to communicate with your paid customers, show enough empathy, and try best to help and ease their concerns.
I once worked as a phone support agent. You can imagine how hard that job is: facing people’s frustration everyday and sometimes got abused. But instead of hating my customers, I learned to understand them more and realized that almost all of them expected and deserved my empathy simply because, hey, no one would like to waste time over the phone seeking for support. So their frustration and concerns must be true, and if I didn’t show them empathy, not only I hurt my company, but I treated our loyal customers very unfairly. In all, I respected my customers much even without being paid nicely then.
The same logic applies here: almost all MSFS issue complainers deserve some empathy from Asobo, because their frustrations are very true. How much you can solve the actual issue is one thing, showing enough empathy and respect your customers is another. Locking the whole thread where helpless customers could at least discuss about the unsolved issue was extremely arrogant and unhelpful.
Someone just commented that Adobo’s customer support was best among other game developers. Really? Just compare them with those third party MSFS addon developers. I myself knew much more about why my $5 Central Idaho Bush Flight addon had weather setting issue, than why my $199 MSFS suddenly had spikes everywhere, especially near where I live. I almost always received Addon developers’ replies over my questions. But here my detailed issue ticket was secretly labeled as “resolved” with no information given and nothing improved then.
They do deserve empathy but asobo also need to make sure the continued repetition on the same issues over and over doesn’t drown out other useful discussions. The key issues are known, acknowledged, understood and being worked on. Repetition adds nothing at this point.
Locking issue discussing threads won’t save much resources. Instead it forced all helpful COMMUNICATIONS among concerned gamers to suddenly end. This means many people, especially new gamers will have a much harder time to check issue updates, find workarounds, or be notified about the successful resolution of the whole issue.In the end this will come back to create more unnecessary issue threads where much less answer and help could be found.
An issue discussing thread is more like a user support community of its own, and almost always help the whole “society”. Too bad people with power tend to see these communities as threats rather than helpers.