Jump to content

Reverting to VAB from KSC Launch Pad creates a new workspace that does not inherit the name of the original one


ToriBee

Recommended Posts

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Win11 | CPU: Intel i7-11800H | GPU: NVIDIA GeForce RTX 3080 | RAM32Gig

 

I encountered this Bug while reverting from a launch (mid air) to the VAB

I started this launch from the KSC screen and selected Launch Pad 1. 

When I reverted to the VAB, the VAB loading in the correct vessel file, and created a new Workspace for it, even through there was a Workspace that already contained the file name. 

By design, or Revert to VAB bug... you decide. I feel this is a bug. 

Spoiler

------------------
System Information
------------------
         Operating System: Windows 11 Home 64-bit (10.0, Build 22621) (22621.ni_release.220506-1250)
                 Language: English (Regional Setting: English)
      System Manufacturer: Alienware
             System Model: Alienware x17 R1
                Processor: 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 CPUs), ~2.3GHz
                   Memory: 32768MB RAM
                Card name: NVIDIA GeForce RTX 3080 Laptop GPU
                  DAC type: Integrated RAMDAC
              Device Type: Full Device
      Device Problem Code: No Problem
             Display Memory: 32405 MB
          Dedicated Memory: 16191 MB
             Shared Memory: 16214 MB

 

Included Attachments:

KerbalBug2023-12-21002443.png.a5263915ca8fa34a23936289b09984be.png

Edited by The Space Peacock
Link to comment
Share on other sites

×
×
  • Create New...