All Activity

This stream auto-updates     

  1. Past hour
  2. Missingno200

    [1.7+] Making Scenariory(Custom Scenario)

    Speaking as a poor guy, I don't actually own Making History(I even made a bit of a comment about this way back during the announcements when I asked about early access Steam users getting the expansion pack), which means that no, it's not even remotely a part of that since you can do this entirely within the base game with some manual save file fiddling. On the note of someone not making a scenario for KSP up until now, it's not exactly the same thing but I believe Kethane used to have a tutorial, or at least this guy from a thread that I can no longer find said that it might've. I know there have been a bunch of threads with people asking about how to create custom scenarios as far back as 2012 but as far as I know, this is the first one publicly released. Semi-related fun fact:The entire name of the scenario(Making Scenariory) is a reference to the Making History expansion pack. I know I can add SAS to the Stayputnik myself but frankly, that means I have to wait for another while. Plus, to be honest, I wouldn't be too angry about this if the Stayputnik wasn't alone, but there's basically an option when starting new games that you could literally rename to "Enable SAS on Stayputnik"(referring to the option to "Enable SAS on all probe cores") because the Stayputnik is the only one without SAS. Even the Rovermate has SAS for some reason. This option is a minor problem when it comes to custom scenarios, and especially a big problem the very basis of Making Scenariory, where you're not supposed to have SAS. Ah, no worries man, I'm a bit surprised I'm the first to break ground here. I hope others do start doing the same, although I might make a scenario editor to help others get into this, seeing as it is a little fiddly to work with. There is SO much potential with scenarios it's not even funny. Some final things I thought I'd talk about... A problem I encountered with making custom scenarios, which frustrated me a bit, is that you cannot turn off the SAS for all probe cores in scenarios, unless presumably you modify how scenarios work directly in the engine. I do not know why this is the case, considering all the other options from the commsnet to even some more obscure and really random ones(I mean, seriously, who needed to ability to disable the MAIN MENU!?) work just fine, but there might be some work arounds for it, maybe even just making a custom probe part that is somehow exempt from this difficulty option. Now, scenario, I've poked around a little but I'm still breaking ground on what you can and cannot do, but honestly, there is a LOT you can do in this game that I'm surprised your even allowed to do. My favorite one, the thing I think might become popular with most scenario creators, is the fact you can literally define CUSTOM TECH TREES for your scenario. This you means you TOTALLY can do a more difficult KSP without even needing to touch the existing tech trees or fiddling with mods. I think you can even get it to not look in the gamedata folder but just the general KSP Folder for these tech trees, which offers a lot. I think there is a way to also add the tutorial's popups to scenarios, but I haven't really tested it yet, but if this is the case, we are looking at some insane possibilities with scenarios. Honestly, since 0.17, Squad hasn't done much with scenarios, and it feels like a crime because the scenarios are so versatile and even have the ability to work in career and science gamemodes, it really feels like it's a crime that must be rectified by the community. This scenario isn't my first foray into the scenario scene, by the ways, but it is the first successful one. My original first had you dealing with 4 parts and was designed as basically a challenge to get to the moon, but I got delayed heavily as a result to a hard drive crash that basically destroyed my steam to tinker with KSP for a while. Speaking as a poor guy, I don't actually own Making History(I even made a bit of a comment about this way back during the announcements when I asked about early access Steam users getting the expansion pack), which means that no, it's not even remotely a part of that since you can do this entirely within the base game with some manual save file fiddling. On the note of someone not making a scenario for KSP up until now, it's not exactly the same thing but I believe Kethane used to have a tutorial, or at least this guy from a thread that I can no longer find said that it might've. I know there have been a bunch of threads with people asking about how to create custom scenarios as far back as 2012 but as far as I know, this is the first one publicly released. As for the entire breaking ground with an exceedingly rare opportunity:I aim to please, and I aim to put my name somewhere in history, so this may as well be my peak here on the forums for all I know, although I'm going to try to make sure it isn't. Semi-related fun fact:The entire name of the scenario(Making Scenariory) is a reference to the Making History expansion pack. I know I can add SAS to the Stayputnik myself but frankly, that means I have to wait for another while. Plus, to be honest, I wouldn't be too angry about this if the Stayputnik wasn't alone, but there's basically an option when starting new games that you could literally rename to "Enable SAS on Stayputnik"(referring to the option to "Enable SAS on all probe cores") because the Stayputnik is the only one without SAS. Even the Rovermate has SAS for some reason. This option is a minor problem when it comes to custom scenarios, and especially a big problem the very basis of Making Scenariory, where you're not supposed to have SAS. Ah, no worries man, I'm a bit surprised I'm the first to break ground here. I hope others do start doing the same, although I might make a scenario editor to help others get into this, seeing as it is a little fiddly to work with. There is SO much potential with scenarios it's not even funny. Some final things I thought I'd talk about... A problem I encountered with making custom scenarios, which frustrated me a bit, is that you cannot turn off the SAS for all probe cores in scenarios, unless presumably you modify how scenarios work directly in the engine. I do not know why this is the case, considering all the other options from the commsnet to even some more obscure and really random ones(I mean, seriously, who needed to ability to disable the MAIN MENU!?), but there might be some work arounds for it, maybe even just making a custom probe part that is somehow exempt from this difficulty option. Now, scenario, I've poked around a little but I'm still breaking ground on what you can and cannot do, but honestly, there is a LOT you can do in this game that I'm surprised your even allowed to do. My favorite one, the thing I think might become popular with most scenario creators, is the fact you can literally define CUSTOM TECH TREES for your scenario. This you means you TOTALLY can do a more difficult KSP without even needing to touch the existing tech trees or fiddling with mods. I think you can even get it to not look in the gamedata folder but just the general KSP Folder for these tech trees, which offers a lot. I think there is a way to also add the tutorial's popups to scenarios, but I haven't really tested it yet, but if this is the case, we are looking at some insane possibilities with scenarios. Honestly, since 0.17, Squad hasn't done much with scenarios, and it feels like a crime because the scenarios are so versatile and even have the ability to work in career and science gamemodes, it really feels like it's a crime that must be rectified by the community. This scenario isn't my first foray into the scenario scene, by the ways, but it is the first successful one. My original first had you dealing with 4 parts and was designed as basically a challenge to get to the moon, but I got delayed heavily as a result to a hard drive crash that basically destroyed my steam to tinker with KSP for a while.
  3. Aperture Science

    Shower thoughts

    No, they shouldn't.
  4. I'm also confused about how to use the map decals. I looked through the first fiveish pages of the thread but I'm still lost. Can someone point m in the right direction?
  5. Q-ver KSP

    Make a wish... and have it horribly corrupted!

    Granted, you get a job, but your designs are so Kerbal that they all blow up, and you get fired. I wish I had cookies.
  6. Option 4 is interesting, as the people who are likely to want to mix and match mods probably have a good overlap with the people who have B9PS installed. separately, the parts are looking very nice!
  7. Equal parts frugalness and ineptitude, with a dash of bad luck.
  8. Gaba_Kerman

    Make a wish... and have it horribly corrupted!

    Granted, you get unlimited power, but only over the individual pixels on your screen I wish for a job at SpaceX
  9. Since 1.6 I've been seeing more frequent random crashes with really no clue where they come from, so I've been spending time since 1.7 chasing exceptions in the KSP.log. Today I found a fix for a TypeLoadException I was getting during startup. I know KSP plugins should target .NET 3.5, but how critical is this? Could this be a source of random crashes or is it just sloppy programming by the modders? What I tracked down is: Decoupler Shroud was compiled against .NET 4.6.1 Dynamic Battery Storage (Near Future Electrical dependency) was compiled against .NET 4.0 Docking Port Sound FX was compiled against 4.5.2 Recompiling locally against .NET 3.5 clears the exception. I found these by downloading the problem mods and checking the project properties in Visual Studio. I double checked the rest of my mods with dotPeek and didn't find any other issues. If a mod reads this: I'm not sure where this topic should go.
  10. Q-ver KSP

    Make a wish... and have it horribly corrupted!

    Granted, you get explosive mouthwatering steamed clams. I wish I had unlimited power.
  11. Mars-Bound Hokie

    Waiter, theres a _____________ in my soup!

    Ah, I was wondering where that kid's shoe ran off to. Waiter, there's soup in my soup.
  12. razark

    Shower thoughts

    Some words should result in capital punishment.
  13. jinnantonix

    High-Occupancy Mun Lander Challenge

    OK, so someone had to do it. 126 command seats <100,000 Kredits Landed at Mun and Minmus https://imgur.com/a/pqkyXJn . Craft file available on request
  14. Maybe making Kerballed rovers more useful too.
  15. Today
  16. I don't play with this mod. But space shuttle from this fashion can enter into the atmosphere
  17. sibaar

    [1.5.1+] Hullcam VDS Continued

    and we love you for it
  18. Some resources for you: This delta-v map is still valid for the stock solar system. This transfer window planner tool helps you plan interplanetary trips. https://alexmoon.github.io/ksp/ Also comes in a mod form. https://spacedock.info/mod/713/Transfer Window Planner As for RSS/RO, I think those are out of scope for this challenge series. Also harder.
  19. I'm having issues with textures on Eve,Laythe and Kerbin is there any fix Im using EVE and Scatter if that has to do anything with it.
  20. dundun93

    Waiter, theres a _____________ in my soup!

    Waiter, please come! theres a.. on my soup!
  21. dundun93

    Really Really Really Tall Building

    5128
  1. Load more activity