Scruce
Ad astra per aspera
- Joined
- Sep 17, 2010
- Messages
- 1,409
- Reaction score
- 0
- Points
- 0
In that case can i go for backup?
OFSS II - Project Info & Discussion Thread
- Thread starter Kyle
- Start date
- Status
In that case can i go for backup?
Kyle
Armchair Astronaut
diogom
Well-known member
- Joined
- Aug 2, 2010
- Messages
- 1,556
- Reaction score
- 913
- Points
- 128
- Website
- github.com
- Preferred Pronouns
- he/him
Kyle, Mission 14 is Scruce's Dragon flight, not the PTV-1. BTW, what did you think of the spotlights idea?
Kyle
Armchair Astronaut
Yea your right, I forgot to post the scenario for that one. Corrected.
Also I thought spotlights were an excellent idea
:thumbup:
Also I thought spotlights were an excellent idea
:thumbup:
C3PO
Addon Developer
- Joined
- Feb 11, 2008
- Messages
- 2,604
- Reaction score
- 31
- Points
- 63
Also I thought spotlights were an excellent idea
I used spotlight module for the PTV-1 mission(attached with Universal Cargo), but I deleted it before posting the post-mission scenario, because I used a custom config file.
Actually my config file was just a copy of the default one with the mesh commented out. But the name was different so it would have crashed on installations without the correct file.
Maybe we could ask for permission to release a OFSSII version so everyone has the same set of files.
There are a couple things I want to bring up/address concerning the OFSS2 addons and some general organization to help the project.
I installed all the required addons just to test out my own installation and see if everything ran smooth in case I'm called for my assigned backup spot next month, and I immediately noticed that surface tiles at Cape Canaveral were white/blank.
Reading through all the pages of this thread, I saw this post:
Now I'm assuming since no one else has posted about this same issue in 17 pages that everyone else's installation of Orbiter and all these addons required for OFSS2 are working in perfect harmony.
What exactly is the install order?
I installed all the addons in the order they're listed on the first post of this thread and I ran into that texture problem. Plus, some base files keep getting overwritten with older files and the landing site table pdf was overwritten by an earlier version.
I think for clarification and to avoid problems with future new pilots the addon list in the first post should be amended to show the proper order so that things like multistage 2/3, base.cfg files aren't overwritten by earlier versions that are included in various addons?
Also, all of these addons dump a ton of new documentation. I really don't even know where to begin on what controls what on the station.
For example, I see the cupola, but after 20 minutes of searching through addon docs I could not find listed controls for opening the windows.
Maybe we can get together a comprehensive list/chart?
An OFSS2 Station User Manual...or something.
Something that shows perhaps a diagram of the station with each module named as it is in the scenarios, and then on the next page a listing of all the module names with descriptions of what their uses are, which functions they have available (cupola doors open/close, solar panels opening/closing, station RMS operation) and which keyboard keys operate said functions.
If a module has features that are too complicated to list in the station user manual, then we should list the addon document by exact name (.pdf or .txt) that provides additional instruction on the use of said module, such as the MFD that controls solar panels that I happened to see as I was browsing through all the addon docs. (and I don't even know if we USE that MFD)
I'll even volunteer to write this manual up that can be included in each mission's briefing packet.
I have photoshop and I can also create PDF files.
To avoid making a new manual for each mission, we can just have the manual include everything the station will eventually have and then list the modules in the order they will be installed. So if a pilot is on mission 42, he can look at pages 1-42 and know everything he can use/operate on the station.
He will know that everything from page 43 on isn't implemented since those modules aren't installed yet.
Basically, I want to make a one-stop-shop of information for the OFSS2. Everything in one comprehensive guide.
Sorry, I just like organization and I feel like I'm drowning in a swimming pool filled with random documents and manuals for all the addons.
I installed all the required addons just to test out my own installation and see if everything ran smooth in case I'm called for my assigned backup spot next month, and I immediately noticed that surface tiles at Cape Canaveral were white/blank.
Reading through all the pages of this thread, I saw this post:
Now I'm assuming since no one else has posted about this same issue in 17 pages that everyone else's installation of Orbiter and all these addons required for OFSS2 are working in perfect harmony.
What exactly is the install order?
I installed all the addons in the order they're listed on the first post of this thread and I ran into that texture problem. Plus, some base files keep getting overwritten with older files and the landing site table pdf was overwritten by an earlier version.
I think for clarification and to avoid problems with future new pilots the addon list in the first post should be amended to show the proper order so that things like multistage 2/3, base.cfg files aren't overwritten by earlier versions that are included in various addons?
Also, all of these addons dump a ton of new documentation. I really don't even know where to begin on what controls what on the station.
For example, I see the cupola, but after 20 minutes of searching through addon docs I could not find listed controls for opening the windows.
Maybe we can get together a comprehensive list/chart?
An OFSS2 Station User Manual...or something.
Something that shows perhaps a diagram of the station with each module named as it is in the scenarios, and then on the next page a listing of all the module names with descriptions of what their uses are, which functions they have available (cupola doors open/close, solar panels opening/closing, station RMS operation) and which keyboard keys operate said functions.
If a module has features that are too complicated to list in the station user manual, then we should list the addon document by exact name (.pdf or .txt) that provides additional instruction on the use of said module, such as the MFD that controls solar panels that I happened to see as I was browsing through all the addon docs. (and I don't even know if we USE that MFD)
I'll even volunteer to write this manual up that can be included in each mission's briefing packet.
I have photoshop and I can also create PDF files.
To avoid making a new manual for each mission, we can just have the manual include everything the station will eventually have and then list the modules in the order they will be installed. So if a pilot is on mission 42, he can look at pages 1-42 and know everything he can use/operate on the station.
He will know that everything from page 43 on isn't implemented since those modules aren't installed yet.
Basically, I want to make a one-stop-shop of information for the OFSS2. Everything in one comprehensive guide.
Sorry, I just like organization and I feel like I'm drowning in a swimming pool filled with random documents and manuals for all the addons.
Last edited:
Been sketching ideas on how the manual will look, but I can't do this project alone.
Kyle, would you be willing to help me?
If you are, I'll need some data. The way I see it, you can do this one of two ways:
If you prefer to keep this as realistic as possible, then a full manual with all functions and module listings won't be available to pilots before the station is completed.
Each mission would have it's own briefing and it's own manual for the payload + all previous payloads. This solution would effectively use a .PDF as a flight manual for each mission.
The .PDF would have the mission name on the front cover (i.e. STS-140, PTV-7), and the rest would include the flight plan, details on module payload installation and EVA's, known functions and operating uses of station modules, and any other information pertinent to the pilot's mission.
I would need mission data ahead of time for all currently planned and posted missions including:
- payloads
- flight plans
- operating procedures and usage for future planned payloads
As more missions are created and scheduled, that data would then become available to me for flight manual prepping.
The second way would have a completed station user manual right from the start. All modules of the station would be included.
For this I would need:
- the finished station scenario
- any modules/addons that you haven't already listed (perhaps kept in secret)
- any un-posted missions including their payloads that you may have already planned out
This method would NOT include flight plan data. It would only be used as a manual for the station, it's modules, and their usage.
This would be an easier route, but not as realistic.
I don't mind doing it the first way, creating a flight manual for each mission. It wouldn't be especially difficult since each flight manual would just build from the last one. The only additions/changes being the name of the mission on the front cover and a new page for that mission's module/payload.
Kyle, if this is something you want to help me build, let me know.
Kyle, would you be willing to help me?
If you are, I'll need some data. The way I see it, you can do this one of two ways:
If you prefer to keep this as realistic as possible, then a full manual with all functions and module listings won't be available to pilots before the station is completed.
Each mission would have it's own briefing and it's own manual for the payload + all previous payloads. This solution would effectively use a .PDF as a flight manual for each mission.
The .PDF would have the mission name on the front cover (i.e. STS-140, PTV-7), and the rest would include the flight plan, details on module payload installation and EVA's, known functions and operating uses of station modules, and any other information pertinent to the pilot's mission.
I would need mission data ahead of time for all currently planned and posted missions including:
- payloads
- flight plans
- operating procedures and usage for future planned payloads
As more missions are created and scheduled, that data would then become available to me for flight manual prepping.
The second way would have a completed station user manual right from the start. All modules of the station would be included.
For this I would need:
- the finished station scenario
- any modules/addons that you haven't already listed (perhaps kept in secret)
- any un-posted missions including their payloads that you may have already planned out
This method would NOT include flight plan data. It would only be used as a manual for the station, it's modules, and their usage.
This would be an easier route, but not as realistic.
I don't mind doing it the first way, creating a flight manual for each mission. It wouldn't be especially difficult since each flight manual would just build from the last one. The only additions/changes being the name of the mission on the front cover and a new page for that mission's module/payload.
Kyle, if this is something you want to help me build, let me know.
Last edited:
PhantomCruiser
Wanderer
Had my computer not been attacked by some screwball virus, I'd have some documentation that you could use as a reference. It was written more as a companion to the missions. I liked what Thorton did with his ISS manual, and this one was laid out in a similar manner, with the addition of what craft/mission (build flight/cargo flight or expedition), what add-on was "new" and the new key commands. For the next block of missions, the key commands moved to the station module section of the manual.
I'd considered adding a "bonus mission" of recovering the outgoing expedition, but it's easy enough to do that if a pilot wants, so it was only a consideration.
If I'm able to recover my stuff, I'll send it to you if your interested.
I'd considered adding a "bonus mission" of recovering the outgoing expedition, but it's easy enough to do that if a pilot wants, so it was only a consideration.
If I'm able to recover my stuff, I'll send it to you if your interested.
If you recover any data I'll gladly use it in the flight manuals.
Thanks.
*edit*
I think I'm leaning towards creating flight manual packages for each mission. It's likely Kyle may not have all the data required to make a complete manual.
I've already begun creating the flight manual template. Cover is complete and placeholder content is starting to go in.
If all goes well I should have something ready for PTV-2, with Kyle's go ahead in advance.
Thanks.
*edit*
I think I'm leaning towards creating flight manual packages for each mission. It's likely Kyle may not have all the data required to make a complete manual.
I've already begun creating the flight manual template. Cover is complete and placeholder content is starting to go in.
If all goes well I should have something ready for PTV-2, with Kyle's go ahead in advance.
Last edited:
The manual's template is complete. I did a test PDF conversion and it looks nice, very legible and big for those who have a little trouble seeing.
The final version will be complete with bookmarks navigation.
So now I've started adding equipment into the manual, and I need some help on a couple things.
Here's a small exert from the manual, namely the OFSS2 equipment list (not spacecraft, just equipment and modules currently in use).
The list is in order of first module installed to the last.
(please feel free to make suggestions on the format of this list and/or the content of the descriptions and functions...after all, this manual is designed to be helpful to you guys, the pilots)
As far as I can tell, there are only 3 pieces of equipment CURRENTLY on the OFSS2 that are interactive:
1. SSRMS
2. Cupola
3. S4 truss
I have the documentation for the S4, which provides both HUD and MFD control of the solar panels.
But, I've looked, and looked and looked, and I cannot find ANY documentation on the cupola window operation.
The SSRMS I believe is a part of the ISS v3.2 package? The documentation lists controls but I couldn't get them to work.
So, can someone point me towards the documentation for the cupola and the SSRMS?
Lastly, I need some clarification on the following modules. They're listed in the scenario editor but I don't find any references in any of the mission briefings or addon documentation:
- PCU
- BCDU
- NTA
- CMGcovered
- KU2(plus boom/holder) - is this interactive or static? I also couldn't find which mission installed this equipment
Finally, here's the logo I came up with for the cover.
Also open to suggestions here.
(I also have a transparent version)
The final version will be complete with bookmarks navigation.
So now I've started adding equipment into the manual, and I need some help on a couple things.
Here's a small exert from the manual, namely the OFSS2 equipment list (not spacecraft, just equipment and modules currently in use).
The list is in order of first module installed to the last.
(please feel free to make suggestions on the format of this list and/or the content of the descriptions and functions...after all, this manual is designed to be helpful to you guys, the pilots)
As far as I can tell, there are only 3 pieces of equipment CURRENTLY on the OFSS2 that are interactive:
1. SSRMS
2. Cupola
3. S4 truss
I have the documentation for the S4, which provides both HUD and MFD control of the solar panels.
But, I've looked, and looked and looked, and I cannot find ANY documentation on the cupola window operation.
The SSRMS I believe is a part of the ISS v3.2 package? The documentation lists controls but I couldn't get them to work.
So, can someone point me towards the documentation for the cupola and the SSRMS?
Lastly, I need some clarification on the following modules. They're listed in the scenario editor but I don't find any references in any of the mission briefings or addon documentation:
- PCU
- BCDU
- NTA
- CMGcovered
- KU2(plus boom/holder) - is this interactive or static? I also couldn't find which mission installed this equipment
Finally, here's the logo I came up with for the cover.
Also open to suggestions here.
(I also have a transparent version)
Last edited:
diogom
Well-known member
- Joined
- Aug 2, 2010
- Messages
- 1,556
- Reaction score
- 913
- Points
- 128
- Website
- github.com
- Preferred Pronouns
- he/him
I know the controls to operate the cupola, but I can't find the documentation. It (the cupola) is included in Dave's STS-130 exp pack, so it should be in something related to it. Anyway, the controls are Numpad Shift+1;2;3;4;5;6:7, if I'm not mistaken.
Yes, the SSRMS is part of ISS by Thorton.
Yes, the SSRMS is part of ISS by Thorton.
HAL9001
super-ninja-orbinaut
I'd love to fly a STS-mission later (when there will be more), I'm a big fan of Space-shuttles and of the Shuttle-Fleet!
In anticipation of PTV-2, I used the template I created and filled in as much data as possible for a rough first version of the OFSS2 Operations Manual.
What I really need is input, since this is for the pilots.
What do you want to see in this? How do you want it organized differently so it's easier for you to fly your mission?
Here's a first draft:
http://home.comcast.net/~ajpongress/documents/PTV-2 Flight Manual.pdf
What I really need is input, since this is for the pilots.
What do you want to see in this? How do you want it organized differently so it's easier for you to fly your mission?
Here's a first draft:
http://home.comcast.net/~ajpongress/documents/PTV-2 Flight Manual.pdf
C3PO
Addon Developer
- Joined
- Feb 11, 2008
- Messages
- 2,604
- Reaction score
- 31
- Points
- 63
Very nice!!! :thumbup:
I've got a few suggestions.
A list of keyboard shortcuts for the piloted ship. In this case the Castor/PTV.
IMHO we don't need that many pictures. A flight checklist is supposed be clear and efficient. Good looks is not in the requirements (unless you're talking engineering-pretty) :lol: The only really necessary image is the station overview.
A list of orbit data/burns for each flight day (that you're not docked) The actual data would have to be blank boxes that the pilot fills out.
Entering all the data is of course optional, and IDK if other Orbiteers like to do stuff like mass/DV/Burn time calculations.
I've got a few suggestions.
A list of keyboard shortcuts for the piloted ship. In this case the Castor/PTV.
IMHO we don't need that many pictures. A flight checklist is supposed be clear and efficient. Good looks is not in the requirements (unless you're talking engineering-pretty) :lol: The only really necessary image is the station overview.
A list of orbit data/burns for each flight day (that you're not docked) The actual data would have to be blank boxes that the pilot fills out.
Code:
FD-1:
Initial orbit: Liftoff Time[ ] ApD[ ] PeD[ ]
Insertion Burn: Init.Mass[ ] DV[ ] t[ ] ApD[ ] PeD[ ]
Phasing Burn:Init.Mass[ ] DV[ ] t[ ] ApD[ ] PeD[ ]
Alignment Burn: RInc[ ] Init.Mass[ ] DV[ ] t[ ] Resulting RInc[ ]
FD-x:
etc.Entering all the data is of course optional, and IDK if other Orbiteers like to do stuff like mass/DV/Burn time calculations.
Well as I said, I wanted to make a one-stop-shop place for information, so that's why the manual doubles as a flight manual plus station manual all in one.
I thought pictures would be helpful for visual based people.
But...I go for perfection in anything I work on so yeah, it has to be pretty!
I thought about ship keyboard shortcuts, but I'd have to make different versions of the manual for each ship. Having all shortcuts for all ships in one manual didn't make sense to me.
I can throw the burn data boxes in. Optional if people want to fill that stuff out. If anything adds some more substance to the flight manual, even if it's all blank.
I think I'll add a page for pilot notes as well, a scratchpad (assuming the person prints the manual out).
I also need to come up with a better title then OFSS2 Operations Manual on the front cover. Because if it has mission specific data, i.e. PTV-2, this becomes confusing.
Maybe just "Flight Operations".
*edit*
I still have yet to hear back from Kyle. PM'ed him several days ago.
Also, only a couple people have shown any interest in this project. I'm starting to wonder if people even want something like this or if everyone is happy with what they have already.
I thought pictures would be helpful for visual based people.
But...I go for perfection in anything I work on so yeah, it has to be pretty!
I thought about ship keyboard shortcuts, but I'd have to make different versions of the manual for each ship. Having all shortcuts for all ships in one manual didn't make sense to me.
I can throw the burn data boxes in. Optional if people want to fill that stuff out. If anything adds some more substance to the flight manual, even if it's all blank.
I think I'll add a page for pilot notes as well, a scratchpad (assuming the person prints the manual out).
I also need to come up with a better title then OFSS2 Operations Manual on the front cover. Because if it has mission specific data, i.e. PTV-2, this becomes confusing.
Maybe just "Flight Operations".
*edit*
I still have yet to hear back from Kyle. PM'ed him several days ago.
Also, only a couple people have shown any interest in this project. I'm starting to wonder if people even want something like this or if everyone is happy with what they have already.
Last edited:
C3PO
Addon Developer
- Joined
- Feb 11, 2008
- Messages
- 2,604
- Reaction score
- 31
- Points
- 63
OK, I see your point.
The cover lead me to believe that this was a mission specific manual.
A detailed blow-by-blow instruction isn't applicable for a generic station manual, or even possible. I like the idea of the a station manual with a notes page thrown in.
It's hard to judge the interest on the amount of replies alone. The best parameter is the number of downloads.
I make add-ons for my own pleasure, and if I think it's good enough, I release it. It's great if anyone else enjoys it. But if no one does, that's fine by me too. That doesn't mean that I'm not open to suggestions.
The cover lead me to believe that this was a mission specific manual.
A detailed blow-by-blow instruction isn't applicable for a generic station manual, or even possible. I like the idea of the a station manual with a notes page thrown in.
It's hard to judge the interest on the amount of replies alone. The best parameter is the number of downloads.
I make add-ons for my own pleasure, and if I think it's good enough, I release it. It's great if anyone else enjoys it. But if no one does, that's fine by me too. That doesn't mean that I'm not open to suggestions.
Last edited:
PhantomCruiser
Wanderer
@ Halcyon, Heck yeah and proceed with what you've got so far. It makes perfect sense to have a companion manual for a project of this magnetude. Thorton's ISS manual has a really nice section that has the hot-keys listed, by module. It sure helps a lot (particularly with the station's RMS).
If you send it to me, I can tack it on as an attachment to the original post for this thread (like as a .zip file). I imagine it'll be a work in progress, since we have a manifest that reaches to the end of this year.
If you send it to me, I can tack it on as an attachment to the original post for this thread (like as a .zip file). I imagine it'll be a work in progress, since we have a manifest that reaches to the end of this year.
diogom
Well-known member
- Joined
- Aug 2, 2010
- Messages
- 1,556
- Reaction score
- 913
- Points
- 128
- Website
- github.com
- Preferred Pronouns
- he/him
I tottaly support the manual thing. BTW, can anyone tell me where the Nadir/Zenith are on the OFSS2? It started has KU/ELC, repectively, but now with the orientation of the PMA, and the S4, it seems to have changed. It also seems to have changed on the scenario descriptions. Simple stuff that messes with my head. :lol:
Last edited:
- Status
