m1sz

I'm also waiting for this to come, I enjoyed the repulsors a lot... :-), making pod racers with wheels is muuuuuuuuuuuch harder and not very cool sadly :-(. gogogo!

Edited the previous post about the mirrorsymmetry. nothing to be found in the .cfg of B and C. Tested it without the editor extensions mod, and it was still the same. I'm using your updated mod "B9-PWings-Fork.v0.40.3" and FAR "Ferram_Aerospace_Research-v0.15.6_Jones". Just tested with the stock control surfaces and they work good! Here's a video of what's happening to me, look how the plane behaves good but the control surfaces look odd ^^

I've just tested with a new vessel, and the only bug is visual. The plane works good enough, but it looks odd XD. I'll try that "mirrorsymmetry" thing you said and report back. Thanks! I haven't found any "mirrorsymmetry" line in .cfgs for B&C. I'm using editor extensions mod, I'll try without it

My control surfaces are not responding good to symmetry, also on the latest FAR version and the 1.1 compatible version from your Github. For example, I set 2 control surfaces in the wings for "roll" only, and they move at the same time when I try to roll (like if it was pitch), and if I do the same with pitch, they move one up one down. Looks like a symmetry problem to me! Thanks for your time

I sent this question yesterday, it might be related:

Nope, doesnt work either. Was the first thing I tried. First, add under input devices another one. Then, tried setting it but it can't work, because in the config.ini it appears with the full name of the device. In this case, Saitek Pro Flight X-55 R , so it doesn't make any difference :(. Really, it's a stupid bug that doesn't make sense to me. Buttons appear like this: BRAKES { primary = B secondary = Joystick1Button5 group = 0 modeMask = -1 modeMaskSec = -1 } Axis appear like this: AXIS_PITCH { PRIMARY { name = Saitek Pro Flight X-55 R. axis = 1 inv = False sensitivity = 1 deadzone = 0.05 scale = 1 group = 0 modeMask = -1 } That may be the reason of why buttons works but axis don't.

Yes, as far as I could read over the internet (including KSP bug tracker) it's an issue with Unity..., KSP only lists one of my two devices, and therefore thinks they are the same (same name in the first 10 characters). I've been messing arround trying to change their names in the registry with no luck (Seems like they have internal names that I cannot rewrite, and managed to chance their windows name but KSP still recognised them with the original one). Biggest thing is that when setting the input, KSP knows it's "joy1axis1" or "joy0axis1" if it's throttle or stick, so it KNOWS there are two, but then, it cannot translate that info to the mapping. Even if it's UNITY's flaw, it's notorious how a mod called Advanced Fly By Wire fixes all the problems (apart from other good things it provides), and even after 1.1 I cannot use my Saitek in KSP (advanced joystick with a space simulator). Anyway, and as I said, the fact that the game knows when I'm moving "joy1" or "joy0" makes me think that there's something pretty wrong with the mapping. Before it would only recognise one joystick. (I think this changed since 1.0, last version I played before coming back)

I've been waiting for the 1.1 release, hoping it will fix the bugs with the joystick mapping for Saitek users (or as far as I know, any joystick which uses 2 different USB [throttle and stick, for example]). I was very happy to see the game recogniced joystick0 and joystick1, but when I try to map one of the axis, It always binds it to the joystick0, despite recognising both of them. I made a quick video to show what I'm talking about. Windows 7 64bits that recognise both devices as separated ones. In the config.ini it only recognises one of them: INPUT_DEVICES { Saitek Pro Flight X-55 R. = 0 } But as you can see, when I try to map the axis to my stick, it recognises the joy1.1, but then it binds it to joy0.1 (axis 1 of my throttle). This doesn't look right at all. More information: Button mapping works. It recognises 2 joysticks as joysticks 1 and 2, and they appear like this "joystick1button0" and "joystick2button0" in the config.ini, and works as intended. Thanks for the help

I stopped playing KSP for a long time, mainly for this reason... :-(, no propper joystick support for advanced joysticks. I own a Saitek X-55 and the only thing I could do to play the game was using the Advanced Fly By Wire mod. As far as I know, it's not updated to 1.1 yet, and I hope it will!

I've waited for 1.1 to play again hoping for joystick support, and find myself again in agony. My Saitek X-55 doesnt work. Worst thing is that KSP detects 2 joysticks now, but still maps everything to the same one, and the input lag persists. This mod is our only hope !

I think radial cockpit would make more sense ^^

It's not updated yet Malec, there's a fix for linux several posts behind. Looks like Taniwha is working on it tho!

that looks like a feasible reason..., on another note, my (in this case, modded build) forgets about control settings quite often

I've been testing it a bit more. There's an issue with the loop option. The script pauses at the last order, before going to the first one. As you can see in the GFY I add below, it doesn't matter that I remove the "wait XX" at the end, it still waits for something, making the walk animation wrong! http://gfycat.com/FeistyWillingFerret Still, a wonderful mod to come :-D About the save scripts, could it be possible to save the script to the .craft of the ship you are using? (so no need to tinker the list in the editor, just make it available to future launches of the same .craft) thanks!

forum user (and old kerbanaut) Taniwha is working to fix Advanced Fly by Wire mod, which pretty much should solve all the issues (it did in previous versions). Here's the forum thread of the mod. ATM there's a working linux version it seems ^^ http://forum.kerbalspaceprogram.com/threads/95022-0-90-AFBW-v1-5-1-%28Joystick-controller-mod-we-re-back%21%29?p=1901187&viewfull=1#post1901187