BMSBugs: A public third party BMS bugtracker
-
Hi TOPOLO,
Its a feature of what your account permissions are. I Hawk, Bad Boy, DeeJay and Mav have accounts with ‘manager’ permissions and can assign issues to any account which is a ‘developer’ or ‘manager’. They can also add new user accounts to the project as ‘developer’ or ‘manager’.
If you are not logged in, or if you are logged in with ‘reporter’ permissions (which is the default), you can report issues, but not assign them to anyone in particular.
It is also possible to set issues which are reported in a particular category, as automatically being assigned to a specific developer, but so far as I know this hasnt been done.
EDIT: TOPOLO, your account should now have permissions set to assign issues to developers. Thanks!
-
Thanks a lot !
-
Do I need to register on new forum as well or can I just report anonymous?
-
It should be possible to report as “anonymous”, but it’s probably better to register so we can put a name & face to the bug reports
All the best, Uwe
PS: It’s not a forum btw.
-
Exactly so. Reporting bugs anonymously is possible, which I’ve chosen to do to try lower the barrier to entry. Registering is encouraged, as it allows email notification of developments to your reported issue - such as workarounds or bug fixes, or requests for feedback. If you report anonymously, you will need to monitor the issue manually, by revisiting the issue page at regular intervals.
I recommend registering, but it is not currently required.
-
Thanks everyone who has reported issues with BMS. I am glad we can have a public list of ‘known issues’, and very grateful - both to the community members who have taken time to list a problem, and reproduction instructions, and also to the devs who have been working hard to fix those problems.
The link above shows some of the results of our efforts - issues which should be resolved in the next release. Thanks again!
-
Thanks for clarification Uwe and Blu3wolf. My problem is better for forum because here I can ask others opinion on my problem too. I don’t know is it computer related because I bought new computer after 433 that I played lot more than 434 or installation issue or just issue with some planes.
My heatblur effect on 435 just look to like wall on behind aircraft rather than cone that extends after aircraft. I don’t remember if that looked like this in older versions.
Just like kouzi’s pic in screenshots 435:
https://www.benchmarksims.org/forum/showthread.php?40651-BMS-4-35-Screenshots/page4Is there problem in my eyes, graphic settings, new hardware, installation issue or my memory?
-
Reminder for any devs looking at the bugtracker: You can contact I-Hawk or myself and advise the username you have signed up with, for permissions to mark bugs as fixed, closed, etc.
-
I’m asked to confirm the resolution of #0000038, how can I perform such a transaction ?
-
-
This is correct. So the life cycle of an issue is:
New -> Just reported, not yet acknowledged or confirmed by devs (at least, publicly)
Confirmed -> Devs have reproduced bug, confirmed it is an issue
Assigned -> Someone has taken on the issue to try resolve it
Resolved -> The bug has been fixed, but the fix is not yet released
Closed -> A new version of BMS has been released, which fixes the bug.So: If your bug is resolved, when the next version is released, please check to confirm that the fix works. At that point, the bug can be closed.
If you are reporting a bug, and see another bug with the same description as yours, which is resolved - This does not mean it is a different bug! Just that the fix has not been released yet.
-
OK, so I’ll wait for U1 being public (internal bugtracker entry has been validated against last internal build)
-
I’ve closed #0000038 after U1 being released, but I’m not able to do the same with #0000028 Mirage F1 not flyable: impossible landing (not reported officially by me as I was logged in as Anonymous when I created it)
How can I do it ? (I do not see any available button or command in “View Issue Details” -
I think with your account permissions, you need to either be assigned to the issue, or to have opened the issue, to be able to close it. It was reported by Anonymous, and Mav-JP is assigned to it.
Ill edit the reporter field to you, and also close the issue. Thanks for updating the public issues!
-
Reminder for everyone who has logged a bug: we’d love an update if your bug has been resolved by 4.35 U1 - you can mark any issues fixed, as closed, once the fix is confirmed.
Thanks for using the tracker!
-
Issue #21 and Issue #81 were both reported anonymously. This is okay, but it does leave us without a reporter who can confirm that the issue they saw has been fixed (or not) in U1.
Id appreciate anyone who is able to try out the reproduction instructions for either issue and see if the issue can still be reproduced in U1, and comment to that effect on the issue.
Thanks again.
-
Looks like I’m unable to add notes to closed issues so I replied by email to “admin@bmsbugs……” to your questions on the two bugs you sent in the comments. Hope that’s ok!
All the best,
Uwe
-
Looks like I’m unable to add notes to closed issues so I replied by email to “admin@bmsbugs……” to your questions on the two bugs you sent in the comments. Hope that’s ok!
All the best,
Uwe
Thanks for getting back to me. Ive just now amended the setting which was preventing users from responding to resolved issues.
To that effect: anyone who has been unable to respond up to now, you should be able to log in and respond on those issues at this point. Thanks for your patience while we work out the kinks in the system.
-
And we got our first bit of spam on the tracker! I may need to tighten up security a little. This may include removing the ability to post anonymously, although this isnt part of the plans just yet.
-
Hi Blu3wolf a few days ago I posted bug no 119. Do I have to make a bug report here in the forum as well?
https://bmsbugs.blu3wolf.com/view.php?id=119