Auto-save functionality should suffix ‘Auto Save’ with the date the campaign was created on.
In other words, starting a new campaign and pressing Back should not overwrite an ‘Auto Save’ from a previous campaign.
Auto-save functionality should suffix ‘Auto Save’ with the date the campaign was created on.
In other words, starting a new campaign and pressing Back should not overwrite an ‘Auto Save’ from a previous campaign.
Auto-save functionality should suffix ‘Auto Save’ with the date the campaign was created on.
In other words, starting a new campaign and pressing Back should not overwrite an ‘Auto Save’ from a previous campaign.
I quickly converted my BMS 4.33 key file (for Saitek X-56) to BMS 4.34 using the provided Excel sheet. I’m publishing this X-56 profile today as it has been very productive, for me, over the years.
When originally setting up this profile, I tried to mimic the F16 HOTAS as much as possible.
This profile uses the Saitek application (using the provided .pr0 profile) to translate the main stick’s mini-stick into countermeasure related keystrokes.
I plan on tuning this up as I spend more time on 4.34 and will publish updates to this thread.
I figured I’d share the mini-stick mapping I have configured in the X56 HOTAS application:
Note that the “Untitled” advanced commands are simply performing the (keyboard) key-strokes used in BMS to fire/manage countermeasures.