As the title states, I'm unable to bind E on any keybinds. I would like to set it to yaw rather than roll. However whether I try to bind it "E" just acts like an "Accept" or "Enter" keybind, even when trying to rebind the keys. KSP and KSP2 are backwards with the roll and yaw default keybinds in comparison to every other flight game I have ever played where Q/E are typically yaw and A/D are typically roll.
Peripherals:
Corsair Scimitar Pro RGB mouse
Razer Blackwidow keyboard
Logitech G432 headset
Stream Deck MK2
Power A Xbox Series S Controller
Thrustmaster T-flight HoTaS 4
(I felt it necessary to include peripherals due to potential conflicts, but if this is the case I have never experienced conflicts with them or their respective software together in the past)
This topic was previously brought up in this post:
Post is claimed to be resolved as of v0.1.3 but I am on v0.1.5.0.28833
Bug Report
Anasyn
Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes
OS: Win11 | CPU: AMD Ryzen 9 5950X | GPU: AMD Radeon RX6700 10GB | RAM: 32GB Corsair Vengeance RGB DDR4 3200mhz
As the title states, I'm unable to bind E on any keybinds. I would like to set it to yaw rather than roll. However whether I try to bind it "E" just acts like an "Accept" or "Enter" keybind, even when trying to rebind the keys. KSP and KSP2 are backwards with the roll and yaw default keybinds in comparison to every other flight game I have ever played where Q/E are typically yaw and A/D are typically roll.
Specs:
Win11
CPU: Ryzen 9 5950X
GPU: AMD Radeon RX 6700 10GB
RAM: 32GB DDR4 3200rpm
cooling: H100i Capellix AIO liquid cooler
PSU: Corsair C750M
mobo: ASUS ROG B550F
Peripherals:
Corsair Scimitar Pro RGB mouse
Razer Blackwidow keyboard
Logitech G432 headset
Stream Deck MK2
Power A Xbox Series S Controller
Thrustmaster T-flight HoTaS 4
(I felt it necessary to include peripherals due to potential conflicts, but if this is the case I have never experienced conflicts with them or their respective software together in the past)
This topic was previously brought up in this post:
Post is claimed to be resolved as of v0.1.3 but I am on v0.1.5.0.28833
Included Attachments:
Link to comment
Share on other sites
17 answers to this question
Recommended Posts