Falcon BMS 4.36.2 Documentation: Bug Reports
-
I hope you’re not fed up with me
BMS-Training
Ver. 4.36.1All here in chapter 4B “Tactical Turns”.
page 68
Is: “RKJK INFO: B 010625Z ILS RWY36 TRL140 360/10KTS 7SM FEW050 15/5 A2980 NOSIG Visibility >5000m, Altimeter 2980.”
Proposed: change “A2980” and “Altimeter 2980” to “A2989” and “Altimeter 2989” because this is how Gunsan reports.page 68
Is: “This mission is designed to train tac-turns with the AI at a contract speed of 350kts and FL200 (20000ft AGL)”
Question: I wonder why we write here that “FL200 (20000ft AGL)” - if referring to FL200, shouldn’t we be flying with altimeter set to 29.92? Aircraft in this mission has 29.80 set and it doesn’t show 20000 ft on barometric altimeter (more like 19500 ft). 20000 ft is in fact shown by the radar altimeter, but FL doesn’t concern radar altitude, but barometric one, right? Also, in this mission we’ll not only fly over water, so height (AGL) will vary. So maybe, to avoid confusion, leave the sentence as “…at a contract speed of 350kts and altitude around 20000ft.”?page 68
Is: “Even when AI Tac-turn orders are not implemented yet in BMS…”
Proposed: change to small letter to “tac-turn”page 74
Is: “Use you’re A-A TACAN to measure the distance to your flight-lead.”
Proposed: “Use your A-A TACAN to measure the distance to your flight-lead.”
Reason: you’re -> yourpage 74
Is: “Depending on the altitude, loadout and drag this contract speed has to be maintained as well as the current altitude of 20000ft.”
Question: something seems not right with this sentence - first we say “depending on the altitude” but then we provide the altitude… Maybe change this to a general statement about importance of the contract airspeed and altitude, like this: “Regardless of loadout and drag the contract speed and altitude hast to be maintained.” or better yet (maybe, just for your consideration): “In general, flight-lead (or flight planner) has to take into consideration the loadout and drag of aircraft in his formation because his wingmen must do whatever it takes to maintain it.”page 74
Is: “At the beginning it will be quiet hard because you have to fly very precise and learn how to use your throttle and stick effectively.”
Proposed: “At the beginning, it will be quite hard because you have to fly very precisely and learn how to use your throttle and stick effectively.”
Reason: added comma; quiet -> quite; precise -> preciselypage 74
Is: “…the goal is to end this turn in a reversed spread formation…”
Proposed: “…the goal is to end this turn in a reversed “Spread” formation…”
Reason: conventionpage 75
Is: “As you may know, the BMS AI has no directive orders or the option to give a call when the turn start.”
Proposed: “As you may know, the BMS AI has no direct order or the option to give a call when the turn starts.”
Reason: directive -> direct; “directive” itself is an order; orders -> order (because then “option” and “turn” are in singular - could also change all of them to plural) changed “when the turn starts”, alternatively “when the turn should start”page 75
Is: “But, this is not far from real life because in some scenarios, tac-turns will be executed silent (= Ziplip) without any communication.”
Proposed: “This is not far from real life because in some scenarios tac-turns will be executed silently (= Ziplip), without any communication.”
Reason: Removed “But” (could leave “but”, but then we’d need to connect this sentence with previous one, like so: “…visual on your flight lead all the time, but this is not far from…”; removed commas where I think they shouldn’t be, added where it should.; silent -> silentlypage 75
Is: “As you can see in the picture right,…”
Proposed: “As you can see in the picture to the right,…”page 75
Is: “Your turning cue start when your flight lead is on your 4 o’clock…”
Proposed: “Your turning cue is when your flight lead is on your 4 o’clock…”
Reason: a turning cue is a signal to start the turn and I think it is a rather precise moment, hence the proposed change - if it is not, and there is a period when you can initiate your turn, then the correction would be only in the form of the “start” verb, like so “Your turning cue starts when…”page 75
Is: “At STPT 4, the flight will do a “Delayed 90 left turn”.”
Proposed: “At STPT 4, the flight will do a “Delayed 90” left turn.”
Reason: changed placement of the closing quotation mark to make it consistent with usage in this sectionpage 75
Is: “At STPT 5 the flight-lead will initiate a…”
Proposed: “At STPT 5, the flight-lead will initiate a…”
Reason: added comma to make it consistent with the same punctuation a couple of sentences before (alternatively, remove comma here and in the sentence starting with “At STPT 4,…”)page 75:
Is: “10NM later at STPT 6 your flight will execute a “Delayed 45” left…”
Propose: “10NM later, at STPT 6, your flight will execute a “Delayed 45” left…”
Reason: added commaspage 75
Is: “Those pretty quick sequences are quiet usual because in certain scenarios a flight has to change direction quite often.”
Proposed1: “Those pretty quick sequences are quite usual because in certain scenarios a flight has to change direction quite often.”
Proposed2: “Those pretty quick sequences are nothing unusual because in certain scenarios a flight has to change direction quite often.”
Reason: quiet -> quite; in second proposal I made a stylistic change to remove repetition of “quite” which in my opinion sounds betterpage 75
Is: “They will be executed less precise and more aggressive, especially if there’s any threat.”
Proposed: “They will be executed less precisely and more aggressively, especially if there’s a threat.”
Reason: changed to adverbs: precisely and aggressively; changed “any” to “a” as this is not a question nor negationpage 75
Is: “Okay we are not done for this training, yet.”
Proposed: “Okay, we are not done for this training yet.”
Reason: added comma at the beginning; comma before “yet” I my opinion could stay if we wanted to make a dramatic effect, which I don’t think we should want too much in this kind of documentpage 75
Is: “Establish a spread formation right 1NM when your flight is reaching STPT 10.”
Proposed: “Establish a “Spread right” 1NM formation when your flight is reaching STPT 10.”
Reason: changed to be consistent with the way in which similar expression was used previously in this section; probably in order is a little discussion on the convention how to write formation names with their parameters, like “Spread” right with 1 NM spacing, but this is topic for another day -
@Fox_15 No no you’re doing good. Good findings
-
@justonce01 All fixed for U3.Thanks for reporting!
-
@Fox_15 All fixed for U3. Thanks for reporting!
-
@101-Spyder
Sorry for the late reply. What you list in the Examples is exactly what I do atm. In addition, a lot more options are available and everything is regrouped.Yes, we still plan with 3 separate cfg files. For good reasons.
BMS can manage the Falcon BMS.cfg at will.
You have to set your User.cfg once and can carry it over to newer versions. Same for the Hosts / e.g. dedicated servers. I really don’t see a problem here. -
Document: BMS Technical Manual, BMS 4.36.0
Page: 10-148, section 10.6.4, first paragraph
Original sentence: The HOTAS controls in the F-16 have a defined set of functionalities (see chapter “Hands-on controls”) which is often reproduced by (v)pilots in their joystick layout.
Corrected sentence: The HOTAS controls in the F-16 have a defined set of functionalities which is often reproduced by (v)pilots in their joystick layout.There is no chapter in the manual called “Hands-on controls”. The same sentence was in the BMS 4.35.0 version of the manual. Apparently, it was referring the reader to page 2-18 of that manual. The figure on that page has been removed from the 4.36.0 manual.
Document: BMS Device Setup Guide
Page: various
The word break appears 10 times in the document. In each case it should be changed to brake.
The word breaking appears two times in the document. In each case it should be changed to braking.GC
-
@greatcouloir
All fixed in U3. -
Document: BMS Training Missions
Page: 209
Original sentence: “GW: 35950 (fuel 6.6 dry). 3 AIM-9P, 2 wing tanks, 1 ACMI pod and 1 Sniper targeting pod.”
Corrected sentence: “GW: 35950 (fuel 6.6 dry). 2 AIM-9M, 1 AIM-9P, 2 wing tanks, 1 ACMI pod and 1 Sniper targeting pod.”The loadout does not match what is described in the first paragraph of section 17.4 (page 217) nor the training TE.
Page: 210 and 221
The two identical MFD figures of the SMS page seem incorrect. OSB 6 indicates 2 A-9LM. Should OSB 6 not read 2 A-9M?GC
-
Document: BMS Training Missions
Page: 14, item 7
Original sentence: “Failure to do so will cause an EQUIP HOT caution light as soon as the systems are powered by the main generator, because they will not be being cooled correctly.
Corrected sentence: “Failure to do so will cause an EQUIP HOT caution light as soon as the systems are powered by the main generator, because they will not be cooled correctly.”Alternatively, it could be changed to “Failure to do so will cause an EQUIP HOT caution light as soon as the systems are powered by the main generator, because they are not being cooled correctly.”
GC
-
Thank you Kolbe for these clarifications concerning the three configuration files that we must analyze for the proper maintenance of our squadrons in the future. Much appreciated.
My point of view was simply that as a squadron leader we now have to check these two (or three) separate files in our members since the user.cfg file can hold options that are possibly no longer desirable after an update (example U1 to U2).
-
Document: \Falcon BMS 4.36\Docs \01 Input Devices\BMS-Keystrokes-Defaults.pdf
Page: 16 (Section 8.05 - WINGMAN COMMANDS)
Original sentence: “WingmanWeaponsFree”
Corrected sentence: “WingmanWeaponsFree_AA”
Add new sentence: “WingmanWeaponsFree_AG”
Page: 16 (Section 8.06 - ELEMENT COMMANDS)
Original sentence: “ElementWeaponsFree”
Corrected sentence: “ElementWeaponsFree_AA”
Add new sentence: “ElementWeaponsFree_AG”
Page: 17 (Section 8.07 - FLIGHT COMMANDS)
Original sentence: “FlightWeaponsFree”
Corrected sentence: “FlightWeaponsFree_AA”
Add new sentence: “FlightWeaponsFree_AG” -
Document: BMS Training Manual 4.36.1
Page: 37, last paragraph
Original sentence: “They are given in hundredths of feet, with the large number being thousands and the smaller number being hundredths of feet”
Corrected sentence: “They are given in hundreds of feet, with the large number being thousands and the smaller number being hundreds of feet”Hundreth = 1/100, hundred = 100.
-
-
Document: BMS Training Manual 4.36.1.
Training doc: suggest to clarify instructions of the very first mission
^ Sorry for creating a new thread in the Documentation sub-forum. I was told about this thread only a little later.
-
-
@greatcouloir @Lupovolante @Elegantly
All fixed for U3. Thanks for reporting!
-
@Micro_440th Great, thank you!
-
Document: Training.pdf
Page: 245
Original sentence: Once you have tally, go back to dogfight mode, which will snooze the radar, and keep him padlocked.
Corrected sentence: If you enter dogfight with a bugged target, it will still be radiating ACM20. Press TMS DN to get NO RAD (snooze). If you entered dogfight with no bugged target then it will be ACM20 NO RAD (snooze). -
-
@jc1 Corrected in U4
-