Just a thought but what about in the xxxxpatch feedback threads, limit responses to like 256 characters. Enough to report an issue but not enough for paragraphs…There are others areas here to expand on things.
The feedback threads start out good about issues…then evolve into bashing Asobo/Microsoft…or people bashing each other because one person doesn’t have any issues but the next does…Like I said, there are other threads for that…But feedback should focus on feedback about an update…
Imposing a limit would focus more on feedback, let users scan issues quicker and even better, let the mods/developers see the issues clearly…
I think if Asobo posts more frequent status updates- even if they’re just announcements and not open for discussion, that will calm a lot of nerves. The problem with Zendesk is the bugs disappear into the ether and we never know what’s going on behind the scenes.
By posting an update or at least some kind of “we’re aware of the issue” will diffuse a lot of the uncertainty and accusations in the first place. What they’re doing now is too little, too late.
Its a good idea, but we already have the zendesk which is the surest way to catch their attention.
Discussing here doesn’t always guarantee that Asobo will notice.
The devs probably use an issues management system (I think its actually called zendesk) which feeds into a triage team who confirms the issue, and then forwards it on to the appropriate group’s in-tray, and they just work through a prioritized list of things to fix.
IMHO, It’s best to keep raising zendesk reports. I suspect that Asobo’s whole flow of issues management is probably managed via zendesk.
They use Zendesk for the communication with the outside world but probably a different issue tracker for internal use. The problem for us is that we cannot see if a Zendesk issue is being worked on, or is finished or rejected or (probably very often) a duplicate that was already reported and somehow ended up the internal process.
Open an insider program, let the general public have early access to the updates. Let us take some load off of them and do the testing for them. It’s free labour from the community plus it exposes their patches and updates to various different hardware specs and configuration and being used by people flying the sim in completely different ways.
Not letting us test for them is merely doing testing in a controlled environment with a specific hardware and specific ways of flying. They can pass all these tests in a lab, but they won’t be able to understand the impact to the general public when it’s fully released.
At least having an insider programme from the general public to test it for them. Reporting early bugs will allows them to have a general idea on what would happen if they roll out the update, and have sufficient time to fix them for the general public release.
It also allows third-party developers to have early access to see how their mods will behave, so if there’s any issue, they can promptly get their mods ready for when the updates roll out for everyone.
There’s only so much the developers can do to test them. Let us help lighten their load by testing these updates and patches earlier than everyone else.