Decouplers not releasing segments without changing control between released segment and command module segment when outside of atmosphere

[Drahkar]

Specs: 

• Operating System:
  • Windows 11 Home 64-bit (10.0, Build 22621) (22621.ni_release.220506-1250)
• Language:
  • English (Regional Setting: English)
• System Manufacturer:
  • Razer
• System Model:
  • Blade 18 - RZ09-0484
• BIOS:
  • 2.02 (type: UEFI)
• Processor:
  • 13th Gen Intel(R) Core(TM) i9-13950HX (32 CPUs), ~2.2GHz
• Memory:
  • 32768MB RAM
• Page File:
  • 16202MB used, 18777MB available
• DirectX Version:
  • DirectX 12
• Card name:
  • NVIDIA GeForce RTX 4090 Laptop GPU
• Manufacturer:
  • NVIDIA
• Chip type:
  • NVIDIA GeForce RTX 4090 Laptop GPU
• DAC type:
  • Integrated RAMDAC
• Device Type:
  • Full Device (POST)
• Display Memory:
  • 32265 MB
• Dedicated Memory:
  • 16064 MB
• Shared Memory:
  • 16201 MB

Severity: Medium

Frequency: High

Description:  

Once the ship leaves the atmosphere, if I attempt to decouple the command module segment from a lower segment, the lower segment continues to be attached to the command module segment, even though it is no longer connected from the perspective of the vehicle.

For example, when separating a segment used to push the ship into orbit from the command module segment that is to remain in orbit, the released segment will continue to be stuck to the command module segement of the vehicle. The only way I have found to release the decoupled segment is to switch to control of that segment, which immediately separates it, and then switching control back to the command module.

This happens on all vehicles, while playing the Exploration mode of the game. It happens on vehicles with and without struts, and has been experienced with both Stack Decouplers and Stack Separators.