Search the Community
Showing results for tags 'how to'.
The search index is currently processing. Current results may not be complete.
-
Hey guys With the latest 1.12.4 update, SQUAD / Private Division decided to introduce an additional launcher to the game which will start up after hitting the "Play" button in Steam instead of launching the game directly. IMO this is rather annoying and doesn't provide any actual benefits, in fact, it actually causes some trouble especially for mods. Since the update, me and others figured out multiple ways to circumvent the launcher which come with their own benefits and drawbacks, so here are a few for you guys to choose from, depending on which solution fits the best for you 1. KSSL (KSP Simple Steam Launcher) Pros: Easy to use You keep all the Steam features like the overlay, game time tracking, etc. Mods will work as usual Cons: Need to be reinstalled if the game ever gets another update or you verify the games file integrity @R-T-B wrote this wrapper which replaces the original executable of the launcher. Simply replace the "LauncherPatcher.exe" provided by them with the one from the stock game and you're already done and ready to go. 2. Change the game launch options (shortcut version) Pros: Resilient to any further game updates Mods will work as usual Cons: Steam features like the overlay and game time tracking don't work anymore Slightly more difficult to setup Steam allows to setup individual launch options for each game, which can be used to redirect the target for the "Play" button in your Steam library. This particular solution by @Gotmachine redirects the button to point to a shortcut, which then again points to the game executable: 3. Change the game launch options (executable version) Pros: Resilient to any further game updates "Purist" solution to keep the game 100% stock Steam features will work as usual Cons: Mods are very likely to break Slightly more difficult to setup So, this was the solution I came up with like an hour after the update but which turned out to be problematic later on. Works in the same way as the previous solution but instead of redirecting the "Play" button to a shortcut, it gets redirected to the games executable: Right click KSP in your Steam Library Click on properties At the bottom of the "General" tab, you will find "Launch Options" and a text field. Write in this text field "FULL GAME PATH TO .EXE FILE" %command% Close the window Profit! for example: The window is not resizable to show the full command but I guess you get it If you are having trouble to find the path to your game executable, you can right click the game in your library -> "Manage" -> "Browse local files". This will open up a window with your game files, showing the path at the top navigation bar. 4. The Kerbal Way (aka jump through three loops to accomplish.... "something") Pros: Mods will work as usual Steam features will work as usual Cons: Fairly janky to setup Not extensively tested A CMD window will be open as long as the game is running This is basically a combination of solution #2 and #3 but instead of redirecting the "Play" button to the game executable or a shortcut of it, it gets redirected to the windows command line (CMD) which then is used to launch the game. Choosing this solutions allows you to eliminate the drawback of missing steam features from solution #2. So, in order to achieve this, you need to follow the instructions from solution #2 but the command in the games launch options needs to be: "PATH TO CMD" %command% /c "start PATH TO SHORTCUT.lnk" The quotation marks are important, as well as using the ".lnk" extension at the end of the shortcuts name, even if it is not visible in your explorer window or part of the name you gave the shortcut. The "PATH TO CMD" should always be the same in windows: c:\Windows\System32\cmd.exe The "/c" will pipe everything in quotation marks after it as a command to the CMD, so we are just telling it to launch the game via the shortcut. In my case, the full command looks like this: "c:\Windows\System32\cmd.exe" %command% /c "start D:\SteamLibrary\steamapps\common\"Kerbal Space Program"\KSP_x64_shortcut.lnk" What about Linux/MacOS??? I dont use neither of those so I can only refer to the post of @Nazalassa : I can't say anything about pros and cons for this solution, not even if it works or details about the execution, sorry. What about other launch options??? Other launch options like "-popupwindow" or "-force-d3d11" should still work as usual for any solution on this list. For solution #2 to #4, you can just add them at the very end of the command, for example: "C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_x64_Steam" %command% -popupwindow or "C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_x64.exe" %command% -popupwindow or "c:\Windows\System32\cmd.exe" %command% /c "start D:\SteamLibrary\steamapps\common\"Kerbal Space Program"\KSP_x64_shortcut.lnk" -popupwindow I hope everyone was able to find a solution which fits bets for their situation but if not, you're always welcome to ask questions right here in the thread. If any other solution comes up to fill up a niche, I'll happy add it to the list, same goes for linux and MacOS versions of the game. Also, any feedback is always welcome
- 49 replies
-
- 21
-
Please could you explain me how to use Kerbal Konstructs and how to build bases with it. I have KK and Kerbin Side installed, but I don't know how to use them. @NHunter please help if you can too.
- 8 replies
-
- 3
-
- advice
- kerbal konstructs
-
(and 2 more)
Tagged with:
-
Hi Kerbonauts! :) When playing KSP, at some point I learned that you can use KAL-1000 to generate infinite thrust and fuel. It was fun at first, but very soon made playing the game non-immersive. If I can go anywhere with ease, it's not a challenging anymore. Taking away the struggle of a gravity-bound flight, you basically defeat the main boss of the game. That is why I want to CLIP the result values of the controller, so cheating is not to be possible. That should regain me will and joy of playing. :)
-
- kal-1000
- controller
-
(and 3 more)
Tagged with:
-
which mods aren't working?
-
Land almost anywhere, with a plane.. How? When you build your plane, put parachutes on the front and back of the plane, on the top of course.. I have landed a 747 on a sloped Mountain, With good Brakes, so you dont go whizzing backwards. Good for them contracts, where you have to land somewhere specific.. When you are near your target.. cut throttle to half, go retrograde, bring your speed down to zero, launch parachutes.. Adjust your Left and Right, A/D , if you need to go forward, just increment your engines with Shift, then X to stop. Float Down. At 1Km your chutes should Open fully.. Making it Easier to navigate. Align your Plane with the Angle of the ground.. Upon Touchdown. Apply the Brakes.. And Hopefully You have Succeeded. Congratulations.. Very difficult to Impossible on slopes more than 45 degrees.. Parachutes.. Thats how I land my Planes.. Because I am Useless at trying to land, even on the runway at KSC.. Practise makes perfect, unless your like me, and no amount of trying will do it.. So Parachutes are your way to go.. BTW. I played a game, years ago.. . Jump, Jump, Jump, into the Lava.. Jump, Jump, into the Lava, Jump into the Lava, Etc times by 1000.. Jump, Jump, Jump, guess what? Yep, Straight into the Lava.. Three weeks into the game.. The next door neighbours teenager.. I asked him, if he could get me past the Lava Lake, with appearing and disappearing Stepping Stones.. One Go.... WOT... He got across the Lava Lake first time... Anyways, Have FUN.. KSP, is Amazing..
- 2 replies
-
- how to
- land plane
-
(and 3 more)
Tagged with:
-
How to go from Explosions on the Launchpad to an Eve Crew lander
Guest posted a topic in KSP1 Tutorials
One of the most interesting things I will ever see on a youtube video by Stratzenblitz or Matt Lowne or Shadow Zone is that in the comments I see people saying "and all I can do is land on the mun" or "I can't even get to orbit." And at one point I felt exactly the same, I felt like no matter how much I did I would never get there. This is my words to give to people on how to get from Explosions to success: When I started playing KSP I got the inspiration to do so via Matt Lowne's amazing SSTOs. I was amazed by them, I dreamed about making my own fleet of SSTOs making cool names and going all over the Kerbol system! And that was the burning point to via a Christmas sale, grab a copy of KSP via steam and start playing. I fired up the game, got ready to go, AND then I was like... UM... HOW DO YOU BUILD ROCKET? Google was the ally of the day and I was able to find out the basics to add parts and delete them too. So I built my first rocket "The Cheetah!" It had an SRB, a command capsule, and a parachute... It didn't make it far. And at that point there was that part of me saying that I was going to go down a bigger loophole then what I have thought. And the next following rockets fell to the same results, now this is where I start to just look at the tutorials. And they helped quite a bit. But it didn't get me into orbit. And I was starting hours of frustration, I didn't realize at the time that at that point this is where most will throw the towel and stop. On the first day after playing for an unhealthy 15 hours, I did it. with 8 SRBs and a big first and second stage, I was able to out of control get into a high elliptical orbit. It was the worst rocket you could have thought, it had no control, barely worked, and well... sucked. I had screenshots but lost them but here is the first thing that you should try doing if you get stuck getting into orbit. ->->->->->->->->->->->->->->->->->->->->->->->-> 1. Evaluate Some of the biggest things that we humans fail to do is to evaluate on what just happened. And that is something that helped make progress was to look at went wrong. I remember at one point where I was looking at the prograde and realize that is what I am using to know where I am going. It's important to observe the failing points of any craft. I still do this today, my first SSTO is a good example and you can watch that here and see how many revisions I made . I still see this problem all over the place and am guilty of the same thing. If you go deep into my forum activity you can find some posts I made about trying to do the Expedition Dres mission THAT STILL HAUNTS ME TO THIS DAY. ->->->->->->->->->->->->->->->->->->->->->->->-> Back to the timeline, ok I got to orbit, but it was a sucky one. so I decided the best way to go was to make a science save and start learning how to fly, this was a starting point of when I wanted to learn parts of KSP better. I had a very old video but I don't want to share it. But something I did wrong here was that I didn't do much that help make progress. But I discovered something when I went back on track for getting into the Mun ->->->->->->->->->->->->->->->->->->->->->->->-> 2. Tutorials help, but won't do all the work I found that tutorials on how to get to orbit and how to get to the Mun where very useful (like how I used ShadowZone's tutorial [and was actually how I discovered SZ].) And one thing I realized is that when you use all tutorials, they help at first, but using them in the long run actually puts you down. Because I learned orbital mechanics easier from the tutorials but I also copied the designs, making all the learning possibilities little to none. The latest I felt like this was when I was learning to fly and Eve lander, it took me over a year and that was because I wasn't really experimenting with designs (and some cheats that where useful wheren't out.) ->->->->->->->->->->->->->->->->->->->->->->->-> So back to the story. Four days after I got the game it finally happened after two attempts at landing: This is the only screenshot I still have of it today. It was an amazing milestone, and the crazy part was I did it on vacation. But there was some kind of nerve I had with it. To get here, I lost a kerbal, and I didn't keep my quicksaves so he was gone. I felt bad about it at first tbh. one of the easiest things that you can mistakenly do is to get sidetracked. I feel like I lost my progress from here on out. I tried making taller and wider and better landers after this design was used 3 times, but I never got it to work. It would take me four months to do another Mun crew mission successfully. And this is where I feel like it's important to realize about one of the worst things you can say to yourself: I can't do it. That's what I told myself every single time I tried. And one time I remember telling myself okay this is the day. And after trying one hour trying to land on the mun I said it was impossible and only if you are lucky. so two months later after playing around in LKO, I decided I should look at another destination. Minmus. I did it! I was so excited Unfortunately I tried again with the same design on the Mun with less spectacular results: ALSO I RECORDED VIDEOS AT THIS TIME I did a new generation of landers which improved on what I learned (which was me implying rule 1.) And for the first time in almost three months I finally did it again after trying twice. At this point I started finally doing celestial bodies again in KSP. But then I met my challenge. Duna! This was the definition of failure for me. but it leads to the next point ->->->->->->->->->->->->->->->->->->->->->->->-> 3. Failure is the only way sometimes One of the most frustrating things that a player can experience in KSP is failure. Generally failure is frustrating especially if you put hours of work into it. I felt exactly like this when doing a Duna mission, before my first Duna mission I had around 5 failure attempts. All of which I put tons of effort into. Something I didn't realize at the time is that you learn from each without noticing and here is a good video of why Sometimes failures will cause me to cancel missions like my Comet Camp but sprout into new ones of what I learned which lead me to make Vall Mobile and Private Tylo. ->->->->->->->->->->->->->->->->->->->->->->->-> But after a few attempts of trial and error I finally made it. Dux was my first successful Interplanetary lander. At around 6:00 PM EDT on March 21st, it happened Also I would love for someone to revist this site here is the link to info about it. This is the point of where I finally realized nothing is impossible. Anything is possible. At this point it's where I made a quest to explore Kerbol system for my ownself. I later did an Ike mission and after that, I joined the Forums... which is kinda cool. I want to timeskip my first return of crew, my first base, and some other things to skip to a mission I have never really revealed to the public. Huoxing: Huoxing-1 became my literal nightmare for crew missions. I call it: the mission that never came back. Because this mission had one final problem, return to Kerbin. And I was able to do everything great from this point. Just that one return to Kerbin problem, where I didn't think about aerobraking and thought I could circulize. I didn't have enough fuel and a year later if I only realized I could have just aerobraked I would have completed the mission. Huoxing was at the time... fear to try again. ->->->->->->->->->->->->->->->->->->->->->->->-> 4. If you are scared to try, you won't fly I was scared to do a crew mission just because of that one failure. Never wanted to try again for a while. Which is important to highlight that if you never want to try again, you won't. sometimes you just have to take that risk and hope that it works out. ->->->->->->->->->->->->->->->->->->->->->->->-> So I decide to take it easy and go with probes. I am going to skip a lot of the probes but what I learned from flying to other celestial bodies in KSP was Being adaptive is key to flying successfully Problem solving is a good ability to have when unprecedented problems arise, thinking outside the box can save a mission. Eventually these probe missions taught me those ideals. So I took up the crew challenge again and wasn't that hard to do. But when I got to late game it got hard. Laythe crew mission pushed my limits. ->->->->->->->->->->->->->->->->->->->->->->->-> 5. If it don't work, fix it something that I learned from Laythe Crew mission (and this was before I used cheats to test.) Was that I was stubborn a lot to try a new lander design, and hope for the best with the current one. I then finally thought of possible ideas and after flying three whole missions to laythe, I finally got a lander that worked. I tried 4 times with number one, 17 with two, and once with three. Now with more current cheats I am able to change my lander a lot faster (which made Eve Crew Lander mission easier.) ->->->->->->->->->->->->->->->->->->->->->->->-> Eventually I got that to work but the biggest challenge yet was by far Eve Crew Mission. It took me another whole year of KSP to successfully do it. Which is honestly probably the hardest process I took on over September 2019 through August 2020, relearning KSP. I tried to learn better efficiency, better launch profiles, d/V savers, and of course no more clipping habits. One of the hardest things you can do in KSP is to relearn how to play it. I had redeveloped how I played KSP and abandoned all my inefficient habits. So the last tip I have for new players or players that are stuck is: ->->->->->->->->->->->->->->->->->->->->->->->-> 6. Small things make big missions I started last year doing The Doodling Adventures which focused on making more efficient spacecraft and make them WAY smaller. I learned new tricks, got better, and even made memories. I still think the craziest one to me at least was the Moho Lander which surprisingly took a whole lot less than I previously thought. Starting with small missions to develop better skills is important. ->->->->->->->->->->->->->->->->->->->->->->->-> And that's where I am going to leave it off, I hope this tutorial and guide helped you with your current issue or if you just started. Thank you and I spent quick a long time typing this so I think I am going to go rest now -
So How Do You Make A Mod? I Know You Need Unity And A IDE So I Have Unity And Visual Studio 2019 Installed