Geeze, guys, c'mon, please. ;-) [And joemc, this is not all meant for you.] But honestly, to address it in general, what good does tearing apart a beta do for anyone, or everyone as a whole?? I know there are ego strokes involved for the people picking it apart, since they get to show how much they know or how great their eye for detail is, but who else does it help, considering the alarm that kind of thing stirs?? No, I do not perceive it all, especially a few pages back, as benevolent, well-meaning bug reporting; everyone knows by now that we have a GREAT beta team, and we've said before that testers or developers mix and match various, often very old, versions of different gauges or features or whatever, for reasons that probably only a developer and maybe a veteran beta-tester would totally understand.
The things pointed out in the last few pages do not mean "uh-oh, Aerosoft doesn't even notice the wind is saying 200 knots!!" (I've not even looked at the pics in question, but whoever mentioned a wind of 200 knots... first, are you sure that wasn't the wind's *heading*? Second, if it WAS where speed should be, if it was reversed or something, does anyone genuinely think that that kind of thing would continue on not ever recognized?) This is not meant as a criticism. It's meant to be informative. But we've got a great beta team, some real experts on it, and have shared several times info such as the things that are causing the road-blocks, w/ the autopilot or Navigraph's best implementation or whatever. And something like the ND, in any given pic, might possibly even be months old (literally), a place-holder put in there by a lone beta tester to compare something or get rid of an ugly, test-string-infested "experiment."
And what some may be thinking, that the very *fact* that there would even need to be a place-holder... please (not sarcastic here at all), really, go look in the SDK and merely begin to develop even a single basic gauge, some kind of rudimentary digital readout of your favorite information, and you will absolutely get a glimpse as to why such screenshot "errors" happen, why they do not mean that the sky is falling, and why the fact that issue X or Y is in some screenshot really is not good cause for certain reactions, especially the "yelling 'fire' in a crowded theater" response.
In fact, you might even think of it like this: if you see something BIG that's wrong, like absurd text in the FMA section, there's a reason for it, as we're TESTING things, things that can only become coordinated in a stepping stone fashion. (What I mean is: developer A implements something, B adapts and adds, then A adapts to THOSE modifications by B and adds still more, and so on, w/ the need to go back and look at some weeks-old interaction probably inevitable.)
Don't get me wrong, because I personally want the minor things pointed out. The detailed eyes are appreciated! But big things... they're actually most likely to not be issues. Maybe judgment can be exercised in "reporting" such bugs, after considering whether it really is likely that both developers and beta team members probably would not notice this kind of thing. It'll save you time too. But if you think it likely to slip by, by all mean, please report! (But recognize that we're beyond the phase of "okay, we'll add that feature before release.")
But to start with the piranha behavior already...? Personally, I think it makes a developer less enthusiastic about sharing anything at all. And in fact it may reinforce an exhausting, enthusiasm-dampening, time-consuming, and dreadful reminder on this end: many users will never be satisfied, and worst of all will sometimes not even be *mildly* content, until the absence of their favorite rivet has been addressed, the rationale for its absence shared, then discussed at length, at large, and until the rivet-haunted simmer has elicited validation and support from other users that it really *is* a big issue, and that you other simmers should be unhappy with it too. Have we not all seen this time and time again. I was just now reminded of all of that kind of thing. Makes me want to take a longer lunch! (But I won't.)
"Would they otherwise miss this issue" is the key question. Because, please consider, whenever any beta screenshots are posted, they're probably intended to appease a forum's voracious appetite, and give a *general* idea of how things look. You can especially assume this if it just says [paraphrasing] "look how nice these pics I'm posting are." If anyone honestly thinks we wouldn't know the difference between altitude hold and airspeed hold, whatever it was, how in the heck do you even tolerate following a beta's progress at all? Seems like it would be very stressful! ;-)