Community bugtracker is up @ il2bugtracker.com

[Ataros]

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

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/showthread.php?t=23405&highlight=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.
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

[Raggz]

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

Thanks!

[FG28_Kodiak]

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

[ZG15_FALKE]

ts ts ts Kodiak:
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.

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

[FG28_Kodiak]

Ah OK overseen this. :rolleyes:

[Ataros]

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

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.

[Ataros]

ts ts ts Kodiak:


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

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

[FG28_Kodiak]

Ok registered ;)

[ZG15_FALKE]

I would trie, no experience in voting system though.

[Ataros]

Got an e-mail from luthier:


Ilya Shevchenko
Добрый день,
Спасибо, очень приветствуем!
Не очень уверен в системе Redmine, так как она вроде не совсем для багов - но будем следить!
С уважением,
Илья

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"

[Dano]

Excellent stuff, my thanks to all involved :)

[albx]

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"

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

[Allons!]

Excellent, works very well.

[Ataros]

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

I shall ask next time if they have any preferences.

[albx]

I shall ask next time if they have any preferences.

ok ;)

[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

[Ataros]

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

[albx]

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

[Ataros]

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

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

[salmo]

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

[SG1_Lud]

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

S! Lud

[Insuber]

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

[ZG15_FALKE]

for voting, take a look at this:
Voting Plugin for redmine (http://www.redmine.org/plugins/redmine_vote)

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

[Ataros]

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

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?

[albx]

for voting, take a look at this:
Voting Plugin for redmine (http://www.redmine.org/plugins/redmine_vote)

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?

[ZG15_FALKE]

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.

[Ataros]

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 maybe revert to 1.2 if it is possible? Just an idea. It is up to you.

[VO101_Tom]

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

[Ataros]

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.

[SG1_Lud]

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

@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

[Allons!]

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.

[Ataros]

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!

[Ataros]

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.

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.

[albx]

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

[Allons!]

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

[Ataros]

Please check bugs with status "feedback" and provide more information. As in one example devs have to comment:
Sorry, but a good bug report should contain more info. What aircraft?

See Kodiak's guidelines above before posting please and be very very extremely detailed.

[Ataros]

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

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.

[albx]

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)

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

[Ataros]

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

luthier has same issue, see UPD. above

JavaScript does not matter...

[Widow17]

Nice!!!!!!!!

[Artist]

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

[ZG15_FALKE]

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?!

[ZG15_FALKE]

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

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

[PE_Tigar]

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

[41Sqn_Banks]

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.

[Artist]

Uups... there's something...
check for registration email first, activate and be habby ;-)?
...in my spam folder.

Feel kind of stupid.
Now I know why. :rolleyes:

Artist

[41Sqn_Banks]

I suggest we have a project for every release.

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


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.

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?

[ZG15_FALKE]

You mean one project for every release version?

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.

It is possible to allow only admins/moderators to assign a report to a person?
Yes, sure is!

[41Sqn_Banks]

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.

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.

Yes, sure is!

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.

[Ataros]

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

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.

[Ataros]

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

[Nephris]

Great Alb and Ataros you got it managed that quick!

[albx]

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

[VO101_Tom]

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

[Continu0]

great work, thanks!

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

[Ataros]

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

Copy and paste the link. Worked for me.

[VO101_Tom]

Copy and paste the link. Worked for me.

Thx.

[Luftwaffepilot]

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?

[salmo]

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

[SG1_Lud]

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?

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.

[41Sqn_Banks]

You can also stalk luthiers profile (http://www.il2bugtracker.com/users/14) to see his activities

[mazex]

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/redmine/wiki/RedmineCustomFields

[mazex]

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

+ 1

[Ataros]

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

Could you become an admin please?

[Ataros]

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.

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.

[Strike]

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

[SG1_Lud]

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.

[mazex]

Could you become an admin please?

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

[FG28_Kodiak]

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.

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

[41Sqn_Banks]

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.

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?

[mazex]

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

[mazex]

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?

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

[FG28_Kodiak]

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?

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

[41Sqn_Banks]

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?

[albx]

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?

[Ataros]

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

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.

[Ataros]

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?

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.

[jimbop]

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.

[Ataros]

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!

[albx]

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

[III/JG53_Don]

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

[salmo]

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.

[albx]

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

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

[Allons!]

He has also changed some requests status to 'rejected' & given a reasoning.

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

[Stealth_Eagle]

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

[GraveyardJimmy]

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


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.

[41Sqn_Banks]

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.

[Ataros]

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.

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.

[41Sqn_Banks]

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

[PE_Tigar]

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

[robtek]

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

[Gourmand]

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

[klem]

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

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.

[Ataros]

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.

[klem]

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

[ATAG_Snapper]

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.

[Luftwaffepilot]

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

luthier:
registered: 04.04.2012
Last login: 04.04.2012

[Gourmand]

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

[SlipBall]

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:

[zapatista]

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.

[41Sqn_Banks]

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


Voting without registration will give wrong results as the same person could vote the same bug multiple times.

A report written by a "casual visitors" unfortunately will not be constructive. Right now most bugs are reported as a single line that contains something that he reporter feels is wrong. That will not help the devs. We need a report that contains as a bare minimum:
- Steps to reproduce: Helps the devs to find the bug and rule out handling errors by the user
- Actual result: Helps the devs to understand what is wrong and what they have to look at to find the bug
- Expected result: Helps the devs to implement the fix correctly
- Additional information: Screenshots, mission files, tracks, excerpts from aircraft manuals, ...
We need this to take away the workload from the devs. E.g. It doesn't help of the dev tries 2 hours to reproduce a bug just to find out that it works as intended and the user that reported it simply pressed the wrong button. Thus we need this even for the simplest bug. Thus, writing just one good and constructive report will take a long time, maybe 1 hour for a dead simple bug. Registering to the system will take 3 minutes.

We need quality and not quantity.


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


There is a "priority" field for this and separation between "bug" and "feature". Also we have different categories to group bugs for FM, Graphics, FMB and so on.


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.

Only reports that were reviewed by the managers and are considered to be complete and of enough quality and content will be reported to the devs.

[Ataros]

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:

I agree with most of your points and Banks' comments but do not know if it is possible to implement them. If you register to the system I can give you admin rights to let you find out if it is possible. I do not see your name registered ATM.

[Ataros]

Also we have different categories to group bugs for FM, Graphics, FMB and so on.

Is it possible to assign 2 or 3 categories to the same issue? Maybe this is what zapatista means.
Some issues may have 2 categories, e.g. Interface and Multiplayer specific.

Importance is defined by number of votes. No need for classification based on importance.

[41Sqn_Banks]

Is it possible to assign 2 or 3 categories to the same issue? Maybe this is what zapatista means.
Some issues may have 2 categories, e.g. Interface and Multiplayer specific.

As far as I've seen this is not possible. However I think our categories are not perfect at the moment and need to be improved to reduce cases where multiple categories would apply.

Importance is defined by number of votes. No need for classification based on importance.
Agreed.

[Flanker35M]

S!

Registered and posted an issue. Thank You for those who made this possible! Great teamwork from the community.

[SEE]

I registered but never received the email with link to verify. I registered again (in case I had mis-typed my email address) but, at the end of the second registration attempt, I got a screen message saying the email address was already in use (so I hadn't mistyped it). :evil:

[Ataros]

I registered but never received the email with link to verify. I registered again (in case I had mis-typed my email address) but, at the end of the second registration attempt, I got a screen message saying the email address was already in use (so I hadn't mistyped it). :evil:

This usually means the e-mail is in your spam folder. Happened several times already.

[SEE]

The only thing in my Spam folder are Viagra offers!.......:grin:

I will look again though!

[albx]

The only thing in my Spam folder are Viagra offers!.......:grin:

I will look again though!

I have activated your account ;)

[Ataros]

@ all participants

Please check if some of issues you submitted have a "Feedback" status and provide more information as requested.

[SEE]

I have activated your account ;)

Many thanks albx!

[SG1_Lud]

Shameless Bump :-P

[albx]

I just wanted let you know that now isn't anymore possible to see the issues if you are not registered and logged in, this to avoid spam with the vote plugin, sorry....

[Wolf_Rider]

That's a bit of a disappointment... didn't a person have to be logged in to vote?

[Tacoma74]

Registered and voting as we speak. Hopefully this turns into a valuable tool for the devs and eventually the mod community once we get an SDK.

[Ataros]

I just wanted let you know that now isn't anymore possible to see the issues if you are not registered and logged in, this to avoid spam with the vote plugin, sorry....

Good. At least now we know that luthier logged in yesterday :) He was probably lurking for some time. http://www.il2bugtracker.com/users/14

Oh dear God. How is this possible? What have I done to deserve this?
:grin: Sounds promising.

[albx]

Good. At least now we know that luthier logged in yesterday :) He was probably lurking for some time. http://www.il2bugtracker.com/users/14


:grin: Sounds promising.

lol, very good... thank you luthier :-)

[41Sqn_Banks]

He even added a note to #97 Spitfire I: de Havilland two position airscrew control pitch settings (http://www.il2bugtracker.com/issues/97#note-11) and changed it to "In progress".

[notafinger!]

Has the issue with the jump or hitch in the Hurricane's elevator been reported on the bug tracker?

Discussed here: http://forum.1cpublishing.eu/showthread.php?t=26911

[salmo]

Has the issue with the jump or hitch in the Hurricane's elevator been reported on the bug tracker?

Discussed here: http://forum.1cpublishing.eu/showthread.php?t=26911

Why don't you look at the bug tracker and see for yourself? If you look in the top right of the bugtracker screen, there's this nifty little box called a search facility :rolleyes:

[Ataros]

Has the issue with the jump or hitch in the Hurricane's elevator been reported on the bug tracker?

Discussed here: http://forum.1cpublishing.eu/showthread.php?t=26911

I think only in the RUS project (with video samples http://www.il2bugtracker.com/issues/132) but do not remember the ENG version. Feel free to create if it is missing.

[klem]

I think only in the RUS project (with video samples http://www.il2bugtracker.com/issues/132) but do not remember the ENG version. Feel free to create if it is missing.

Added as Bug, #197 and cross-referenced to the Russian entry.

[Stipe]

Just registered and voting. Nice tool. Great job guys! :grin:

[Ataros]

Added as Bug, #197 and cross-referenced to the Russian entry.

Thanks a lot!

[Ataros]

Any bugs from this list missing yet? http://forum.1cpublishing.eu/showthread.php?t=23405

[SG1_Lud]

Any bugs from this list missing yet? http://forum.1cpublishing.eu/showthread.php?t=23405

Will check it :grin:

[Ataros]

Some underrated issues so far imo. Please vote if agree:

- sound radar http://www.il2bugtracker.com/issues/154

- visible border on a landscape http://www.il2bugtracker.com/issues/141

- TrackIR stuck centred when going in and out of the "close to gunsight" view http://www.il2bugtracker.com/issues/87

- TrackIR view jumps to centre when closing a canopy http://www.il2bugtracker.com/issues/204

- exception errors in dedi server even with simple missions not having any scripts http://www.il2bugtracker.com/issues/129

- allow scripts to see chat events (e.g. passwords for online wars, etc.) http://www.il2bugtracker.com/issues/111

- a key to start/stop track record http://www.il2bugtracker.com/issues/50

- annoying Hurricane Mk I elevator 'bump' in its operation http://www.il2bugtracker.com/issues/197

- country flags do not appear when joining MP. Not possible to join game. Critical for newbies http://www.il2bugtracker.com/issues/83

- AI taking-off before player in SP http://www.il2bugtracker.com/issues/194

- tree collision model http://www.il2bugtracker.com/issues/186

- Bf 109: Exploding Fuel tank - Multiplayer DM bug http://www.il2bugtracker.com/issues/179

- Gunner unified controls http://www.il2bugtracker.com/issues/148

- missing contacts in medium LOD http://www.il2bugtracker.com/issues/153

- Bf 109 textures http://www.il2bugtracker.com/issues/127

- hanging chassis in MP http://www.il2bugtracker.com/issues/15

- Historical Spit Ia performance www.il2bugtracker.com/issues/84

- COOP http://www.il2bugtracker.com/issues/51

Please also vote for all FMB issues to help the few mission-builders create more and better missions for us.
We all benefit from their work but they will not get enough votes without our help.
http://www.il2bugtracker.com/projects/cod/issues?query_id=3&sort=id%3Adesc%2Cvotes_value

[podvoxx]

to albx

Hi. We need to activate account user whith nickname Aspid. The letter did not come to his mail. Can you help with this (activate his account)?

[albx]

to albx

Hi. We need to activate account user whith nickname Aspid. The letter did not come to his mail. Can you help with this (activate his account)?

done, and activated Retnek also

right now we have 317 registered users

[podvoxx]

done, and activated Retnek also

right now we have 317 registered users

thx!

[Osprey]

Some underrated issues so far imo. Please vote if agree:

- missing contacts in medium LOD http://www.il2bugtracker.com/issues/153



- Historical Spit Ia performance www.il2bugtracker.com/issues/84




Ataros,

"underated" - The LOD bug is #2 lol

And bug 84 is coming in the patch - this is the modelling that Luthier applied. Trouble is, it's for 6.25lbs 87 octane FM. The real issue is bug 174, the missing 12lbs boost 100 octane.

http://www.il2bugtracker.com/issues/174

Also, worryingly I don't see any activity from Luthier on the bugtracker - does he actively use it?

thanks

[salmo]

There's already a 100 octane mod ( http://forum.1cpublishing.eu/showthread.php?t=25260 )

Luthier has alreasdy indicated there is no impotus from the devs to intoduce 100 octane into COD. It's just a couple of text file changes to impliment 100 octane, so the modders will be all over it once the game is opened up to community-made content.

[bongodriver]

The mod cannot be used online....

[Ataros]

Discussed with B6 how to process beta patch bugs at sukhoi.ru. I think it is a good sign :) Keep fingers crossed.

BTW albx, how many simultaneous connections the provider can handle? We can face several hundred connections I think. In the past when I posted several links on the main forum page I noticed site slowed down a bit. B6 mentioned that maybe he may post a link to the bugtracker in patch notes.

[albx]

Discussed with B6 how to process beta patch bugs at sukhoi.ru. I think it is a good sign :) Keep fingers crossed.

BTW albx, how many simultaneous connections the provider can handle? We can face several hundred connections I think. In the past when I posted several links on the main forum page I noticed site slowed down a bit. B6 mentioned that maybe he may post a link to the bugtracker in patch notes.

it's hosted on dreamhost, I don't know... the main problem can be mysql because redmine use innodb, but i think it can handle it

[Ataros]

New version number 1.06.17582 is entered into the bugtracker. Please use it to report and vote for new bugs. http://www.il2bugtracker.com/projects/cod/issues?set_filter=1

[Ataros]

@ all members

Please recheck issues that you reported after each patch. If the issue you reported was fixed in this patch or later patches please tell admins to change its status in this thread. Admins can not look through all the issues on regular basis searching for status change requests.

[Gourmand]

wheel break of stuka already not work... again... since the release...
is it too dificult to make a ju-87 break?

i fear to go to the link... old bug are still here, and new bug coming... :cry:

[Ataros]

I asked naryv about some fixes. He said they do not add them till graphics more or less stabilized. No need to report old bugs, tell what is fixed if any.

[5./JG27.Farber]

wheel break of stuka already not work... again... since the release...
is it too dificult to make a ju-87 break?

i fear to go to the link... old bug are still here, and new bug coming... :cry:

They do work, I used them 5 mins ago. There is different breaking for the red/blue aircraft. The Stuka uses the seperate toe breaks same as the 109. The red fighters use a different system.

[Gourmand]

They do work, I used them 5 mins ago. There is different breaking for the red/blue aircraft. The Stuka uses the seperate toe breaks same as the 109. The red fighters use a different system.
i'm use to play with 109 i now the separate break ;)
and stuka don't break ( we ear the sound... ) but no break..
you should test : try to turn with one toe break or try to overturn...
the plane don't reduce this speed... so break not working

[podvoxx]

to albx

Hi. We need to activate account user whith nickname =S=Fogot. The letter did not come to his mail. Can you help with this (activate his account)?

[albx]

to albx

Hi. We need to activate account user whith nickname =S=Fogot. The letter did not come to his mail. Can you help with this (activate his account)?

there is no user with this nick, only a Fogot with name Oleg Sherkozhukhov registered April 19 and he is active :confused:

[podvoxx]

there is no user with this nick, only a Fogot with name Oleg Sherkozhukhov registered April 19 and he is active :confused:
Ok, thx!

[Ataros]

Admins and managers please check out the bugtracker forum from time to time to share your opinion on bugtracker management.

[Jugdriver]

Albx,

I think I fatfingered my email address since I never got an email to activate my account, can you shoot me a PM to fix the issue or delete the account so I can set it up again?

Thanks

JD
AKA_MattE

[Ataros]

New version number added. Please use the recent beta version to report bugs.

[III/JG53_Don]

Ive got one question regarding the fixed bugs/features. For example the jericho horn of the Ju-87 was added in the recent beta, so shouldn't this be deleted at least when the official patch is out?
Would help the overview of the buglist to delete ones which arent present in the game anymore and it would lighten up some bad spirits to see the list of bugs decreasing (hopefully ;) )

[Artist]

Ive got one question regarding the fixed bugs/features. For example the jericho horn of the Ju-87 was added in the recent beta, so shouldn't this be deleted at least when the official patch is out?
Would help the overview of the buglist to delete ones which arent present in the game anymore and it would lighten up some bad spirits to see the list of bugs decreasing (hopefully ;) )

Right: as the patches are beta, the whole buglist will be worked over only when the official release is out. I see the point about the psychological factor, but beta is beta and the truth will be known with the official release :cool:

Artist

[III/JG53_Don]

Fair enough for me ;-)
I'm curious how many bugs we can delete after the official patch is out :D

[SG1_Lud]

Fair enough for me ;-)
I'm curious how many bugs we can delete after the official patch is out :D

If we could only scratch only a few of them, but the most important ones (read the bombers sights for example)...

S!

[III/JG53_Don]

When will the new beta be added in the bugtracker?

[Artist]

When will the new beta be added in the bugtracker?
Thanks for the reminder. Just added it.