Falcon BMS 4.37.3 - Documentation Bug Reports
-
@P-J - Once again, BRO… (and everyone else commenting on his comments)-- these posts are off-topic here. Please post somewhere else unless you want to bring attention to an issue with the DOCS.
-
-
BMS Training Manual, ver. BMS 4.37.3
Page 131
Original - You may also encounter Mk-81 (250 lb) and Mk-83 (1000 lb), but theyare less commonly used than the Mk-82 and 84s, especially by F-16s.
Correction – You …. they are …Page 133
Original – Ripple has many release parameters that are explained in the Dash-34 (chapter 4.2.14.1.2.1).
Correction - Chapter 4.2.14.1.2.1 does not exist in the Dash-34 (ver. BMS 4.37.3). Discussion of release parameters for ripple release receives one sentence in CCIP delivery Dash-34, section 4.2.2.1.2.1. Consider deleting the sentence in its entirety or change the referenced chapter in the Dash-34 to what was intended.BMS Dash-34, ver. 4.37.3
Page 367
Original – Two MFD figures demonstrate CCRP.
Correction – Replace the two MFD figures to demonstrate CCIP operation per the section title and the caption below the figures. The figures do not complement the text.Page 368
Original - Maintaining a stable delivery is crucial to assist the MMC (Missile Motion Compensation) calculation process.
Question – For MMC, was Modular Mission Computer intended in lieu of Missile Motion Compensation?Page 375
Existing - The FCC/MCC will also compute maximum toss ranges,……
Correction - The FCC/MMC ……GC
-
Document: BMS-User-Manual
Page: 177
Original sentence: “3. Fill in AIRCRAFT type, ROLE, SIZE, SQUADRON & skill in the newly opened window”
Corrected sentence: “3. Fill in AIRCRAFT type, ROLE, SIZE & SQUADRON in the newly opened window”The picture just above the line should be replaced as well.
Based on the changelog the ‘skill’ is now removed from the campaign:
- Fixed: make invisible the “Skill” field on the “add flight” window callback for campaign
-
@Micro_440th
Document: BMS Technical Manual
Page 48, Para 5.7 Presets table Agency UHF (leftmost column)
Original: 10, 11, 12 ALT Ground, Approach, Tower
Corrected: 10, 11, 12 ALT Approach, Tower, Ground -
@Micro_440th
Document: BMS Tech Manual
Page: 30
Original: g_bActivateDebugStuff … (config option is listed twice)
Corrected: g_bActivateDebugStuff … (delete duplicate) -
@Micro_440th
Document: Threat Guide
Page: 41 & 42 (2 Tables)Original:
SA-3
Typical Range/Alt 9nm/120,000
Max Range/Alt 11nm/12,000ftCorrected:
SA-3
Typical Range/Alt 9nm/12,000
Max Range/Alt 11nm/120,000ft -
@Micro_440th
Document: Threat Guide
Page: 41 & 42 (2 Tables)Original:
SA-2
Minimum Range/Alt 4nm/300ft
Typical Range/Alt 15nm/230,000ft
Max Range/Alt 38nm/230,000ft230,000 ft can’t possibly be correct.
My research indicates:
SA-2
Minimum Range/Alt 4nm/300ft
Typical Range/Alt 15nm/12,000
Max Range/Alt 38nm/65,000ft -
Threat guide definitely needs reviewing but the main typo here is that the SA-3 Max altitude should be 120,000ft and not 12k. Typical engagement altitude is definitely higher than 12,000ft as well!
For the SA-2, max engagment range is likely closer to 28nm with typical engagment happening inside 18nm. Maximum altitude for the SA-2 is easily over 65k with typical altitude not too far from that.
It looks like the range nautical miles were simply converted to feet and placed as the altitude for some SAMs.
I’ll reach out to Teesquare and review this for U4.
-
Falcon BMS 4.37.3 (eventually Falcon BMS 4.37.4 or Falcon BMS 4.38.0?)
Document: Technical Manual.pdf
Page 29g_nPOV1DeviceID:
Original sentence: “Setting to override POV1 hat ID. Should be in 0…1 range”.
Corrected sentence: “Setting to override POV1 hat ID. Should be in 0…15 range”.Idem for:
g_nPOV2DeviceID:
Original sentence: “Setting to override POV1 hat ID. Should be in 0…1 range”.
Corrected sentence: “Setting to override POV1 hat ID. Should be in 0…15 range”.Note:
I’m using Alternate Launcher and I can see these values in my “Falcon BMS User.cfg”:
set g_nPOV1DeviceID 2 // SETUP OVERRIDE
set g_nPOV2DeviceID 5 // SETUP OVERRIDESo, I think that current range 0…1 is out of date and must be corrected.
For the corrected sentences, I’m assuming that BMS now support up to 16 DX devices (0…15). Correct me, if I’m wrong… -
Dcoument: User Manual
Page: 190
Original:
ALR in BMS uses flags #12 to 15 in the MissionData_0X.dat in the \Data\Campaign folder.
……Also note that ALR can be set for each team independently, by editing the MissionData_0X.dat for each team
individually via MC.Correction: MissionData_0X.xml
Also addition description similar to: Each MissionData_0X.xml is for corresponding campaign slots 1 (MissionData_00.xml) thru 6 (MissionData_05.xml). For instance, to adjust the ALR flags of the fourth down Campaign, “Double Dragon,” edit MissionData_03.xml.
-
@Prot said in Falcon BMS 4.37.3 - Documentation Bug Reports:
Document: TO 1F-15C-34-1-1 BMS
Page: 48, 49, 59
Original sentence: “STT (Signal Target Track)”
Corrected sentence: “STT (Single Target Track)”I’m not sure what the mode is called in the F-15, but as far as I know it is called “Single Target Track” in all other fighter aircraft.
Edit: page no added
Sorry, I’m a bit late on this, but you are right, in the F-15 manuals STT is called Single Target Track.
-
Page 38
“The COMM1 power knob is equipped with an ON/OFF switch and controls the volume for the COMM1 radio (UHF) when rotated
past the ON position.”Correction:
“The COMM1 power knob is equipped with an ON/OFF switch and controls the volume for the COMM1 radio (UHF) when rotated
past the OFF position” -
@SoBad which manual?
-
@Micro_440th said in Falcon BMS 4.37.3 - Documentation Bug Reports:
@SoBad which manual?
Dang-- Dash 34. I put it in the title… lolol
-
Document: KTO AIP
Page: 26
Original sentence: “2.4.2.2 IFR”
Corrected sentence: “2.4.2.2 VFR” (and indentation) -
BMS User Manual, ver. BMS 4.37.3
Page 18
Original - Those devises will be recognized by BMS automatically.
Correction – Those devices …. automatically.BMS Technical Manual, ver. BMS 4.37.2
Page 29
Original - 0 is disabled
Correction – 0 is disabled.
Add a period at end of sentence in six locations starting with set g_nAxisExp_AXIS_PITCH discussion.BMS Technical Manual, ver. BMS 4.37.2
Page 30
Original - Variable to set exponential saturation for for CURSOR Y axis…
Corrected - Variable to set exponential saturation for CURSOR Y axis.
Delete extra word, for, and delete extra period in two locations starting with set g_nAxisSat_AXIS_CURSOR_Y discussion.BMS Technical Manual, ver. BMS 4.37.2
Page 30 –
Original - 0 is disabled
Corrected - 0 is disabled.
Add a period at end of sentence in two locations starting with set g_nAxisSat_AXIS_CURSOR_Y discussion.BMS Dash-34, ver. 4.37.3
Pages 369 and 376 (MSL STEP rotary table)
Original – When a bomb is selected, the delivery mode rotary operates in the following sequence:- CCIP (Continuously Computed Impact Point)
- DTOS (Dive Toss)
- CCRP (Continuously Computed Release Point)
Sections 4.2.2.1.2 to 4.2.2.2.1 verbiage are presented in this order.
Conflict or correction – In Falcon BMS 3D world, the rotary operates in the following sequence.
- CCRP (Continuously Computed Release Point)
- CCIP (Continuously Computed Impact Point)
- DTOS (Dive Toss)
BMS COMMS-NAV-BOOK, ver. BMS 4.37.3
Page 13
Original - As a consequence, compromises are made in the ATC code that sets BMS apartfrom real life ATC.
Correction – As a consequence, …. apart from….ATC. -
@Micro_440th
My last documentation post for today, I promise.GC
BMS Dash-34, ver. 4.37.3
Global corrections: Consider changing these inconsistent terms used throughout the manual.
nonnuclear to non-nuclear
laser guided to laser-guided
inertially aided munitions to inertially-aided munitions
IAM’S to IAMs
built in to built-inPage: 475
Original sentence: In order for ab LGB to guide on a laser beam, their codes must match.
Corrected sentence: In order for a LGB to guide on a laser beam, the codes must match.Page: 475
Original sentence: An LGB is set on the ground with a specific laser code, usually by the weapon crew and cross checked by the pilot during it’s pre-flight.
Corrected sentence: A LGB … during its pre-flight.
Change An to A; change it’s to its. Consider changing weapon to weapons.Page: 475
Original sentence: For specific operations and procedures for releasing laser Guided bombs, refer to the TGP, UFC, HUD and MFD chapters in this manual and training manual for Paveway II release procedure training (Training mission #11)
Corrected sentence: For … guided bombs, … and MFDS… the training …(Training mission #11).
Uncapitalize guided, insert the, change MFD to MFDS to match the chapter title, and add period at end of sentence.Page: 477
Correction: For items 2, 3, and 4 in section 4.2.8.2.2, add a period at the end of each sentence.Page 605
Original sentence: LDR type)
Correction: All acronyms in the Glossary for the letter L starting with LDR are incorrect due a formatting (spacing) mistake. -
Thank you all for the reports.
-
BMS Dash-34, ver. 4.37.3
Page: 497
Original sentence: When Impact or attack azimuth is selected for JDAMs or WCMDs, a LAR2 will appear on the HUD pp.
Suggestion or correction: What is intended by pp? Consider replacing it with the word pages, deleting it, or clarifying it. PP is not in the glossary.Page: 497
Original sentence: The LAR2 upper tick will mark the minimum release range which will allow the bomb to follow the attack azimuth on the way to the target.
Suggestion or correction: Confirm minimum is correct. Should it be changed to maximum?Page: 497
Original sentence: Release above that range will force the bomb to give up the attack azimuth and fly directly to the target
Corrected sentence: Release … target. Add period.Page: 500, SPICE LAR2 Scale figure
Original sentence: LAR2 [small font 2] Scale
Corrected sentence: LAR2 ScalePages: 601 to 609
Suggestion or correction: Locations of bold-face text vary throughout the section. Consider reformatting to make it consistent. (Examples – On pages 601 to 607 and 609, acronyms in the left-most column are bolded, but acronyms in the third column are not. On page 608, all text is bolded.)