Just a quick thought here guys. I noticed, as you have, that issues tend to get buried in threads that started on a different subject, and it's making it hard to get to the root of problems. I'm wondering if you could start (for AS2, of course) a series of posts with the Subject being a specific issue that seems to come up frequently (relatively speaking), and pin them at the top so they are in plain sight. The first post of each thread, of course would be yours, outlining exactly what you need to see from the complainant (such as screenies, ini files, etc.) and a brief description of what that particular thread covers (i.e. swiftly changing clouds, another for weather that doesn't match what AS2 is reporting, fast changing altimeter settings, etc.). Hopefully, this would accomplish 2 things: 1) Organize the bug reports more concisely and clearly so folks know what to post where, and 2) enable people with issues to do an easier search before they post themselves about an issue, hopefully to cut down on duplication and maybe even find an answer to their particular problem BEFORE they need to post. Worst case scenario, they may get an idea as to what to try on their own rig before they post in that thread.An example might be that I had a flight this morning up the BC coastline where I had wx suddenly change (in an instant), the baro-setting changed 4 times within one minute, with the final change being 1/2 mile from the runway threshold, and where winds and wx didn't match my departure point actual wx (I don't usually have these many issues, and I wouldn't post on these unless I could duplicate them again as this is probably just a setting I was experimenting with). Given that scenario, I would post each (if I could duplicate it) issue in the respective thread, not all under one where it would be hard for you guys to disseminate it. In addition, I would read the initial post that would tell me (for that subject heading) what you needed (screenshot of AS window, view out the window of the aircraft, fsuipc ini file, AS ini file, whatever).Anyway, just a thought that might make it easier for you, and easier for us to get a grip on things. Most of the time, I'm seeing duplicate posts of some items that have already been explained, and for which there is some answer for. It is the READER's obligation to post his respective problem under one of those headings, OR to alert you to a new problem in the Subject heading. My feeling would be that if it is a duplicate post of something that has a heading for it already, then that post can go unanswered (the Reader has some responsibility to make this work as well!!).Thoughts? Go stick my head in a pail of molasses?? :-). Anyway, I'll leave it with you (look for my duplicate post on this further up the line tomorrow :-lol <-- just kidding)

Glenn,Thanks for the suggestion and for all your help over here. I'll tell you what happens. A number of users start posting and it becomes very hard to follow individual threads. What we find is that usually problems are user/computer specific and with everything in one thread it becomes very confusing. JimActiveSky Support

Ahh, ok. I was hoping my idea might assist in decreasing those, but in the end, you guys know what is best. If you can use any part of the idea though - feel free, but I do understand if it doesn't work for you :-). Whatever works :-hah.