Falcon BMS 4.37.2 - Documentation Bug Reports
-
Document: All Incheon Departure and ILS ARR charts
Page:
Original sentence: “NCN VORDME Morse Code Identifier is … , . - - - ,- - - ” (remove commas)
Corrected sentence: “NCN VORDME Morse Code Identifier should be -., -.-., -.” (remove commas) -
@Micro_440th
Dash 34
Page 173, Bottom of page
Original:
“…ensure the Master Mode switch…”
Corrected:
“…ensure the Master Arm switch…” -
Preface: The Aux Comms panel referred to in the Training Manual is labeled IFF in the 3D sim for the training exercise and is referred to as the IFF Control Panel in TO 1F-16CM/AM-1 BMS. The illustration on page 11 of the Training Manual also needs to be updated, but not sure how/where to report that. If I had any skill as a graphic artist I’d submit a correction. Assuming the TO is authoritative here are some bug reports.
Document: BMS - Training Manual
Page: 13
Original sentence:2. Moving up we quickly check the AUX COMM panel to check that the CNI knob is turned to BACKUP.
Corrected sentence:
2. Moving up we quickly check the IFF panel to check that the CNI knob is turned to BACKUP.
Document: BMS - Training Manual
Page: 18
Original sentence:Move back to the left console and the AUX COMM panel.
Corrected sentence:
Move back to the left console and the IFF panel.
Document: BMS - Training Manual
Page: 108
Original sentence:The UFC is not available, so you need to switch the CNI knob on the AUX COMM panel to the BACKUP position.
Corrected sentence:
The UFC is not available, so you need to switch the CNI knob on the IFF panel to the BACKUP position.
-
Dash34
2.12.2
Original
“Activated or deactivated the alignment mode is using M-SEL on the ICP”
Corrected
“Activate or deactivate the alignment mode by using M-SEL on the ICP” -
Not a definite bug report but a curiosity, when directed to land RWY18 at Gunsan the parking spot I’m directed to was 00 but on the RWY36 chart, not RWY18 chart. I would expect that the chart called RWY36 would apply to landing and takeoff ops on 36, not 18. Or is it that the takeoff parking for one runway is the landing parking for the other? In either case the charts could be more clear.
-
@Frederf said in Falcon BMS 4.37.2 - Documentation Bug Reports:
Not a definite bug report but a curiosity, when directed to land RWY18 at Gunsan the parking spot I’m directed to was 00 but on the RWY36 chart, not RWY18 chart. I would expect that the chart called RWY36 would apply to landing and takeoff ops on 36, not 18. Or is it that the takeoff parking for one runway is the landing parking for the other? In either case the charts could be more clear.
Hi @Frederf!
What did ATC told you after requesting taxi back? In U2 you get taxi route and parking spot information. Not sure why you should use any RWY36 related info. ATC will not give any active RWY information when request taxi back. The APC RWY18 does have a parking spot 00.
-
@Micro_440th Right, but I went to the RWY36/00 parking spot and then the next AI came in and parked in RWY36/01. The ATC just said to park at parking “00” without telling me which but obviously the desired spot was the RWY36 one despite runway 18 being active.
I just landed Gunsan RWY18 as #2, (#1 AI). I got told “taxi to parking A P 01”. AI lead went into RWY36/00.
-
This post is deleted! -
@Frederf okay thanks for clarification. Will check
-
Not really that big of a deal but I have been confused because I have never seen an “A-Pole” Pre launch but it turns on that and M-Pole are the same. There is no pre launch distance estimation of HPRF.
TO 1F-16CMAM-34-1-1 BMS
Page 197Original
A-POLE: Range from your aircraft to the target when the missile will go active (HPRF).Corrected
A-POLE: Range from your aircraft to the target when the missile will go active (MPRF).Needs be be removed.
M-POLE: Same as A-POLE but MPRF active.A-Pole = M mnemonic
Pg 200
In the image the M-Poles need to replaced with A-Poles -
TO 1F-16CMAM-34-1-1 BMS and/or TO 1F-16CMAM-1 BMS
Page: N/AAll mention of how IFF functions on the FCR (what symbols mean what, what buttons to press to initiate IFF interrogations, etc) are missing from either the -34 or -1, whichever document is appropriate for it. The -1 directs the user to the -34 to learn more about the TMS switch and IFF, but the -34 has no mention of TMS switch as applicable to IFF, nor does it mention how IFF functions on the FCR at all. The training manual briefly mentions IFF in the IR Intercept and BARCAP mission segments, but it only mentions initiating a scan and receiving negative response, no guidance on how to use IFF is included.
-
@abradyson said in Falcon BMS 4.37.2 - Documentation Bug Reports:
TO 1F-16CMAM-34-1-1 BMS and/or TO 1F-16CMAM-1 BMS
Page: N/AAll mention of how IFF functions on the FCR (what symbols mean what, what buttons to press to initiate IFF interrogations, etc) are missing from either the -34 or -1, whichever document is appropriate for it. The -1 directs the user to the -34 to learn more about the TMS switch and IFF, but the -34 has no mention of TMS switch as applicable to IFF, nor does it mention how IFF functions on the FCR at all. The training manual briefly mentions IFF in the IR Intercept and BARCAP mission segments, but it only mentions initiating a scan and receiving negative response, no guidance on how to use IFF is included.
Working on it https://forum.falcon-bms.com/topic/24758/falcon-bms-4-37-2-status-of-the-dash-34?_=1683280000040
-
Document: BMS-Comms-Nav
Page: 10
Original sentence: “Departure is the 4th page…”
Corrected sentence: “Departure is the 5th page”Actually, the whole section reports incorrect “3rd page, 6th page, 7th page, etc.” references because apparently at the time you were updating it, they hadn’t added an intervening ‘Approach 2’ menu, so that threw everything off.
-
@Micro_440th
Document: BMS-User-Manual
Page: 169 - Starting a Campaign
Original sentence: “We will start with Rolling Fire in the Korea standard theatre…”Yet every single picture for the next 12 pages shows a Tiger Spirit campaign being referenced.
-
@SoBad already fixed for u3
-
This post is deleted! -
In the BMS User Manual, the Briefing Window is addressed starting at page 174.
Each major section of the Briefing Window is briefly discussed… EXCEPT the ‘Steerpoints’ section of the Briefing Window, which is entirely absent. (???)
-
Hi Micro_440th,
I think there are some very minor issues in Document:
\Falcon BMS 4.37\Docs\03 KTO Charts\01 South Korea\Cheongju\Cheongju_ILS_24R.pngCheongju has 2 runways 24/06 both Left and Right with runway headings 059/239.
Tacan CHO with 42X is located pretty close to runway 24R/06L.
I find 3 possible issues as can be seen in attached picture:-
In order to intercept runways 24 you might want to turn inbound at radial 070.
Original sentence: “R-060” and “Start LEFT turn passing R-060 …”
Corrected sentence: “R-070” and "Start LEFT turn passing R-070 …” -
MIssed Approach procedure says:
“Climb on runway heading … Intercept R-230 …”
Runway heading is 239. In order to intercept R_230 I might want to turn left instead of right, as shown by the dashed line. -
At the bottom of the chart in the vertical profile it says “320”, when arriving at DME13.
I’m wondering, if this shouldn’t be “330” ?
Thanks
Sunnny -
-
This post is deleted! -
Hi,
Complete newcomer to BMS (and study sims). So I’m going to post here from a very naive perspective.
I’m following the training manual and I’m finding it good, but at times a bit “frustrating” with some omissions that leave the reader a bit lost. I’ll give a couple examples later, although watching some of the videos has also helped significantly, so I might have missed other things.
But before that, I’d like to suggest something a little more profound. Judging from my experience, and lots of threads online, one of the main challenges a newcomer faces is actually doing the key mapping. It’s overwhelming to map dozens of buttons when you don’t know what 90% of those do and if they even matter at all.
I think each of the training missions could have a preliminary section where the user can incrementally be informed of what new bindings are now necessary to add. This might be particularly useful when it gets to advanced stuff like weapon systems (I haven’t gotten there yet).
I don’t know if this follows the “spirit” of this training manual, as I can appreciate if it’s written to emulate a real life training guide (and you don’t bind keys in real life! :P).
But I think this would make BMS much more approachable to complete beginners, as they’d be guided both on how to use the systems, as well as to what they need to bind at that point in time, without being overwhelmed by things they don’t yet need to understand.With that said, here’s a couple more tactical pieces of feedback, following the template:
Document: BMS - Training Manual
Page: 41
Original sentence: “Passing 14000 feet set your altimeter to QNE: 1013 Mb or 29.92 inHg.”Corrected sentence: “Passing 14000 feet set your altimeter to QNE: 1013 Mb or 29.92 inHg (use the barometric setting knob, located at the lower left corner of the instrument. Refer to section 29.1 of the -1 flight manual for detailed information about the altimeter)”.
Rationale: As a newcomer, it’s not obvious how to adjust the Altimeter, and which units does it use (Mb or inHg?). Reading the -1 clarifies it, but one needs to know what to look for (e.g., there’s no mention of QNE on the -1). This also fosters a closer relationship of the user to go back and forth between the training manual and the airplane manuals.
====
Document: BMS - Training Manual
Page: 55
Original sentence: “In this training it is recommended to take seat #2 or #4 of the flight.”Corrected sentence: “In this training it is recommended to take seat #2 or #4 of the flight. <insert small image with the shape of numbers>"
The image could look something like this: