Falcon 4.36.0 Documentation: Bug Reports
-
@Fox_15 Thanks for reporting! Very nice.
I will go through them.One note: Muan is now an airport with a VORTAC. So no change needed in AIP.
Cheers
Micro -
not sure if it’s a bug but I can now hit a target very easily in DTOS mode simple because of the TGP application. Is that the real case or is it exaggerated?
-
-
I have a question regarding the new parking charts.
Say that we are looking at a parking chart for 06R. It shows spots where spawn happens. But when landing I am sometimes not sure where to go - do the parking charts give hints on where you are supposed to go after landing on 06R or its cardinal opposite ?
So how is this documentation: The documentation talks about parking spots for takeoff, but does not mention if they are relevant for landing. Up till now you could park anywhere after landing, but the parking charts could suggest that there are some places better suited, based on which runway you land on
Thx
-
I guess this thread shows why there are no RTFM posts on this forum.
-
@jayb said in Falcon 4.36 Documentation: Bug Reports:
I have a question regarding the new parking charts.
Say that we are looking at a parking chart for 06R. It shows spots where spawn happens. But when landing I am sometimes not sure where to go - do the parking charts give hints on where you are supposed to go after landing on 06R or its cardinal opposite ?
So how is this documentation: The documentation talks about parking spots for takeoff, but does not mention if they are relevant for landing. Up till now you could park anywhere after landing, but the parking charts could suggest that there are some places better suited, based on which runway you land on
Thx
You are right about this. “Taxi back” procedures are explained pretty weak. Right now, ATC cant handle “taxi back” procedure and route you to a shelter/parking spot.
BUT, improvements for that are already cooking. -
@Micro_440th thank you that sounds great. So for now “park anywhere” still applies
-
Document: BMS Comms& Nav Book
Page: 33
Original Sentence: “The wingman menu (“z” for US layout or “w” for most other layouts)”
Corrected Sentence: "The wingman menu (“w” for US layout or “z” for most other layouts) -
Document: BMS User Manual
Page: 196
9.10 Setup
Original Sentence: The SETUP section is documented in Chapter 4 of this manual.
Corrected Sentence: The SETUP section is documented in Chapter 3.4 of this manual. -
Document: BMS COMMS & NAV Book, BMS 4.36, 30 Mar 2022
Page: 60Original sentence: “In this example, the DED CRS was set to 355° which is the magnetic heading for ILS RWY 36 Gunsan.”
Corrected sentence: “In this example, the DED CRS was set to 356° which is the magnetic heading for ILS RWY 36 Gunsan.”
The magnetic heading noted throughout the verbiage and images in the example provided in section 3.1.2 does not match the heading shown on the KTO charts located at C:…\Docs\03 KTO Charts\01 South Korea\Gunsan.
GC
-
Document: BMS COMMS & NAV Book, BMS 4.36, 30 Mar 2022
Page: 61, last paragraph, last sentenceOriginal sentence: “The EHSI does not label ILS but uses PLS instead for Precision Landing System.”
Corrected sentence: “The EHSI does not label ILS but uses PLS instead for Precision Landing System.”
Change formatting of last line in paragraph to left justified.
GC
-
BMS KTO AIP
ver. 4.36
14 MAR 2022Compared changelog, AIP and 2D and in some cases the names were not updated, so here’s the list:
1.2.4.1 (ATIS South Korea)
Choongwon (old name) should be deleted, because Jungwon (new name) is already in the table.1.2.4.4 (ATIS North Korea)
Wonsan (old name) should be changed to Kalma (new name).
Uoiju should be Uiju (according to stations+ILS.dat, but in game it is pronounced and spelled as Uiji)2.2.3
RK-111: Kunsan (old name) should be changed to Gunsan (new name)
RK-14: Kwangju (old name) should be changed to Gwangju (new name)2.3.1 (MOAs South Korea)
MOA 5: Choongwon (old name) should be renamed to Jungwon (new name)
MOA11: RKTI should be changed to RKTY (correct Yecheon’s ICAO code)
MOA6, MOA7, MOA30, MOA31, MOA32, MOA33: Kangnung (old name) should be changed to Gangneung (new name)
MOA17, MOA18, MOA19: Kunsan should be changed to Gunsan (new name)
MOA15, MOA20, MOA21, MOA22, MOA23, MOA24, MOA25, MOA26: Kwangju (old name) should be changed to Gwangju (new name)
MOA14: Taegu (old name) should be changed to Daegu (new name)
MOA27, MOA28, MOA29: Sachon should be changed to Sacheon (new name)
MOA13 EAST, MOA13 WEST: directions from Pusan but there is no such airbase3.1.4 (North Korea airbases)
KP-0021 Sunch’on (old name) should be changed to ZKSC Sunchon (new name)
Uiju ILS (Rwy) is: 110.4 (05), 110.0(23) should be should be: 110.0 (05), 110.4(23). Checked in stations+ILS.dat and confirmed in 3D.4.36 changelog
Is: Pyongtaek AB => Pyongtaek AAF (RKSG)
Should be: Pyongtaek AB => Pyeongtaek AAF (RKSG)
Reason: current implementation based on Stations+ILS.dat and 2D -
Would it be possible to run the pdf manuals or documentation through the Microsoft Word grammar and spellcheckers (assuming Word is the creating source, as it seems to be), to correct, probably 95% of those errors in the manuals? It still needs to be verified for accuracy, of course, but I’ve done that on my manuals (open the pdf’s in Word as a docx file, let it find all of the errors, then re-save back as a pdf. (It took about an hour per 100 pages for me, to verify each of the changes and corrections. Be aware that it’s NOT perfect!)
There is a lot of missing punctuation in the manuals that the grammar checker finds and fixes. These simple, auto-grammar (and spelling) corrections clarify the ideas, thoughts, directions and concepts much better than the original text in many cases. A properly placed comma or semicolon can make a world of difference in the meaning of the text!
Go U1! -
@ShawnTaylor Thanks for reporting!
-
@greatcouloir Thanks for reporting!
-
@Fox_15 Thanks for reporting!
-
@Dan I would not recommend to do that. Spellchecker is great but as you said, not perfect. So its better to do it by hand/eyeball.
-
Document: BMS Training Missions
Page: 9
Original sentence: “FAIR weather, few clouds at 5000 feet, winds 320°/13 knots, temperature 18°C, dew point 02°C, altimeter 1007 (2974),
no significant changes.”
Corrected sentence: “FAIR weather, few clouds at 5000 feet, winds 320°/13 knots, temperature 18°C, dew point 02°C, altimeter 1007 (2984),
no significant changes.”QNH is 2984.
GC
-
@greatcouloir said in Falcon 4.36 Documentation: Bug Reports:
Document: BMS Training Missions
Page: 9 METAR not correct
Original sentence: “WHEATHER Brief: RKJK INFO: B010055Z 320/5KT 9999 FEW050 9/ -1 Q1007 NOSIG”
Corrected sentence: “WHEATHER Brief: RKJK INFO: B010055Z 320/13KT 9999 FEW050 18/ 2 Q1007 NOSIG” -
@Falcon316 said in Falcon 4.36 Documentation: Bug Reports:
@greatcouloir said in Falcon 4.36 Documentation: Bug Reports:
Document: BMS Training Missions
Page: 9 METAR not correct
Original sentence: “WHEATHER Brief: RKJK INFO: B010055Z 320/5KT 9999 FEW050 9/ -1 Q1007 NOSIG”
Corrected sentence: “WHEATHER Brief: RKJK INFO: B010055Z 320/13KT 9999 FEW050 18/ 2 Q1007 NOSIG”Better go back, Wheather is spelled “Weather”… or is that olde english?
-
@Icer sorry for having misspelled “weather”, I wanted to say that the METAR and weather info are not giving the same info.