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

thanks a lot taniwha!! :-)

sad to hear man, read a lot about windows 8.1 and AFBW problems in their github reports. anyway, it's definitely doable by a dev team!

Being able to quickly add a new one in the correct spot makes editing an existing one not that much needed, so as a solution, I think it could be very handy! BTW, I forgot to report a bug I found while tinkering with the mod. It's about the "wait for moves". Sometimes it gets stuck waiting "for moves", while nothing is moving. I found it to happen when you give 2 orders to the same part, one in one direction and the other in the other direction, and the second order takes place before the first is complete (before the first movement reached the value you set). I didn't try it further but happened to me several times that day! thanks for the time and effort!

evilC, I read your recommendation in the AFBW thread. I've been using UJR for several months with my old joystick (had some issues with the throttle control not being recognised entirely). Just went here to say thank you!, it's a wonderful program that helped me before. The difference now with my X-55 is that I miss a lot of buttons and to be honest, it's against my will to use third party programs to set a damn joystick in a space/fly game!!!, dammit! Anyway, thanks for the very nice software :-), if things don't change, i'll configure it for my x-55 ! cheers!

I've just spent a few hours trying to make a robot walk with these sequences... :-), it's a very nice mod, it allows for complex operations, but the inability to configure the preset in the SPH makes it really hard. Anyway, considering the tinkering you have to do all the time with IR timers and speeds, it would be really good if the sequence could be modify, and not just replaced with a new order, so instead of adding a new order with a few more degrees and speed, you can just modify the current one. Moving orders in the middle of 20+ other orders is kinda messy and boring :-P But after all, I'm just amazed of what a wonderful addition this is!!

That's exactly my concern!!!!, it's a internet known problem with unity games and saitek software..., but saitek joysticks happens to be one of the most advanced and complete joystick for simulators, and despite the problems, one single guy managed to fix it perfectly with a mod, that also, lets you change control settings midflight, have different profiles, and many more easy-to-use features!

I made a support thread about the issue I'm having with my x-55, in case you want to add anything http://forum.kerbalspaceprogram.com/threads/117360-Saitek-X-55-throttle-and-stick-KSP-considers-both-the-same-joystick

proper joystick support pls :-) (also known as Advanced Fly By Wire mod!)

How would you delay that call?, the stock joystick support is just..., very bad. I need this mod to play :'(

It's a problem I had since I bought this Joystick: game version: v1.0.0.830 in windows 7 64bits. clean install of KSP. The joystick consist of 2 separated parts, each of them with his own USB cable and independent between them. In fact, windows recognises 2 different devices, as seen here: The problem is that, when I'm binding the axis, KSP thinks they are the same device, mixing the inputs..., so one of them is useless. This happened before (in 0.90), but I dodged the problems using the Advanced Fly By Wire mod, that worked perfectly since the start. This is how the config file looks like: (ignore the fact that they are both controlling the pitch, it was just a test to map the same axis from both devices) AXIS_PITCH { PRIMARY { name = Saitek Pro Flight X-55 R. (MADE USING THE STICK) axis = 1 inv = False sensitivity = 1 deadzone = 0.05 scale = 1 group = 0 modeMask = 7 } SECONDARY { name = Saitek Pro Flight X-55 R. (MADE USING THE THROTTLE) axis = 1 inv = False sensitivity = 1 deadzone = 0.05 scale = 1 group = 0 modeMask = 7 } Also, on input devices only one is shown: INPUT_DEVICES { Saitek Pro Flight X-55 R. = 0 } The joystick gives correct values in windows, and works in games like DCS and War Thunder, being recognised instantly without anything else to do. I used some workarounds before, with virtual joysticks, but I think it's not the way to go in a 1.0 release! Thanks in advance for the time and help :-) edit: Also, I get about 1 second lag from the inputs -.-. This was a known issue back in previous versions, apparently between Saitek software and Unity. Anyway, must be doable to fix, considering it was fixed perfectly by a mod in previous versions (Advanced Fly By Wire mod).