Surely #5 and #23 should be combined - and potentially also combined with #10 (Dreadful performance)? These must all be effectively the same thing - albeit I get that there may be a number of fixes and improvements to be made, but that’s 3 slots out of the top 24 taken on the same issue. Also if the votes are combined, guess what jumps up to number 1 on the list…
Also #12 pxelated clouds - “Under Investigation, WU III”…which was a couple of weeks ago??
It does feel like sometimes these aren’t proof read before they go out and own goals like these just provide fuel to those who want to point the finger at Asobo
Nice to see the “asap” for the performance issues after SU3. A sentence about this in the text would have been nice. Even if it is just a repetition of what has been communicated before (we are investigating, considering a hottfix). Not everyone reads every news and announcement and it would be certainly reassuring for many to hear again that there is focus on this issue.
“Dreadful Performance” has been there since launch, so I presume they’re using that item to track overall optimisations. It seems they’ve got something planned for Summer 2021 (not sure if it’s DirectX 12 because that’s been moved to a more general “2021” release), which probably is not related to the 188.8.131.52/Manipulators issues.
Would’ve been nice to have a more detailed report on the Performance issues to ease some minds, nice to see it listed as “ASAP” in the Snapshot but a little extra goes a long way.
Yet again the opening paragraphs are just severely lacking in actual information on any of the points in the Snapshots, this is long past needing improvement.
I still find it incredible that the immersion breaking “Horizon Line visible” is not even started yet(?!?!)
Still no VR Wishes Snapshot…
VR Bugs Snapshot hasn’t got much in it when there’s much more in the VR Bugs Section…
I do like the more detailed Snapshots release scope, but as ever with software coding priorities change and sometimes drastically, all it serves to do is get people exited for an update then they’re left frustrated when things don’t get fixed/introduced as they would like (see Contrails, GARMIN in SU3).
Ultimately though the “Voting System” is highly flawed, it needs replacing and it needs Asobo to take notice of the major issues of their Sim and prioritise accordingly and at the same time take more notice of the Bug Sections in this forum. Prioritising via Votes is NOT the way to improve this Sim.
Would you rather have developers spend time fixing the bugs or pleasing your mind by giving you every intricate detail of what they’re doing every day?
Keeping the community engaged with what’s going on is a luxury we are granted. They could simply close the door and continue without us. Which I’d rather have than the way this forum is heading - its worse than the stock market!
MSFS has a much more transparent and informative dev communication than any other flight sim! I really appreciate that they listen to feedback and the improvement in this week’s feedback snapshot is a good example of that.
Naturally, as with everything, there are always room for improvement, but these weekly updates and the Q&A sessions are much appreciated!
This is also good news that I hope people noticed:
“We have expanded our SDK Team this week by adding a new tech QA and an engine programmer. They will help provide more features, bug fixes, and direct technical support.”
I guess they will continue working on it and the OFF option is a temporary solution. I’m flying in icing conditions almost daily in real life (on a suitably equipped aircraft), I’m fine with no icing effect at all. No icing effect at all is pretty close to reality, 99% of the flight time in icing conditions there might be a little bit of ice building up on the leading edges which is easily shed by de-icing boots, its a non-event. Visually there hardly is any ice on the rest of the airframe ever.
I really hope they are working on ICAO phraseology as most of the world is pretty close to ICAO standard, hPa instead of inHg and correct transition altitudes. If not I hope they at least added options to the ATC system which makes it possible to tweak it ourselves to represent ICAO phraseology, I did that already in my mod (below), but there are too much limitations and missing features to make it 100% correct.
I added some Eurocontrol recommendations so its representing EU phraseology but the differences from standard ICAO phraseology are really minor.
Capt it’s a community driven voting system I mean unless the moderators interveen then if a topic gets enough votes it’s going to appear in the charts. Kind of reminds me when Ed Sheeran had 16 songs in the UK top 20 sick!
I think quite a lot of us are frustrated but this is by no means a reflection on yourselves as moderators, at least for my part.
I for one appreciate the feedback you are giving and also the opportunity you are giving us to air our views without shutting down a load of critical threads which seems to be the way some other forums react. Well done
I agree but it’s all in the Q&A streams which are great and getting better - outside of which is just bite size snippets. The partner series and discovery series are good but they feel like a product of marketing instead of a traditional dev diary which is the one part of the communications which is missing.
Official communications are always a balance between too much details and marketing.
Of course Microsoft doesn’t want to have the blog look like everything is broken and having open statements in the Q&A is basically the counterweight.
It’s still a company relying on profit from selling the sim and Marketplace content. This is why most of the screen of such a Dev update is nice screenshots/photos and Marketplace updates.
If you expect such a company to lay out all issues in broad for every potential customer, you’re naive.
I also think they could get a bit more in-depth on the current performance issues, but since I don’t believe this would speed up anything, I’m okay with waiting since that’s what I’d do anyway.
What a wonderful and positive response. You obviously know exactly what the issue is and how it should be fixed as you seem to think not much of the fact that MS is working on it.
You should certainly let them have the benefit of your wise council.
Potentially providing more information on what is causing the performance issues could help identify workarounds that would allow people to have decent performance before a patch release comes (likely in April at this point).
I’m pretty sure if they would have some workaround, they’d communicate it, just like they did on the flaps issue.
I guess the devs are the best source for this if they identified the issue and find a workaroumd without hotfixing. There is no reason to think MS/Asobo would hold back that information.