Hi, Complete newcomer to BMS (and study sims). So I'm going to post here from a very naive perspective. I'm following the training manual and I'm finding it good, but at times a bit "frustrating" with some omissions that leave the reader a bit lost. I'll give a couple examples later, although watching some of the videos has also helped significantly, so I might have missed other things. But before that, I'd like to suggest something a little more profound. Judging from my experience, and lots of threads online, one of the main challenges a newcomer faces is actually doing the key mapping. It's overwhelming to map dozens of buttons when you don't know what 90% of those do and if they even matter at all. I think each of the training missions could have a preliminary section where the user can incrementally be informed of what new bindings are now necessary to add. This might be particularly useful when it gets to advanced stuff like weapon systems (I haven't gotten there yet). I don't know if this follows the "spirit" of this training manual, as I can appreciate if it's written to emulate a real life training guide (and you don't bind keys in real life! :P). But I think this would make BMS much more approachable to complete beginners, as they'd be guided both on how to use the systems, as well as to what they need to bind at that point in time, without being overwhelmed by things they don't yet need to understand. With that said, here's a couple more tactical pieces of feedback, following the template: Document: BMS - Training Manual Page: 41 Original sentence: “Passing 14000 feet set your altimeter to QNE: 1013 Mb or 29.92 inHg.” Corrected sentence: “Passing 14000 feet set your altimeter to QNE: 1013 Mb or 29.92 inHg (use the barometric setting knob, located at the lower left corner of the instrument. Refer to section 29.1 of the -1 flight manual for detailed information about the altimeter)”. Rationale: As a newcomer, it's not obvious how to adjust the Altimeter, and which units does it use (Mb or inHg?). Reading the -1 clarifies it, but one needs to know what to look for (e.g., there's no mention of QNE on the -1). This also fosters a closer relationship of the user to go back and forth between the training manual and the airplane manuals. ==== Document: BMS - Training Manual Page: 55 Original sentence: "In this training it is recommended to take seat #2 or #4 of the flight." Corrected sentence: “In this training it is recommended to take seat #2 or #4 of the flight. " The image could look something like this:

<p>Hi folks<br /><br />Is there any LOD Editor for 4.35? <br /><br />I keep getting this error “Hdr #4 Array Overrun”.<br /><br />Thx</p>

if ATC told you that you are #2 that means you are #2 which means you must take off behind the J11

yes, i already know

the problem is therefore that you are placed in #2 instead of #4
can u confirm that it is a taxiway arrangement problem (only in Osan)?
i can't choose start position freely, so i can't test all parking lots 1 by 1.
i tested other airports, seems some parking lots don't have this problem. but i m not sure. I don't have the tools or ability to test more.

how many times will I have to repeat it
you have to wait for 4.36
Not only code has benefit from fixes but all airbases have been redo

if ATC told you that you are #2 that means you are #2 which means you must take off behind the J11

yes, i already know

the problem is therefore that you are placed in #2 instead of #4

can u confirm that it is a taxiway arrangement problem (only in Osan)?
i can't choose start position freely, so i can't test all parking lots 1 by 1.
i tested other airports, seems some parking lots don't have this problem. but i m not sure. I don't have the tools or ability to test more.

you call taxi ok
the you are granted taxi ? Yes or not ?

if yes after you start taxiing the other aircrafts don’t continue taxiing ?

yes, i m granted taxi, in number 2 in queue (in the pic above).

no, they don’t continue taxiing. only J-11 continued taxiing and takoff, all other AI flight stop.
now Mig-29 stop at taxiway before me, so i can't takoff too, (unless i go into grass land, overtake him, which not real life action)

if ATC told you that you are #2 that means you are #2 which means you must take off behind the J11

the other AC stopped to let you overtake

the problem is therefore that you are placed in #2 instead of #4

this has been fixed in 4.36

Hi! @bowser said in [2021 A Falcon BMS Year to remember\!](/post/336870): > @dee-jay said in [2021 A Falcon BMS Year to remember\!](/post/336648): > > @bowser > > 1 > - AI fuel consumption is way off compared to human, especially low- and high level. > > 2 > - AI should not use afterburner when rejoining in flight. > > > > 1 - Please elaborate. > > How did you evaluated this? > > Have you considered AI (robot) behavior and leader abilities to be a good leader considering the nature it his wingmen? > > > > 2 - Please provide factual examples. > > Also, consider that is could not be possible to make a difference between rejoin and other flight phases ... so ... if we prevent IA from using afterburner, it may be all also prevent them from using is in combat ... > > See the problem ? > > 1) Straight and level flight with AI wingmen in formation, throttle constant just below mil power. Try at 1000 ft and at 35k feet. Evaluate fuel diference between ownship and AI. > > 2) Just get the AI separated from ownship and have them rejoin. > In 4.33 wingman did not use afterburner for rejoin. 1 - What do you consider as "lots of fuel / big difference" on an entire flight? 1000lbs, 2000lbs, 3000lbs ? ... We may not have the same definition of "big difference". I will try to check is (again) but I didn't had big difference since low time ago (of course, on a standard navigation without defensive/offensive actions). The best would be to join an ACMI if you can and the TE so I can fly it also on my side in the exact same conditions. 2 - The issue was that the AIs were in some case NEVER able to rejoin the flight after a takeoff (I.E. runway 36 departing northbound on a straight track). So we made some leader actions to maintain 6000kts outbound and slower speed (not sure about the speed) until #4 rejoin (that will be allowed to use a bit AB for this and should not take long time) ... then, once rejoined, leader is allowed to start climb again and once cruise FL reached, accelerate to match the TOS. In case of human leader, the rejoin plan can even be smarter (making a triangle to help the wingmen to rejoin) that ca can't do for AIs. Also other things about flight planning but none ensure 100% efficiency. The only way to fix this was to re-allow IA to use AB for rejoin for a shorter period of time (if human leader is not dumb and take care of his wingmen). Ideally, the AI leader would be amble to perform a pre-planed trajectory routine of few turns (one or two) to help the rejoin, ... examples:   ... but it is not possible at that point to hardcode it. It is always a matter of difficult compromises.

I often have AI #2 and #3 report higher fuel than me and #4 about equal on initial climbout until I call for the first formation change.

yes I just tested it and it's currently not possible to have the element refuel first. Thank you very much for the good news about 4.36, this feature is very important. If you can do that then perhaps we can even tell #4 to refuel before # 3 because #4 is the only ship that looses lots of pounds first. One more thing I noticed, when the tankers speed reads 290 I always have to maintain a 300 (on calculated "c") to be in formation with it. Is that an area that needs an update or is it accurate the way it is now

@zeus Hey Zeus, thank you very much for the explanation, sir!! It was probably what happened. I Remember he contacted the tanker and #3 and #4 were not within 10nm from the tanker... We'll try contacting it when everyone is inside the "bubble" from now on! Thank you again and happy new year!!! @Snake122 Hey snake, Y3 was called, but the problem persisted... As Zeus said above, the most possible explanation is that the other elements were not within 10nm from the tanker when it was contacted. Thank you and happy new year!!!

There are a lot of variables when it comes to AAR so let me present a possible explanation. Any additional info you can provide might help to narrow it down. First, I personally have never tried the scenario I think you are presenting; a 4-ship flight made up of human, AI, human and human in that order (so 1, 3 and 4 are human but 2 is AI). I don't think that will make a difference to the tanker but again, I have never tried that. One possible explanation could be in when the tanker was initially contacted. If, for example, #1 and his AI wingman were within the 10nm bubble of the tanker but 3 & 4 were outside the bubble then only 1 and 2 would have been entered into the queue. There would be no way for you to know or recognize this until #2 finished in which case the tanker would think it was done (this appears to be what happened). If #3 would have called for the tanker at that point (using Y1) the tanker should have put him (and #4?) in the queue and possible even 1 & 2 since they would all be inside the bubble. The only thing strange we are seeing on a consistent basis is that if you need to refuel more than once, on any AAR after the first one you will likely need to press Y2 after being cleared to precontact in order to get cleared into contact position. First AAR works fine but second, third, fourth, etc. all require this extra step.

@zeus Hey Zeus, thank you very much for the explanation, sir!! It was probably what happened. I Remember he contacted the tanker and #3 and #4 were not within 10nm from the tanker… We’ll try contacting it when everyone is inside the “bubble” from now on! Thank you again and happy new year!!!

@Snake122 Hey snake, Y3 was called, but the problem persisted… As Zeus said above, the most possible explanation is that the other elements were not within 10nm from the tanker when it was contacted. Thank you and happy new year!!!

So, I tried the following: Ran scenario out past the end of the refueling, all the way past Stpt 4. Saved. Went to MC, and removed the wing tanks, applied and saved in MC. Went back to BMS, ran the new save: Fuel remaining on #4 was 3800 lbs. So, removing the tanks removed all 5033 lbs of fuel, as expected. Went back to MC, restored the tanks, applied and saved in MC. Ran the new save in BMS- results: 8800 lbs remaining on #4. So that did not work out as I had hoped (I had hoped to see the full 5033 lbs added back to the 7162-694 lbs to give me 11501 lbs remaining, but it did not do so. Conclusion from this experiment: if you run a scenario out in 2D, and save it, any fuel used is lost, and cannot be "added back" using Mission Commander. If I knew the right place (hex) and file to alter to add the used fuel back for each aircraft, I'd use a HexEditor and do that, but, as it stands, I don't know how to trace it. Sure could use some insight from the BMS team or other BMS programmers (Oakdesign?) Thanks, Regards, Tomcattwo (VoiceClone)

@mjones said in [ATC Comms Grayed Out](/post/334831): > @mav-jp Yes, I was advised to change to tower. I pressed "T" once to change from approach to tower frequency. Tower commands all grayed out. Ok, pressing "T" does not change anything, it simply brings up the "Tower" menu. If you are are set to "Approach" (preset #4), try pressing Comm1, then 3, then Enter on the ICP.. that switches you to Tower to report on final, etc.

@vandroy Preset #4 is only to "Report Airborne" on departure and to ask for landing information on initial approach. After you depart for example no one tells you to switch to #6 (Tactical) but that's what you need to do to communicate with AWACs or use functions to communicate (not "verbally", that's Comm2) with your flight..

@oakdesign said in IVC PTT keys - any way to reassign?:

👍 ah got it

Now discussing on FO Discord how to get the correct map for BfL Online for WDP and Helios… 😉

@Amraam:

Your EHSI are in NAV, not in NAV-PLS or TCN-PLS.

Thanks Amraam, I forgot to set the EHSI you have to click on the M to set it. I should have simply RTF training manual mission #4. Duh!