Amandanaut

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Ryzen 7 1700X | GPU: GeForce RTX 2070 | RAM: 16Gb When trying to activate a sepratron or LES rocket via action groups, the rocket won't fire if a stack decoupler is decoupled within the same action group. Liquid rocket engines and SRBs don't seem to have this issue. I initially encountered the bug while testing an LES setup where the LES rocket is decoupled from the crew capsule and activated at the same time, but I was able to test and verify that the LES rocket also wouldn't fire if I decoupled a different decoupler and left the LES rocket attached to the crew capsule. If the sepratron or LES rocket is still part of the controlled craft, activating the action group a second time, will, however, cause the rockets to activate. If no decoupler is decoupled within the action group, both the sepratron and LES rocket will activate as expected when the action group is activated. This issue also occurs with stack separators. I have not tested with radial decouplers. In the included craft file, both the Abort and Custom 9 action groups are set up to trigger the LES rocket and a decoupler. Abort is set up to decouple the capsule from the main stack and activate the LES. Custom Action Group 9 is set up to decouple the LES rocket from the craft and activate it. Included Attachments: CometMKII.json .ipsImage { width: 900px !important; }

Wow, that pre-release UI is so much more legible. I generally like pixel art, and I like the concept of the current KSP2 UI, in theory. But, in practice, all the little decorative dots and squiggles only serve to obfuscate the information that the UI is supposed to be providing me. It just makes the core experience of controlling the craft much more frustrating. Honestly, it's my number one complaint about KSP2. I can tolerate bugs, I can wait for missing features, but not being able to read the UI is just miserable.