Community bugtracker is up @
il2bugtracker.com
Many thanks to
albx who set it up and purchased the domain name.
The tracker allows voting for bugs and required features that would help the devs to get priorities right. E.g. no performance improvements at the expense of CTDs
Please register and use it. The idea is to test it now and get ready for the upcoming patch when it can become a very effective tool to speed up the development process.
Admins are wanted. If you criticise CloD this is a chance for you to make something useful
Quote:
Originally Posted by albx
il2bugtracker.com up and running, now you can register... I need to configure the categories (graphic/aircraft systems, etc...) who wants to help? and who want to admin? |
Here is an old list of some priority bugs.
http://forum.1cpublishing.eu/showthr...=priority+bugs If you support some of them please enter at least 3 most important from your viewpoint into the tracker. It will not take long.
I will announce the tracker at sukhoi.ru and e-mail a link to this thread to luthier.
The system is still being tested please report any issues.
Mods, maybe a sticky if you do not mind?
---------------------------------------------
HOW-TO USE
- register and login
- select Cliffs of Dover
- in the top menu select "Issues" to view list of issues and vote for some of them
- to add a new issue select "New issue", then chose tracker type: bug or feature request, title, description, category (important), etc.
Do a search before adding a new issue. There is a chance that similar issue already exists and many people voted for it already. Then add your vote to it.
UPD. When registered change settings to hide your email, otherwise it will be visible if you click on username in the issues list. It can't be changed for default.
Please use a guide at the link in Banks' post below to make sure your report is useful and will be understood by the devs correctly.
Quote:
Originally Posted by 41Sqn_Banks
IMHO we need a "guideline" for bug reports, e.g. https://developer.mozilla.org/en/Bug_writing_guidelines
We really need quality bug reports, especially as the developers are not part of the system, i.e. they do not interact with the reporter, they only read the report.
A low quality report might be written in 1-2 minutes, but the workload for the admins or developers are increased considerably. If one wants to report a bug that he things is important he should take the time to write a high quality report.
For aircraft system this includes researching the subject and providing evidence. There are so many bug reports on aircraft systems in this forum that a simply wrong and not or bad researched.
For game bugs this requires a step by step instruction to reproduce the bug.
The reporter has to provide (depending on type of issue)
- step by step instruction to reproduce the issue
- screenshots to display the issue
- mission files/tracks to allow easier reproduction of the issue
- documents/sources to proof the issue |
More on how to create a useful bugreport (based on ArmA2 example)
https://dev-heaven.net/projects/cis/wiki/CIT
To Spanish speaking users:
LUD kindly offered his help in translating your reports if you do not speak English. Please contact him via PM
http://forum.1cpublishing.eu/member.php?u=25029