Community bugtracker is up @ il2bugtracker.com
 

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 :grin:

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 :)

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.
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

Wow, awesome. This is MUCH needed and should make it quite easier for the dev team :)

Thanks!

Made it sense to post bugs before the next patch is out? May be some of them are (hopefully) already fixed.

ts ts ts Kodiak:
Thx alot, for choosing redmine! That´s what I use for Development of an ERP and is very effective.

Ah OK overseen this. :rolleyes:

I think it is better to test it now to make sure it works when the patch is ready. Maybe we manage to make luthier to officially announce it in the patch thread too if it works. We still need to configure some plugins, get more admins, etc.

Can you become an admin/manager to help with managing it? None of us is familiar with this software :) E.g. we need a voting system installed somehow :)

Ok registered ;)

I would trie, no experience in voting system though.

Got an e-mail from luthier:

Translation:
"Good afternoon,
Thank you, the tracker is very welcome!
I am not very sure about Redmine system as it seems it is not exactly for bugtracking - but we will watch it!
Regards,
Ilya"

Excellent stuff, my thanks to all involved :)

good.. but we can change it anytime if another system can be suggested...

Excellent, works very well.

I shall ask next time if they have any preferences.

ok ;)

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

It looks like at dev-heaven they have votes showing in issues list on the right-hand side https://dev-heaven.net/issues

hhmmm... is this a free plugin or they made it for them? need to discovery...

S! Added to the 1st post of the thread.

Thankyou Ataros, I hope the dev's will use the bugtracker. I've posted one issue but first time I entered info the new issue form screen refreshed & info disappeared. The second time I entered info the form completed correctly, however, there are now 2 versions of the issue on the DB. Could you look at the setup with a view to correcting this problem. :)

Im in. Thanks for the people behind this. This community is awesome.

S! Lud

Ataros - I still have the OpenOffice xls file with the bugs/improvements of my old topic re. "priority bugs", let me know if I can help.

Cheers,
Insuber

for voting, take a look at this:
Voting Plugin for redmine

Only compatible to redmine version 1.2, installed is 1.3.2 still one could give it a try

Thank you. I do not know if someone (I know nothing about web databases) can import it into the tracker database and then users will vote for these bugs again? In case some bugs were fixed already they will get no votes and then can be deleted in some time.

Maybe it makes sense?

I tried it, crashed redmine, it's for an older version 1.2, the one i'm using is the latest 1.3, we need to wait if he will update it or need wait for me to figure how fix it :grin: but i think we can live some time without a voting system, ok?

or we need to take a look at it and update the voting plugin to be compatible to 1.3, I´ll check on this.

Or maybe revert to 1.2 if it is possible? Just an idea. It is up to you.

Great stuff.
I will upload my beugreports, when i have a little time.

Falke, Banks, Kodiak and luthier :) got admin rights now.

If anyone else is interested please let albx know.

Yes, luthier registered to the system himself.

@Ataros; I am publishing and mantaining a Spanish translation of the guidelines for reporting and tracking bugs here: http://sg1.es/foro/viewtopic.php?f=54&t=3267

Ataros, shall we transfer the already mentioned bugs to the Tracking system? Then, i would link the bugreport to this forum for then we wouldnt have to transfer all the graphics (screenshots etc.) as well.

The devs changed status of some bugs and commented on them.

Important!

Please stop double-posting the bugs and make sure you select the right Category before posting. If luthier has to reject double posted tasks and assign category himself this tool will not help development but will slow it down instead.

Let's make sure we do it right!

I would leave it to everyone to decide unless the devs ask us specifically to do or not to do this. If you feel like you know about very important bug that you want to be fixed ASAP post it. But do a search to make sure it was not reported earlier and fill in Category.

I think it is possible to give links to this forum for pictures, videos, etc.

I think we got a very good communication if this thing will go ahead!! Please, everybody be patient. Thanks to Ilya and the team for updating it...

The system reports "page not available" if you send a bugreport thats why some were doubled..

Please check bugs with status "feedback" and provide more information. As in one example devs have to comment:
See Kodiak's guidelines above before posting please and be very very extremely detailed.

albx, can you check what can be wrong?

When I posted my 1st test bug it appeared only once. Maybe Java must be allowed in a browser? (I did allow it)

UPD. luthier wrote that he also has a bug-report :) : every time he posts there he gets a message "cannot be found" smth. but the post is saved correctly. Same issue.

don't know, need to check if is something else...

luthier has same issue, see UPD. above

JavaScript does not matter...

Nice!!!!!!!!

I'm sorry, but probably did something wrong: I registered as "Artist" and then tried to login, but was rejected with "Invalid user or password". If I click on "Lost password" I do get an email (with my username "Artist"), I can change my password, but am still rejected in the login screen.

Tested with firefox and chrome. Cookis are allowed and set. Feel kind of stupid.

Artist

I suggest we have a project for every release.

Within on of those projects the incoming bug reports should be checked for being provided with the necessary information.
Only after being checked and being complete in terms of necessary information provided, a bug report should then be assigned to Luthier for nearer observation and feedback requests or status info concerning this bug report.

Otherwise dev team gets spammed and will soon loose interest.
Providing all necessary information for a bug report should be done by the community to get some workload impact off the devs shoulders.

Maby this is a topic which is to be talked about e.g. via TS / Skype?!

check for registration email first, activate and be habby ;-)?

Excellent idea - I have a bunch of stuff to report.

Suggestions for changes in issue categories:
3D models (cockpits and ext.) --> should include all types of objects and skins, suggestion 3D models and skins
AI and communication --> as is AI and communication
Aircraft performance and FM --> typically goes hand in hand with DM, systems and controls, suggestion Aircraft FM, DM, systems and controls
Aircraft Systems Errors --> duplicate Remove
Damage model --> visual DM is covered by 3d model, negative effects are covered by aircraft FM, duplicate Remove
FMB and scripting --> as is FMB and scripting
Graphics --> Graphics and visual effects
Interface --> User interface and menu
Online multiplayer specific --> Multiplayer specific
Sound --> as is Sounds
System/critical --> we shouldn't use severity as a category, better General
New --> Maps
New --> Singleplayer specific

Maybe we should add a own project for issues with the bugtracker.

Uups... there's something...
...in my spam folder.

Now I know why. :rolleyes:

Artist

You mean one project for every release version? Or one project for CoD and one for sequel (aka BoM)?

Agreed. I don't think we can enforce a high quality standard for incoming reports. Therefore only reviewed bug reports (confirmed, complete, ...) should be assigned to luthier or one of the devs. It is possible to allow only admins/moderators to assign a report to a person?

I would suggest one project per released version and correspondingly named. Makes it easier to keep trrack for which version/bugfix the bug or feature was reported/requested.

Yes, sure is!

I've seen that it is possible to add a new versions in the settings. Don't know if this is the feature you are looking for.

This should do it. IMHO reporters don't need to assign a issue. The managers/moderators could manually assign a issue or use the auto assignment by category to assign it to a certain manager/moderator that is responsible for reviewing it. After review it is assigned to luthier.

Please feel free to create one if you know how. Maybe we can get luthier's opinion on the categories there.

To me Preformance, FM and DM, systems and and controls are different. The rest I agree with.

is there a forum in the system? If yes, we can ask luthier there what is better for them and easier to use.

Created a forum http://www.il2bugtracker.com/projects/cod/boards

Great Alb and Ataros you got it managed that quick!

I'm looking into logs to see if there is something wrong with the error some are having reporting issue.

I have a newbie question....
How can i add a link to the description? The source file too big, i can't attach...

great work, thanks!

You may want to try to get it on airwarfare.com as some more people may read it there...?

Copy and paste the link. Worked for me.

Thx.

Wow this is great. Would it be possible to sort the list so that the bugs Luthier has commented on are divided from the ones that arent adressed?

I posted a bug/missing feature today & within 8 hrs Luthier has edited the report to indicate a fix is "in progress". I can also see from today's activity report that other bugs/features have been updated to "in progress", while others have been "rejected". I can at last see some of the work that is being done. :)

Not exactly what you ask, but If you clik on summary you can have an overwiew. And like salmo said, in activity you have also a good source of info.

You can also stalk luthiers profile to see his activities

Big Kudos for putting this up... It has been needed for a long time and what is needed to get it working is voluntary admins that reject duplicates and do a quality check before accepting the bugs if they are not filled in properly with steps to reproduce, system specifications and other details needed for the developers according to rules regarding how to file bugs... Otherwise Luthier will get tired of this very fast...

I have not worked with redmine, is it possible to add custom mandatory fields like "Describe background / Steps to reproduce / Your detailed system specifications" etc?

EDIT:

Here is how to set up custom mandatory fields in Redmine:

http://www.redmine.org/projects/redm...neCustomFields

+ 1

Could you become an admin please?

Then unfixed bugs have to be imported from the old project to the new one or not? It may become confusing for the devs to keep track of 3-4 projects.

Dev-heaven has a separate column for version #. Maybe they configured it somehow? https://dev-heaven.net/projects/cis/issues?query_id=30
Proposals for future are marked as NEXT GEN version.

Finally guys!

Excellent!

I've been promoting this type of communication myself earlier. I have a lot of good impressions from it by playing ARMA 2 and using the dev-heaven tracker :)

Will start registering well-documented bugs in the future. Youtube/printscreen are our friends :)

Long time no post mate. Really, I thought of you when I saw this and recalled how you promote the idea. But finally is here and with the devs involved. Good times.

Absolutely... We need some admin "forum" to set up the guidelines and policy's of the desired work flow for the bug reporting too.

Added the column "Zielversion" may be the translation is target version.

I've created a version (1.05.xxx), issues can now be assigned to this "target version", however my impression is normally used to define the version that should fix the issue. Maybe we can misuse is to define the version where the issue occurred?

Another thing for users that register on the site. Remember to hide your email address in your profile settings if you don't want to be spammed, by default it's publicly available as this is a tool that is often used internally in LAN:s... The spiders out there are fast ;)

I think that is a good way as we are not an internal team that knows which is the next version ;) As long as everyone knows how to use it. Is it possible to change the text to "Game version" maybe? As there is a lot of localization going on I don't know if that is tough...

Let's force everyone to use the English locale anyway so people don't get confused and start reporting in their native language ;)

I've added the current version to every post, but target version should be renamed, but i don't know how.

Ok seems it's only possible in the translationfiles:
--\redmine-1.3.2\redmine-1.3.2\config\locales
de.yml
field_fixed_version: Zielversion

en.yml
field_fixed_version: Target version

And if there is a new release we check all open bugs and assign them to the new version or keep them in the old version?

I have added the category as a required field....

just found that to modify some parameters in redmine I need to edit source files, so for any other issue or request please ask, ok?

You have admin rights now.

Here is a forum for tracker discussion. It is open to all users, but we need to keep it clean if we want luthier and BlackSix involved. http://www.il2bugtracker.com/projects/cod/boards

BlackSix has admin rights too.

Maybe automatically assign current version now, but after the patch make Game Version a required field? (to allow both versions to be reported)

PS. Game(target) version does not show as a column in the table now.

Full marks for this effort - thanks!

The key to success will definitely be quality control on the bug reports that get elevated. It can't be allowed to become more of a burden than a useful tool. Let me know if there's anything I can do to help.

I think we all can provide more information on some bugs to allow the devs better understand what is needed. E.g. I commented today on COOP feature providing links to Alpha's messages. http://www.il2bugtracker.com/issues/51

I think everyone (not only managers) can add comments providing more information on other bugs. If not please let me know.

In some cases if there is not enough information or evidence provided a bug can be rejected by the devs. Make sure you provide all the details, steps needed to reproduce the bug, images, videos and system specs.

Everyone is welcome to help!

Finally, after a looooong time I enabled the voting system... had to modify the plugin to make it working properly....

please report any issue you can find with the voting system.

Alberto

Is it right, that the devs can add a "In Progress" to a certain feature if they are allready onto it or maybe a "fixed" in the status of a certain bug?

That would be really awesome and everyone could stop complaining about certain bugs or sth. if they are allready fixed internally

Yes. I posted a bug/request about missing air-raid siren sounds. Someone else posted about missing Stuka dive-horn sounds. Both reports were changed by Luthier from a status of 'new' to status: 'in progress' :) He has also changed some requests status to 'rejected' & given a reasoning.

only the devs are changing the status, the admins (community members here) are helping in finding duplicated requests or fixing wrong categories. :)

And you guys here wouldnt bet what is rejected.. :)

That made my day.
 

Posted by Luthier on the bug tracking site:

"Updated by luthier 1 day ago
Status changed from New to Closed
Will not be changed. Engine model for AI is inherently simpler than that for the player. If we decide to make it more complex, there'll be a domino effect, and in any case there are more apparent game-affecting issues due to this than start-up.

Just assume that AI pilots have thorough mechanics, and yours is a lazy drunk."

Thanks for the community involvement Luthier.

Link for disbelievers: http://www.il2bugtracker.com/issues/13#change-13

For mods: I intended no offense in this post and if I did, please let me know. Thanks, Eagle

I assume that since it is possible to have an airstart it is at least possible to have a prewarmed up engine for takeoff. Hope they can implement that for the player. Or at least a pause before the other aircraft take off.

It's possible by script at the moment to delay the engine-start of the AI. Of course this is no solution for the average user. An difficulty setting to enable a prewarmed engine should be to difficult.

You can open 2 new tickets for this in the bugtracker if you want it happen.

Personally I think the delay should be a standard feature in campaigns, single player and coops without need to be scripted by hand.

The delay should be depending on aircraft type. E.g. the Blenheim needs longer warmup time than a Spitfire. But back to topic ...

Back to topic - how about someone take it upon themselves to include the known big bugs into the tracker (i.e. missing antialiasing, etc.)?

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.