How good is the new flanker model!

<p>Just out and about in KTT:<br /><br /><img class=“ql-image” src=“https://i.imgur.com/mTdOuW8.png” /><br /><br /><img class=“ql-image” src=“https://i.imgur.com/HOW3gqH.png” /><br /><br /><img class=“ql-image” src=“https://i.imgur.com/dtYZa5c.png” /></p>

<p><a style=“color:unset;background-color:unset” href=“https://i.imgur.com/5BNA5AG.png[/img]” target=“_blank”>https://i.imgur.com/5BNA5AG.png</a><img src=“https://i.imgur.com/5BNA5AG.png[/img]” alt=“https://i.imgur.com/5BNA5AG.png[/img]” class=“shrinkToFit transparent” /><br /><br /><br /></p>

BMS’ deep, dark nights.

Something about Vipers over the desert…

Hi! I’ve experienced the same annoying problem in 4.36.

I investigated this and here is what Razgriz (who developed the really awesome new acmi recording format) had to say:

“1. The small block jets’ (blk32 and below) AVTR switch has three settings: OFF, AUTO (record for 30 seconds on trigger pull or pickle), and ON (record constantly). The BMS avionics are based on that.
2. The tall block jets have different settings, in a different order: OFF, ON, and EVENT MARK. The latter is not the same as Auto IRL - Event Mark is something you momentarily flick up to insert some sort of mark (a tone? Not sure) into the running recording. Unfortunately BMS doesn’t model this, and to make matters worse, I believe the DOFs in the tall block cockpits aren’t adjusted accordingly. ON in the pit corresponds to AUTO in the code, and EVENT MARK corresponds to ON (because of how they’re arranged in the small blocks). (edited)
I’m thinking that your AVTR switch is in the middle position, which is labeled ON in the pit but is actually AUTO.”

Ultimately, if you are flying a ‘small block’ jet, you will need to press Fx2 to get the acmi recording properly. If you are in a ‘tall block’ (block40 and up) then you only need to press F once to get ACMI recording started properly.

The documentation and/or cockpit switchology will need to be fixed in a future update.
In the meantime you can use the above information as a guide for setting the correct switch position you need or you can set -acmi in your BMS command line to auto record .acmi files whenever you load into 3D (it’s what I do now, you just have to make sure to clean out your ACMI folder from time to time as it will fill up fairly quickly!).

Cheers!

FALCON BMS 4.36 - NEW AAR BASKET PHYSICS – 02:39
— Dusty

Under the Saved TE tab, please try the ‘TE_BMS_00_Benchmark_Test’ and report back on your FPS.
If you attach a copy of your current settings and system specs, we might be able to help you optimize your performance.

Other tricks are to use Mission Commander to move either your squadron or other AI squadrons to a different airbase so you don’t have so many aircraft launching at the same time. Or take control of the AI squadrons at your base and change their mission takeoff times to well before or well after your mission T/O time.

Cheers

@glajtman Only the KC-10 is equipped to provide A-A TCN range and bearing information. All other tankers give only range information.

Thank you @Fox_15 for a thorough report! I’ll aim to repro ASAP and forward internally.

Cheers!

Hi! I’ve experienced the same annoying problem in 4.36.

I investigated this and here is what Razgriz (who developed the really awesome new acmi recording format) had to say:

“1. The small block jets’ (blk32 and below) AVTR switch has three settings: OFF, AUTO (record for 30 seconds on trigger pull or pickle), and ON (record constantly). The BMS avionics are based on that.
2. The tall block jets have different settings, in a different order: OFF, ON, and EVENT MARK. The latter is not the same as Auto IRL - Event Mark is something you momentarily flick up to insert some sort of mark (a tone? Not sure) into the running recording. Unfortunately BMS doesn’t model this, and to make matters worse, I believe the DOFs in the tall block cockpits aren’t adjusted accordingly. ON in the pit corresponds to AUTO in the code, and EVENT MARK corresponds to ON (because of how they’re arranged in the small blocks). (edited)
I’m thinking that your AVTR switch is in the middle position, which is labeled ON in the pit but is actually AUTO.”

Ultimately, if you are flying a ‘small block’ jet, you will need to press Fx2 to get the acmi recording properly. If you are in a ‘tall block’ (block40 and up) then you only need to press F once to get ACMI recording started properly.

The documentation and/or cockpit switchology will need to be fixed in a future update.
In the meantime you can use the above information as a guide for setting the correct switch position you need or you can set -acmi in your BMS command line to auto record .acmi files whenever you load into 3D (it’s what I do now, you just have to make sure to clean out your ACMI folder from time to time as it will fill up fairly quickly!).

Cheers!

Amazing shot Kouzi! Are you using a tree mod?

Hey, you’re absolutely right. A ‘say again’ feature is on the todo list I’m fairly certain.

I haven’t experienced your other problem though, I’ll keep an eye out.

FALCON BMS 4.36 - UOAF LFE 'TRAP HOUSE' – 39:42
— Dusty

@ADCD-0 Not yet but 4.36 version will come in the near future. Chihiro is working on about 37429834734 different tasks right now. I can’t imagine how he is able to prioritize all of them!

No you should be absolutely ok to load 2x AGM-65L on the F-16.

Make sure you click ‘ok’ on the loadout screen before you exit to set the loadout.

Damn @spooky - Thought this was real for a sec!

Which HAF SQ/block is this?