Falcon 4.36.0 Documentation: Bug Reports
-
Falcon BMS team member Micro_440th suggested that documentation errors be provided in the following “bug format”:
Document:
Page:
Original sentence: “”
Corrected sentence: “”Hopefully, this Topic will serve as a central point to make bug reports regarding the 4.36 documentation, as that would be a very convenient central resource for Falcon BMS team members who are responsible for the 4.36 documentation.
@Micro_440th - If you agree with this in principle, could you pin this topic?
Let me start with something I noticed the first day I downloaded 4.36…
BMS User Manual
Page 2-9"To be able to run the 64-bit version of BMS you obviously need a 64-bit operating system. It is now advised to r
At the time of writing this manual Windows 10 x64 is probably the best choice of operating system for BMS."
As you can see, whatever was supposed to be after “It is now advised to r” is missing.
-
Good stuff!
I’m not able to make it sticky here.
Edit: sticky now -
-
-
-
@SoBad Fixed. Thanks.
-
Small stuff, but this is what I encountered while setting up:
Document: bms user manual
Page: 2-14
Original sentence: “joystick files can be restored from earlier version”
Correction: maybe explicitely name the files needed? (axismapping.dat and
axismapping_tmp.dat)Original sentence: “RTT server/client.ini files received an update. Old files
should not be used.”
Correction: Both RTTClient.ini files (335 and 336) state the same
version of 4.1 made by DUnc 2021/07. Either they are the
same, or it’s a typo within the header of the ini file.Page: 7-83
Original sentence: “Please note there are no new flyable aircraft in BMS 4.35”
Correction: BMS 4.36Document: Falcon BMS Editor manual
Page: 2/4
Original sentence: “Updated Keyboard Tab (Prontout) descriptions”
Correction: Printout -
Document: BMS Device Setup Guide, BMS 4.36.0, Change 2, 04.2022
Page: section 3.13, page 3-14
Original sentence: “Select one of the two provided key files located in the …/03 HOTAS Setup/TM Cougar (Dunc_DX) folder:…Copy the file of your choice and paste it to the …/User/Config folder.
Corrected sentence: “Select one of the two provided key files located in/User/Config folder.”
The copy/paste operation is no longer necessary with 4.36.0.
GC
-
Document: HOTAS Print Layout.pdf
Location: C:…\Falcon BMS 4.36\Hotas\TM Cougar
Original sentence: “GEAR: PARKING BREAK Switch - Cycle"
Corrected sentence: “GEAR: PARKING BRAKE Switch - Cycle"
That one has been around for quite a while.
GC
-
Document: BMS-Training Manual 4.36
Page: 53 - section 3.3 Taxi back and shutdown the jetOriginal sentence: “Once the runway is cleared, retract your speedbrakes and witch the nosewheel light from LANDING to TAXI.”
Corrected sentence: “Once the runway is cleared, retract your speedbrakes and switch the nosewheel light from LANDING to TAXI.”
Correction: typo -> witch corrected to switch.
-
@Fluke said in Falcon 4.36 Documentation: Bug Reports:
Page: 2-14
==FIXED==Either they are the
same, or it’s a typo within the header of the ini file.
==FIXED==Page: 7-83
Original sentence: “Please note there are no new flyable aircraft in BMS 4.35”
==FIXED==Document: Falcon BMS Editor manual
Page: 2/4
==FIXED==Thanks for reporting.
-
@greatcouloir said in Falcon 4.36 Documentation: Bug Reports:
Document: BMS Device Setup Guide, BMS 4.36.0, Change 2, 04.2022
Page: section 3.13, page 3-14
FIXED
Thanks for reporting.
-
@greatcouloir said in Falcon 4.36 Documentation: Bug Reports:
Document: BMS Device Setup Guide, BMS 4.36.0, Change 2, 04.2022
Page: section 3.13, page 3-14
FIXED
Thanks for reporting.Fun fact: This damn typo haunts me since 4.33. I hope you finally found its last occurrence.
-
This post is deleted! -
@ZeeMan90 said in Falcon 4.36 Documentation: Bug Reports:
Document: BMS-Training Manual 4.36
Page: 53 - section 3.3 Taxi back and shutdown the jetOriginal sentence: “Once the runway is cleared, retract your speedbrakes and witch the nosewheel light from LANDING to TAXI.”
Corrected sentence: “Once the runway is cleared, retract your speedbrakes and switch the nosewheel light from LANDING to TAXI.”
Correction: typo -> witch corrected to switch.
Thanks! Will be fixed in U1
-
Document: BMS Training
Page: 33
Original sentence: “In this training scenario your jet is empty, you only caring 1 AIM-9M + T50 on the wingtips.”
Corrected sentence: “you only carry / you are only carrying”Document: BMS Training
Page: 159, first image caption
Original sentence: “Riffle”
Corrected sentence: typo “Rifle”Document: BMS Training
Page: 159
Original sentence: “You mission is accomplished”
Corrected sentence: typo “Your mission is accomplished”(i’m no native english speaker, so if these are no error I apologize)
-
BMS User Manual, version BMS 4.36, change 4.00, 04.2022
9-130
Is (bullet): “TOS: Time over Steerpoint in local (Falcon) time”
Should be (proposal) : “TOS: Time over Steerpoint in TE’s UTC time”
Reason: this field currently shows UTC time9-143
Is: “TEs by default start Day1 at 0000 ZULU Time and end at Day 2 0000z.”
Proposed: “TEs by default start Day1 at 0000 ZULU Time and end at Day 20 0000z.”
Reason: update according current implementation9-143
Is: “It is interesting to vary the time of the TE to avoid having all TEs starting at 0000z (1000Lt)”
Proposed: “It is interesting to vary the time of the TE to avoid having all TEs starting at 0000z (0900Lt)”
Reason: Time zone in Korea is UTC+99-144
Is: “The initial plan for this TE also calls for the destruction of the nearby Soktam-Ni radar station.”
Proposed: “The initial plan for this TE also calls for the destruction of the nearby Tach’ung-ni (previously Soktam-Ni) radar station.”
Reason: Name of the radar station changed.9-145
Is: “Click OK and repeat the process for the other two squadrons.”
Proposed: “Click OK and repeat the process for the other squadron.”
Reason: Prior text mentioned only 2 squadrons, not 3.9-146
Is: “The target for the second Strike flight will default to the Underground Factory as well so select Soktam-Ni Radar station from the drop down list.”
Proposed: “The target for the second Strike flight will default to the Underground Factory as well so select Tach’ung-ni Radar station from the drop down list.”
Reason: Name of the radar station changed.9-146
Is: “Click OK and repeat the same process for the other 3 flights. Assign a 4-ship block 50 for Escort with target as one of the Strike flights and 2 flights of 2 Korean block 52s for Strike.”
Proposed: "Click OK and repeat the same process for the other 3 flights. First create two flights of 2 Korean block 52s and then create 4-ship block 50 for Escort with target pointing to one of the Strike flights.
Reason: When Escort flight is created before Strike flights, it is impossible to point Strike flight as the escort’s target.9-148
Is: “Steerpoint 4 will be the PUSH point over the small village of Yongp’a-don, 38 Nm NNW of Incheon.”
Proposed: “Steerpoint 4 will be the PUSH point over the small village of Yongp’a-dong, 38 Nm NNW of Incheon.”
Reason: Correction of the name of the village.9-148
Is: “The exit from the target will be to the left towards steerpoint 7 at P’yungyang-Ni city, which is common again for the whole package.”
Proposed: “The exit from the target will be to the left towards steerpoint 7 at P’yungyang-Ni Village, which is common again for the whole package.”
Reason: Correction of the name of the village.9-149
After sentence “Steerpoint 5 is the package IP. The SEAD flight will start their SEAD duties enroute to Steerpoint 5 and will continue to do so until the strikers are safely out of the target area. Assign altitude accordingly.”
Add (proposed): “Note that strike flights in this example by default have IP assigned to steerpoint 6. To make all flights have IP on steerpoint 5, delete the original steerpoint 5 for strike flights.”
Reason: Strike flights by default in this example have one extra steerpoint, as compared to SEAD and escort flights.9-149
Is: “055200z for the Strike flight attacking the Radar station.”
Proposed: “055205z for the Strike flight attacking the Radar station.”
Reason: Making it consistent with prior description9-149
Is: “055230z for the Strike flight attacking the underground factory.”
Proposed: “055235z for the Strike flight attacking the underground factory.”
Reason: Making it consistent with prior description9-150
Is: “The Roster states that a SA-11 battalion is made of 6 SA-11 vehicles, 3
support trucks, …”"
Should be (proposed): “The Roster states that a SA-11 battalion is made of 6 SA-11 vehicles, 2
support trucks, …”
Reason: Slight change in current roster9-151
Is: “Add a MiG-29 squadron at Sunan airbase, a MiG-23 squadron at Kalma and a MiG-25 one at Ongjin.”
Proposed: “Add a MiG-29S Fulcrum-C squadron at Sunan airbase, a MiG-23ML Flogger-G squadron at Kalma and a MiG-25 Foxbat one at Ongjin.”
Reason: Discussion about MiG-29’s loadout mentions AA-12 missile, which is only supported by Fulcrum-C variant. Since we provide exact name of the MiG-29’s variant, exact names of the two other types of aircraft are updated as well. -
TO BMS 1F-16CM-34-1-1.pdf
Page 190/191:
“Note well: Flight models were comprehensively updated in 4.33 for many missiles, including the AIM-120B and AIM-120C, which now have very different characteristics. Experienced pilots will notice many missiles behave more realistically now. As a result the DLZ can be relied upon as a much more accurate trigger for offensive and defensive maneuvers; previously you often needed the target deep in the No Escape (Rtr) region in order to kill it. In simple terms, if you shot at Rpi the missile loss of energy at end game allowed targets to be head-on when the missile went active (Pitbull), turn away, accelerate while going low, out drag the missile for a good 30s and come out of it alive.
This also meant that Minimum Abort Ranges (see below) were not really critical and you could usually overshoot MAR without sweating too much. Hopefully, with the new missiles, this won’t happen and Minimum Abort Range will be critical again.”This note can be removed.
We’re at 4.36 now and most of what is mentioned in the note is not valid any more.
The missile loss of energy at end game is incredible. The target just has to turn away, go low and light up the AB to evade a missle.
Instead add a reference to the training manual, where additional stuff (chapter 18.3.1 WEZ & co.) is explained. -
Document: TO BMS1-F16CM-34-1-1
Page: 78
Original sentence: “The symbol on the HMCS is initially moved on the ground point with head movement Once the symbol is ground stabilized, it may be slewed.”
Corrected sentence: typo, a period is missing between the two senteces
“The symbol on the HMCS is initially moved on the ground point with head movement. Once the symbol is ground stabilized, it may be slewed.”Page: 80
Original sentence: “The backup sensor can be accessed also from any OFF MFD page”
Corrected sentence:“The backup sensor can be accessed also from any A-G FCR MFD page” -
@vandroy Thanks for reporting. Will be fixed for U1 (both training and Dash-34>except the OFF MFD report page 80 which is reported wrong)
-
@Razor161 Thanks for reporting. Will be fixed in U1.
-
Document: BMS-Training.pdf
p. 255+256, the blue radio transmissions to the right of the text:
It seems the readback on p.256 does not match the 9-line on p.255:
Elevation on 9-line is 099 but read back as 2854.
The N/E values for line 6 are slightly off as well.p.258:
If you have no ordnance left (Winchester) or you
must go RTB, press (7) to check-out with the JTAC.Suggest to replace “Winchester” with “Dakota” in the CAS context
Thx,
JayB -
@Fox_15 said in Falcon 4.36 Documentation: Bug Reports:
BMS User Manual, version BMS 4.36, change 4.00, 04.2022
9-130
…
9-143
…
9-143
…
9-144
…
9-145
…
9-146
…
9-146
…
9-148
…
9-148
…
9-149
…
9-149
…
9-149
…
9-150
…
9-151
…All Fixed. Thanks for reporting.
You guys really do a good job here. This helps a lot. Those details are easily overlooked.