Bug #18906
Mission builder Start node roster messes up crew assignments
Status:
New
Severity:
Low
Assignee:
-
Category:
Application
Target version:
-
Start date:
05/14/2018
% Done:
0%
Language:
English (US)
Mod Related:
No
Votes:
Description
Steps to reproduce:
- Start a new mission.
- Delete the Spawn vessel node created by default
- Add a spawn Kerbal node floating on its own. Name it Crew
- Add a spawn Kerbal node floating on its own. Name it Tourist
- Set the crew to Jeb, and the tourist to Any Tourist.
- The Crew node was created first, so dock it to the Start node.
- Open the roster in Start node. Observe that Jeb is in the Crew node.
- Click OK (not cancel)
- Observe the nodes have the correct names.
- The Tourist node was created second, so dock it to the Start node (pulling Crew out)
- Open the roster in Start node. Observe that Jeb is in the Crew node.
- Click OK (not cancel)
- BUG: Observe that Jeb is in the Tourist node.
- Open the roster in Start node again. Observe that Jeb is in the Tourist node.
- Move jeb to Crew node. Click OK.
- BUG: Observe that Jeb is in the Tourist node.
Conclusion: Which ever node is created first seems to have greater importance in assigning crew in the roster.
Expected result: Roster should not alter the intended assignments per node.
History
#1 Updated by jclovis3 almost 6 years ago
Here's a demo: https://youtu.be/z1uDAD2S11A