Let's get these bugs squashed so we can all go back to enjoying the incredible work of Asobo!

And so, in the spirit of bug squashing and greatly improving the default aircraft, I propose we set up a bug-tracking subforum for aircraft, with separate threads for individual aircraft. The first post in each aircraft's thread can contain all known issues along with the status of that bug and whether or not it has been reported to Asobo via the Zendesk system. I know something vaguely similar exists in the forums over on the Microsoft/Asobo site, but the focus on identifying bugs (and other issues) with tracking isn't there (as far as I know). This will help reduce clutter in the main forum and hopefully serve as a reference to the development team at Asobo. For example, I've seen (and experienced) many issues, inaccuracies and omissions with/from the Citation Longitude, but user reports are scattered across at least five forums on four websites, and it's unclear what bugs have been reported. I'd really love to see this aircraft and all others in their full glory, and I think we as a community can facilitate efforts by Asobo to fix the planes. I'm willing to head up the Longitude subforum and welcome any/all input from other users and (of course, perhaps especially) RW pilots.

In regards to the aircraft tweaks that people are already putting out, the individual aircraft threads can also serve to organize tweaks, at least until the issues have been addressed by Asobo. Community mods and liveries can also be posted in the individual threads. As the outstanding issues are gradually resolved, the aircraft forums can transition to discussion and implementation of "non-mission critical" items, such as expanding the capabilities of the G1000-5000 suites (on-screen charts, sophisticated modeling of electrical and hydraulic systems), failures, etc...

Thoughts? Feel free to torpedo this idea if something similar has been proposed (or if the idea plain sucks). Just trying to help make this sim into something truly amazing.

-Elliot

I second the idea.

Well it would be an organized effort which I like. Right now things are thrown around willy nilly and it's very difficult to finds things again since the forum pace has increased since MSFS launch :) 

9 minutes ago, charliearon said:

?

1 hour ago, Eman said:

Thoughts?

Given the torpedo has been fired, I have another possible suggestion...just a thread dedicated to each aircraft for this purpose and then maybe the mods would pin a master thread with links to each of the aircraft threads. That way, we don't have to mess with the forum structure, but we'd still have quick access into the threads. The only problem I see is that it isn't possible for users to continuously update the top thread with a list of known/reported issues. With enough volunteers, it could be possible to maybe temporarily assign a mod to each aircraft, or some kind of super user that CAN edit the top post in the thread as issues are identified.

My last pitch is that this could be an effective means of managing what looks like it might be a more robust community of people willing to open-source improvements and bug fixes in default aircraft. For example, I've begun working on the CJ4. I'd love a way to collaborate with others, for example, I need to recruit a developer to assist in making some changes to the HTML/JS for the FMS, while I work on engine performance. And obviously the Neo project is another example, with nearly 5000 people in that discord already working away on it...

Just another possible approach to this...

I just use the forums Search function if / when I need help

All you have to do is come up with a standard tag for these threads (e.g. "Acft Mods") and use it, and then anyone can set the search filter to sort through them. 

We don't want the forum structure to become a convoluted labyrinthian maze worthy of an adventure game, so we avoid the well-intentioned but problematic calls for creating even more subforums.

 

17 hours ago, RustyFlyer said:

?

I was torpedoing the OP's idea as stated in his last paragraph.