Falcon BMS 4.37.0 - Documentation: Bug reports
-
Please provide 4.37.0 documention bugs in the following “bug format”:
Document:
Page:
Original sentence: “”
Corrected sentence: “”Thank you for your support!
-
Document: TO BMS 1F-16CM-34-1-1
Page: 252, section 4.4. 5, last two paragraphs.Duplicated sentences.
Pre-launch information is displayed below the LSDL directly above the selected missile station. Post Launch information is displayed above the LSDL and in reverse order from the station.
-
Document: BMS-Training.pdf
Page: 91
Original sentence: All other previous chapters 5.1 - 5.3 schould …
Corrected sentence: All other previous chapters 4D.1 - 4D.3 schould … -
Document: BMS-Training.pdf
Page: 128
Original sentence: … avionics in 10 independent missions.
Corrected sentence: … avionics in 11 independent missions. -
Document: BMS-Training.pdf
Page: 132
Original sentence: … (see screenshot on the next page).
Corrected sentence: … (see screenshot below) -
BMS Device Setup Guide Change 2
6-140
“Parking break Switch”
“Parking Brake Switch”
“This sets the parking break (discrete on/off or toggle) of the jet. The parking break is automatically released above roughly 83% RPM (Rounds per Minute).”
“This sets the parking brake (discrete on/off or toggle) of the jet. The parking brake is automatically released above roughly 83% RPM (Revolutions per Minute).”
In the table - column - ‘UI Name’ - “BREAK” should be “BRAKE”.Sorry the last one doesn’t follow your format!
-
BMS Device Setup Guide Change 2
2-7
“To make the key file (in specific: the DX code lines) work a specific order of the devices is necessary. Otherwise you run into trouble. As we do not know which and how many devices you have installed the DeviceSorting_Example.txt should give you a short overview how the first code lines in your DeviceSorting.txt should look like.”
“To make the key file (specifically: the DX code lines) work, a specific device order is necessary, otherwise you can run into trouble. As we do not know which, or how many devices you have installed, the DeviceSorting_Example.txt should give you a short overview of how the first code lines in your DeviceSorting.txt should look.”2-8
“I f you need an additional print layout for the keyboard please refer to …\Docs\01 Input Devices\01 Keyboard Layouts…”
“If you need an additional print layout for the keyboard please refer to …\Docs\01 Input Devices\01 Keyboard Layouts…”2-10
“Pibuilders may see that different…”
“Pit-builders may see that differently…”“We will only describe how to setup your devices via DX as much as possible. If intend to set it up using keystrokes, please refer to the vendors programming software manual.”
“We will describe how to setup your devices via DX as much as possible. If you intend to set it up using keystrokes, please refer to the vendors programming software manual.”2-10
“Therefor it was necessary work out some strict naming conventions to make it clear what the purpose of a function is.”
“Therefore it was necessary to work out some strict naming conventions to make clear the purpose of a function.”3-56
“Please refer to CH’s installing instructions.”
“Please refer to CH’s installation instructions.”3-58
“Select you main Input device from the drop down list.”
“Select your main Input device from the drop down list.”3-61
“Depending on how many device you have connected you should press one button of each device.”
“Depending on how many devices you have connected, you should press one button on each device.”4-107
“So, in order to safe you some time you can skip it for now and instead read it if you need to.”
“So, in order to save you some time you can skip it for now, and only read it if you need to.”4-107
“The main Input device is always the controller providing axis for pitch and roll input, namely the Stick. There are HOTAS versions out there which provide a combined unit of Stick and Throttle, e.g. the Saitek X-45 or the TM Cougar. In this case you must select the X-45 or Cougar as you main input device in the Setup Controllers screen in BMS like shown in the picture below:”
“The main Input device is always the controller providing axis for pitch and roll input, namely the Stick. There are HOTAS versions out there which provide a combined unit of Stick and Throttle, e.g. the Saitek X-45 or the TM Cougar. In this case you must select the X-45 or Cougar as your main input device in the Setup Controllers screen in BMS, as shown in the picture below:”“On the other hand there are also HOTAS systems which have two controller units (Stick and Throttle) like it is the case for TM Warthog. In this case you must select the Stick.”
“On the other hand there are also HOTAS systems which have two controller units (Stick and Throttle), as is the case for TM Warthog. In this case you must select the Stick.”4-110
“These tabs provide a list of all available in-game axes. Depending of the nature of the axis, each of these axes may have one of the following controls:”
“These tabs provide a list of all available in-game axes. Depending of the nature of the axis, each of these axes may have one of the following controls: (Shown opposite.)”4-111
“It might happen that an axis is not available at the corresponding drop down list because it simply is assigned somewhere else.”
“It might happen that an axis is not available at the corresponding drop down list simply because it is assigned somewhere else.”4-112
“The only way to solve that is that you go through all four control setting pages and search for the throttle axis.”
“The only way to solve that is to go through all four control setting pages and search for the throttle axis.”4-113
“We also provide a DeviceSorting_Example.txt to show you how the order should look like in your DeviceSorting.txt.”
“We also provide a DeviceSorting_Example.txt to show you how the order should look in your DeviceSorting.txt.”“1. On a short button press (>200ms) it has the real functionality as the Pinky button on the stick.”
“1. On a short button press (>200ms) it functions normally as the Pinky button on the stick.”4-114
“Note: Since 4.36 BMS also supporst devices with up to 128 buttons.”
“Note: Since 4.36 BMS also supports devices with up to 128 buttons.”4-115
“This is also the case if you use in addition rudder pedals.”
“This is also the case if you use rudder pedals.”“How DX devices are programmed via the key file is explained in depth in the chapter 10 and in short in chapter 2 of the BMS Technical Manual.”
“How DX devices are programmed via the key file is explained in the BMS Technical Manual, briefly in Chapter 2, and in more depth in Chapter 10.”“One tool to help you setting up your devices the full DX path is the Key File Editor, located in the …/Docs/01 Input Devices folder.”
“One tool to help you set up your devices using the full DX path is the Key File Editor, located in the …/Docs/01 Input Devices folder.”“If the issue persists and you can rule out #1, #2 and #3 please feel free to report your problem, preferable in this public forum thread.”
“If the issue persists and you can rule out #1, #2 and #3 please feel free to report your problem, preferably in this public forum thread.”6-141
“This switch in CAT III position stets an AOA (Angle of Attack) limit depending on the loadout (e.g. bombs, wing tanks are carried) to prevent damages to the jet. CAT I is for pure A-A loadout and has no limits.”
“This switch in CAT III position sets an AOA (Angle of Attack) limit depending on the loadout (e.g. bombs, wing tanks are carried) to prevent damage to the jet. CAT I is for pure A-A loadout and has no limits.”Sorry this is so long…
I would guess that the author does not speak English as their first language so I have taken the liberty of tidying up some sentences to make them read more naturally. Please feel free to ignore these corrections if you would prefer. -
Document: Dash 34
Page: 196
Original: The Clear avenue of Fire for AI is also implemented for IR seekers (such as AIM9)
Corrected: The clear avenue of fire for AI is also implemented for IR seekers (such as AIM-9)
Remark: Optionally ‘Clear Avenue of Fire’ with A capitalized as well.Page: 206 (under Time to Pull)
Original: and the VSCcoincide over the FPM
Corrected: and the VSC coincides over the FPM
Remark: I think ‘over’ should be ‘with’.Page: 216
Original: The AGM-65G + L uses a larger kinetic energy penetrator
Corrected: The AGM-65G and L use a larger kinetic energy penetratorPage: 227
Original: With the FCR as SOI TMS UP will command
Corrected: With the FCR as SOI, TMS Up will commandAGM-65L sections (p. 237 and elsewhere): “Laser” is capitalized a lot, should not be capitalized.
-
-
Hi @Micro_440th
TO 1F-16CMAM-1 BMS.pdf
Page 9 :
31 SERVICING DIAGRAM … 217
… Fehler! Textmarke nicht definiert.
32 Normal procedures … 218I think there is a “Fehler”.
-
Training manual:
3d -> 3D (dictionary)
(Many occurrences)p. 302
Original: beare of low level ground threats such as MANPAD’s and AAA
Corrected: beware of low level ground threats such as MANPADS and AAA
Rem: The S in MANPADS is ‘system’.p. 302
Original: Descent, make aggressive
Corrected: Descend, make aggressivep. 303
Original: find the best way for SEAD/ EW
Corrected: find the best way for SEAD/EWDash 34:
p. 276
Original: The lowest the best accuracy.
Corrected: Lower index means better accuracy.p. 278
Original: as secondary targets: see 1.4.3.1TMS down on a
Corrected: as secondary targets: see 1.4.3.1. TMS down on ap 279 (illustration)
Original: Requierd Turn
Corrected: Required Turnp. 279
Original: and the Aircraft Maneuver Zone (s are not available in RUK mode.
Corrected: ??? Not sure what is unavailable in RUK. Missing close parenthesis.p. 279
Original: The Loft angle and Apex Altitude are not implemented
Corrected: The Loft Angle and Apex Altitude are not implementedp. 284 (lower illustration)
Original: WCMD SMS cotrol page
Corrected: WCMD SMS control page -
edit: sorry, just realised I’m not quite following the proposed reporting format, will have to correct later.
DASH1:
p2
Table of contents is named “appendix”p63
Not sure if the chapter refers to ground refuel (not implemented), or goes on to explain air refueling. May be an error in subtitle levels, and 4.1.1 AIR REFUELING should have been 4.2?p66
5.1 to 5.3 sections are empty, not sure if intended - usually there’s a N/I remark on non implemented systems.p88-90
“TEF’s” plurals shouldn’t have an apostrophe.p109,110
Flaps section (15) refers to STANDBY GAINS in “this section”, however gains are covered in section 16, FLCS. -
This post is deleted! -
Document: README_FIRST_Welcome_To_The_Docs.pdf
Ver. 4.37, 14 December 2022p.2-4
In the whole “Welcome To The Docs” document and in the Foreword chapters of other manuals I propose to standardize the names of the manuals. Currently different names and different ways of writing (hyphenated in one place, non-hyphenated in other) are used. For instance, instead of “BMS-User-Manual” I suggest to write BMS User Manual. If the name appears within a body of text, to emphasize that we’re referring to a concrete document, I propose to either italicize it or enclose in double quotes (both at the same time seem excessive).
BMS-User-Manual -> BMS User Manual
BMS-Device-Setup-Guide -> BMS Device Setup Guide
BMS-Comms-Nav-book -> BMS Comms & Nav Book (also, in the said manual’s title page the title should be updated to “Comms & Nav Book” instead of “COMMS-NAV-BOOK”)
BMS-Training -> BMS Training Manual
BMS-Technical-Manual -> BMS Technical Manual
BMS-Threat-Guide -> BMS Threat Guide
BMS-Naval-Ops -> BMS Naval Operations Manual (or BMS Naval Ops Manual)
BMS-Key-File-Editor-Manual -> BMS Key File Editor Manual
BMS-Cockpit-Guide -> BMS Cockpit Interaction Guidep.2
Original: Documenting a study-sim like Falcon 4.0 BMS cannot be done in 50 pages.
Corrected: Documenting a study sim, like Falcon BMS, cannot be done in 50 pages.
Reason: correction in punctuation; “study-sim” to me does not need a dash; everywhere (including on the main loading screen) we use the name “Falcon BMS” not “Falcon 4.0 BMS”p.2
Original: To try to guide you, here is a quick explanation of what each manual attempt to cover, followed by a proposed flow.
Corrected: To try to guide you, here is a quick explanation of what each manual attempts to cover, followed by a proposed flow.
Reason: typo, missing “s” in “attempts”p.2
Original: All documents are in the \Docs folder of your Falcon BMS installation.
Corrected: All documents (except BMS Device Setup Guide) are in the \Docs folder of your Falcon BMS installation.p.2
Original: Or just click on ‘Documentation and Manuals’ on the Launcher.
Corrected: You can navigate to this folder with Windows Explorer or just by clicking “Open Docs Folder” button in the Launcher.
Reason: made this sentence connect with the prevous onep.2
In bullet VR/TRACK IR/VOICE PROGRAMS:
Original:
(\Docs\01 Input Devises\04 VR)
(\Docs\01 Input Devises\05 TRACKIR)
(\Docs\01 Input Devises\06 Voice Programs)Corrected:
(\Docs\01 Input Devices\04 VR Guide)
(\Docs\01 Input Devices\05 Track IR)
(\Docs\01 Input Devices\06 Voice Programs)Reason: incorrect folder names
p.3
Original: Learning to fly a study sim is a steep curve but rewarding curve.
Corrected: Learning to fly a study sim is a steep curve, but a rewarding one.
Reason: corrected punctuation and removed repetition of “curve”.Also, consider the following alternative that makes the sentence stronger. I think we should not be trying to make a general statement about all study sims here. After all this is a document about BMS - probably the first one that a new user reads, so let’s make it specific:
Alternative: Learning to fly Falcon BMS is a steep curve, but a rewarding one.p.3
Title of section 2.2
Original: Setup your devises
Corrected: Setup your devices
Reason: typo -
Hey,
just found another one.
Document: BMS-Training.pdf
Page: 13
Original sentence: “Note that all external lightning is implemented since 4.36”
Corrected sentence: “Note that all external lighting is implemented since 4.36”cheers
Magic -
Document: TO 1F-16CM/AM-1 BMS
Page: section 1.5, page 25
Error - The number-keyed diagram for the left console has two instances of 22.
Correction - At the location of the manual pitch override switch, change 22 to 24.Page: section 39.4, page 348
Omission - Acronym NVIS is not listed.
Correction - Add definition of NVIS (night vision?) to glossary.GC
-
Document: BMS-VR-Guide.pdf
Page: 2Original sentence: 1. If your VR headset requires to set an runtime option in the headset software, make sure it is linked to Stream VR
Corrected sentence: 1. If you have OpenComposite installed, use the OpenComposite launcher to set the OpenVR runtime to SteamVR.
Notes: The documentation includes a screenshot of PimaxXR. This tool - along with OpenXR Tools for Windows Mixed Reality and the Oculus settings - only change which OpenXR runtime is used, not which OpenVR runtime is used.
These tools can only switch between:
- BMS -[openvr]- > OpenComposite -[openxr] -> PimaxXR -> Pimax drivers
- BMS -[openvr] -> OpenComposite -[openxr] -> SteamVR -> PimaxDrivers
OpenComposite is not compatible with BMS at all due to the use of the overlay app type, so you want:
- BMS -[openvr] -> SteamVR
This requires that SteamVR is set as the OpenVR runtime - not that SteamVR is used as OpenComposite’s backend - so you need to set this through the OpenComposite launcher, not any vendor-specific tools.
-
Document: BMS Technical Manual ver. 4.36.2
Page: 27
Original sentence: “Sets the time in minutes before Takeoff time players will join 3D.”Corrected sentence: “Sets the time in minutes players have before Takeoff when launching 3D.”
Page: 31
Original sentence: “Activates (1) activates experimental support for native Tacview .zip.acmi format. It saves ACMI files in a new format ‘<timestamp>.zip.acmi’. Option (2) reverts to old .vhs ACMI format.”Corrected sentence: “Set to 1 activates experimental support for native Tacview.zip.acmi format. It saves ACMI files in a new ‘<timestamp>.zip.acmi’ format . Setting 2 reverts to old ‘.vhs’ ACMI format.”
Remarks:
- Original first sentence has ‘activates’ twice.
- In original first sentence, there is a space between ‘Tacview’ and ‘.zip.acmi’
- The entire paragraph needs to be formatted/ justified to match previous entries.
Bonus: In the 4.37 Changelog, under the General list of affected assets:
Original sentence: “Features added that make XML files incompable”
Corrected sentence: “Features added that make XML files incompatible”
-
page 60: line break necessary after “…than 18,000 pph for 30 seconds.”
page 128: 1. Power switch (3 positions) - OFF, Standby (STBY), Operate (OPR) - > standby position not implemented
-
34 Dash 1
Page 101 numbering starts from 3:
"The following applies to the initiation and verification of a successful data link transmission round:
3. Verify data link mode DMD or ASGN is displayed next to OSB 6 on the A-A FCR. Press OSB 6 if necessary to cycle through
the modes."Could be mistaken for missing steps/pages
-
Document: BMS-Training.pdf
Page: 47
Original sentence: AKEOFF OPTION: …
Corrected sentence: TAKEOFF OPTION: … -