Maybe it would be better not to clutter the tracker with stuff where we know that is already in the works.

great stuff
it will make a great visibility to community asking about bug and feature...
don't forget to vote :)

But how do we know?

I don't see the general Flight Model issues listed. I don't see the Memory Leak issue listed. Well we know the patch is supposed to sort the memory leak but shouldn't it be listed? As for the FMs it would be nice to know if its WIP or not being looked at yet.

Please feel free to add anything you consider important. Please make sure you provide enough supporting data and evidence though.

OK. I've added Feature #84 ref Spitfire 1 performance and links to data on the Spitfireperformance website.

So, If its Spitfire 1a performance that bothers you go and vote for it.
http://www.il2bugtracker.com/issues/84

Done!

Also went through all the issues and voted for those that I hope will be addressed ASAP.

Hopefully that wasn't all of Luthier's activity on this bugtrackersite.

luthier:
registered: 04.04.2012
Last login: 04.04.2012

as luthier registered and use it ( making in progess status )
could a administrator sticky this post please...

if Luthier or B6 use it often, it will show a great interest for their community ( us ;) )

More people should visit the site daily, and vote on the things that they find important...really the only way to get the attention of devs as to the priorities, as felt by the community. :grin:

there are some problems with how this bug tracker is implemented at the moment, and this makes it less likely to become a productive tool:

1) the site needs an easy way for non registered people to vote on issues, similar to the poll system used on the 1c forum. many casual visitors who want to quickly provide some constructive feedback wont bother registering. if you want to force people to register to post a new bug, or comment on solutions implemented, fine, but this should not be the case for people voting on the priority importance of certain fixes

2) there is no classification system or categories for bugs and problems reported, and as people post a mix of minor specific bugs and others that are major problems, it just becomes one giant mess that people like luthier will NOT spend hours on sifting through to find a few important snippets that might be relevant for them. categories need to be used for:
- broken important elements that affect normal gameplay and "normal use" of the sim (eg game crashes under specific conditions etc, like the multiplane formations and dreaded 30 min play bug some experience, constant micro-freezes and stutters that prevent normal gameplay for some, etc..)
- missing or incomplete important features that affect gameplay and "normal use" of the sim (lack of dynamic campaign engine, lack of cloud and weather changes, missing coop features, etc..)
- aircraft performance issues (a prolonged technical debate with for/against information that can go for months or years)
- minor specific bugs and omissions, eg landing gear, lights, flaps, control bugs on specific plane models
- general improvements in "ease of use" issues and making it more intuitive and user friendly to use ( like improvements in the mission builder, control setup, the need for the release of a SDK so fans can start working on a dynamic campaign themselves if this is not forthcoming by 1c, etc..)

3) there also has to be some weighting and prioritizing in importance of feedback. with the threaded listing of responses by date of contribution, right now people posting their "opinion" is not differentiated from a detailed factual list of information posted by a more knowledgeable person

however well intentioned, in its current form it is unlikely to a productive tool to inform luthier and Co of the fixes that are most urgently needed.