BMSBugs: A public third party BMS bugtracker
-
Introducing BMSBugs, a centralised community bugtracker for BMS.
Easier to query than the forum for looking up specific issues. Easily accessible by browsers across whatever platform you are currently using.
No! No you Blu3wolf
DO IT! TEST THE GAME? DO THE LIST? PUBLISH IT!
Well, this is a community bugtracker, not a Blu3wolf bugtracker. If you know of a defect in BMS, but cant see it in the bugtracker, please feel free to add it. You can view bugs without an account, but account signup is is required to report bugs (requires email verification). Signing up allows you to report bugs, monitor the progress of your bug, as well as update it with further details, add attachments, and identify yourself.
Writing a bug report is pretty easy, follow the link and follow the prompts. If you want guidance on writing a good report, Nick has written an excellent post here. Keep reading below for more specific instructions relevant to writing a useful bug report.
You can file a report here. Thanks for doing your part to improve BMS!
Bug Report Checklist
1. Has this bug been reported already? Search to see if the bug is already known.
2. If the bug hasnt been reported, create a new report.
3. Describe clearly and concisely the actual behavior, and the expected behavior of the software.
4. Describe clearly, the steps to reproduce the behavior, or if you cannot reproduce the bug, the steps you took when the bug occurred.
5. Supply additional information to help clarify the bug, like pictures, logs, crash dumps, etc.
6. Stop and read your report before submitting. Can it be made clearer? Can you follow the instructions to reproduce the bug?Bug priority versus bug severity
Bug severity should be set based on how significantly it affects your ability to use the sim. Options include feature, trivial, minor, major, crash, or block. Feature requests are the least severe ‘bug’. Trivial bugs do not affect your ability to use the sim - such as very minor graphics glitches rarely seen, or issues affecting the display of a menu which do not prevent you using that menu, etc. Minor and major bugs both affect your ability to use the software as a combat flight sim - for example, a bug preventing you from contacting AWACS would be a minor bug, while a bug preventing you from firing missiles would be a major bug. Major bugs have no workaround, while minor bugs can be worked around. Crash is for critical bugs - for example, bugs which crash or lock up the software.Bug priority should be left as “normal” - the default value. Bug priority is decided on by the team, internally, and setting “high” or “low” priority on issues will not have any effect whatsoever on the team’s decision making process. Therefore, new issues should be set as “normal” priority.
Bugs in other theatres
Bugs in other theatres may be a bug in BMS’ code, or a bug in the data defining that other theatre. If you experience a bug in another theatre, before reporting it as occurring in that other theatre, try reproducing the bug in KTO. If the bug occurs also in KTO, it is more likely a bug within BMS.If the bug only occurs in that other theatre, it can still be reported. In fact, there are separate projects here specifically for reporting bugs in other theatres, including ITO and EMF. You can use the drop down menu in the top right of the page to select whether you are reporting a BMS bug (in KTO), or another theatre bug.
You can visit the BMS project home page here, and the ITO project home page here.
Resolved issues versus closed issues
Issues which are marked as “resolved” will still be present in the current release. Issues marked as “closed” should not be present in the current version.When an issue is fixed, the issue will be marked “resolved” and may have a target version set. When the issue is fixed in a public release, it will be marked “closed”. If you are searching to see if your issue has been reported already, this should include checking resolved issues. Resolved issues are fixed, but the fix is not yet included in a public release. Searching for closed issues may help see if similar issues have been reported and fixed in the past - sometimes fixes are not as perfect as we would like.
If in doubt, open a new issue - we can link the new issue, to the old one, if need be - and it may be that a bug that seems similar is actually a totally new bug, and not related to old bugs.
You can see issues fixed in the next version here. If you report an issue and it is fixed in a new version, we would appreciate you closing the issue when you confirm the issue is fixed. Thanks for doing your part to improve BMS!
-
Is missing the version of BMS of the bug
Please impose the same bug report format that we did here
-
Hi BlueWolf,
This is a VERY nice initiative! Thank you!
I think you can improve the categories field by using same as we use internally:
Unknown 2Dpit 3DDB AI ATC Avionics Campaign Cockpit CTD Database Documentation Dogfight Editor Flight model General Graphics Multiplayer Particle system Shared memory TE User interface
-
Is missing the version of BMS of the bug
Please impose the same bug report format that we did here
Id thought I had. Ill take another closer look. The field is called ‘Product Version’, and the drop down allows you to select BMS 4.35, or BMS 4.34 U5. I considered that we probably didnt need bugtracking for obsolete versions at this stage.
Hi BlueWolf,
This is a VERY nice initiative! Thank you!
I think you can improve the categories field by using same as we use internally:
Unknown 2Dpit 3DDB AI ATC Avionics Campaign Cockpit CTD Database Documentation Dogfight Editor Flight model General Graphics Multiplayer Particle system Shared memory TE User interface
Thank you for the suggestion, I was not really sure what categories would be useful. Ill update those now.
If you or any of the team would like their account able to access the management tools (like setting bug priority, etc), let me know you’ve created an account and Ill hit the buttons to set those permissions.
-
Thank you for the suggestion, I was not really sure what categories would be useful. Ill update those now.
If you or any of the team would like their account able to access the management tools (like setting bug priority, etc), let me know you’ve created an account and Ill hit the buttons to set those permissions.
Cool, I just registered, you can allow me permissions, thanx!
-
It’s great to see good old Mantis is still alive Thanks for setting this up,bluewolf. I just registered and tried to document the Shared Texture bug (also posted links in the relevant threads here).
All the best,
Uwe
-
Thanks for posting a bug! I think a fair bit of the credit for this idea goes to DeeJay actually, per my post above. His idea.
-
Here we go.
About categories : 2Dpit => is 3Dpit now.
…
Known issues: you can add wheel track of some vehicles like M106, M109, … (See in tacref).
-
Hmm. There is a ‘Cockpit’ category as well as the 2Dpit category. I (or I-Hawk) could delete one if its a duplicate and no longer needed?
-
Hmm. There is a ‘Cockpit’ category as well as the 2Dpit category. I (or I-Hawk) could delete one if its a duplicate and no longer needed?
Yeah right. So Cockpit is enough. (category list is not 100% up to date and not perfect)
…
One thing we NEED to have in the description is the THEATER. (normally, a bug should be reported ONLY if encountered in KTO but if the bug-tracker includes the Theater it is even better, either to be sure, or to list possible specific theater issues so the bug-tracker is not only useful to the core KTO team but also for the others)
-
Awesome Idea!
Hope the community would use this tool wisely
Should we Stick this post ? -
Excellent suggestion. Is there a list of all theatres currently available?
-
Registered, i also granted for permissions
Thanks in advance
-
Is missing the version of BMS of the bug
Please impose the same bug report format that we did here
BMS versions are added, from 4.34 U5, 4.35, and 4.35 U1 (next version, unreleased).
I am not entirely certain I can impose the exact same format from Nick’s sticky post without digging into the PHP for the report page. It seems that you can select which fields you want to show or hide, but not what order they should be shown in. For now at least, I am going to settle for having a working report page which has the same fields, despite those fields being in a different order.
On the note of compatible formats, I understand this software has the ability to export issues as XML, with a plugin. Ive not looked into it as yet.
Yeah right. So Cockpit is enough. (category list is not 100% up to date and not perfect)
2Dpit has been removed.
One thing we NEED to have in the description is the THEATER. (normally, a bug should be reported ONLY if encountered in KTO but if the bug-tracker includes the Theater it is even better, either to be sure, or to list possible specific theater issues so the bug-tracker is not only useful to the core KTO team but also for the others)
Theatre of Operations has been added. Current possible selections are KTO (default), ITO, EMF, and ‘Other’. Im not sure which other Theatres are in use at this stage, but Id appreciate a reply from anyone wanting another theater added.
-
Known issues: you can add wheel track of some vehicles like M106, M109, … (See in tacref).
Disregards … not yet in 4.35 … sorry.
-
I am not entirely certain I can impose the exact same format from Nick’s sticky post without digging into the PHP for the report page.
Just as use instructions in post #1
…
Also … ppl must follow their entries and not just throwing them here and never comes again.
The “shall” check from time to time along updates and change the status once it has been fixed. -
I think Balkans is also available for 4.35.
Cheers,
Uwe
-
I’ll also try collecting info on the MP tanker / AAR bug and create an issue for it.
Cheers, Uwe
-
Also … ppl must follow their entries and not just throwing them here and never comes again.
The “shall” check from time to time along updates and change the status once it has been fixed.Indeed, an active community is far better than an inactive one.
I hope that wont prove to be an issue. I am not entirely clear on the scale of the BMS community. If its large enough, and the tracker sees enough use, I might need to look for assistance managing the issues.
-
I think having a public bug tracker is already a big step ahead compared to 1,000 posts in a hundred threads here on the forum
I hope the community will pick up the ball that you’ve thrown them blue and run with it, especially as we already see some devs warming up to the idea. This is a great chance to streamline BMS bug reporting and -tracking.
All the best, Uwe