Spikes in the scenery
Working on FPS and stutters
You could RTFR to get the list
Some people are just complaining that their specific issue, which in their view is the most basic one, is not fixed soon enough.
Why not just sit back and relax and accept that Asobo will keep fixing issues in time (and undoubtedly will cause new ones, because there’s lot of untrodden ground here) and give it a priority according that they think is best.
It’s all a matter of what they are able to do with the people they have hired.
And don’t tell me that they didn’t deliver magic.
The problem is, if you have 10`000 of beta testers you would have the same ccomplaints over and over again. But the devs can only focus on some issues with every update. Thats why betatesting is always limited.
I think the way they chose now is a good one. Having a few selected ones that know what they are doing with specific topics to test. Plus the additional 300 randoms to have a wider variety of systems.
If you let in 10000 "average joes" you would get 10000 bugs reported that are already reported and on the list and the developers have more work to filter out the things they want to fix in this update.
Beta-Testing is always done in a very small “circle” of trusted and known users.
Everything else makes no sense.
Its not that the testers are privileged, they just proved that they are useful and trusted to give accurate feedback. Basically, Beta-Testing is work and not just having an update 2 weeks earlier than others.
I was in many Beta-Teams in the Flightsim industry and believe me, its not always fun, its real work if done right. So trust the testers and the developers that they know what they do and that there are multiple reasons to not let thousand of unorganised individuals in the tests.
Yes, I look forward to the correction of the 1 degree lateral drift error as it pertains to turbine overcompensation, insufficient fuel flow, air temperature, rudder deflection and wear and tear on the landing gear with a 60% prop feather and the dew point at the outer marker on a Tuesday. None of that means anything of course but even if it did this game will be the same slow, clumsy, unreliable mish mash of bad decisions it always has been. At some point you have to ask yourself, are you talking to the right people or do we need more pragmatism here?
It is complicated, because besides what you write here, there’s 10.000 others reporting other, and in Asobo’s view more important issues. They will first fix the most important things before they can fix in their view more minor issues.
Looking forward to the testing. Will do my usual flying about and having fun whilst looking for issues that are new and following the guidelines from MS/Asobo. Will see how many of my world tour legs I can fit in over the weekend.
Just picking up on a few things from the posts above and more generally:
To the doubters I’ve seen elsewhere about whether people will raise bugs etc or just want early access - well last time the private forum area was a wealth of good information exchange between many of the 300 testers - I didn’t count, so don’t know exactly how many - we spotted a bunch of bugs - sometimes hard to tell if they were new or existing, but we raised them anyway.
Of course they did - they wrote the code in the first place - easy to throw rocks though. Plus the point of this kind of testing is to find some of these issues, so not sure why you are unhappy about it - surely this is progress?
This builds on the last test where it was only us 300 randoms - so this is the next evolutionary step. There are handpicked testers, based on a number of different criteria, as well as us randoms.
If I can help a little bit to make everyone’s sim a bit better I’m happy to play my part. So I’m happy to do my “work” and be unpaid - can’t say I’m going to think it feels like work. I’m thinking I’ll have a lot of fun, and if I can help out with some of my time to explore and investigate and capture some bugs in the process, I’m willing to do so - and I’m going to bet that is exactly why most people wanted to sign up for this. It would be interesting to know if this time around the testing was more oversubscribed than last time. I bet more - because more people see this as a useful process they can help with.
You’re assuming that because they haven’t fixed it they don’t know about it - clearly not the case given all the feedback etc. They are juggling priorities - their priority list just isn’t the same as yours
Not commenting on the NDA, but the private forum was really helpful last time becuase we could share info etc and it would have been massively distracting to have questions and input from others not able to see the same things as we were. I wouldn’t have a problem opening that forum up after the test though (it would certainly kill a lot of nonsense that has been written and assumed about the apparent inpetitude of MS, Asobo and the testing population).
Having the branch public and having NDAs are not the same thing. This is a closed beta - doesn’t seem to be about load or scaling tests that you would use a public beta for. The areas of the sim to be tested are set out for the testers by Microsoft. NDAs - don’t have a view and not bothered if there is one - other than that we can’t refute all the nonesense that is written in these forums about the testing!
I already joined the insider program and then left, very much on purpose. I was not a fan of some of the things it was doing to my system, so as much as I would like to participate in this and future MSFS betas, if it takes being an “insider”, I’m gonna have to give it a pass.
That’s the reason why I am holding back at the moment as well. I would like to have an opt in and out so that I would be able to choose when to test and when to play ‘current school’. Maybe Asobo will add such a feature in the future.