BMS 4.34 Documents correction report
-
BMS-Comms-Nav-book page 17
“There are 4 main approaches available with BMS ATC:”
5 are listed.
Edit RD [Fixed]
-
BMS Training Manual
Pg 11On the EXT LIGHTS panel we set…
instead of EXT LIGHTNING;
THE ELEC SYS caution light…
Typo
Pg 21
The sky conditions scheme has the “AMB” fields actually white (on the COMMS & NAV Manual instead are amber).Pg.33
…at this speed you will need ~65 seconds to reach the steerpoint…
Picture reports ETE 000:58 (not sure if refers to the picture though)
Pg.36
With the AP in STRG SEL the aircraft will steer towards the HSI bearing pointer the.
Typo (or I didn’t catch the meaning)
Edit RD [Fixed]
-
Well spotted; keep 'em coming please :thumb:
-
A few edits for this departure procedure.
Edit RD [Fixed] & MSA is always the airport station in BMS
-
BMS-Comms-Nav-book page 42
Spotted by MadDoc in my voice attack profile thread, not yet listed here: element commands depicted do not match the in game menus.
-
It seems that this thread is starting to have items that are not really corrections. Could the moderators make a sub thread that shows only the confirmed corrections and lock out any changes to that sub thread?
-
A few more approach plate edits.
Edit RD [Radar Fixed] & Patro is at DME33 so it’s not PATRO
-
Redundant approach plates.
–--------------------------The Taegu (ILS RWY 32) permits a circle to land on runway 14.
The Taegu (CIRCLE TO LAND RWY 14) approach plate is not necessary.
Edit RD [Fixed] & on purpose
-
I’d like to suggest that the (IAF) be relocated to the KMH TACAN. The approach will make more sense in the plan view.
Edit RD [Fixed]
-
Recommended addition for ease of reading.
Edit RD [Fixed]
-
BMS 4.34 Dash 1
2.1 RAMP START in 3 SWEEPS, page 164, paragraph 4.
… “The audio volume for ID is not implemented.”should read
… “The audio volume for ILS is not implemented.”
similar to BMS 4.34 Training manual page 12 paragraph 4.Edit RD [Fixed]
-
Thanks to Unleashed Code for pointing the following.
BMS Training AGM-88 Training chapter. SAMs are described to have a search radar (EWR, I assume) displaying as a “S”. I don’t know if a S does appear if you enable Search Radars display, but EWR Flat Face, to give the example of the SA-6, is not a generic S, rather a F (described in Avionics Checklist and effective in .34.0) - regardless of Search radar display on RWR, obviously. .
There could be some confusion from the use or Search and Acquisition Radar and EWR, both terminologies being used for the apparent same meaning if different parts. If they litteraly are the same, this last sentence is pointless.
Edit RD [Fixed] -
Red Dog,
Unfortunately, I just noticed that there are many approach procedures with incorrect holding patterns.
The inbound or outbound arrows should point towards the holding fix. ie TACAN/DME/Waypoint. You should be flying towards the fix and then make your reciprocal course change after station/fix passage. I hope this makes sense, it’s hard to explain without drawing it in front of you.
–-----------------------------------------------
You have 2 options to correct this problem.1.) A new DME fix can be created as in the picture below.
2.) Or you can change the arrows indicating direction of holding turn.
Edit RD [Fixed]
-
**Falcon BMS Manual
page 6-74**
6.2.2 For Campaign Missions
1. Open the campaign module and stop the clock. Build TGT STPTs/LINES/PPTs as described above.
2. Upon completion, open the DTC and hit the Save button. This will write the information to the callsign.ini file. Upon entering the 3d world, the pilot will see the data on the HSD.
Unfortunately, due to technical reasons, each pilot will have to create/build the data they want to see in the cockpit in the campaign screen right before committing to 3D, since it is not possible to share it like with TEs.–-----------------------------
This appears to be saying that you cannot share ini files between players before Multiplayer Campaign missions…? This is not true, we do it all the time.
Share the ini with another player on the server, they drop it into the campaign folder, click Load DTC, it works. -
where is the error GZA?
-
Misunderstanding maybe? How are a TE PPT and Lines shared? Just upon connection, without sharing files? That would explain the extra paragraph.
-
this is a Campaign related paragraph,
unless I am mistaken, a DTC can’t be shared in Campaign, because there is no TE.ini file generated and the DTC is in the pilot.ini file.
That’s what the text says, basically, each pilot should create his DTC before going to fly, since there’s no easy way to share a single PPT/line configurationUnlike in a TE scenario where the TE creator can create the TE.ini file and spread it to the participant, then upon entering the TE, all participants will have the same PPTs and lines …
-
Hi all. Training Manual. Aspect Angle.
On page 157 the picture on the left show 18L (so 180° LEFT) on the other side the aspect angle indicator is on the right. so it means doesn’t mach with the picture on the left.
Is it correct? Thanks!
Ciao
Gundam
-
It’s explained in the text line below
Basically, there was a bug at the time of writing with the L and R
Unfortunately, there was not time to update the picture -
@Red:
this is a Campaign related paragraph,
unless I am mistaken, a DTC can’t be shared in Campaign, because there is no TE.ini file generated and the DTC is in the pilot.ini file.
That’s what the text says, basically, each pilot should create his DTC before going to fly, since there’s no easy way to share a single PPT/line configurationUnlike in a TE scenario where the TE creator can create the TE.ini file and spread it to the participant, then upon entering the TE, all participants will have the same PPTs and lines …
Then yes Red Dog, you can share PPT and Lines in campaign files, this is not a misunderstanding. A dtc save in a campaign alters the campaign.ini file. This is not how we proceed, since we rather use WDP, but when I load my own campaign missions, I have my previously set PPT and Lines re-appearing from the .ini.
Actually WDP generates ini with the same save name, so this is very much the same.