Falcon BMS 4.36.1 Documentation: Bug Reports

[Micro_440th]

Please provide 4.36.1 documention bugs in the following “bug format”:

Document:
Page:
Original sentence: “”
Corrected sentence: “”

Thank you for your support!

[arabianjules]

3 new TE`s in training, training manual in docs not updated?

John.

[Birdy.dma]

@arabianjules

It is. On the very first page of the Pdf:

Ver: BMS 4.36.1
Date: 04 July 2022

[airtex2019]

@arabianjules Looks heavily updated to me. Here’s the file-size info for 4.36.1… is yours different?

[Jackal]

@arabianjules
It is, dear John, it is… check its new size and release date (as precised above), and if you give a look to its contents, you will find also the three new training missions listed.

I don’t think that you will be obliged to download the installer once again if those data don’t match with yours…

With best regards.

[Korbi]

Document: BMS-User-Manual.pdf
Page: 8-96
Original sentence: “…by pressing LISt - M SEL 0 - M SEL 0…”
Corrected sentence: “…by pressing LIST - M-SEL 0 - M-SEL 0…”

[Kolbe-49th]

@Korbi said in Falcon BMS 4.36.1 Documentation: Bug Reports:

Document: BMS-User-Manual.pdf
Page: 8-96
Original sentence: “…by pressing LISt - M SEL 0 - M SEL 0…”
Corrected sentence: “…by pressing LIST - M-SEL 0 - M-SEL 0…”

Du Erbsenzähler

Fixed for U2

[drtbkj]

@airtex2019 said in Falcon BMS 4.36.1 Documentation: Bug Reports:

@arabianjules Looks heavily updated to me. Here’s the file-size info for 4.36.1… is yours different?

Hi, Airtex. I found this file, and the Dash-34, from the BMS Wiki, seeking the new 4.36.1 info on HTS assigning SPI’s . What I got identifies itself as for 4.6.1. Birdy.dma wrote the info on the first page, but I don’t see it.

[101-Spyder]

Document: BMS Technical Manual.pdf
Page: Not currently available (missing info).
Original sentence: “n/a”
Corrected sentence: “g_bShowWpErrorsOnMap” :
“Enable or disable flight plan errors display on 2D Map interface”,
0=Disable (default), 1=Enable.

g_bShowWpErrorsOnMap config option is already available in “Falcon BMS.cfg”, but is absent (not described) in the technical manual.

I think “g_bShowWpErrorsOnMap” and the explanation should appear at the end of page 26, after the option “g_bImageBasedLighting”. as it is ordered in the Falcon BMS.cfg file.

[justonce01]

Document: TO BMS 1F-16CM-34-1-1
Page: 3
Original sentence: “2.5.6 Air-To-Ground Intraflight Data Link”
Corrected sentence: "2.5.6 Air-to-Ground Intraflight Data Link”

That makes it consistent with the Air-to-Ground above.

Document: TO BMS 1F-16CM-34-1-1
Page: 5
Original sentence: “4.2 CONTINUOUsLY COMPUTED RELEASE POINT (CCRP)”
Corrected sentence: “4.2 CONTINUOUSLY COMPUTED RELEASE POINT (CCRP)”

[LorikEolmin]

Threat Guide p 45
J-20 missing.
(in Misdata, PL-12 is said to be a copy of 120. Not the case anymore. Update forgotten?)

[justonce01]

Document: TO BMS 1F-16CM-34-1-1
Page: 243
Original sentence: “The GS option is will either be on (highlighted), or GS off.”
Corrected sentence:The GS option will either be on (highlighted), or GS off.”

[Kolbe-49th]

@101-Spyder
Thanks for your report but I won’t address this before the next major release. The cfg file and descriptions in the manual will receive a big update for 4.37.

[jacqueslees]

I wonder here that I have seen naval ops manual updated listed in 4.36.1 change log but the actual manual’s front cover is still showing 4.36 …

[Micro_440th]

@jacqueslees said in Falcon BMS 4.36.1 Documentation: Bug Reports:

I wonder here that I have seen naval ops manual updated listed in 4.36.1 change log but the actual manual’s front cover is still showing 4.36 …

Negative. No updates.

[101-Spyder]

@Kolbe-49th
Thanks for your answer Kolbe.
In the next update 4.37, is it possible to have those informations for each config options? (standard);

Example:

• Default_Value;
• Min _Value;
• Max_Value;
• Inc_Step_Value (ex: 0.25, else N/A);
• MP_Critical (true/false);
• Host overwrite client (true/false).

This can be a simple line at the end of each option (in reverse video or another color) , all in the same format.

In many config options in the Technical Manual, we already have these informations (very helpful, thanks!), but some of them did’nt indicate the “max_value” or no indication if this option is overwrited by the host server, etc.

I know that each value type is already avail with g_b (boolean), g_n (Numeric), g_s (string), etc.

I think that if every options was having an lastline always showing every possible values listed here, will really help outside programmers to validate every inputs from the config files of our teammates (via a little validation program as we have in my VFS).

As a second question/suggestion: Do you still plan to maintain three separate configuration files files in 4.37 (… Base.cfg, User.cfg and Server.cfg)? I must admit that is a big issue now for a squadron manager. In my point of view, the filter option of Joel Bierling was a better way to maintain only one active current configuration file because it was so easy to compare all my teammate’s config file with a little home made program tool (home squadron validation tool). These three config files to scan now is a much harder way to maintain stability for all our squad members…

So your input will be appreciated, because I’m currently working hard for our VFS with a new “F4Patch” like program (as done by Joel Bierling in 2004, but now including all know Options listed in technical manual in 4.36.1. This is a Treeview (hierarchical list on the left side, with input user data on the right side. My program scan every config options in all three config file (Base, User and Server) to output the «final result» of the current active config for this user. So I will probably standby with this personnal project if the actual “config method” is going to change in 4.37…

Thanks for your input and also thanks for this very helpfull technical manual.

[Fox_15]

Avionic Checklists
Rev: 2009 BMS 4.35 (latest version as of 4.36.1)

page 6
Is: “The EWS can be set through the DTC programming at prefight and may be reprogrammed in flight through the UFC by LIST # 7.”
Proposed: “The EWS can be set through the DTC programming at preflight and may be reprogrammed in flight through the UFC by LIST # 7.”
Reason: corrected a likely typo “prefight” -> “preflight”

page 8
Is: “The F-16 navigation computer is able to store 100 steerpoints (1 to 99)”
Proposed: “The F-16 navigation computer is able to store 99 steerpoints (1 to 99).”
Reason: it is in fact 99 steerpoints; added comma at the end of the sentence.

page 8
Description for point “4. Tacan channel” is:
“Set 63 apart: (at or above 64, add 63 – below 64, subtract 63)”
Proposed: “Set 63 apart: (at or above 64, subtract 63 – below 64, add 63)”
Reason: since maximum allowed TACAN channel is 126 (as per Dash-34 2.3.2), the original description is wrong

page 9
Is: “Own ship markpoints are stored in STPT 26-30.”
Proposed: “Ownship markpoints are stored in STPT 26-30.”
Reason: correct form seems to be “ownship”, used accross docs

page 9
Is: “Ownship markpoints are displayed on the MFDs with large X cross.”
Should be: “Ownship markpoints are displayed on the MFDs with small x cross.”
Reason: ownship markpoints are smaller “x” on HSD than data-link markpoints; also convention in Dash-34 is to use “x” for ownship and “X” for data-link markpoints

page 11
Is: “Check own ship and intraflight address in DED AA page (LIST ENTER SEQ)”
Proposed: “Check ownship and intraflight address in DED AA page (LIST ENTER SEQ)”
Reason: correct form seems to be “ownship”, used accross docs

page 12
Is: “Data link steerpoints and markpoint appear as a small x on the HSD. Ownship markpoints as a larger X.”
Should be: “Data link steerpoints and markpoints appear as a larger X on the HSD. Ownship markpoints as a smaller x.”
Reason: ownship markpoints are smaller “x” on HSD than data-link markpoints; also convention in Dash-34 is to use “x” for ownship and “X” for data-link markpoints; also changed markpoints to plural as it seems proper here

page 13
In section “Receiving a Steerpoint/Markpoint”
Is: “Check MKRT DATA in HUD and VMS DATA sound”
Proposed: “Check MKPT DATA in HUD and VMS DATA sound”
Reason: as per figure 62 in Dash-34 2.5.6.1 HUD information when receiving datalink markpoints is “MKPTxx DATA”

page 13
In section “Receiving a Steerpoint/Markpoint”
Is: “Check data linked steerpoint (small X) in HSD”
Should be: “Check data linked steerpoint (large X) in HSD”
Reason: steerpoints sent via datalink appear in HSD as larger X than those of ownship markpoints

[Fox_15]

Dash-34
Ver. 4.36.1

page 93
Is: “Ownship markpoints are shown as a big X. Datalink steerpoints are shown as a small x.”
Should be: “Ownship markpoints are shown as a small x. Datalink steerpoints are shown as a big X.”

############

BMS-Training
ver. 4.36.1

I propose to add in chapter 4A.1 a refresher on basic nomenclature of aircraft in formation, since we’re using it, i.e. something along these lines:
First element:
#1 - flight lead
#2 - wingman
Second element (or just “element”):
#3 - leader of second element
#4 - second element wingman
Flight = first element + second element

page 58
Is: “The fighting wing is flown when maximum maneuverability is required…”
Proposed: “The “Fighting Wing” is flown when maximum maneuverability is required…”
Reason: “fighting wing” is not used in ordinary meaning but as a formation name, so I propose put it as in other places where formation name is referenced

page 58 and page 62
Is: “A good flight lead always maintain speed and heading if possible to so the wingman can maintain the formation easier.”
Proposed: “A good flight lead always maintains speed and heading, if possible, so that the wingman can maintain the formation easier.”
Reason: corrected verb to “maintains” for third person singular; added punctuation; fixed “to so”

page 58:
Is: “The spread formation is similar to the LAB formation…”
Proposed: “The “Spread” formation is similar to the LAB formation…”
Reason: adhering to convention of writing of formation names

page 59
Is: “In BMS it is an even tighter fluid four (see 4-ship formations) formation with all aircraft separated by less than 2000 feet.”
Proposed: “In BMS there is an even tighter “Fluid Four” (see 4-ship formations) formation with all aircraft separated by less than 2000 feet.”
Reason: the intent of the original sentence is unclear for me - if it was meant to provide information what is the most compact formation, then it could have been corrected to my proposal, but not sure if this is still correct, since “Fluid Four” does not seem to be the most compact one as there is also a “Res Cell” formation described as “similar to “Fluid Four” formation but tighter”.

page 60
Is: “The route formation is a lose formation which corresponds to an enlarged fingertip formation.”
Proposed: “The “Route” formation is a loose formation which corresponds to an enlarged “Fingertip” formation.”
Reason: typo correction in word “loose”; changed writing of the formation names to quoted names as the words “route” and “fingertip” are not used here in their ordinary meaning

page 60
Is: “The flight can operate at the same altitude level or 200ft higher/lower.”
Proposed 1: “The element can operate at the same altitude or 200ft higher/lower.”
Proposed 2: “The flight can operate at the same altitude or element can be 200ft higher/lower.”
Reason: changed “flight” to “element” because what would mean for the “flight to operate 200ft higher/lower” (higher/lower from what?); also removed “level” as just “altitude” seems enough and “level” has its special meaning (maybe as flight level, but still…)

page 61
Is: “Both wingman are flying in fingertip formation.”
Proposed: “Both wingmen are flying in “Fingertip” formation.”
Reason: corrected “wingman” to plural; adjusted to convention of writing formation names

page 61
Is: “For the box formation each element…”
Proposed: “For the “Box” formation each element…”
Reason: adjusting to convention of writing formation names

page 61
Is: “The elements can slightly offset (right picture) or flight directly behind each other.”
Proposed: “The elements can slightly offset (right picture) or fly directly behind each other.”
Reason: corrected “flight” to “fly”

page 61
Is: “The wingman are flying in spread (0-30° cone).”
Proposed: “The wingmen are flying in spread (0-30° cone).”
Reason: corrected “wingman” to plural

page 62
Is: “The advantages of the wedge formation for each element is that the leader is well protected in the 6 o’clock area and is free to maneuver aggressively.”
Proposed: “The advantages of the “Wedge” formation for each element are that the leader is well protected in the 6 o’clock area and is free to maneuver aggressively.”
Reason: corrected “advantages (…) are (…)”

page 62
Is: "The tactical advantage is that especially flights with an Air-to-Air task (Sweep, etc.), can establish much quicker 4-ship tactics like a grinder, a CAP or a bracket because there is already distance between elements.
Proposed: "The tactical advantage is that flights, especially with an Air-to-Air task (Sweep, etc.), can establish much quicker 4-ship tactics like a grinder, a CAP or a bracket because there is already distance between elements.
Reason: moved “flight” to a different place and added comma, so that the structure of the sentence (around supplementary information starting with “especially”) improved

page 63
Is: “The “Arrowhead” formation is a mixture of a wedge formation (first element) and LAB formation (second element).”
Proposed: “The “Arrowhead” formation is a mixture of a “Wedge” formation (first element) and LAB formation (second element).”
Reason: adjusting to convention of writing formation names

page 63
Is: “This formation can be flown tight or lose…”
Proposed: “This formation can be flown tight or loose…”
Reason: corrected typo in “loose”

page 64
Is: “The fingertip (close) formation is…”
Proposed: “The “Fingertip (close)” formation is…”
Reason: adjusting to convention of writing formation names

page 64
Is: “The wing tip rail / wingtip missile…”
Proposed: “The wingtip rail / wingtip missile…”
Reason: “wingtip” as part of “wingtip rail” seems more appropriate here

page 64
Is: “The „Finger Four“ formation is similar to the „Fingertip“ formation, but more lose with a spacing up to 1500-2000ft.”
Proposed: “The „Finger Four“ formation is similar to the „Fingertip“ formation, but more loose with a spacing up to 1500-2000ft.”
Reason: corrected typo in “loose”

page 64
Is: “The echelon formation (left / right)…”
Proposed: “The “Echelon” formation (left / right)…”
Reason: adjusting to convention of writing formation names

page 64
Is: “Echelon formations are normally flown very tight (similar to fingertip).”
Proposed: ““Echelon” formations are normally flown very tight (similar to “Fingertip”).”
Reason: adjusting to convention of writing formation names

page 65
Is: “Especially in IFR departure conditions, a trail/radar assisted trail formation is used.”
Proposed: “Especially in IFR departure conditions, a “Trail”/radar assisted “Trail” formation is used.”
Reason: adjusting to convention of writing formation names

page 65
Is: “The spacing between each aircraft is defined by each flight lead or by outside conditions (IFR, etc.).”
Proposed 1: “The spacing between each aircraft is defined by flight lead or by outside conditions (IFR, etc.).”
Proposed 2: “The spacing between each aircraft is defined by each element lead or by outside conditions (IFR, etc.).”
Reason: word “each” seems unnecessary since the whole chapter considers a single flight only - this is the proposal 1. If, however, the spacing is defined per element by element’s leader, then proposal 2.

page 65
Is: “The ladder formation is similar to the trail formation…”
Proposed: “The “Ladder” formation is similar to the “Trail” formation…”
Reason: adjusting to convention of writing formation names

page 65
Is: “The stack formation is similar to a trail formation but with tighter distance limitations and a must for vertical stacking.”
Proposed: “The “Stack” formation is similar to a “Trail” formation but with tighter distance limitations and a must for vertical stacking.”
Reason: adjusted to convention of writing formation names

page 67
Is: “At STPT 6 the flight lead will call for a “Fluid four” formation.”
Proposed: “At STPT 6 the flight lead will call for a “Fluid Four” formation.”
Reason: correction of the capital letter in “Fluid Four”

page 67
Is: “STPT 9-10 will again a “Fluid Four” formation as a preparation for the approach in Gunsan.”
Proposed 1: “STPT 9-10 will again be a “Fluid Four” formation as a preparation for the approach in Gunsan.”
Proposed 2: “STPT 9-10 will again transition into a “Fluid Four” formation as a preparation for the approach in Gunsan.”
Reason: proposals to fill-in missing verb

page 67
Is: “The last formation will be echelon left or right…”
Proposed: “The last formation will be “Echelon” left or right…”
Reason: adjusted to convention of writing formation names

page 67
Is: “The flight will be inbound to runway heading in echelon at about…”
Proposed: “The flight will be inbound to runway heading in “Echelon” at about…”
Reason: adjusted to convention of writing formation names

page 67
Is: “The AI uses 4-5 seconds delay in between breaks. So wait 4-5 seconds before you brake.”
Proposed: “The AI uses 4-5 seconds delay in between breaks, so wait 4-5 seconds before you break.”
Reason: connected unnecessarily split sentences; I think that the word “break” instead of “brake” was intended

page 67
Is: “…and sees you at the position where he’s expect you to see.”
Proposed: “…and sees you at the position where he expects you to be.”
Reason: “he’s expect” is incorrect here, co changed to “he expects”; replaced “to see” with “to be” as this seemed more logical (to me, ofc)

[Micro_440th]

@Fox_15 Thanks for reporting!
Old checklists will not be touched anymore.
-34 and training manual mistakes will be checked soon.

[Fox_15]

I hope you’re not fed up with me

BMS-Training
Ver. 4.36.1

All 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 -> your

page 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 -> precisely

page 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: convention

page 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 -> silently

page 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 section

page 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 commas

page 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 better

page 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 negation

page 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 document

page 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