Jump to content

Kuiper_Belt

Members
  • Posts

    115
  • Joined

  • Last visited

Reputation

771 Excellent

About Kuiper_Belt

Profile Information

  • About me
    Certified Not a Rocket Scientist
  • Location
    Launch Complex 39
  • Interests
    Likes long walks on the beaches of Laythe.

Recent Profile Visitors

1,954 profile views
  1. Thanks! That would be Cormorant Aeronology. Interesting! I keep that in mind If I ever revisit it.
  2. I love what you did with the custom icons! I’m right there with you with wanting to start a new career save! Don’t sweat it dude. Take your time! You’re creating this wonderful thing for the game, the least we can do is be patient!
  3. Thanks! I never really noticed that about Pirs and Poisk but in retrospect it makes total sense! I rotated the docking port for future missions. Thanks for the tip! Expanding on that, I’m thinking that when Pirs was designed for this rotation was to make clearance for Nauka which was originally going to be placed where Rassvet now rests. In that timeline I believe Pirs would be replaced by the Universal Docking Module. But in regards to our timeline… Progress M1-7 Coming Soon! In glorious version 1.12.2!
  4. Thanks a lot! The shape is right but I the I think the makeover really pushed it further. In regards to 1.12 performance, they changed KSP to a newer Unity version and its supposed to give better performance (Here is an example!). I'm not sure how much of this will translate to the the modded mess that is my GameData folder but I am hopeful for a measurable difference! I'll be sure to note and inform you guys on my FPS in various situations in both versions to see if there is an actual difference. Granted PC component idiosyncrasies will cause the results to vary but if there is a measurable difference for me I'd wager to say that It would affect most people. Thank you! In regards to CanadArm generally do a heaviest autostrut but if you're having trouble I'd try root after heaviest. BE SURE TO LOCK ALL THE JOINTS FIRST! If you are in 1.11 or above you could send a Kerbal on EVA to strut the arm down to the payload bay.
  5. You are correct it is some root part offset trickery! The only way to get the Modular Launch Base to work with the Katniss Pads is to have the root part be somewhere NOT over the flame trench. For the shuttle launch base I set the root part to the base part of the fixed service structure. For Apollo and SLS pads I clip a little cubic strut into the pad and set it to the root part. Be warned, the launch clamp WILL NO LONGER WORK! Why? I don't know! I don't make the rules ! To remedy this I usually just clip in a stack decoupler and call it a day. Remember to autostrut everything as the connection between the rest of the rocket and the decoupler is rather weak. Hope this helps and good luck!
  6. Another fantastic mission! I love what you did with the tiles! I would've never thought of placing them on the path of the RCS. Can't wait to see the next missions and thanks you again for adding me to the flight list, its an honor !
  7. The DIRECT 3.0 Proposal - May 29th 2009 Authors Note: This'll be a rather long one! Hope you enjoy it as much as I loved making it ! DIRECT was proposed and advocated by a group of space enthusiasts including engineers of NASA and other aerospace contractor as an alternate path developed to replace the Space Shuttle as NASAs primary launch vehicle. Competing against the Constellation Program's Ares Shuttle Derived vehicles would be the Jupiter launch vehicles. Their naming scheme being Jupiter-XXX with the first number indicating the number of cryogenic stages, the second number indicating the amount of first stage RS-25s and the third indicating the number of second stage engines. Jupiters could be configured to launch Crew, Cargo, or both. The idea behind DIRECT was to reuse as many facilities and components of legacy Shuttle hardware as possible, the primary target was engines as it was supposed that developing new engines would lead to the longest delays. The Jupiter launch vehicles used modified External Tanks designated the "common core stage" that were identical in volume and diameter but with a blunt liquid oxygen tank. This modification permitted the addition of an inline payload fairing or second stage that wouldn't be possible with the ogive shape of the standard External Tank. This would allow Lockheed Martin to continue using most of the existing tooling used to manufacture the External Tanks. Beside the external tanks were 4 segment Space Shuttle Solid Rocket Boosters. The RS-25s would be mounted on a linear thrust plate where Jupiter 130 Jupiter-130 was the first of the two proposed vehicles being composed of only the common core as the final stage with 3 RS-25s. Though it's engine configuration looks unstable, the RS-25s large gimbal range could account for the unstable center of thrust. A Jupiter-130 could deliver 60 tons to LEO at a 51.6 degree inclination. Due to the large payload capacity that could loft the Orion Space Craft and the delivery of a separate payload module to LEO, DIRECT enabled missions such as but not limited to ISS crew rotation and resupply Or Hubble Servicing missions After a given mission is done, Orion would separate from its mission module and then eventually its service module and reenter. Jupiter 246 Jupiter-246 was the second proposed rocket under DIRECT 3.0. Sporting the same common core stage and SRBs, as the 246 suggests it has a 4th RS-25 on the first stage to help it lift off. As a result of this addition, the first stage will burn out faster than the Jupiter-130. The Jupiter Upper Stage or JUS which is indicated by the 2 in 246 would finish up the orbital insertion. Designed with structural similarities to the Centaur upper stage, the JUS would act as the Earth Departure Stage of the Ares V. Instead of requiring the new J2-X engine, the JUS would use 6 RL-10B-2s which were already active on the Delta IV launch vehicle as the engine in the DCSS. Jupiter-246 would be able to deliver 91 tons to LEO in a 241 km 29 degree orbit and act as the direct competitor of the Ares V. It holds the advantage of being comprised of all crew rated engines, such that you could launch lighter crewed missions to The Moon in one launch with. Designed with this objective in mind Jupiter-246 would be the rocket that would deliver humanity to surface The Moon. DIRECT To The Moon - Mid to Late 2010s DIRECT have a direct transition from Shuttle and LEO activity to The Moon and Mars. Following this will document the profile of a launch of crew to the surface of The Moon. As it was in competition with Constellation it would use the Altair Lunar Surface Access Module (LSAM) and the Orion Space Craft. Due to the lower margins to orbit than the Ares V, Jupiter 246 could not deliver the LSAM to lunar orbit, then immediately dock with Orion and finally initiate the trans-lunar injection. Thus the solution found would be to launch Orion and Altair to LEO and then rendezvous with a fully fueled JUS that was launched beforehand. Rollout of the crewed variant of Jupiter-246 to Pad 39-A while the other is being prepared for launch at Pad 39-B Liftoff off of the Jupiter-246 with the TLI JUS. Fairing jettison. Though not much is being carried beyond the docking mechanism is crucial for the completion of the mission. Stage Separation and Second Stage Ignition. The JUS finishes its orbital insertion and begins to wait for its visitors. Meanwhile back at Pad 39-A the crew prepares the second Jupiter-246 for flight. Liftoff! Jupiter has cleared the tower! Booster and LES separation. MECO, Second Stage Separation and Second Stage Ignition. JUS finished orbital insertion into a rendezvous path with the TLI JUS. Afterwards Orion will separate simultaneously with fairing jettison and will reposition for extracting Altair. Orion and Altair would coast in its phasing orbit and make course corrections as needed. After hard capture is made, the combined JUS Altair Orion craft will prepare for TLI. After the TLI, Altair and Orion will separate from the JUS. They'll coast to the moon making adjustments as need. Altair uses its RL-10 to capture in an elliptical orbit around the moon. This orbit will be circularized further by Orion but due to its small service module could not completely do a circularization burn. Orion and Altair orbit the moon and eventually separate. Altair prepares for descent by putting itself on a suborbital trajectory using its RCS. (Authors Note: I'm not entirely sure if this was the process, I was cutting it close on fuel and needed to conserve ) Afterward Altair would fire its RL-10 all the way to landing Touchdown! Altair lands safely in The Mare Crisium. The crew will spend a week on the lunar surface conducting experiments. The crew prepares Altair for liftoff and rendezvous with Orion. Goodbye Moon. Altair will spend some time in a phasing orbit before it rendezvous with Orion at which point it will dock and begin to transfer science and samples. Orion undocks from Altair and prepares for Trans Earth Injection and the trip home. After the final coast phase Orion prepares to jettison its service module and orient itself for reentry, final descent and a parachute aided splashdown off the coast of Hawaii. Welcome home Orion! DIRECT actually wasn't a complete competitor to Constellation and The Ares rockets. Jupiter 130 and 246 were also designated Ares 3 and 4 respectively seeing it as advantageous to integrate with the program. Ultimately Jupiter and Ares would fall unused as DIRECT wasn't selected and Constellation was canceled. DIRECT 3.0 was the third iteration of DIRECT with other designed hiding in the older versions including THE KERBAL Jupiter 3 I would like to go into depth on Jupiter 3 and Direct 1 and 2.0 but I felt that it didn't make sense to integrate them into this mission as it had grown quite long! I'll get to it at some point in the future as well as covering Constellation. I have more real and proposed missions queued up but unfortunately real life does a good job of taking up time! But I'll work hard to dig out time that can hopefully keep up some sort of cadence. This will also hopefully be the last mission on 1.11! I'll be working on updating to 1.12 as it gives performance benefits that are quite useful for a project that may or may not include ~450 parts cough* ISS cough*. Hopefully you enjoyed! More missions coming soon!
  8. Straight And To The Point, Direct, if you will. The DIRECT 3.0 proposal coming soon! While maneuvering the arm I find it's best to keep all joints locked except one and move them one at a time slowly. Always have the traverse rate set to the lowest possible speed. While stowed, lock all the joints and autostrut the end effector. It is crucial that the robotic parts are locked because otherwise autostrut will not work as intended. Lastly patience is key! Hope this helps you out!
  9. I'm real excited for this! I spend a lot of time in a 2.5x Kerbin sized real solar system scaled game and play with nearly all the mods listed! In science mode with all those mods, the stock tech tree leaves a lot to be desired. I really appreciate care you've been putting in and I can't wait to start up a new save with this tree! Awesome job and keep up the great work!
  10. I've been loving the series so far! I'm impressed with all of this being conducted in RSS! I would always have trouble in real scale due to lack of competence lack of struts . This series actually helped solidify my desire for me to make a RSS install again! Keep up the great work!
  11. Progress DC-1 & The Pirs Docking Compartment - September 14th 2001 Pirs meaning "Pier" in English was the third major component added to the Russian Orbital Segment of the International Space Station. Pirs provided an additional docking port to the ISS and an airlock for those utilizing an Orlan space suit. Docking to the nadir port of Zvezda, Pirs would adapt the Russian Hybrid SSVP (which in addition to standard SSVP hardware, the hybrid version features an APAS hard docking ring for the permanent mating of space station modules) to the standard SSVP docking system, one that was compatible with the Soyuz and Progress. Pirs was planned to be the first major module of the ISS to be removed. It was to be replaced with the Universal Docking Module though Russia eventually found their funding issues insurmountable and retooled the planned ROS by moving the Nauka module from Zarya's nadir port to Zvezda's counterpart. Pirs' undocking date was eventually placed in the year 2013 giving it a 12 year stay at the ISS but due to delays with Nauka, Pirs would eventually spend nearly 20 years docked to the orbital outpost, departing the International Space Station on July 26th, 2021, with Progress MS-16. Pirs' spirit lives on with her nearly identical sister module Poisk meaning "Search" still attached to the zenith port of Zvezda. Pirs couldn't be launched just on its own. Unlike Zarya and Zvezda, Pirs was effectively inert on its own as it didn't feature integrated fuel systems, propulsion or power generation to manage its orbit and sustain itself during rendezvous. RKK Energia's solution to the problem was to launch it aboard a modified Progress. Progress DC-1 replaced the traditionally present pressurized cargo module with Pirs, leaving only the progress service module to manager it's rendezvous procedures. Once docked to the ISS, the service module would be jettisoned leaving Pirs with the exposed SSVP docking port. Pirs stood by at Site 1/5 of the Baikonur Cosmodrome on a Soyuz U carrier rocket awaiting launch for the station at 23:34 UTC. Once in orbit, Progress DC-1 with Pirs coasted in the standard two day rendezvous orbit, making adjustments when necessary. Pirs docked to Zvezda's nadir port on September 17th 2001 beginning its 7000 plus day stay at the orbital outpost. The crew of Expedition 3 began work to integrate Pirs with the rest of the Russian Orbital Segment. Progress DC-1 would spend a total 9 days attached to the station, undocking on September 26th 2001 and deorbit the following day over the Pacific Ocean. Though with the departure of Pirs' service module and the end of the Progress DC-1 mission, the work of integrating Pirs was not done. Vladimir Dezhurov and Mikhail Tyurin crew of Expedition 2 would conduct 2 spacewalks. The first EVA took place on October 8th, and the second on October 15th. Dezhurov and Tyurin worked on connecting data, electrical and fuel conduits between Pirs and Zvezda while Commander Frank Culvertson directed the EVAs from within the station. 4 days after the EVAs concluded, on October 19th, 2001, the crew boarded Soyuz TM-32 to give Pirs the ultimate test and undocked from the ISS to dock with the new module. The whole relocation took 16 minutes from detachment to capture. Authors Note: I would like to thank the incredibly innovative @lemon cup for designing the Pirs module! It looks fantastic ! After boarding the ISS, the crew of Expedition 3 prepared for the primary purpose of the relocation. Soyuz TM-32 had been approaching its designed limit of time in space which necessitated a replacement lifeboat Soyuz. Up Next, Soyuz TM-33!
  12. Gave my computer the ultimate stress test: And a little Voyager fun:
  13. Almost there Bill! Just focus on the surface Jeb. I love the work you guys have done. It's beautiful!
  14. If there's room on any upcoming missions Kuiper Kerman would love to go to Freedom! He's got some old silica tiles he'd like to test in space from a now long defunct proposed reusable space plane . Loving how the series is going and cant wait to see more!
  15. Hey thanks a lot! That’s one of the two configs I’ve been working on in time between missions! I’ve had them for about a month but I have been messing around with others profiles. Glad to hear you like them!
×
×
  • Create New...