To begin, I apologize in advance for any errors I make in this post; I only just joined the forum on account of the problem I've encountered. KSP Version: 1.0.4.861 System Specs: intel core i5 4300-U CPU @ 1.90 GHz 2.50 GHz., 800 GB RAM, 64-bit op. system, x64-based processor, Windows 8.1 Installation: Clean Description: I play on a Surface Pro 3, through Steam. I acquired the SP3 about one week ago. The first signs of the problem I've encountered appeared yesterday as I was completing a 'collect surface sample/EVA report' contract. To complete the mission, I flew two kerbals across the ocean east of the space center and landed on the west coast of the next continent over. The overseas trip took about ten minutes of real time and no apparent issues arose. After landing, I took Valentina on EVA to collect the samples. During these missions, I've started quicksaving before EVA because whenever my kerbals fall from a cockpit onto the ground, they clip through the ground as they stand up and die in a puff of smoke. On this particular mission, Val accidentally fell, clipped, and died, so I reloaded the quicksave. Here is where things started going wrong. After holding down the quickload key, the screen cut to the dark grey background of the game (as it always does for an instant when loading a save), and stayed on it. I initially thought the save hadn't loaded (not holding the key down long enough, perhaps) but holding it again only produced the 'hold down to quickload save' line for an instant before it disappeared, not changing anything. Moving the cursor to the top right corner of the screen produced the highlighted electric charge/fuel/oxidizer info for an even shorter instant, leading me to suspect the game had loaded and the screen was just stuck. I paused the game, but was unable to return to the station. At the top-center of the screen, the 'retrieve vessel' and 'return to station' dropdown buttons were not present, nor was the abort button. The main module (I'll call it that) to which these three buttons were connected appeared and disappeared like the fuel and mission info icons in the top-right corner. Seeing no alternative, I forced the game to close, then reloaded it. Since I had quicksaved at the site of the 'freeze', I simply selected that vessel from the tracking station and found myself where I would have been had the quickload worked properly. With one problem: the kerbals were now moving in slow motion. There was no lag during the walking/running/jumping/etc. animations, but the animations themselves were significantly slower. I managed to return Val to the ship and recovered it, but the animation bug has persisted ever since. Now for the throttle issue. Earlier today, I attempted to use a Logitech Wingman Attack 2 Joystick (around a decade old) to control aero/space planes. At this point I had not EVA'd since the mission described above, and didn't know the animation bug was still present. Anyhow, I set up the joystick by inputting controls for pitch, roll, and yaw. However, I also input secondary key bindings (on the joystick) for raising/lowering the throttle. I immediately went to test the new controls in-game. The controls didn't work well anymore. Specifically, the two buttons on the stick that now raised/lowered the throttle only a tiny degree, as if they were only being tapped lightly. I tried the pitch/roll/yaw, but found they were similarly slow. Take note, the response time was correct; there was no lag on any controls. For example, pitching a plane as high as I could on the stick only produced a slight increase in pitch in-game, with no discernible lag or delay. Frustrated, I reverted back to the default keyboard controls, only to find the slowness was still present. The throttle was also slow, even when shift/control were used. I closed the game, unplugged the joystick, and have not used it again since. I have been trying to correct the problems of slowed controls, throttle, and kerbals. They are present in old and new save files. Manually resetting all inputs in the settings had no effect. Deleting the game files and forcing it to be reinstalled on Steam with all default settings (including inputs) also had no effect. Reducing graphics, rendering, and resolution had no effect. It affects all kerbals and vehicles. I do not know to what extent, if any, the two incidents described above are related, so I have included both of them. I sincerely apologize for the wall of text, but I honestly don't understand these problems or how to fix them, so I've mentioned everything that might be relevant. Thank you for any help you may be able to afford me!
