Falcon BMS 4.34 Bug thread
-
I am not a BMS dev but work in the gaming industry and as a FYI bug for simple things maybe a quick screenie is ok…
BUt really when submitting a bug please give DETAILED description of your issue and when it is happening preferable a step by step to reproduce the issue. If they cant reproduce the problem they cant fix it so… -
there were 2 situations:
1. like in the picture - from outside look the gear is down, from the inside there is no gear (true also for air brakes)
2. gear was been locked down, but there isnt gear from the external look. (other case)if you need more details, ask me for specific points, you think that will help you to better understand the situation.
-
I have problem with take off button in mission TR_BMS_06_ILS_WEATHER. I can not click it. Is it Bug?
Also When Clicked theather button then clicked re- back button, main screen gives black screen. -
If you Start the clock running in the top right hand corner does it let you click take off?
-
Black comms are by intention, btw. Not a bug.
-
1- unable to communicate with ground, tower, Departure and Awacs in the sixth korea campaign (korea side). Yes, all presets and freqs were checked.
2- unable to volume down the INTERCOMM in setup > sound options (awacs keeps talking outloud even though the volume is all the way to the left)
3- During touchdown, the AI F-16 “enters” the ground (Kunsan Airbase)
4- in the sixth korea campaign, a 4 ship f-18 holding short of the active runway did absolutely nothing even though their takeoff time were 3 minutes before ours (and we got to the hp a little late)
To be honest, I don’t know whether or not this last one is a “BUG”, but as the AI was reworked and is supposed to be more efficient, i think it’s worth the report.
And again: Thank you, BMS team!! Awesome job!! -
Hi guys,
Please, we really appreciate your feedback, but only ONE thread per bug report.
Maybe this is helpful…
Effective Bug Reporting
An effective bug report communicates well with the BMS developers and avoids confusion or miscommunication.Before you add a new bug report, please use the search function to check if the same bug has been reported or not. A good bug report should be clear and concise without any missing key points. Any lack of clarity leads to misunderstanding and slows down the development process as well. The most important point that you should keep in mind is not to use a commanding tone or harsh words in the report. This breaks the morale and creates an unhealthy work relationship. Use a suggestive tone. The import information that a bug report must communicate is:
-
Version and Build number
-
Detailed Description
-
Pictures
-
Example files*
-
Crash logs*
-
Reproducibility Procedure
-
Expected Behavior
-
.cam, .tac, .twx, .ini, .vhs (ACMI), … if applicable depending on type of bug
The report should clearly answer how the test was performed and where the defect occurred exactly. The reader should easily reproduce the bug and find where the bug is. Hence it is best to split multiple issues into separate bugs. This ensures that each bug can be handled individually.
Always use KTO as your standard Theater of Operations and the current Vanilla installation without any further modifications!
If you discover a bug in another theater, please reproduce it in KTO as well. This can already exclude some sources of error.It is very important to layout exactly what you did, in a step-by-step manner if necessary. Try to include all the information that you think would be helpful, but don’t be overly verbose. Now try to explain what happened the best you can. If you received an error message, it is always important to include the full, specific message. If you’re having trouble explaining it, pictures can be better than 1000 words. Use the attachment option whenever reasonable. Finally, try to explain what you expected to happen. This helps everyone understand what you were thinking and will often lead to improvements.
You can easily just copy and paste from this template:
Version
4.34.0 (x64)Build
19631Detailed Description
…Pictures
…Example files
…Crash logs
…Reproducibility Procedure
1.
2.
3.
4.
5.
6.
7.
8.
9.Expected Behavior
…Your effort towards writing a good bug report will not only save the resources of our team, but also create a good relationship between you and the developers.
If you already solved the problem on your own, please report back.
Makes sense?
Thank you all!
Cheers,
Nick -
-
Might want to sticky that somewhere? I am sure people will want to help as much as they to find those tricky bugs.
God knows its one of the most time consuming part of development. -
No, we need a separate thread for each bug! Sorry, but this should be closed. We have not THE official “Falcon BMS 4.34 Bug thread”.
-
It is fantastic that we now have several thousand more people testing and reporting on issues that they find, but we are only a small group of volunteers working in our spare time.
Help us to help you. Follow the guidelines to report on any issues as Nick said above, but most of all we need a repro case. If we can reproduce the issue it is much easier to find the cause. Only when we know what is causing the issue can we start to think about a possible fix.
Thank you.