SturmVogel Posted February 29, 2024 Posted February 29, 2024 Hi to all! Keybinds lost after F1EE patch, this will 3 or 4 times since original F1 was released. Simple ctrl+c/ctrl+v doesnt work for new .cfg of Mirages. Somebody know how to simply restore it from older .cfg files? To Aerges: no one module in DCS dont make so much pain like F1, no one 3rd developer dont change keymap more than ones in my expirience. This is why I'm not fly with this module since F1EE patch, its unplayble and no sense for binding 70+ keys again. P.S. Im wating for F-104, but 10 times think about this buy, cause my expirience with F1 were so bad. Best of luck...
fausete Posted February 29, 2024 Posted February 29, 2024 Hi @SturmVogel, There's been no major changes to keybinds on our side since the release of the BE 6 months ago. 1
SturmVogel Posted February 29, 2024 Author Posted February 29, 2024 8 минут назад, fausete сказал: Hi @SturmVogel, There's been no major changes to keybinds on our side since the release of the BE 6 months ago. Thank you for response, Im wrong with F1EE, this was F1BE patch. Im late with this feedback. Am I understand correctly-the one way to fly again at F1 is manualy rebind all maps? BL
fausete Posted February 29, 2024 Posted February 29, 2024 Hi, If you hadn't done the rebinding after the BE update then the only possibility is a manual rebind, yes. If you were up to date, this update shouldn't have broken your keybinds. As I said, no major changes on our side so using the previous .cfg should be okay. Regarding the F-104, it is being developed with all the input options accounted for, so there shouldn't be any major remappings needed. 2
Loukuins Posted March 1, 2024 Posted March 1, 2024 22 hours ago, SturmVogel said: Hi to all! Keybinds lost after F1EE patch, this will 3 or 4 times since original F1 was released. Simple ctrl+c/ctrl+v doesnt work for new .cfg of Mirages. Somebody know how to simply restore it from older .cfg files? To Aerges: no one module in DCS dont make so much pain like F1, no one 3rd developer dont change keymap more than ones in my expirience. This is why I'm not fly with this module since F1EE patch, its unplayble and no sense for binding 70+ keys again. P.S. Im wating for F-104, but 10 times think about this buy, cause my expirience with F1 were so bad. Best of luck... You can load the profile through the game and search for input > Mirage-F1XE > your Peripherals 1 My Setup : i5-4690 3.50GHz + 24GB RAM DDR3 1600MHz + MSI RTX 2060 Super Ventus OC + 2 SSD + 4 HDD + Oculus Rift CV1 + TM T.16000M Hotas Super Etendard for Life !
1Arc Posted March 1, 2024 Posted March 1, 2024 22 hours ago, fausete said: Hi @SturmVogel, There's been no major changes to keybinds on our side since the release of the BE 6 months ago. To be fair, I had my cursor toggle (which I rebound to "=") not working, while the default bind LAlt + C still worked. I found it a bit strange since in my keybind it did have "LAlt + C; =" and when readding "=" to the bind I didn't remember if it says "=" is in use with another keybind. This happened just few days ago after the Feb 2024 patch, on which before I did rebind a lot of keys when BE keybinds were introduced. Just a heads up if anything didn't go as planned. Cheers.
Recommended Posts