Falcon 4.36.0 Documentation: Bug Reports

[MaxWaldorf]

@Fox_15 said in Falcon 4.36 Documentation: Bug Reports:

BMS Comms & Nav Book 4.36
p.14
Is: “Since 4.36 you can now intercupt the transition at any time when changing the VHF frequency.”
Should be: “Since 4.36 you can now interrupt the transmission at any time when changing the VHF frequency.”
Reason: typos

Training Manual 4.36
p.106 - duplicated sentence “When you ripple bombs in CCRP, the pipper shows where the first bomb will impact.”

Dash-34, change 4.36.0

p.83 (section 3.4.7.1.3)
Is: “DBS2 will provide a FOV roughly double that of EXP and DBS1 with improved resolution (64:1).”
Proposed: “DBS2 will provide a FOV roughly half of that of EXP and DBS1 with improved resolution (64:1).”
Reason: When we zoom in, FOV is narrower, not wider.

AIP 4.36
TACAN ranges cross checked with Stations+ILS.dat:

1.2.1.1 (TACANs South Korea)
Gimhae - current range: 35 NM, should be: 140 NM
Seosan - current range: 50 NM, should be 35 NM

1.2.1.2 (TACANs Japan)
Hiroshima - current range: 140 NM, should be 35 NM

2.2.3
RK-110 PILSUNG (KOTAR) - KOTAR frequency provided (306.8) is incorrect; it should be 233.8 (as indicated in Training Manual 4.36 p.105 ).

Thank you for your feedback, taken into account!

@Micro_440th changes done in our tools (cloud)

[greatcouloir]

@MaxWaldorf

I’m sure you are speaking with authority in the conversion; I’m not. However, I was unconvincingly attempting to point out QNH in the training TE appears to be 2984 despite what is noted in the accompanying documentation.

GC

[Micro_440th]

@MaxWaldorf said in Falcon 4.36 Documentation: Bug Reports:

@greatcouloir Sorry but 1007 -> 2974 …

Mission is 1010->2983. Will be changed

[greatcouloir]

@SoBad
Document: BMS Training Missions
Page: 71
Original: last figures in section 5.3 illustrating refueling sequencing, Receiver is spelled incorrectly four times in captions
Correction: change Reciever to Receiver

GC

[SoBad]

User Manual:

Page 2-14
“IVC config files is not compatible”
Should be:
“IVC config files are not compatible”

Page 3-26, bottom of page
“g_fSmartScalingThreshold defaults to 1.0 which is 1nm. Replacing 1.0 with 0.2 or 0.5 will provide no automatic scaling for objects closer than 0.2 or 0.5 Nm respectively and start the BMS Smart Scaling from that point”
Suggest instead, for clarity:
g_fSmartScalingThreshold defaults to 1.0. This means that SmartScaling will not begin until the object is 1nm away. You can make this value higher or lower, which will determine at what distance SmartScaling will begin

Page 9-192
“The ACMI conversion has been greatly improved, so you get from 3D to briefing much shorter.”
Suggest:
“The ACMI conversion has been greatly improved, so you get from 3D to briefing much more quickly.”
or
“The ACMI conversion has been greatly improved, so you get from 3D to briefing in much less time.”

[LorikEolmin]

I suppose I don’t need to explain what’s wrong.

BMS-Training p153.

EDIT: actually there’s no dome on D either at the moment, but I suppose it was reported already.

[Fox_15]

BMS Training Manual 4.36

Date: 05 APR 2022

p.63
Is: “The drop of pressure prevents the fuel external tanks from being transferred to the internal tanks.”
Proposed 1: “The drop of pressure prevents the fuel from external tanks from being transferred to the internal tanks.”
Proposed 2: “The drop of pressure prevents the external tanks fuel from being transferred to the internal tanks.”
Reason: missing “from” or wrong word order

p.63
Is: “If the AAR door remains open for too long though the depressurized external tanks may create a trapped fuel situation as they contain fuel not being transferred into the main tanks.”
Proposed: “If the AAR door remains open for too long though, the depressurized external tanks may create a trapped fuel situation as they contain fuel not being transferred into the main tanks.”
Reason: punctuation

p.104
Is: “In any case LADD in BMS is
not fully implemented.”
Proposed: “In any case LADD in BMS is not fully implemented.”
Reason: unnecessary line break in the middle of line

p.115
Is: “Select Pupo-ri Naval Base in the target list and click on the first dock crane (yellow).”
Proposed: “Select Pupo-ri Naval Base Port in the target list and click on the first dock crane (yellow).”
Reason: the actual name in 2D is Pupo-ri Naval Pase Port.

p.115
Is: “Select Pupo-ri Naval Base in the target list and click on the first dock crane (yellow). It will turn green in the list and the Recon window will show the selected crane in the center.”
Proposed: “Expand Pupo-ri Naval Base Port in the target list and click on the “Dock Crane” entry. The entry in the list will turn green and the Recon window will show the selected crane in the center - confirm it is the yellow crane.”
Reason: making it clearer what user should do and what is the outcome

p.125
Is: “Since only two HARMs can be carried a second TE run need to be done focusing on the SA-4 battery using
the HTS pod and HAD page.”
Proposed: “Since only two HARMs can be carried, a second TE run needs to be done, focusing on the SA-4 battery using the HTS pod and HAD page.” or even better (to my taste): “Since only two HARMs can be carried, a second TE run, focusing on the SA-4 battery using the HTS pod and HAD page, needs to be done.”
Reason: missing “s” suffix in “TE run needs to be done” and punctuation/clause ordering proposal.

p.125
Is: “Another targeting system is available only when the AN/ASQ-213 HTS (Harm Targeting System) pod is loaded on the left chin pylon: HAD (Harm Attack Display).”
Proposed: “Another targeting system is available only when the AN/ASQ-213 HTS (HARM Targeting System) pod is loaded on the left chin pylon: HAD (HARM Attack Display).”
Reason: HARM acronym should be in capitals

p.125
missing bullet points before:
SEAD (Suppression of Enemy Air Defenses).
DEAD (Destruction of Enemy Air Defenses).

p.125
Bullet by “PPT 57: SA-2 (fixed) Fan Song missile guidance (‘2’)” has orange color instead of black.

p.125
Is: “Before entering 3d, we will have a look at the DTC in 2d.”
Proposed: “Before entering 3D, we will have a look at the DTC in 2D.”
Reason: typo/consistency - 2D

p.128
Is: “4.35 introduced changes if the radar is not emitting:
If the radar is not emitting the missile will either FLEX (…), or GLIDE (…) or hit (…).”
Proposed: “4.35 introduced changes if the radar is not emitting: if the radar is not emitting the missile will either FLEX (…), or GLIDE (…) or hit (…).”
Reason: the line break seems unnecessary since we are enumerating options in a single line rather than in bulleted list.

p.130
Is: “Should the missile be fired now it would go toward Steerpoint 4, activate its seeker at a defined range and look for radar emissions from a Fan Song or Spoon rest radar.”
Proposed: “Should the missile be fired now it would go toward Steerpoint 4, activate its seeker at a defined range and look for radar emissions from a Fan Song or Spoon Rest radar.”
Reason: “Spoon Rest” should be capitalized

p.130
In sentence: “The HARM missile is capable of Mach 3+ speeds, has a missile motor burn time of about 45 seconds and a range of up to 60 Nm in BMS. This is longer than any SAM engagement zone in Korea (the SA-10 is 50 Nm and the older SA-5 is 53 Nm).” there seems to be some weird long space between “missile” and “motor” and between “60 Nm” and “in BMS”.

Dash-1 4.35

Change 3.00

p.127
Is: “Lead on the other hand has to ensure that the difference between the A/L and the F/R needle values do not exceed 600 Pounds each way.”
Proposed: “Lead, on the other hand, has to ensure that the difference between the A/L and the F/R needle values does not exceed 600 pounds each way.”
Reason: added punctuation around OTOH, decapitalized “pound”, corrected form of the auxiliary verb because it refers to the “difference” not to the “needle values”.

p.128
Comma after “obviously” in first paragraph: “Obviously, the centre of gravity moves according to the way the aircraft is loaded.”
Comma after “in this way” in first paragraph: “In this way, fuel load and fuel transfer will greatly impact the centre of gravity position.”
Comma separating parenthetical clause: “The CG moves along two axes, depending on the load, and must remain within certain limits for the aircraft to remain controllable.”
Missing “as”: “In the same way as asymmetric weapon loadouts induce the heavy wings to drop, a fuel heavy wing will drop as well.”

p.128
Is: “This CG longitudinal shift is much more subtle than left & right shift because it often goes unnoticed but may induce quicker departure at higher AOA, especially dangerous for aerobatics, approach and landing.”
Proposed: “This CG longitudinal shift is much more subtle than left & right shift, so it often goes unnoticed, but may induce quicker departure at higher AOA, especially dangerous for aerobatics, approach and landing.”
Reason: subtlety causes the longitudinal CG shift being unnoticed, not the other way round, so conjunction “so” is appropriate, not “because”; added commas separating independent clauses

p.128
Is: “We can therefore define two types of imbalance and luckily the least dangerous one will probably happen before the more dangerous one, which will help you to correct it before it becomes serious.”
Proposed: “We can therefore define two types of imbalance and, luckily, the least dangerous one will probably happen before the more dangerous one, which will help you to correct it before it becomes serious.”
Reason: punctuation

p.128
Is: “Since the left and right side empty first into the fuselage any kind of imbalance happening soon after take-off will probably induce a shift of the CG to the left or to the right, inducing a roll which can be neutralized with the aileron trim in the exact same way an asymmetrical loadout is compensated.”
Proposed: “Since the left and right sides empty first into the fuselage, any kind of imbalance happening soon after take-off will probably cause a shift of the CG to the left or to the right, inducing a roll, which can be neutralized with the aileron trim in the exact same way as an asymmetrical loadout is compensated.”
Reason: punctuation, missing “s” in “sides”

[Fox_15]

Also, while reading Dash-34 about HARMs I noted places that could use some improvement, mostly stylistically. Since this turned out to be a lot of text, I opted to link to the file on Google drive. However, I can copy it here if you think it would be better.

Dash-34
Change 4.36.0
Chapter 4.4 HARM - mostly stylistic suggestions here

[greatcouloir]

Document: BMS User Manual
Page: 8-117, section 8.7.2
Original sentence: “The left image shows the default NVG view. The right image shows the full screen option.”
Corrected sentence: “The left image shows the full screen option. The right image shows the default NVG view."

The caption below the images is reversed. Alternatively, leave the caption as is and invert the order of the images.

GC

[Micro_440th]

@greatcouloir Fixed in U2

@Fox_15 : HARM issues fixed in U2

Thanks for reporting!