Feedback BMS Manual 4.33u1
-
Be aware that I will take a break from manuals for a few weeks and concentrate on flying BMS So forgive me if I won’t give this top priority as We just released the manausl and the next revision is nowhere soon
Chapter 3.1.1, page 12:
A short mention that a minimum install for Falcon 4 (~150 MB) is sufficient to create a valid installation for the BMS installer would be advantageous.
I know it’s 2016 and disk space grows on trees, but the F4 installation required by BMS is basically dead weight, much like a hung Mav on the rail.Yeah, could be done
One of the many web-based alternatives to Winmerge is, e.g. https://www.diffchecker.com. Worth a mention for people who don’t want to go through the hassle of installing a separate tool.
Same, but then another will come up with his recommendation and we’ll end up with 200 pages extra
I’m not into adding alternatives? We referenced what we used because well, we use themOne of the many web-based alternatives to Winmerge is, e.g. https://www.diffchecker.com. Worth a mention for people who don’t want to go through the hassle of installing a separate tool.
Snake, can you explain them as well? There are a lot of these configs lines that have been forgotten and where explanation is not so evident.
Without having them properly explained, I can’t really add them -
No problem:
g_nHotasShiftQuickPressTimeLimit xxx time in milliseconds it takes the HOTAS shift button to become active, for instance allows me to have my pinky button as normal for a quick press but if I long press it for xxx it to then becomes the shift button
g_nNoPlayerPlay x number of hours between mission in campaign before the player’s mission rating effect wears off. Useful for 24/7 campaign servers and for those single players that don’t like the 2 hour between missions tempo. -
Page 241:
Manual: “g_fMeanTimeBetweenFailures Set the time in flight hours (logbook) between random failures. If set to 0 (default) random failures are disabled.”
Falcon BMS.cfg: “set g_fMeanTimeBetweenFailures 0 // The MTBF in hours. If set to 0, uses the value in ac.dat”I assume that the comment in the config file is the correct one?
-
As far as I know, there is no such value in AC data. if there was We would have a lot of fake bug report on this very forum
So both statement would be right
the later actually planning more the future than the formerRemember random failures are not fully coded for now.
It was just intended for debug. It works to some extend (when outside of zero) but will need a revamp in 3-4 years -
I think the mentioned URL for the interactive KTO map is outdated. But this isn’t really a problem, at least for me
-
-
@Red:
As far as I know, there is no such value in AC data. if there was We would have a lot of fake bug report on this very forum
So both statement would be right
the later actually planning more the future than the formerRemember random failures are not fully coded for now.
It was just intended for debug. It works to some extend (when outside of zero) but will need a revamp in 3-4 yearsIt’s not that I’d use this feature anyway (imagine a spontaneous engine or hydraulics failure over the Yalu…nope, nope, nope).
Just wondering because of the discrepancy. -
Manual name and page might be useful.
BMS-Manual.pdf
Page: 11
Chapter: 2.9 Updated and new tools
“http://www.candyparty.com/ST/BMS_KOREA_interactive/index.html”
should be
“http://www.ravico.com/ST/BMS_KOREA_interactive/index.html”Why?
Because URL was changed:
https://www.benchmarksims.org/forum/showthread.php?23374-KTO-Interactive-map&highlight=Korea+Interactive+Map -
Yep, my fault. I completely forgot there was a link in there. Sorry.
At least the forum here has the correct link -
I’m new user, but judging purely from the contexts, I may have found a minor error in …
BMS1F-16CM-1
Flight Manual Falcon BMS 4.33, (ver 2)Initially I noted it in my printed copy of dash 1 (from Lulu). The top of the printed page says BMS 4.33 Change 1.05 … but the error (if it is one) exists also in the Change 1.06 version on both the the BMS Forum’s link to dash 1 and the UI menu (under Documentation).
pg 79, (change 1.06)……as documented……submit it should be
……FCR: FCR cone and ghost radar cursors
……PRE: pre-planned steerpoints and their threat rings.
……AIFF: IFF response (not currently implemented)
……LINE1: DTC line 1 (steerpoints 31 to 35)
……LINE2: DTC line 2 (steerpoints 36 to 40)
……LINE3: DTC line 4 (steerpoints 41 to 45)…… LINE3: DTC line 3 (steerpoints 41 to 45)
……LINE4: DTC line 4 (steerpoints 46 to 50) -
Red Dog –
Training Manual, page 35, near the top…
“With the AP in STRG SEL mode the aircraft will steer automatically towards the bearing pointer of the HSI.”
My experience is as follows:
With the AP in STRG SEL mode the aircraft will steer automatically towards the current steerpoint.
With the AP in HDG SEL mode the aircraft will steer automatically towards the bearing pointer of the HSI.Of course, I’ve been wrong before…
-
Nope, you’re right Sobad.
Thanks I’ll correct it