- Joined
- Feb 6, 2008
- Messages
- 37,588
- Reaction score
- 2,312
- Points
- 203
- Location
- Wolfsburg
- Preferred Pronouns
- Sire
Correct my if I'm wrong, but to play with something like ISS assembly flights we just need to create a mission (file), edit it so it has RMS, ExtAl, set the launch time, pad, etc, and save it, and for the other missions you just reload that same file, change the OV and launch time and payload, and save with a new name. :shrug:
On the mission file(s), is it really wise to have 3 or 4 more files to work with? And in the end they would do +/- the same... in the end the data is the same, SSUW provides a UI for ease of editing and creates scenarios, and the vessels just read what they need. The only problem I can see is if we have more than one vessel of the same type in the scenario.
Yes - and if you change something at the first mission, you repeat the whole process. If WE change something deep inside SSU, the same.
If we have a manifest concept, we can at least reduce the work to those cases where a human decision is needed. And since we will change a lot, its a good idea to keep the work low in advance.