I think it is purely by accident.
Posts made by Fox_15
-
RE: Why BMS team put a Link 16 device in Christmas message photo?
-
RE: Mouse Lag
Hi,
I think what you describe can be due to low FPS. I have the same when flying on a low-spec laptop.
Try to put those lines in theFalcon BMS User.config
located in<bms install dir>\User\Config
.set g_bEnvironmentMapping 0 set g_bWaterEnvironmentMapping 0 set g_bEnvMapRenderClouds 0 set g_bEnvMapRenderFocusObject 0 set g_bShadowMapping 0 set g_bShadowOnSmoke 0 set g_bReducePSFires 1 set g_bHdrLighting 0 set g_bHdrLightingStar 0 set g_bUseHeatHazeShader 0 set g_bShowFarRain 0 set g_bShowRainDrops 0 set g_bShowRainRings 0
If it helps with the mouse and in general fluidity, you can enable them one-by-one to improve graphics at the cost of FPS.
There is some discussion about performance optimizations in https://forum.falcon-bms.com/topic/23970/fps-optimization-for-campaigns
and there were others, which I cannot find right now. -
RE: Falcon BMS 4.37.3 - Documentation Bug Reports
@P-J I understand that you may be facing some issues, but this thread is exclusively for issues with documentation, not with the game itself. Please create dedicated threads for each issue you have and maybe someone will be able to help you out.
-
RE: FoxVox Free voice control software for BMS
@Rasmus I was playing with FoxVox VCC just yesterday and found the same issue. It seems the “Ready Start Two” command does not switch to the “Post Start” configuration. To fix that, I edited the “Test: rpm to 65” output command (by clicking little pencil icon) by its name and then set “Post Start” in “Config” fields for both keys and voice:
I don’t know if this is the only way or the most proper, but it worked
Remember to save the library after the change.I also noticed that you need to take care not to break the flow of the check. If, for instance, you break the flow by software recognizing your command as being further down the line, you may not be able to go back to the intended step, or you need to execute some previous command again, that would set the variables to the “correct” state. To learn what is going on, you need to track the conditions for voice commands and variables set by output commands:
The settings page for variables set by output command is displayed by clicking the round (x) button to the left of the “Output Name” label on the voice command edit window.@foxster thank you for this software and VCC library - it is much fun! For now I’ve been playing without BMS running to learn the flow and how to speak to being recognized. Is there a way to see what is the current value of variables? I think it would aid in analyzing more complex flows, like the one of VCC.
-
RE: 4.37 Screenshots
Are you guys really putting those screenshots from 4.37 or you’re teasing with 4.38 “leaks”? I swear the planes in u3 look better and terrain also looks beautiful, especially from some height and setting. Also, I have a feeling that something in F-16 cockpit has been improved too
-
RE: Falcon BMS nstaller for 4.37.3 re-upload
In response to:
https://forum.falcon-bms.com/topic/25932/falcon-bms-nstaller-for-4-37-3-re-uploadPlease update the tracker and file information on
https://www.falcon-bms.com/downloads/For instance SHA256 on the page for the file Falcon BMS_4.37.3_Full_Setup.exe still shows
67ca7ce95e89b14d3edbde7c24e91be711e5cde4b73868d5aeb5fc1401008a20
which is for the “previous” version. -
RE: Virtual Crew Chief for BMS demo
This is superb!
On a side note, I find the way that the cockpit lights up at 3:04 heartwarming
This video goes to my BMS feel-good videos, thanks! -
RE: BLU-107 impact point
@Alfred Hi Alfred, the middle part of the needle in HSI is CDI - Course Deviation Indicator. It shows you the offset from the course (CRS) you set. CRS is the course with which you want to reach the steerpoint (in NAV mode) or TACAN station (in TCN mode). In case of runway, you usually want to approach it from the runway heading or its reciprocal (you have to know it). If your steerpoint is a building and you want to approach it, say, directly from the East, you would set your CRS to 270 (this is what you would see on your heading tape when approaching from the East). If you’d like to approach it from S-W, you’d set CRS to 45. Then, if the CDI is aligned with the needle, it means you are on the right course from the destination (but you also need to make sure you are traveling towards the destination, so you need to maneuver so that the bearing pointer - the little arrow on the outer edge of the compass circle - moves to 12 o’clock - when you have matched those two variables, it means that you go directly torwards the destination on set course). Bottomline is - you decide what is the course you want to reach your destination on.
-
RE: X52 throttle rampstart proble
Have you tried pressing Alt+I ? This is default keybind for Idle Detent.
Alternatively, you can click on the detent lever in 3D cockpit (marked with the arrow in pic below):
After this you should be able to move throttle. -
RE: Neo's Countermeasures settings
Here you go (all credit for this doc goes to @Neo, and if he’s willing to share it here by himself, I’ll remove the share) :
https://drive.google.com/file/d/1uDk1GMNOSf8atdgknBsR__sbx_FxUPjG/view?usp=sharing -
RE: BMS manual on Kindle
@SemlerPDX said in BMS manual on Kindle:
You just need a better PDF reader app,
I think Arsenius means Kindle ebook reader not Kindle Fire tablet. Or you’re saying that you can alter the default reader in Kindle ebook reader? I haven’t heard of that. From my experience ebook readers are not convenient to read PDFs directly, because in PDF the content is “static” (i.e cannot change font size, as on webpage or as on mobi/epub) and zooming in on page-as-a-picture was slow. There are converters from PDF to mobi or epub but they tend to produce poor results with more complex material, like BMS manuals.
-
RE: Falcon BMS 4.37.0 - Documentation: Bug reports
Document: README_FIRST_Welcome_To_The_Docs.pdf
Ver. 4.37, 14 December 2022p.2-4
In the whole “Welcome To The Docs” document and in the Foreword chapters of other manuals I propose to standardize the names of the manuals. Currently different names and different ways of writing (hyphenated in one place, non-hyphenated in other) are used. For instance, instead of “BMS-User-Manual” I suggest to write BMS User Manual. If the name appears within a body of text, to emphasize that we’re referring to a concrete document, I propose to either italicize it or enclose in double quotes (both at the same time seem excessive).
BMS-User-Manual -> BMS User Manual
BMS-Device-Setup-Guide -> BMS Device Setup Guide
BMS-Comms-Nav-book -> BMS Comms & Nav Book (also, in the said manual’s title page the title should be updated to “Comms & Nav Book” instead of “COMMS-NAV-BOOK”)
BMS-Training -> BMS Training Manual
BMS-Technical-Manual -> BMS Technical Manual
BMS-Threat-Guide -> BMS Threat Guide
BMS-Naval-Ops -> BMS Naval Operations Manual (or BMS Naval Ops Manual)
BMS-Key-File-Editor-Manual -> BMS Key File Editor Manual
BMS-Cockpit-Guide -> BMS Cockpit Interaction Guidep.2
Original: Documenting a study-sim like Falcon 4.0 BMS cannot be done in 50 pages.
Corrected: Documenting a study sim, like Falcon BMS, cannot be done in 50 pages.
Reason: correction in punctuation; “study-sim” to me does not need a dash; everywhere (including on the main loading screen) we use the name “Falcon BMS” not “Falcon 4.0 BMS”p.2
Original: To try to guide you, here is a quick explanation of what each manual attempt to cover, followed by a proposed flow.
Corrected: To try to guide you, here is a quick explanation of what each manual attempts to cover, followed by a proposed flow.
Reason: typo, missing “s” in “attempts”p.2
Original: All documents are in the \Docs folder of your Falcon BMS installation.
Corrected: All documents (except BMS Device Setup Guide) are in the \Docs folder of your Falcon BMS installation.p.2
Original: Or just click on ‘Documentation and Manuals’ on the Launcher.
Corrected: You can navigate to this folder with Windows Explorer or just by clicking “Open Docs Folder” button in the Launcher.
Reason: made this sentence connect with the prevous onep.2
In bullet VR/TRACK IR/VOICE PROGRAMS:
Original:
(\Docs\01 Input Devises\04 VR)
(\Docs\01 Input Devises\05 TRACKIR)
(\Docs\01 Input Devises\06 Voice Programs)Corrected:
(\Docs\01 Input Devices\04 VR Guide)
(\Docs\01 Input Devices\05 Track IR)
(\Docs\01 Input Devices\06 Voice Programs)Reason: incorrect folder names
p.3
Original: Learning to fly a study sim is a steep curve but rewarding curve.
Corrected: Learning to fly a study sim is a steep curve, but a rewarding one.
Reason: corrected punctuation and removed repetition of “curve”.Also, consider the following alternative that makes the sentence stronger. I think we should not be trying to make a general statement about all study sims here. After all this is a document about BMS - probably the first one that a new user reads, so let’s make it specific:
Alternative: Learning to fly Falcon BMS is a steep curve, but a rewarding one.p.3
Title of section 2.2
Original: Setup your devises
Corrected: Setup your devices
Reason: typo -
RE: Falcon BMS 4.37 VR READY "and Beyond" Trailer 4K
@chihirobelmo I’d like to congratulate you, and others who helped you, on putting a clip with such emotional tones. To me it conveys a message that BMS dev team indeed feels that this VR release is a milestone, something you have been striving for a very long time. And only you knew how distant the goal felt when you embarked on it. The pride radiates from this trailer, and rightfully so.
I’d like to wish the whole BMS team a spark of interest in BMS in general public, good reception of the new release, endurance to iron out the inevitable bugs and passion to continue with the development of this one-of-a-kind sim we all love. All the best guys!
-
RE: Typhoon FGR4 Improvement
@buraktunahan Looks very nice. Is it “only” texture work or did you modify the mesh as well?
-
RE: Falcon BMS 4.36.2 Documentation: Bug Reports
I hope you’re not fed up with me
BMS-Training
Ver. 4.36.1All here in chapter 4B “Tactical Turns”.
page 68
Is: “RKJK INFO: B 010625Z ILS RWY36 TRL140 360/10KTS 7SM FEW050 15/5 A2980 NOSIG Visibility >5000m, Altimeter 2980.”
Proposed: change “A2980” and “Altimeter 2980” to “A2989” and “Altimeter 2989” because this is how Gunsan reports.page 68
Is: “This mission is designed to train tac-turns with the AI at a contract speed of 350kts and FL200 (20000ft AGL)”
Question: I wonder why we write here that “FL200 (20000ft AGL)” - if referring to FL200, shouldn’t we be flying with altimeter set to 29.92? Aircraft in this mission has 29.80 set and it doesn’t show 20000 ft on barometric altimeter (more like 19500 ft). 20000 ft is in fact shown by the radar altimeter, but FL doesn’t concern radar altitude, but barometric one, right? Also, in this mission we’ll not only fly over water, so height (AGL) will vary. So maybe, to avoid confusion, leave the sentence as “…at a contract speed of 350kts and altitude around 20000ft.”?page 68
Is: “Even when AI Tac-turn orders are not implemented yet in BMS…”
Proposed: change to small letter to “tac-turn”page 74
Is: “Use you’re A-A TACAN to measure the distance to your flight-lead.”
Proposed: “Use your A-A TACAN to measure the distance to your flight-lead.”
Reason: you’re -> yourpage 74
Is: “Depending on the altitude, loadout and drag this contract speed has to be maintained as well as the current altitude of 20000ft.”
Question: something seems not right with this sentence - first we say “depending on the altitude” but then we provide the altitude… Maybe change this to a general statement about importance of the contract airspeed and altitude, like this: “Regardless of loadout and drag the contract speed and altitude hast to be maintained.” or better yet (maybe, just for your consideration): “In general, flight-lead (or flight planner) has to take into consideration the loadout and drag of aircraft in his formation because his wingmen must do whatever it takes to maintain it.”page 74
Is: “At the beginning it will be quiet hard because you have to fly very precise and learn how to use your throttle and stick effectively.”
Proposed: “At the beginning, it will be quite hard because you have to fly very precisely and learn how to use your throttle and stick effectively.”
Reason: added comma; quiet -> quite; precise -> preciselypage 74
Is: “…the goal is to end this turn in a reversed spread formation…”
Proposed: “…the goal is to end this turn in a reversed “Spread” formation…”
Reason: conventionpage 75
Is: “As you may know, the BMS AI has no directive orders or the option to give a call when the turn start.”
Proposed: “As you may know, the BMS AI has no direct order or the option to give a call when the turn starts.”
Reason: directive -> direct; “directive” itself is an order; orders -> order (because then “option” and “turn” are in singular - could also change all of them to plural) changed “when the turn starts”, alternatively “when the turn should start”page 75
Is: “But, this is not far from real life because in some scenarios, tac-turns will be executed silent (= Ziplip) without any communication.”
Proposed: “This is not far from real life because in some scenarios tac-turns will be executed silently (= Ziplip), without any communication.”
Reason: Removed “But” (could leave “but”, but then we’d need to connect this sentence with previous one, like so: “…visual on your flight lead all the time, but this is not far from…”; removed commas where I think they shouldn’t be, added where it should.; silent -> silentlypage 75
Is: “As you can see in the picture right,…”
Proposed: “As you can see in the picture to the right,…”page 75
Is: “Your turning cue start when your flight lead is on your 4 o’clock…”
Proposed: “Your turning cue is when your flight lead is on your 4 o’clock…”
Reason: a turning cue is a signal to start the turn and I think it is a rather precise moment, hence the proposed change - if it is not, and there is a period when you can initiate your turn, then the correction would be only in the form of the “start” verb, like so “Your turning cue starts when…”page 75
Is: “At STPT 4, the flight will do a “Delayed 90 left turn”.”
Proposed: “At STPT 4, the flight will do a “Delayed 90” left turn.”
Reason: changed placement of the closing quotation mark to make it consistent with usage in this sectionpage 75
Is: “At STPT 5 the flight-lead will initiate a…”
Proposed: “At STPT 5, the flight-lead will initiate a…”
Reason: added comma to make it consistent with the same punctuation a couple of sentences before (alternatively, remove comma here and in the sentence starting with “At STPT 4,…”)page 75:
Is: “10NM later at STPT 6 your flight will execute a “Delayed 45” left…”
Propose: “10NM later, at STPT 6, your flight will execute a “Delayed 45” left…”
Reason: added commaspage 75
Is: “Those pretty quick sequences are quiet usual because in certain scenarios a flight has to change direction quite often.”
Proposed1: “Those pretty quick sequences are quite usual because in certain scenarios a flight has to change direction quite often.”
Proposed2: “Those pretty quick sequences are nothing unusual because in certain scenarios a flight has to change direction quite often.”
Reason: quiet -> quite; in second proposal I made a stylistic change to remove repetition of “quite” which in my opinion sounds betterpage 75
Is: “They will be executed less precise and more aggressive, especially if there’s any threat.”
Proposed: “They will be executed less precisely and more aggressively, especially if there’s a threat.”
Reason: changed to adverbs: precisely and aggressively; changed “any” to “a” as this is not a question nor negationpage 75
Is: “Okay we are not done for this training, yet.”
Proposed: “Okay, we are not done for this training yet.”
Reason: added comma at the beginning; comma before “yet” I my opinion could stay if we wanted to make a dramatic effect, which I don’t think we should want too much in this kind of documentpage 75
Is: “Establish a spread formation right 1NM when your flight is reaching STPT 10.”
Proposed: “Establish a “Spread right” 1NM formation when your flight is reaching STPT 10.”
Reason: changed to be consistent with the way in which similar expression was used previously in this section; probably in order is a little discussion on the convention how to write formation names with their parameters, like “Spread” right with 1 NM spacing, but this is topic for another day -
RE: Falcon BMS 4.36.2 Documentation: Bug Reports
Dash-34
Ver. 4.36.1page 93
Is: “Ownship markpoints are shown as a big X. Datalink steerpoints are shown as a small x.”
Should be: “Ownship markpoints are shown as a small x. Datalink steerpoints are shown as a big X.”############
BMS-Training
ver. 4.36.1I propose to add in chapter 4A.1 a refresher on basic nomenclature of aircraft in formation, since we’re using it, i.e. something along these lines:
First element:
#1 - flight lead
#2 - wingman
Second element (or just “element”):
#3 - leader of second element
#4 - second element wingman
Flight = first element + second elementpage 58
Is: “The fighting wing is flown when maximum maneuverability is required…”
Proposed: “The “Fighting Wing” is flown when maximum maneuverability is required…”
Reason: “fighting wing” is not used in ordinary meaning but as a formation name, so I propose put it as in other places where formation name is referencedpage 58 and page 62
Is: “A good flight lead always maintain speed and heading if possible to so the wingman can maintain the formation easier.”
Proposed: “A good flight lead always maintains speed and heading, if possible, so that the wingman can maintain the formation easier.”
Reason: corrected verb to “maintains” for third person singular; added punctuation; fixed “to so”page 58:
Is: “The spread formation is similar to the LAB formation…”
Proposed: “The “Spread” formation is similar to the LAB formation…”
Reason: adhering to convention of writing of formation namespage 59
Is: “In BMS it is an even tighter fluid four (see 4-ship formations) formation with all aircraft separated by less than 2000 feet.”
Proposed: “In BMS there is an even tighter “Fluid Four” (see 4-ship formations) formation with all aircraft separated by less than 2000 feet.”
Reason: the intent of the original sentence is unclear for me - if it was meant to provide information what is the most compact formation, then it could have been corrected to my proposal, but not sure if this is still correct, since “Fluid Four” does not seem to be the most compact one as there is also a “Res Cell” formation described as “similar to “Fluid Four” formation but tighter”.page 60
Is: “The route formation is a lose formation which corresponds to an enlarged fingertip formation.”
Proposed: “The “Route” formation is a loose formation which corresponds to an enlarged “Fingertip” formation.”
Reason: typo correction in word “loose”; changed writing of the formation names to quoted names as the words “route” and “fingertip” are not used here in their ordinary meaningpage 60
Is: “The flight can operate at the same altitude level or 200ft higher/lower.”
Proposed 1: “The element can operate at the same altitude or 200ft higher/lower.”
Proposed 2: “The flight can operate at the same altitude or element can be 200ft higher/lower.”
Reason: changed “flight” to “element” because what would mean for the “flight to operate 200ft higher/lower” (higher/lower from what?); also removed “level” as just “altitude” seems enough and “level” has its special meaning (maybe as flight level, but still…)page 61
Is: “Both wingman are flying in fingertip formation.”
Proposed: “Both wingmen are flying in “Fingertip” formation.”
Reason: corrected “wingman” to plural; adjusted to convention of writing formation namespage 61
Is: “For the box formation each element…”
Proposed: “For the “Box” formation each element…”
Reason: adjusting to convention of writing formation namespage 61
Is: “The elements can slightly offset (right picture) or flight directly behind each other.”
Proposed: “The elements can slightly offset (right picture) or fly directly behind each other.”
Reason: corrected “flight” to “fly”page 61
Is: “The wingman are flying in spread (0-30° cone).”
Proposed: “The wingmen are flying in spread (0-30° cone).”
Reason: corrected “wingman” to pluralpage 62
Is: “The advantages of the wedge formation for each element is that the leader is well protected in the 6 o’clock area and is free to maneuver aggressively.”
Proposed: “The advantages of the “Wedge” formation for each element are that the leader is well protected in the 6 o’clock area and is free to maneuver aggressively.”
Reason: corrected “advantages (…) are (…)”page 62
Is: "The tactical advantage is that especially flights with an Air-to-Air task (Sweep, etc.), can establish much quicker 4-ship tactics like a grinder, a CAP or a bracket because there is already distance between elements.
Proposed: "The tactical advantage is that flights, especially with an Air-to-Air task (Sweep, etc.), can establish much quicker 4-ship tactics like a grinder, a CAP or a bracket because there is already distance between elements.
Reason: moved “flight” to a different place and added comma, so that the structure of the sentence (around supplementary information starting with “especially”) improvedpage 63
Is: “The “Arrowhead” formation is a mixture of a wedge formation (first element) and LAB formation (second element).”
Proposed: “The “Arrowhead” formation is a mixture of a “Wedge” formation (first element) and LAB formation (second element).”
Reason: adjusting to convention of writing formation namespage 63
Is: “This formation can be flown tight or lose…”
Proposed: “This formation can be flown tight or loose…”
Reason: corrected typo in “loose”page 64
Is: “The fingertip (close) formation is…”
Proposed: “The “Fingertip (close)” formation is…”
Reason: adjusting to convention of writing formation namespage 64
Is: “The wing tip rail / wingtip missile…”
Proposed: “The wingtip rail / wingtip missile…”
Reason: “wingtip” as part of “wingtip rail” seems more appropriate herepage 64
Is: “The „Finger Four“ formation is similar to the „Fingertip“ formation, but more lose with a spacing up to 1500-2000ft.”
Proposed: “The „Finger Four“ formation is similar to the „Fingertip“ formation, but more loose with a spacing up to 1500-2000ft.”
Reason: corrected typo in “loose”page 64
Is: “The echelon formation (left / right)…”
Proposed: “The “Echelon” formation (left / right)…”
Reason: adjusting to convention of writing formation namespage 64
Is: “Echelon formations are normally flown very tight (similar to fingertip).”
Proposed: ““Echelon” formations are normally flown very tight (similar to “Fingertip”).”
Reason: adjusting to convention of writing formation namespage 65
Is: “Especially in IFR departure conditions, a trail/radar assisted trail formation is used.”
Proposed: “Especially in IFR departure conditions, a “Trail”/radar assisted “Trail” formation is used.”
Reason: adjusting to convention of writing formation namespage 65
Is: “The spacing between each aircraft is defined by each flight lead or by outside conditions (IFR, etc.).”
Proposed 1: “The spacing between each aircraft is defined by flight lead or by outside conditions (IFR, etc.).”
Proposed 2: “The spacing between each aircraft is defined by each element lead or by outside conditions (IFR, etc.).”
Reason: word “each” seems unnecessary since the whole chapter considers a single flight only - this is the proposal 1. If, however, the spacing is defined per element by element’s leader, then proposal 2.page 65
Is: “The ladder formation is similar to the trail formation…”
Proposed: “The “Ladder” formation is similar to the “Trail” formation…”
Reason: adjusting to convention of writing formation namespage 65
Is: “The stack formation is similar to a trail formation but with tighter distance limitations and a must for vertical stacking.”
Proposed: “The “Stack” formation is similar to a “Trail” formation but with tighter distance limitations and a must for vertical stacking.”
Reason: adjusted to convention of writing formation namespage 67
Is: “At STPT 6 the flight lead will call for a “Fluid four” formation.”
Proposed: “At STPT 6 the flight lead will call for a “Fluid Four” formation.”
Reason: correction of the capital letter in “Fluid Four”page 67
Is: “STPT 9-10 will again a “Fluid Four” formation as a preparation for the approach in Gunsan.”
Proposed 1: “STPT 9-10 will again be a “Fluid Four” formation as a preparation for the approach in Gunsan.”
Proposed 2: “STPT 9-10 will again transition into a “Fluid Four” formation as a preparation for the approach in Gunsan.”
Reason: proposals to fill-in missing verbpage 67
Is: “The last formation will be echelon left or right…”
Proposed: “The last formation will be “Echelon” left or right…”
Reason: adjusted to convention of writing formation namespage 67
Is: “The flight will be inbound to runway heading in echelon at about…”
Proposed: “The flight will be inbound to runway heading in “Echelon” at about…”
Reason: adjusted to convention of writing formation namespage 67
Is: “The AI uses 4-5 seconds delay in between breaks. So wait 4-5 seconds before you brake.”
Proposed: “The AI uses 4-5 seconds delay in between breaks, so wait 4-5 seconds before you break.”
Reason: connected unnecessarily split sentences; I think that the word “break” instead of “brake” was intendedpage 67
Is: “…and sees you at the position where he’s expect you to see.”
Proposed: “…and sees you at the position where he expects you to be.”
Reason: “he’s expect” is incorrect here, co changed to “he expects”; replaced “to see” with “to be” as this seemed more logical (to me, ofc) -
RE: Falcon BMS 4.36.2 Documentation: Bug Reports
Avionic Checklists
Rev: 2009 BMS 4.35 (latest version as of 4.36.1)page 6
Is: “The EWS can be set through the DTC programming at prefight and may be reprogrammed in flight through the UFC by LIST # 7.”
Proposed: “The EWS can be set through the DTC programming at preflight and may be reprogrammed in flight through the UFC by LIST # 7.”
Reason: corrected a likely typo “prefight” -> “preflight”page 8
Is: “The F-16 navigation computer is able to store 100 steerpoints (1 to 99)”
Proposed: “The F-16 navigation computer is able to store 99 steerpoints (1 to 99).”
Reason: it is in fact 99 steerpoints; added comma at the end of the sentence.page 8
Description for point “4. Tacan channel” is:
“Set 63 apart: (at or above 64, add 63 – below 64, subtract 63)”
Proposed: “Set 63 apart: (at or above 64, subtract 63 – below 64, add 63)”
Reason: since maximum allowed TACAN channel is 126 (as per Dash-34 2.3.2), the original description is wrongpage 9
Is: “Own ship markpoints are stored in STPT 26-30.”
Proposed: “Ownship markpoints are stored in STPT 26-30.”
Reason: correct form seems to be “ownship”, used accross docspage 9
Is: “Ownship markpoints are displayed on the MFDs with large X cross.”
Should be: “Ownship markpoints are displayed on the MFDs with small x cross.”
Reason: ownship markpoints are smaller “x” on HSD than data-link markpoints; also convention in Dash-34 is to use “x” for ownship and “X” for data-link markpointspage 11
Is: “Check own ship and intraflight address in DED AA page (LIST ENTER SEQ)”
Proposed: “Check ownship and intraflight address in DED AA page (LIST ENTER SEQ)”
Reason: correct form seems to be “ownship”, used accross docspage 12
Is: “Data link steerpoints and markpoint appear as a small x on the HSD. Ownship markpoints as a larger X.”
Should be: “Data link steerpoints and markpoints appear as a larger X on the HSD. Ownship markpoints as a smaller x.”
Reason: ownship markpoints are smaller “x” on HSD than data-link markpoints; also convention in Dash-34 is to use “x” for ownship and “X” for data-link markpoints; also changed markpoints to plural as it seems proper herepage 13
In section “Receiving a Steerpoint/Markpoint”
Is: “Check MKRT DATA in HUD and VMS DATA sound”
Proposed: “Check MKPT DATA in HUD and VMS DATA sound”
Reason: as per figure 62 in Dash-34 2.5.6.1 HUD information when receiving datalink markpoints is “MKPTxx DATA”page 13
In section “Receiving a Steerpoint/Markpoint”
Is: “Check data linked steerpoint (small X) in HSD”
Should be: “Check data linked steerpoint (large X) in HSD”
Reason: steerpoints sent via datalink appear in HSD as larger X than those of ownship markpoints -
RE: Old Simmer Looking For Advice
Hi,
In Docs folder of BMS installation is a file _README-FIRST_How-to-use-Docs.pdf. In its second chapter, especially in 2.3, it outlines a BMS’s team suggested approach what to read and in which order.I think that starting with training missions and their excellent description in BMS-Training.pdf is a good way to start flying. If you feel you need a break from flying or want to read again about some aspects of F-16 or its weapons, go to Dash-1 and Dash-34. Ultimately you’ll want to read all the manuals, but you need to be realistic - given the sheer amount of information it’s a marathon rather than a sprint, so you have to give yourself time to digest it. You will probably return to some manual sections multiple times and fly training missions multiple times and you’ll notice things will start to appear in a more manageable pace.
First make yourself comfortable with navigation and landing in various conditions, then move to weapons deployment. Since training starts with A-G weapons, which there is a variety of, and lots of associated avionics, I mixed A-G training missions with Instant Action where I could practice A-A with easy targets (in first waves).
As for youtube content - yes, there’s a lot of good content, but I feel most of it is advanced stuff (except for videos of training missions, I recommend Stevie’s channel) . For starters, I’d focus on manuals though. But if you feel like watching, here’s a recent thread about it: https://forum.falcon-bms.com/topic/23108/video-tutorials.
I also started playing BMS about 1,5 and half years ago, after a very long break from flight sims, and I’m still in the training. As you can tell I’m not rushing things now I remember when I tried to play campaign in original F4.0 my situational awareness was non-existent and I was shot down fast. Now I want to learn F-16 as represented in BMS well, before I jump into combat (which, honestly, I don’t feel the urge to do so).
Another way to learn BMS would be to join an online squadron, maybe there are some sessions for newbies, but I haven’t explored it and don’t know what are prerequisites (I guess you at least need to be able to complete all training missions).