Jump to content

DunaManiac

Members
  • Posts

    1,345
  • Joined

  • Last visited

Everything posted by DunaManiac

  1. There are of course the staples; the early-career powerhouse the terrier and the swivel, as well as the mainsail. I would pick the skipper, as its more efficient than the mainsail, but I find it to be too weak. It really needs to have side boosters to be viable. The vector is small and powerful, with high gimbal to boot. I would however, pick the aerospike. Its one of the most efficient 1.25 meter engines, but not ludicrously overpowered like the vector, nor weak like the NERV. It also has a decent amount of thrust, enough for a relatively small 1.25 meter rocket or a spaceplane. And it has a unique look on top of that.
  2. Finished conceptualizing my ambitious Mun base, MSB1. Now, exactly how I'm going to get all this there is another question. But anyway, this base is in contrast to my more modest Minmus base design, In other news, the first 2 modules of the Kerbin Starbase are going up.
  3. Its important to note that this isn't the finished game, nor even the latest build. It'll probably be refined and polished as we get closer to release. It's too early to criticize what is most likely a rough placeholder.
  4. Part 0: Construction and Service Missions. Launch #1: The Central Truss. Launch #2 the Second Half of the truss, as well as the uncovering of a massive blunder. Service Mission #1 Launch #4 - The Airlock/Converter/Fertilizer storage module. Launch #5 - Supply storage module Launch #6 - Agroponics Module Launch #7 - Scientific/Scanning Storage Module Launch #8 Fuel Reserve Launch #9 - Tylo/Vall/Pol/Bop Lander Launch #10 - Laythe SSTO/Lander Launch #11 - the propulsion module. And with that, the structure of Jewel 1 is complete! The next part will detail the second service mission, the crew launch, leaving Kerbin and the launch of the two probes.
  5. This is my attempt at @JacobJHC's Jool 5 challenge. A few months ago, I had realised that I had been playing since version 0.25 and yet had never attempted a Jool 5, nor even conducted a manned landing on any of Jool's moons and return, even though it was well within my skills to do so. Part of the reason why it took me so long to build and complete a Jool 5 is because aside from real life concerns, it is an active save and I was engaged in doing other things. And now, I have finally done it! My my, what a journey it was. One of the most complex missions I have ever designed. Another thing that made the mission challenging was having USI life support installed, so no stuffing kerbals in lander cans for decades! It forced me to build a true mothership that could keep them in relative comfort for years. This also comes on the heels of the completion of another challenge, a Minmus elcano. But first, some general information: MODDED 3rd level submission (notable mods include SSPrx, USI life Support, Scansat, Near Future Electrical and B9 Procedural wings). Game version 1.10.1 Non-ISRU (Didn't refuel.) 5 kerbals are onboard. (Jebediah, Hadley, Bobrim, Barke, and Melfrod) 11 Launches were required (13 counting the two service missions that I will go into greater detail later). Two probes were launched along with the mission (separately), a satellite (Deep Space 1), and a laythe drone, (Laythe Skipper). The vessel chosen for this endeavor was the Jewel 1. The first in a line of interplanetary vessels. Its sister vessel, as of the completion of this challenge, Jewel 2 has been completed and has now served two missions to Minmus to construct a station and base in orbit. Being 70 meters long and weighing 779 tons, it is by far the largest vessel I have ever constructed. It carries all the logistical necessities with USI life support to bring a crew of 5 to Jool and back in its upper portion, including scansat data, supplies and fertilizer storage, a converter and a greenhouse. It carries several modules, including the Tylo/Vall/Pol/Bop lander, the Laythe spaceplane, a small LF+OX fuel reserve, and the Hibiscus, the crew return vehicle. The mission took 8 years, from its first module to its return. Well, let's get started, shall we?
  6. With the base and station fully complete and staffed, its time to take the mothership home. I've had the station berthed to Jewel 2 for most of the time, and watching them separate was spectacular. We leave Minmus to return its crew home. Once in orbit, I sent up a majesty-class SSTO to pick up the two remaining kerbals aboard; Calbert and Dildrin. Piloted by Malfen, after staying for a few minutes to get ready for a complete shut-down, Malfen, Calbert, and Dildrin leave in the Majesty-class. Reentry is smooth, but I always overdo it. And touch down!
  7. I've dealt with that before. I believe its because the normal map is saved in an incorrect format.
  8. Banned for not spelling it like blood hungry
  9. What is that exactly? Where's bonnie and clyde? Thought I saw them somewhere...
  10. If I had to say most visited, it would probably be Minmus. I've spent a lot of time on that frozen wasteland, including building several bases and an elcano. Second to that would be Duna. The least visited would probably be either Moho or Eeloo. I've only sent one manned mission there and it required such a beast of a rocket that I'm not inclined to try it again, and at least 2 probe missions that I can remember. I did send a manned mission to Eeloo once a few years back. Haven't been there in years, but I do remember sending at least one probe.
  11. This is my attempt at an Elcano, specifically circumnavigating Minmus. As I'm on vacation I've had a lot of time for KSP lately, so I decided the best way to waste my time would be to circumnavigate Minmus. The rover; the Standard Reconnaissance Vehicle is a mostly stock rover, with several modded parts such as the SSPRx service bay, the KIS containers, and the Near Future command pod. I wanted to develop a rover that could be used reasonably well on most bodies, so I figured that an Elcano would be a perfect way to see if it really deserves the title "Standard." It can carry two kerbals, and its service bay contains a generous amount of science experiments. It can also carry a large amount of BG surface experiments, as well as items within its KIS cargo containers. This is the first time I have attempted a long drive like this, since the time I drove 70 kilometers on Minmus a few years ago. However, I was very pleased with the SRV's final performance. It only crashed once, and that was after 90 kilometers of driving, and even then only because I was careless and wasn't monitoring it. For the other 280 kilometers, I drove completely without incident. The starting position was at MSB1, located at 14 degrees north, 65 degrees east. Part 0: Launch and Delivery
  12. The Jewel 2 sets out for Minmus. I had to rearrange a few of the modules so that the CoM would be more balanced. It has a crew of 2 regular crew, 2 base crew, and 4 station crew. I planned to rendezvous with the currently derelict Service Station 1 in Minmus Orbit, before using the trailer tug at MSB1 to ferry the base modules down to the surface. The Jewel 2 mothership rendezvoused with the station. I planned to use the tug to assemble the station modules that Jewel 2 brought. The only problem that I could forsee was the fact that in order to reduce part count I didn't add a docking port to the other side of the solar array. So I employed Dildrin to move a spare docking port from another module to the end of the solar panel, allowing it to be moved. Things went smoothly however, and the station was completed. Soon after, I berthed with it in order to allow the kerbals to transfer over. And with that, Service Station 1 is complete. All that's left to do now is transfer the base modules down to the surface with the help of my trailer tug down at the Minmus Base.
  13. Banned for not posting enough outside of forum games.
  14. I collect the rust with a gigantic vacuum cleaner. Rust Hill
  15. But how do we prevent the visual shift? It would be even more pronounced than the planetary bubbles, as you could literally have a night-to-day transition.
  16. But my point is, that system does desync players inside kerbin's supposedly uniform bubble. First off, how do the individual vessel bubbles' time relate to the planetary bubble's time? Could you see a situation where you have multiple stations at different times? Secondly, if one can step outside of multiplayer at any point to timewarp while inside the bubble, then that is, by definition, desynching players inside the bubble, which it's only purpose is for players have a supposedly uniform time. What purpose then, does the planetary bubble serve? How does that avoid all the problems of ordinary timewarping? Furthermore, you'd agree that most people given the option, would timewarp rather than spend a few hours waiting for a kettle to boil. So you have the bubble violated in every rendevous. So what you're describing is a system where each vessel has its own bubble, and you are synced to its time whenever you enter its physics range. The planetary bubble is irrelevant by giving one the option to step outside of multiplayer. That's not to mention the virtually impossible to hide jump as you move to a completely different point in the orbit due to the vessel-sync up. It's not impossible to have a scenario where one is approaching the station at night, only for it to be day when you get inside its bubble. So I ask again, how is the hybrid system compatible with;
  17. Hold on, forgive me if I have this wrong, but I thought that the system was that each planet was in a pocket-dimension of sorts where time flows normally. Only leaving this bubble could you use time-warp, as you effectively step outside of time. Then you can time-warp for as long as you want before you re-enter another bubble, moving time backwards or forwards in order to be back to the same time as everyone else. But what if said shipyard is inside said bubble? I mean, if you've ever attempted a rendevous than you'd know that most rendevous take hours. "Just build a torchship lol" isn't an answer, especially if we're dealing with a progression-type mode. Even an autopilot doesn't solve the problem of having to leave your computer on for literal hours as you slowly orbit in real time. And how does: Square with your earlier statements; I mean, are you arguing that you can step outside of Kerbin's time and timewarp even while you're near the planet? If that's so, then why do you need the extra step of a planetary bubble, if its simply irrelevant? Why not just use ship-based bubbles then?
×
×
  • Create New...