sal_vager

This is more of a Gameplay Question so it's moved to the relevant forum

Nothing obvious there, maybe the output_log.txt in KSP_Data has some info, if the log is being spammed with entries it may explain it. Other than that maybe try with as much turned off as possible, and whitelisting the KSP.exe in your antivirus program, not that I can even see one in your list, but if you are using an AV it may be scanning all the KSP files when you try to start it.

Hi mrmcp1, have you tried two finger scrolling or edge scrolling with your touchpad? It is likely that your old laptop just sent the "mouse scroll" command to KSP, as KSP doesn't actually have support for pinch-to-zoom, just for mousewheel scrolling. Your new laptop may have an option to use pinch-to-zoom as a regular scroll in its options.

Actually it might be, although I agree it's not the same behavior as from 1.0.4, a lot was changed with radiators so we can't expect them to be the same. The static radiators, like the folding radiators now, will actually draw extra heat from hot parts rather than just match their heat, allowing them to actively cool, or refrigerate, the vessel instead of just getting as hot as the hottest part. Also, the folding radiators can draw heat from anywhere on the vessel but only when unfolded, and they consume E/C while they do so. The static radiators are "on" all the time, don't need E/C, but can now actively draw heat from their parent part, and from the parent of that part, and all its children, basically two parts in every "direction". So they can suck up heat from the fairing directly if they are two parts away, and even if they aren't, they can draw heat from other parts as it conducts in. They won't overheat though, all radiators have a saturation point where they can't take in any more heat, this is so they won't explode. But there is a bug here, or more accurately an omission, in that the radiators are not disabled when checked for occlusion by fairings or cargobays, some other parts aren't either such as the fixed solar panel and the rover wheels. So they will continue to function even when they and other parts around them are occluded. Other aspects of the radiators such as exposure to airflow will be blocked while stowed, so they won't contribute to drag, they'll just be sucking in heat when you don't expect them to. Also if you could add this to the bug tracker that'd be great

There's two throttle bindings, normal and incremental, so try the other if one doesn't work for you, also when changing stick modes (or sticks completely) restart KSP with the new stick/mode (this may need a second restart) so KSP detects it at startup, KSP does not have any hotswap ability with controllers.

Hi MAFman, please try again after starting the KSP.exe directly Also, please make sure you are not using any addons.

This has happened for gears forever, this is new though, can you please write this up on the bug tracker Alshain ?

Hi kingOFspace, last I looked the experiments were only biome specific when landed, and there's only a few levels for flying and space when using them, while the crew and eva reports take the biomes into account. You can see this too in the SienceDefs.cfg in GameData/Squad/Resources, but there's a ton of spoilers in there. The "missing" file is usually the settings.cfg, as Steam detects it as something it shouldn't overwrite after the player has changed it, the error message is unfortunate though, more info here.

Many aero parts were moved so you will need to re-research them.

Also different intakes have different static "suck", so if you're making a VTOL you will want the nacelles or precoolers, as they draw the most air. But as skepticon says it helps to be moving, air is now calculated by intake area, speed, direction (less air at an angle to the flow) and pressure.

It parses particularly like a peeve PercyPrune, and as all wheels are being replaced in 1.1 (it's been in the devnotes for a while now...) wheel issues are deferred until then

Hi Xasin, KSP is still a bit ropey when it comes to controllers of all kinds, all I can suggest is that you restart KSP with the controller attached until it is detected (usually on 2nd restart). If you bind any axis or buttons and start KSP without the controller attached they can show as "Not found" when you later plug it back in, so again just restart KSP once or twice with the controller in and it'll find it. Unfortunately KSP doesn't check for controllers at all after it's started, so plugging in after starting KSP, or hot swapping controllers just doesn't work. Let me know if this helps.

Yep, fixed, thanks to you luizopiloto

Hopefully KSP 1.1 / Unity5 fixes this for good, the UI is all new. That'd be why any reports on this aren't considered high at the present time, as all UI work is deferred. It's also difficult to reproduce as it seems to be hardware/driver specific, but Apple doesn't seem to make OSX drivers available. honkbert, please let us know if the workarounds that max_42 and smjjames mention work for you.

The trouble here is this only affects a few people, for example I can't get this effect at any resolution I try, and I'm using an Nvidia GTX 650 with the nvidia-352 driver. So can you please provide more information such as the exact driver you are using, and whether this issue persists when changing the resolution back or after deleting the settings.cfg

The trouble is that most software is installed, so the paths the program can use are set in the Windows registry and you are given a shortcut in the menu to start the program. If you move most of these programs out of their install folder, such as from Program Files to the Desktop, they can fail to work correctly because they ask the registry for the absolute path to where their files are, but because they were moved they can't find them. KSP from Steam and from GoG have an installer and provide a shortcut in your menu, but both of these are based on the store version of KSP that is simply unzipped to a location, if you move these versions of KSP from their install folder they will still work because they look for files relative to themselves, and don't need to ask the registry, but they also can't find their files if started from some other folder. This also happens with other programs that aren't installed, they expect to find files relative to where they were started so you're usually asked to start the program.exe directly. This is one reason why installers exist, as most people don't mess with their installed files, just use the shortcut in the menu and never know that this issue exists. Users of mobile applications will run into this from time to time, though usually they just use the program.exe anyway. As for the Dove, there were jet engine changes and the Dove is a spaceplane so it'd not be much use if it couldn't take some heat, as for KER, please make sure your mods are up to date, and don't rule out bugs in the mods as well.

Yeah, well spotted, though hopefully the effect is small as the lift, drag and CoM of the fairing resets to the fairing base when staged, so while the bodymass (that's the cyan line) looks to be offset incorrectly the force should be small, and dropping as air density decreases.

Also please see here, it was stickied quite prominently, basically the launcher will not update KSP.

Okay, yeah I have never seen that, that is very strange indeed :/ Hopefully someone here has seen it.

Planes in KSP do pull to the side a bit, some more than others, this goes back a long way and it's why we have stuff like SAS. Can you upload the craft please, maybe I can help reduce the effect.

Maybe it would, as this doesn't sound like something I have seen before, and maybe someone else has seen it.

Not seeing anything obvious, are you overclocking at all ?

Can you screenshot your taskmanager processes list, maybe something is conflicting. I know that KSP is really sensitive to overclocking, and something called PrecisionX is making it crash.

Yeah, or worked around, either way it's not a problem for you

Okay, looks like the fallback shader is on, it's rubbish so I recommend not using it. And the graphics driver does look a little old, your dxdiag says you have 34752, current is 35891. Other than that it looks fine, so maybe try the new driver and see how it goes, don't forget to reboot!