@Micro_440th surely you don’t mean VR … is there a separate MP guide document? (there probably should be) edit: lol it is confusingly similar name as g_bVRNoPresent … here I am asking about the new MP server cfg added in 4.37.1 I’d expect to find these in sec 3.3.1 of the technical manual… although there are other things there like g_fAmbientMin which don’t seem to be purely MP specific.

@mustangs6551 I see what you mean. The new content is good – but it jumps quickly into alphabet soup of TLAs (three-letter acronyms)… FLO, DOR, MAR etc. And they’re the kind of acronyms that, just spelling out the words (“Desired Out Range”) doesn’t really help much. Even the long-form definitions, don’t help much, because they define in terms of other jargon that isn’t defined or explained anywhere in the doc. eg. what is meant by “L-D tactics”? [image: 7HRJgy6.png] There are diagrams that help illustrate some of this, a few pages later… but it’s still not 100% clear to me.

@suhkoi69 said in Table of possible faults (PFL & MFL): I’m sorry, but it’s a bit strange to have put these tables in the technical manual, no? it would have been much wiser to put in document TO-BMS1F-16CM-1 in reference to faults panel. I find the recasting of the documents sorely lacking in clarity: in particular, what is implemented in game and what is not. ( example HUD TRP Fuel Warning) there’s a lot of details as can be found in the real docs, but I don’t understand the point insofar as certain functions are not implemented … basically, it’s more confusing than anything else. Yes I have seen that this is being worked on.

For now, I will park the topic since our goal is to think of a contributive platform for the english documentation first… Having 20 different tools to manage our stuff isn’t viable. I’ll think about it when 4.38 time comes…

@suhkoi69 it is improved in the new - 34.

from the -34: how does coast work in STT vs SAM? the manual says on STT mechanization: “Currently in BMS a track target will flash after one failed update but is not dropped until 13 seconds have elapsed; the COAST indication happens only 5 seconds before the track is dropped. So there is a period of around 8 seconds when the TD box and TTL in the HUD/HMCS isn’t dashed.” After one failed update sounds like its talking about SAM mode when the antenna trains back towards the target and updates its position. Isn’t STT basically one long “update” in real time? There’s this from the internet (one of the real life manuals?): [image: Nl0Kgzy.png] Also wondering if someone can clarify this from the BMS manual regarding the target’s radar return degrading: “A radar track will start degrading if the radar doesn’t pick it up again within a reasonable (pattern dependent) time frame. If the radar has not detected the tracked target lately (for example in the last 5 paints where the beam passes over the target aircraft but doesn’t get a strong enough return) and the radar is coasting (4 seconds since the last actual hit) extrapolation continues. After the coast time the symbol will flash to indicate imminent loss of track status; sometimes you won’t see this depending on where the target was in the scan pattern. In this situation the track will disappear unless you get a paint and detection almost immediately.” –Why wouldn’t the radar enter coast for a full 5 seconds simply because of where the beam was in the pattern?

some thing like the page 111 in this link? -> https://wiki.falcon-bms.com/manuals/4_37/to_1f-16cmam-34-1-1_bms.pdf

@tonpilot This is an “outbound” hold for the sole purpose of gaining the required altitude. Its not an “inbound” hold for landing.

@Atlas the old Prima guide is a great read.

@MaxWaldorf That is amazing, thank you.

Its ICOM IC-PW1 Solid State 1000W Linear Amplifier/Tuner 160m-6m available. The unit works flawlessly and when interfaced to an ICOM HF transceiver with the included inter-connect control cable will support automatic band switching and memory tuning. This is the later version. The remote panel also as lights dual meters that monitors SWR, ALC, Temp Po, Vo, Io that can be placed adjacent to the transmitter for easy viewing while operating. I am including the Palstar DL2K 2kW dummy load and 10 ft inter-connect control cable . Priced at $1,630.00 Elecraft K3, P3 And Power Supply Combo. The Set Is In Excellent Cosmetic And Functional Conditions With No Dings, Dents Or Scratches And Has Been Very Well Cared For. K3 Has Dual Receiver (Main & Sub) And Both Has Same Options (Filters & Boards). P3 Has SVGA And TX Monitor Options. Both K3 And P3 Has Latest Firmware Updates Installed. Accessories: 13.8v 30 Amp Matching Power Supply With AC Power Cable And DC Power Poles Cable. DC Power Cable, RS-232 Cable And BNC To BNC Cable For P3 Panadapter. Elecraft MH2 Hand Microphone. USB To RS-232 Serial Cable For PC To K3 Or P3. User Manuals For Both K3-F And P3-F. Original Factory Shipping Boxes With Inserts. Prices at $1,410.00 KC5EDU ROBERTO SEDA Oklahoma Whatsapp: +1 (840) 466‑7441 [email protected]

@SoBad Amazing! Thanks for sharing.

@airtex2019 said in ILS at Pohang AB wrong runway: @Ironman53rd well at the time, this was my primary source of confusion also it was super low-viz and ATC was directing me to runway 28 … seemed legit [image: U51XE47.png] Good catch. Typo indeed. Fixed in U3 (both AIP + Kneeboards) As Ironman described, ILS 10 is valid for ILS.

@hnhnnhnh I think you might be able to do it using joystick gremlin and mapping it to a virtual joystick…only way I can think of. I also recommend using joytokey as a way to expand its abilities by mapping key combos…and voice control like Foxvox (free) or voiceattack for more input and to handle comms.

@Stevie That’s actually a good idea. Ended up using zamzar.com which got the job done. Thanks!

@jayb Kneeboards and charts in general.

Does anyone know where there might be a collection of brief checklists for systems and weapons please? I am not talking about the checklists in the documentation folder, something more like the kneeboard checklists users make in DCS