Falcon BMS 4.37.3 - Documentation Bug Reports
-
This post is deleted! -
This post is deleted! -
-
This is not a F15 key file.
-
57? 75? Whatever, it’s still not on KTO’s list. This comes with no answer to Tiags’ question 2, which is the answer to this one. No better way to acknowledge that fact that keeping it silent…
-
So far, the docs seem correct about all of that.
-
-
@P-J
-
Please read the manuals before you state in multiple threads that 4.37.3 is a “mess”. You are trying to use the keyfile of the F-16 in a F-15, that will not work.
-
When you install mods that try to hack things like the things you described, it is NOT the BMS responsibility that these hacks work. If you have any trouble with them, please contact the corresponding team.
The BMS team answers for the KTO theater, ITO (Vaicon and others) and Balkans (Cougar and others). If anything is wrong in one of these theaters, please report in the corresponding threads. NOT here.
-
-
@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)