liquidhand

I just updated KSP to v1.1.2 and the controller name is now listed as "xbox 360 for windows", but unfortunately the real problem I'm having didn't get fixed. I did some more testing and discovered, if the kerbal's movement gets locked in one axis from trying the analog control, if I press the "orient to view" button it seems to fix keyboard control. At least sometimes. A couple times when I pressed the "orient to view" button it seemed to lock the kerbal into spinning around, but pressing "orient to view" again restored normal movement with the keyboard. Weird.

That's my settings.cfg from v1.1. I didn't have any other version installed. Tried that and the controller is still listed with that name in the newly generated settings.cfg. The controller works fine if I bind it for any other actions in any of the other controller categories. The problem only occurs when any of the pitch, yaw, or roll under the kerbal control section is bound to an analog axis. I can use the analog controls just fine for flight or docking or during ground vehicle control. It's only when binding the pitch, yaw, or roll for kerbal control that the problem happens.

I just added my settings.cfg file to the other log files at the top in the original post.

I happened to find a similar bug report in the bug tracker: http://bugs.kerbalspaceprogram.com/issues/4899 Unfortunately it's a year old and still marked as new. It doesn't seem like anyone's looked at it yet.

I've noticed this as well. Weird scrolling, saw-tooth shadows. clean install v 1.1 GOG version No mods Windows 10 64-bit intel i5-4690 8 GB RAM AMD Radeon r9 280 3 GB

Thanks Ampen for joining in. I'm glad I'm not the only one. I added my game logs and such so hopefully a moderator or someone can peak in on this thread and maybe have some suggestions.

System: Windows 10 64-bit, Intel i5-4690, 8 GB RAM, AMD r9 280 3GB I did a clean install v1.1 GOG version buildID.txt says: build id = 012302016.04.19 at 19:27:27 CESTBranch: master Unmodded I'm using an Xbox 360 controller. I've done the mapping and the controller works fine in flight and vehicle modes, but when I have a Kerbal on EVA the controls are unresponsive. Also, after having tried the controller, if I go back to the keyboard the a, s, d, w keys ALL only move the Kerbal forward. If I turn on the Kerbals jetpack the controller works to control the RCS except for the triggers that I have mapped to rotate. If I fly up and then try to rotate, the RCS animation shows but no rotation occurs. If I go back to the keyboard and press Q or E rotation no longer works either and NO RCS animation now shows for rotation keyboard inputs. If I use the keyboard before trying the controller, the keys work fine, but after touching the controller analog sticks it messes up the keyboard as well. I've tested this in both career mode and during tutorials with the same results. Anyone else come across this issue, or have a suggestions? DxDiag.txt https://www.dropbox.com/s/t95ni7bl7l3oain/DxDiag.txt?dl=0 Output_Log.txt https://www.dropbox.com/s/7ltbn9yj4aha1q7/output_log-controls.txt?dl=0 KSP.log https://www.dropbox.com/s/m3bxxkhmvxmqvh3/KSP.log?dl=0 settings.cfg https://www.dropbox.com/s/w22j01zhb3lkrqp/settings.cfg?dl=0

For those asking, no I don't have any mods installed. I've always been hesitant to use them for some reason. I think I'm starting to get the hang of things. I've read some more and I know how to calculate delta v now. Hopefully that will help some. I seem to be making some progress, although, with this game it seems that whenever I think I've got things figured out something else happens to flip me on my head. Thanks everyone for your help

First thank you everyone for your responses, you're all giving me a lot of good info. It looks like I've got some changes to make. I think I might also need to make some adjustments to my ascent and some more practice. I had my engines throttled back because I had read that it's inefficient to go more than 200 m/s below 10000 or so meters, but I thought that I also needed the extra thrust when I got higher than that. I'll try out some of the ideas posted.

I've managed to get into orbit with just a basic rocket, but I can't seem to scale it to get a larger payload up. I want to get some science stuff up there with another rocket stage to get to the Mun, but I can't get it into orbit no matter what I do. I've tried multiple stages using various different engines and boosters. I've tried to make the rocket have as little dead weight as possible. One thing that bothers me is that I get no closer to orbit using six engines firing at the same time than I do with three. I try to limit my speed to around 200 m/s below 10000 m and then start to throttle up. I figured that with more engines firing that each individual engine wouldn't have to work as hard and that the fuel for each would last longer, but it seems that each engine can barely carry itself with some fuel and nothing else. I've read all kinds of stuff on the wiki and here on the forums, but I just can't figure it out. I'm in career mode so I don't have all techs unlocked. Here's what's in my rocket: What I want to get into orbit is - command module, science jr., service bay with some batteries and science stuff, FL-T200 & FL-T400 fuel cells, and a LV-909 engine. I'm hoping I can get to the Mun with that. Below the LV-909 I have a FL-T400 and a LV-T45 engine to use to adjust and finalize my orbit around kerbin.. For the main thrust stage I have in six sided symmetry - two FL-T400 tanks stacked above a LV-909 engine. EDIT Sorry, I miss typed. I'm using six LV-T45's for the main thrust stage, not the LV-909. Like I said above, I've tried it with three in symmetry without success as well, and I've also tried it using the LV-T30 engine instead, but I would lose control at between 6000 - 10000 m. Any help would be appreciated.