Search the Community

Showing results for tags 'launcher'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • The Daily Kerbal
  • General KSP
    • KSP Discussion
    • Suggestions & Development Discussion
    • Challenges & Mission ideas
    • The Spacecraft Exchange
    • KSP Fan Works
  • Gameplay and Technical Support
    • Gameplay Questions and Tutorials
    • Technical Support (PC, unmodded installs)
    • Technical Support (PC, modded installs)
    • Technical Support (PlayStation 4, XBox One)
  • Add-ons
    • Add-on Discussions
    • Add-on Releases
    • Add-on Development
  • Community
    • Welcome Aboard
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
  • International
    • International
  • KerbalEDU Forums
    • KerbalEDU
    • KerbalEDU Website
  • KSP Pre-release
    • 1.2.9 Pre-release Branch
    • 1.2.9 Pre-release Modding Discussions
    • 1.2.9 Pre-release Bug Tracker

Categories

  • Developer Articles

Found 5 results

  1. Hi, I'm playing KSP for 2 months and have Some Experience, But to Some cause, I needed to re-start my Game and Now I'm in Early-Mid Carrer. As in this Phase Many, Build subassemblies for Fast and Effective Missions. Most subassemblies are Launcher. I want to Request our Modders to Create a Mod that creates a Report for a Launcher about its Specification. I.E. Weight, Thrust, Delta-V, Thrust Vectoring, Speed and most Important for Choosing a Perfect Launcher, A Launch Capability Report, about, Weight to Low Kerbin Orbit, Kerbin Stationary Transfer, Stationary Orbit and Trans-Munar and Trans-Minmas Injection Orbit. Plz Recommended An Mod or Create one, Its an Idea for Modders not a Planned Project. Plz ,Thanks
  2. Dear @Kerbal Astronautics it's ready! Here comes a full stock Pegasus-Stargazer system called Chrysaor-Kalliroe. Coming from a old project started about two years ago it was not possible to create a TriStar-like carrier powerful enough a this time with the Whiplash being the only turbofan available. I threw away the carrier file and just keep the launcher in case of better days : Time passed by and a week ago I discovered the work of Kerbal Astronautics who made a Pegasus-Stargazer craft. It immediatly brings me back the envy to finish an incompleted work. And now with the Goliath available no way to step back again. The craft in available on KerbalX : https://kerbalx.com/XB-70A/Chrysaor-Kalliroe-Pegasus-Stargazer Build with 93 parts, the carrier is powered by three Goliath engines and able to climb to 10 km before dropping the launcher, but at this altitude the whole system whill be about to stall. The best launch configuration is between 5-8 km, at this time the speed should between 170-115 m/s. Stabilize the roll as much as possible, keep the Y-axis a bit positive then drop Chrysaor as your will. Once free you have some seconds to stabilize a bit more if you need it then you can light up the first stage. The rest is more than basic and easy. Honestly it's the sole system with one of my shuttle I decided to ensure the whole control from the launch to orbit for the first time since maybe a year. Its whole stability is surpprinsing good enough to make it easy to fly. First stage separation after a minute. Second stage activation. . The third complete its function of circularization. The payload is a small relay satellite only built to confirm the system possibilty to place a payload of 1-1.5 tons in orbit. I decided to use its own engine to place it on a more convenient orbit for its limited capabilities. After these maneuvers some dV was still available. But to me the best part of the system is that : The carrier is recoverable with Stage Recovery mod. The whole flight album is available here : http://imgur.com/a/Jsct4
  3. Greetings. Firstly let me just explain that I am quite new to the game as I have only been playing for a week or so. I'm having a bit of difficulty getting my Mun lander into orbit of Kerbin, let alone to the Mun. My main issue is loss of control - the rocket spins, flips and does whatever it wants, even with SAS enabled, whenever I engage the main liquid engine. It's fairly stable whilst using the initial boosters to get off the ground though...until I fire up the main engine that is... I have tried many different setups using my brain to design them but to no avail, so I thought i'd ask you guys for some help. I'm not asking for someone to design a rocket for me (i'm not that lazy), however if what I am doing needs to be binned, then I will happily accept any help that is offered. My lander and command module is 13T in mass...which might be my first problem. Here is a screenshot (not including AE-FF1 protective shell - is this needed?) without any of the many rocket designs I have tried below it. I have tried both slim and fat launch vehicles, usually with 2/4 boosters at the bottom. I have tried attaching some boosters further up near my payload to "tug" it unto orbit and that also doesn't work. Perhaps I need to learn more about launch profiles, perhaps just rocket design. Either way, I have been trying all day to launch this to no avail. I can get to 80km+ but when I try to round off my orbit, the rocket spins out of control even on quite a low throttle. Redesigning my lander isn't out of the question either. Does anyone have any tips, suggestions or help please? Many thanks in advance.
  4. Hello, Just wanted to point out, that since version 1.1.2 the Steam launcher automatically launches KSP in x32, by default, instead of x64 like in version 1.1.1. If one would want to launch in x64 (most of us do), you would have to go to the Steam Library, right click on the game and click on "Launch KSP (64-bit)". I would like an option to choose which one it should launch by default, or go back to launchit it in x64 by default. Or some suggestion as to how to configure the launcher with the "Set launch options" so that the game starts in x64 when clicking on the shortcut.
  5. While updating to 1.1.2 through the launcher I noticed an error in red. The rest of the install carried on fine so I didn't look too hard. I got into 1.1.2, put a plane on the Tier 1 airstrip (one up from dirt) and all three wheels of a plane that worked in 1.1 were completely embedded into the ground. Throttling took ages to create speed because it wasn't just visual, the wheels are failing to function at all as wheels, and are basically just a rigid part grinding against the surface. When I hit around 22km/s the steering wheel in the rear exploded. So I went back to see what this updating error was, and if something had broken the install. I'm unhappy to report that the error is the launcher's updater trying to update a file that the updater itself has in use and won't release. (see screenshot above) I'm going to assume that this log file that wants renamed is just a log file, and doesn't affect the rest of the update process. Which means I have a good clean copy of 1.1.2 - the version that patched broken wheels from the 1.1.1 patch for the broken wheels in 1.1 - and this new version has broken wheels on a whole new level. --- Career mode doesn't work so long as you can't use the first wheels the game gives to you. You can't build your first plane. You can't do any of the site survey missions that take players to new biomes where they can legitimately collect more science. (You can, but players mustn't be expected to build crazy rockets, out of early-game parts, to deliver them to locations below 18km -- and I don't believe that's not how you intend it to be played.) Between getting an orbit and starting to run Moon missions all you can do is test parts and move tourists around. Building planes is not an option right now, even though it is exactly the intended path for players to follow and exactly what Mission Control emphasizes at that stage of the game. Dear Squad, THIS is the game of your game. You don't seem to pay much attention to the game of your game. Version after version, since 0.24, and well past 1.0 now, I have watched as this team has favored adding new parts and new game mechanics, tweaking the physics, altering atmospheric drag formulas, and developing virtually every other area of the sandbox in which the game takes place OVER THE GAME THAT TAKES PLACE. Your playtesters clearly do not have a script to follow to test career mode, and they should. This team, and I'm talking about the development team, needs to have more than just a soft-idea of what players will be doing with their newly unlocked parts as they progress through the career mode of the game. Mission control should be a central priority for you, as it is the conduit through which new players see what they should try next, as well as what the game believes them able to do with the tech they have, or will be getting soon. And at least some portion of your playtesters need to have a checklist of basic milestones to fulfill in each and every new iteration of the game that is passed down to them to verify that the path of the game -- most importantly the early game -- still works no matter the version. Because that's the GAME of this game. It's important. It should be the MOST important. I'm taking time to write this because you could not have released this version, or the two that preceded it if you had already taken this idea to heart; if it truly was a priority to you. Releasing, but over and over again, in this state evidences a mind that has been so focused on implementing a more expansive sandbox that it has come to devalue game progression to the point that it's okay for the Career paths to be completely and utterly broken -- if just for *this* release. It is not okay. It hasn't been okay since 1.0. And it should not be okay to you any more, or ever again. --- I will make myself available if you'd like to hire me to direct playtesting. That role is supposed to be filled by an impassioned critic who rubs you the wrong way. Someone who won't quietly let things like this slide. Who will demand your attention and challenge you to make it better every time. Right now, you're in the hug-box.