TLDR: Your controls may need a rebind after the next update. For the last few weeks we’ve been working on updating the way B17:The Mighty Eighth handles controls. This has been a top to bottom change involving configuration and game systems. The original game stored all data in a binary options file. Controller information is stored based on the order that windows presents the controllers to the game, which means that adding or removing controllers can mess up player’s bindings. Default controls were also stored this way, making it tricky to alter the game to add new bindings. We’ve updated the default control bindings to be in a human readable standard JSON (JavaScript Object Notation) format, this will allow us greater flexibility to add new controls and fields. We’ve also updated the user’s individual control bindings to include the unique identifier of each control, meaning your bindings will stay consistent when adding or removing peripherals. This will also allow us to support a wider array of peripherals in future updates, or a more focused experience for players who play on Steam Deck or with game controllers. We’ve added a migration for your existing bindings, from the old format to the new format. This should be seamless for most users, however a rebind of controls may be necessary. Here at MicroProse we consider working on Mighty 8th Redux to be a labour of love. It serves as a real and direct link to our company’s history. Thank you for helping us bring this game to a new generation! Brave the deadly skies! [img]{STEAM_CLAN_IMAGE}/43121699/b9cf358297bbb4a2d98ef4aa459264f8b2430413.png[/img]