Search the Community

When I control a craft I'm seldom interested in the "Display Staging" info (lower left). I want to see the "Maneuver Mode" view, with info about apsides, inclination etc. Similarly, I'm most comfortable with UT rather than MET "Time Mode" (upper left). It's getting very old having to toggle these views Every. Single. Time. I switch between craft. Is there some way to make these settings stick? (I'm no stranger to manually editing files if that's what it takes.) (I have an annotated screenshot that shows what I'm talking about, but there doesn't seem to be any way to attach an image to a post? Just "Insert image from URL"?)

Better Specialization Settings v0.0.4 @ 2019-05-22 This mod provides a bunch of settings to allow finer customization of gameplay revolving around crew specializations (i.e. Pilot, Engineer, Scientist). The bulk of its functionality is focused on making crew specializations more relevant and meaningful in sandbox and science sandbox play. There are also settings to allow customization of the level requirements needed to perform certain tasks in career mode. Oversimplified tl;dr: Make autopilot/SAS require a pilot in science/sandbox Make wheel/leg repairs require an engineer in science/sandbox Allow adjusting engineer level required for wheel/leg repairs in career Make parachute repacking require an engineer in science/sandbox Allow adjusting engineer level required for parachute repacking in career ~ ~ ~ ~ ~ Preface: stock KSP settings In stock KSP, the primary setting affecting gameplay behavior related to crew specializations is the "Enable Kerbal Experience" setting found under "Advanced" in the difficulty options for new games: In Career mode, this setting is turned on by default, which means that kerbals need to gain experience in order to level up and unlock more abilities, such as different SAS stability modes for pilots, or wheel repair skills for engineers. In the Science or Sandbox modes, it is turned off by default, and all kerbals start with their level already maxed out. This option can be changed at the start of a new game (but not for existing saves), which means it is actually possible to play a Career game without having to level up your kerbals, or play Science or Sandbox modes with the experience system turned on. However, this setting is very coarse-grained and has other side effects. Consider: When the setting is on, certain tasks can only be performed by specialized kerbals of a particular skill level, e.g. a pilot of particular skill level is needed to access various SAS stability modes like normal/anti-normal and radial/anti-radial. But with the setting turned off, many of these tasks can suddenly be performed by all kerbals regardless of specialization. Scientists and engineers can fly vessels with full SAS and all stability mode options. Pilots and scientists can repack parachutes and perform repairs. You can do almost everything with just a scientist, etc. This behavior cheapens the specializations, so the specialization type of a crew member does not matter as much anymore. And because this is the default setting for Science and Sandbox games, it can contribute to the gameplay in those modes feeling more shallow. Now, I'm not actually opposed to having an "easy mode" option where the skill levels and specializations do not matter very much. The real problem here is that there is a lack of a middle ground between the "on" and "off" settings. Why can't we have a setting where we don't have to deal with the XP and leveling up aspects, but where the different specializations are still meaningful in terms of needing certain types of crew to fill different roles and do different tasks? This mod was born to address that flaw. ~ ~ ~ ~ ~ Autopilot/SAS For players with mods that add other crew specialization types: when "pilot" is mentioned here, it includes any modded crew specialization that has the "Autopilot" skill. Stock behavior: If Enable Kerbal Experience is on, SAS and the stability modes available to a vessel depends on having a command module with a pilot of adequate skill level for crewed vessels. For uncrewed probes, a part with the required SAS service level is needed. (SAS service level is analogous to pilot experience level: cheaper, simpler probe cores have lower level than the more expensive and advanced models. For example, the QBE is equivalent to a Level 0 pilot and only has stability assist, whereas an OKTO2 is equal to a Level 2 pilot.) For KSP versions before KSP 1.6, if experience system is turned off, then none of the above crew skill requirements and part SAS service level requirements are respected. SAS and all stability modes are available with any type of crewmember in a command module, or any probe core. This actually makes it pointless to use more expensive, "better" probe cores when a cheaper one would still give full SAS. To fix the issue, since KSP 1.6+ an additional option called "All SAS Modes on all probes" is available in the "Advanced" tab of the difficulty options when the game mode is Science or Sandbox: If the option is turned on, the behavior is the same as having experience system turned off in earlier versions, as already described above. If it is turned off, then the intended behavior is for any type of crewmember to be able to provide all SAS stability modes on crewed vessels, but uncrewed probes would still need to have a part with the required SAS service level. However, testing has shown that when "All SAS Modes on all probes" is off, SAS availability for crewed vessels actually depends on having a crewmember with either Autopilot Skill, Repair Skill, or Science Skill, i.e. these are being used as a proxy to test if there is a Pilot, Engineer, or Scientist on board the vessel. This works for stock KSP, but if you use any mod that adds crew specialization types that don't have any of these skills, then it is no longer true that "any crewmember" is able to give full SAS control. What this mod provides: If "Enable Kerbal Experience" is on, stock behavior as described in the previous section will be used. Full requirements are imposed for SAS availability. If "Enable Kerbal Experience" is off, but "All SAS Modes on all probes" is on, stock behavior will be used: none of the SAS requirements are imposed. For backwards compatibility, this mod adds the "All SAS Modes on all probes" option to older KSP versions before KSP 1.6. This option is located under the "Better Specialization Settings" tab of difficulty settings dialog, rather than under the stock "Advanced" tab. If both "Enable Kerbal Experience" and "All SAS Modes on all probes" settings are off, then custom behavior of this mod will be used. This is governed by a setting called "Require pilot for SAS": (KSP 1.6+) (KSP < 1.6) When "Require pilot for SAS" is on, SAS and the stability modes available to a crewed vessel will depend on having a command module with a pilot. Crew level is irrelevant as it is always maxed out. Other crew types will not be able to provide SAS. Uncrewed probes will need to have a part with the required SAS service level. If the setting is off, then any type of crewmember will be able to provide all SAS stability modes on crewed vessels. Uncrewed probes will still need to have a part with the required SAS service level. This is a bugfixed version of the KSP 1.6+ behavior when "All SAS Modes on all probes" is off, in that truly (almost) all crew types will provide SAS. (Tourists, and the modded specialization type "Civilian" don't count.) ~ ~ ~ ~ ~ Wheel/leg repair For players with mods that add other crew specialization types: when "engineer" is mentioned here, it includes any modded crew specialization that has the "Repair" skill. Stock behavior: If Enable Kerbal Experience is on, an engineer of level 3 or above will be required to repair damaged wheels and landing legs. Much, much older versions of KSP needed only level 2 to repair legs, but that has not been the case since around KSP 1.1 when the old ModuleWheel, ModuleLandingLeg and ModuleLandingGear were replaced by ModuleWheelBase and its submodules. If Enable Kerbal Experience is off, any type of crewmember can perform repairs. What this mod provides: If Enable Kerbal Experience is off, an option "Require engineer to repair legs/wheels" is available. When this option is on, it will limit the ability to perform repairs to engineers only. Turning this option off will cause stock behavior to be used instead. If Enable Kerbal Experience is on, an option is provided to override the engineer level required to perform repairs. If this option is not used, then the stock reqirement of level 3 will be followed. ~ ~ ~ ~ ~ Parachute repacking For players with mods that add other crew specialization types: when "engineer" is mentioned here, it includes any modded crew specialization that has the "Repair" skill. Stock behavior: If Enable Kerbal Experience is on, an engineer of level 1 or above will be required to repack parachutes. If Enable Kerbal Experience is off, any type of crewmember can repack parachutes. What this mod provides: If Enable Kerbal Experience is off, an option "Require engineer to repack parachutes" is available. When this option is on, it will limit the ability to repack parachutes to engineers only. Turning this option off will cause stock behavior to be used instead. If Enable Kerbal Experience is on, an option is provided to override the engineer level required to repack parachutes. If this option is not used, then the stock reqirement of level 1 will be followed. ~ ~ ~ ~ ~ License All rights reserved. Download Better Specialization Settings v0.0.4 for KSP 1.7.x (backward compatible with KSP 1.6.x - 1.3.x) Caution: Dev build. Backup your saves before proceeding. Requires Module Manager (please obtain separately.) Download includes the Harmony library, version 1.2.0.1. See this comment for explanation. Installation: Delete older version, if any. Place contents of GameData into your installation's GameData folder. Source: GitHub Changelog: v0.0.4 ~ 2019-05-22 ~ KSP 1.7.x - 1.3.x Dev Build - Harmony 1.2.0.1 included Add restrict parachute repacking to engineers Add adjust level requirement for parachute repacking Fix bug in engineer (repair skill) requirement check for wheel repair v0.0.3 ~ 2019-05-13 ~ KSP 1.7.x - 1.3.x Dev Build - Harmony 1.2.0.1 included - Add restrict wheel/leg repair to engineers - Add adjust level requirement for wheel/leg repair - Rename mod due to feature for career mode - Refactored code v0.0.2 ~ 2019-04-17 ~ KSP 1.7.x - 1.3.x Dev Build - Harmony 1.2.0.1 included - Refactored code, improved robustness, optimizations - Backward compatibility for KSP < 1.6.x v0.0.1 ~ 2019-04-15 ~ KSP 1.7.x - 1.6.x Dev Build - Harmony 1.2.0.1 included - Prototype autopilot/SAS restricted to pilots

As straightforward as the title of this post, my shadows are at a low resolution whilst my settings are maxed out. It first seemed to happen when i changed my graphics card (from a GTX 1050 to an RTX 2060) so i think it might have to do something with that. I hope someone knows what's happening Here's an image of the situation: My settings (tried upping shadow cascades in the settings.cfg): Technical info KSP: 1.11.2 GPU: Nvidia RTX 2060 CPU: Intel Core i5-7400 RAM: 16GB

I have a problem with the joystick axis assignment. I have 2 joysticks but it does not allow me to map them. Let me explain better. When I go to configure the joystick the pitch axis for example, it recognises joy1.0 (axis 0 joystick one), but when I click on accept it gives me Joy0.0, so when I enter the KSP game it does not see the joystick. Same thing with joystick 2... it always accepts it as joy0.0. The problem is similar to this: Is it possible that this problem has not been solved since 2016? Do you have any suggestions?

th

so, where can i set minimum and maximum for an axis, even wiggling the axis did not set the min-max, resulting in max-min-step-max behaviour. you cant test the controls in the settings, and you have to go all the way in to flight to test them, then just to find they were not working right. edit: why does alt-tabbing out of the program in win 10 64-bit make it white-hangup, crash?

I tend to run fairly heavily modded games, as ive exhausted the stock game and i need more to enjoy it and challenge me. However, with modded installs i tend to run into performance issues sometimes. I have a pretty decent pc, ryzen 5 2600, 2070 super, 16gb 3200mhz ram. With the stock game i can run it at max settings over 100 fps, but with modded installs it tends to to down, which is fine, but not as low as it is sometimes. With ksp being pretty cpu dominant, and single threaded at that, i imagine graphics mods wont affect me that much? As i have a powerful gpu with 8gb vram, and 16gb ram should be more than enough too? Im using ksp 1.8.1 at the moment, as i want to play with sigma dimensions. I was using 6.4x scale with 9.6x orbits. I was also using astronomers visual pack with the 8k textures. About 150 mods total installed with ckan. I was getting 1 fps. Not even 2. I had a few guesses as to what it could be, maybe the 8k textures, or the ground scatter being scaled as well, which was weird. But if i went eva, i got 50 fps, but not inside the ship? I downgraded to 4k textures for avp, uninstalled my skybox mod, and fixed the ground scatter, and its at 20fps roughly now, but thay may well be just cos i restarted the game. Using alt f12 and looking at the performance tab, it looks like im only using 4gb ram, with 5gb allocated? I installed this mod called heap padder, as i thought it would improve performance. I havent uninstalled it yet, but maybe thats causing a bug? All i really want is a general idea of what kind of mods affect performance the most. Part mods, plugins etc. Sorry for rambling but its getting on my nerves especially with my pc being more than up to par.

When I load up KSP and go to my save it shows the menu looking like this: At first I thought it was a sunrise thing so I time warped to noon: I also had problems in the MK-IV parts where it was completely black but didn't get screenshots of that Here are my settings for this game: I don't believe that it is a mod problem, just a settings problem.

I only have 8 gigabytes of RAM, and KSP uses up 7.5 gigabytes normally. Whenever I build big ships or go into high physics warp, it starts having to swap about 1 gigabyte, which really lags the game. Are there any settings in KSP that I can adjust that could potentially decrease the RAM usage? I have one mod, Restock. Edit: P.S. I am on macOS.

I'm doing a KSP cinematic that requires a framerate of 24 frames per second. Can I get this framerate by editing the config file? Also, using capture software doesn't apply because I have a motion blur mod installed, and the blur will look wrong if the framerate is too high.

I'm doing a cinematic that required 24 frames per second, and I have a motion blur mod installed. The blur is therefore too "short" when capturing the game running at a higher framerate. Is it possible to set the limit this low?

So, I've got the 1.8 update fresh. I've landed on the Mun and not been able to see any difference. Anyone know how I get to the new textures? One more thing: My altimeter is completely broken. It's not displaying a thing. I've had to track my altitudes from the map screen, but it gets pretty darn annoying after a bit.

Hi. I recently bought game in Steam and i have problem - my graphic settings not saved. I restart the game and the settings go wrong. How to fix it? Version 1.8.0.2686

HI, this is starting to really get on my nerves as I am trying to learn interplanetary transfers now. Is there a setting I am missing or mod maybe that can hide all the useless text when I am trying to plan a maneuver?!? I feel like I got to be missing something really obvious. Thanks in advance.

My kerbals don't wear their helmets in IVA, and I wonder if there is a way to fix that.

Can someone link the RAPIER settings? I was messing around and messed up the gimbal range and I don't know how to exactly did it.

In my Orbit world [production], I currently have 283 flights in progress. The quicksaves are taking longer (naturally) and I have to monitor memory (only ~8GB) and restart KSP when memory usage heads toward swap territory (running KSP 1.3.1 on Linux Mint 18.2). Switching between vessels seems to be what grows memory -- not so much operating them. What I'd really like to know is: what's the practical upper limit to # of flights one can have (depending upon memory available) what's the biggest number anyone has running? I'm simply doing some forward planning here. Will I eventually need to ration flights? My (old) motherboard has its max memory already so, clearly, a new computer (yay!) is in the future. I note that the debris clean-up limit goes up to 10,000: can this mean that 10K vessels is actually a possibility??

Well, once again my install of KSP corrupted... The physics are whacked again and all craft pull to the right for no reason. A fresh install solved the problem (again) and it continues to work fine after putting my mods back (again). But now I've gotta redo all my game bindings and various settings. I have multiple installs of the game and was wondering which file(s) I might be able to copy across to the new install to bring back all of my graphics, game, joystick, and key binding settings? Anyone know which file(s) I would need to copy across?

I'm seeing the Woomerang Launch Site even tho "Allow other Launchsites" is off. Also getting a comm net signal from there even tho "Enable Extra Groundstations" is off. I might try removing my mods and see if it's still happens. Don't have anything that touches comms tho I think. Just wondering if anyone else noticed it. A quick google search turned up nothing. Career game, KSP version 1.1.4.2 with Making History dlc

Does checkboxes' clicking in the Difficulty settings send some GameEvents ? I move some code (which doesn't need to be updated every tick) from LateUpdate() to the functions, called by events, and it almost works with OnGameSettingsApplied() and some flight-scene-events. But I noticed, what if you open difficulty settings while in the flight-scene, and then click some checkboxes, LateUpdate() on-the-fly take this new values, so I need GameEvents for this (something like OnGameSettingsChanges(), but it isn't there) or how to limit flight-scene to take only saved settings, after OnGameSettingsApplied event (I am using HighLogic.CurrentGame.Parameters.CustomParams<modSettings>().setting_name, and they are taken on-the-fly)

Hi all. I'have been playing a lot this game (1000+ hours) and i'm having a lot of fun, i already reached almost all the planets apart from moho and eloo and downloaded a crapton of mods. However a week ago i have probably messed up something in the settings and now i can't see the distance to the target and stuff like that, and that's make docking very hard, especially on the dark side of the planets ( and it's even harder with eve+scatterer) where you can't see anything. Especially where is the other ship that you are trying to dock with ( lukly right now thanks to Kerbal Alarm Clock i can set very accurate rendezvous up t0 5 meters of distance). My question is; what is the setting that i have to change to have the distance back? Because i can't seem to find it Thanks to everyone who will help

Looking through the settings.cfg I spotted two items I'm not clear on the function of... } TOGGLE_SPACENAV_FLIGHT_CONTROL { primary = ScrollLock secondary = None group = 0 modeMask = -1 modeMaskSec = -1 } TOGGLE_SPACENAV_ROLL_LOCK { primary = None secondary = None group = 0 modeMask = -1 modeMaskSec = -1 } What are these? (I'm guessing I already know but am not making the right mental connection somehow...)

If I try to change my graphics settings from the normal ones, it doesn't work. The "Apply" and "Accept" buttons don't respond to any clicks. If I click "Cancel" and go back into the graphics settings, they'll still be the default ones Yes, I have seen the other forum posts about this. Seemingly, their solution doesn't work. Maybe I'm doing it wrong...? Here's the output log: https://drive.google.com/open?id=17CuTCIQCiyb8wlMigqA9vPX6i8MryEAF Thanks for any help!

Hi.. i want to change my graphics setting in in KSP but it will not apply. i can click the accept and apply button but noting happens. i am using KSP version 1.3.1 without any mods and i have also recently re-installed windows 10 on my PC. Also, i can't find settings.cfg in my game file. here is the output_log Thanks in advance!

I change BypassEntryPurchaseAfterResearch to false in the save_file and parts from new-opened Tech tree node are unpurchased as expected. How make all old parts unpurchased too? There is that unpurchased/purchased params for every part at save-file?