Thank you very appreciated
@DUSTOFF17 said in ACMI problem:
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!