Search the Community

Showing results for tags 'features'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • The Daily Kerbal
  • Kerbal Space Program 2
    • KSP 2 Discussion
  • 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
  • Making History Expansion
    • Making History Missions
    • Making History Discussion
    • Making History Support
  • Breaking Ground Expansion
    • Breaking Ground Discussion
    • Breaking Ground Support
  • International
    • International
  • KerbalEDU Forums
    • KerbalEDU
    • KerbalEDU Website

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Skype


Twitter


Location


Interests

Found 4 results

  1. Kopernicus Continued Planetary System Modifier is a mod that provides for the graceful introduction of new celestial bodies to Kerbal Space Program. This is where we test new things and learn how break the universe with gusto. Disclaimer This is R-T-B's "Bleeding Edge" branch of Kopernicus, intended to support the latest features, KSP editions, and also the latest bugs. Please keep in mind this branch may be more buggy than Prestja's mainline Kopernicus branch, but it also supports more KSP versions and has more features implemented for testing reasons. Many features that make it into mainline Kopernicus are born, tested, and trialed by fire here. These features do get tested, briefly, and they generally work, but still, bugs can be slip by and be real, so it is important to BACK UP YOUR SAVEGAMES! It should be noted I am a member of the current Kopernicus Maintainence effort and this is an official Kopernicus-Continued subproject. Features: Presently, over the base Prestja Kopernicus-Continued branch, this branch also features. 1.) Particle System support (it existed before, but was removed in 1.8.1). 2.) A common source code base for both 1.9.1 and 1.10/1.10.1, enabling easy retrocompatability when we fully move to 1.10.x. Yes, this means we can support old releases well into the future if this works. 3.) Cool stuff you have no idea... (do I even?) 4.) bugs??? FAQ: 1.) When will this leave development? A.) It won't. The whole idea is this is the eternal testing ground. It stays here forever and ever and ever... 2.) What does this mod do? A.) On it's own, nothing. It's generally a dependency or modders tool. No more FAQ for now, ask me something frequently and I may add it to stop you... Downloads Kopernicus "Bleeding Edge" Unified Downloads Please ensure you grab the right version for your KSP version! 1.9.1 needs a zip with _191_ in the filename, 1.10 needs _110_, 1.10.1 is _1101_, etc. Credit Credit must be given to other current Kopernicus Maintainers @prestja, as well as previous authors @Thomas P. , @Sigma88 and many others for their incredible work in building an elegant solution for bringing new worlds to KSP. Source Code Source code can be found on the GitHub repository. See branch dev110 for details. License Kopernicus is licensed under the GNU Lesser General Public License
  2. Basically, I have a lot of multi-role machines in orbit or on the ground. I've gone pretty far with this "multirole" stuff to be honest. Even as far as to build an amphibious scientific research vehicle (no lab, I didn't think to incorporate one) with vehicle recovery ability (robot arm with Klaw). After finishing my amphibious science machine, I started to wonder if I was feature creeping my designs. https://en.wikipedia.org/wiki/Feature_creep (Yeah, Wikipedia. It's just for a simple definition.) I mean, less can definitely be more, but Swiss Army Knives sell well for a good reason too. Minimalism isn't an excuse to be lazy; it's a reason to be efficient, sure. But in a game like KSP, can you really feature creep with scientific modules so small and portable? Are you really that bad off trying to cover all the bases? Especially when one of the important parts of progressing in this game is scientific research. Honestly, so far, I haven't experienced much trouble with this beyond price tags. That's even manageable if you can inadvertently create something that can do many of your contracts with little modification. Do you ever get the sense you may be trying to mash too much into a design? When do you realize you've gone too far? Asteroid harvesters on space stations? ISRU on rovers?
  3. Hi all, since 1.1 pre-release I am playing a new career game and I have (unluckily...) sent a bunch of tourists out to a Mun/Minmus sightseeing trip w/o any chute to re enter Kerbin atmosphere. My fault of course, then I suddenly realized I could not bring them home safely if not by strapping some chutes to the craft - an auxiliary chuted&clawed skycrane seems like the only feasible option in stock. If tourists could be allowed to go EVA just for switching vessel or to man a command chair that could bring at hand a few more "quality playtime" opportunities. They obviously should not be allowed to collect samples or reports and to gather and move samples from pod A to pod B. Just sayin'.
  4. Here are my tips on how to keep the core spirit of KSP intact while giving it some more features that enhance the immersion and wow factor of the game: Give the player an avatar Kerbal. This avatar is the director of the KSP and you can name him whatever you want. The campaign should start off with a car pulling up to the center with your kerbal inside, and you are given a tour of the center with Von Kerman. The previous director had an "accident" with one of the rockets and you were recruited to replace them ASAP. As a result, new safety features need to be put into place to prevent any more "accidents" from happening and to improve and inspire the rest of the kerbal race for space exploration. Your first job is to allocate budge for R & D and launches. Gathering science should NO LONGER be the only way to unlock new parts, but it can be used for a boost to funding and engineers. Parts require 2 things, money and engineers. And as oppsed to being able to unlock and use a part as soon as you can afford them, the parts should be researched that requires TIME. The more advanced the part, the more time it requires to research (and thus more funds). Science gathered from missions can be used to attract and hire newer engineering teams that can make the process go by faster and cheaper. SCIENCE SHOULD NOT BE A CURRENCY TO UNLOCK PARTS. I thought this was a silly idea since it was implemented. For example: Lets say you gather science from Mun on an EVA and return it to Kerbin. The science you gather is complied into your space programs science reputation pool, which in turn unlocks better engineers who want to work for you. At the beginning of the game only the craziest and dumbest engineers are part of your program staff but as you get more scientifically reputable smarter engineers start applying to work for your program. ANY engineering team can start research on a part in ANY part of the tech tree BUT it would take more or less time depending on the skill of the team doing the research. YOU SHOULD ONLY HAVE a limited number of teams, each with specific skill and knowledge level that impact how quick it takes to research and develop new tech. ONCE the part is built, you need to TEST IT at least a couple of times to certify it is usable for rocket craft. We as the player DON'T have to actually test the part BUT we can watch the test if we wanted to in the testing facility. Each part that we test has a chance to fail depending on the engineering teams safety record. If the part was a rocket engine, it needs to survive ignition, burn for x amount of time, gimbals in all axis (if it has gimbal ability) and survive shut down. IF a parts fails, it costs money and requires re-testing. In order to test a part we need a new testing facility. We should also be able to upgrade this facility, further improving the safety stats for each part we test. Once the parts passes testing, it is green lit for use on our rockets in the VAB. Engineering teams should have the following characteristics: - stupidity - safety - efficiency/speed - SALARY (per unit time) Our space program should have finite engineering teams with their own salaries, and finite slots to research parts. Engineering slots depends on our level of science facility. Tech tree needs to be overhauled. No more progression. It should be cut up into Engines, Structural, Tanks, Utilities etc. You can research ANY part you want at ANY time. The problem is that the more advanced the part, the longer it will take. Your program becomes a BALANCING ACT of funds spent on R & D, salaries for engineers and launches. If you start your program with crappy teams and start research on the KS-25 engine, all you're gonna do is spend a lot of money and TIME on one engine part. Your goal should be to develop simpler parts that allow rocket launches to gather MORE science to attract BETTER teams to research better parts FASTER, SAFER and THUS CHEAPER. Continued....