Explosive Charges Crash

oem

Just updated to 0.14.5 and decided to mess around in creative. Immediately crashed the game by detonating an explosive charge with the Ctrl + D hotkey. It does not crash when I detonate explosive charges with the button on the UI.

System.NullReferenceException: Object reference not set to an instance of an object.
at Cosmoteer.Simulation.PlayerInputHandler.HandleInput() in C:\Users\Walt\Documents\Code\Cosmoteer\Source\Simulation\PlayerInputHandler.cs:line 262
at Cosmoteer.Simulation.SimRoot.Input(Boolean allowWorldInput) in C:\Users\Walt\Documents\Code\Cosmoteer\Source\Simulation\SimRoot.cs:line 558
at Cosmoteer.Game.GameRoot.Input(StateMethodInvoker inputParent) in C:\Users\Walt\Documents\Code\Cosmoteer\Source\Game\GameRoot.cs:line 1161
at Halfling.Application.AppStateEx.Halfling.Application.IAppState.Input(StateMethodInvoker inputParent) in C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\AppStateEx.cs:line 186
at Halfling.Application.Director.CallInput() in C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Director.cs:line 876
at Halfling.Application.Director.DoInput() in C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Director.cs:line 789
at Halfling.Application.Director.<GetRunIterator>d__83.MoveNext() in C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Director.cs:line 335
at Halfling.Application.Bases.GenericApp.<ApplicationMainIterator>d__48.MoveNext() in C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Bases\GenericApp.cs:line 279
at Halfling.Windows.D3D11.D3D11Window.RunGameLoop(String[] args, IEnumerable`1 iterator) in C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingPlatformWDX\Windows\D3D11\D3D11Window.cs:line 890
at Halfling.Application.Bases.GenericApp.ApplicationMain(String[] args) in C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Bases\GenericApp.cs:line 193
at Cosmoteer.GameApp.Main(String[] args) in C:\Users\Walt\Documents\Code\Cosmoteer\Source\GameApp.cs:line 145

CaptainRedstone

oem Huh. Try going to settings → controls, and changing the keybind to something else. Do you have a non-standard, or non-American keyboard?

oem

Seems like it only happens when the keybind is Ctrl + D. My keyboard is EN-US.

I think I've figured out what's going on here. I was fooling around with keybinds a while back and had one of the Create Part Group keybinds set to Ctrl + D. So I'm going to guess that it crashes trying to make a part group with a part that no longer exists.

Another keybind-related issue I've found: clearing the Boost Mode Off keybind doesn't seem to prevent boosted thrusters from toggling off with Ctrl + B. In fact, both the Boost Mode Off and Boost Mode On keybinds seem to do the same thing. I cleared the Boost Mode On keybind and only had Boost Mode Off on Ctrl + B, but boosted thrusters still toggled on when I pressed it.

CaptainRedstone

oem Whether the cause or not, the game shouldn't be crashing from that. @Walt should probably see this

Walt

oem I think I've figured out what's going on here. I was fooling around with keybinds a while back and had one of the Create Part Group keybinds set to Ctrl + D. So I'm going to guess that it crashes trying to make a part group with a part that no longer exists.

Seems plausible, thanks for investigating.

oem Another keybind-related issue I've found: clearing the Boost Mode Off keybind doesn't seem to prevent boosted thrusters from toggling off with Ctrl + B. In fact, both the Boost Mode Off and Boost Mode On keybinds seem to do the same thing. I cleared the Boost Mode On keybind and only had Boost Mode Off on Ctrl + B, but boosted thrusters still toggled on when I pressed it.

This is by design (pressing the hotkey for an already selected mode will revert to the previous mode if no other modes share that hotkey). But I agree it's weird and probably only useful for auto-fire, so I think I'll turn that behavior off for everything but that.