Bug #20442
Adding subassembly or merging craft with existing craft modifies existing craft naming / affects saved craft files.
Status:
New
Severity:
Low
Assignee:
-
Category:
Controls and UI
Target version:
-
Start date:
11/23/2018
% Done:
0%
Language:
English (US)
Mod Related:
No
Votes:
Description
I tested this in clean installs in both linux (Ubuntu 18.04 / KSP 1.5.1.2335) and windows 10 (steam version 1.5.1). The issue did not present in windows, only linux.
Steps to reproduce:- create a craft and save as either a regular craft (via the save button in the top right) or as a subassembly. Eg: a satellite
- create a new craft Eg: a ship to launch the satellite, and then either merge the first craft, or click the subassembly button to bring it back into the scene.
- The main craft file will be renamed as the subassembly/merge name. This will result in the original satellite/merge craft file being overwritten if the main ship is subsequently saved.
Pictures attached.
| screenshot0.png (1020 KB) screenshot0.png | satellite subassembly creation | ||
| screenshot1.png (1.05 MB) screenshot1.png | ship creation | ||
| screenshot2.png (1.04 MB) screenshot2.png | satellite brought in from subassembly pane, note top bar name is changed | ||
| screenshot3.png (1010 KB) screenshot3.png | part naming is still correct | ||
| screenshot4.png (464 KB) screenshot4.png | naming still ok after launch |
