JimTheDog

I'm having some problems with the Surface Experiment Pack, and I think it ties into the KIS integration. Almost all of the parts are now odd sizes and generally much larger than they were before the update. Is it possible t he volumeOverride lines, from the part configs, isn't being processed anymore?

Appreciate the information. I do have RealChute. (I wonder if I got confused because it's right next to RCS on my install list...)

I have a weird error, which vanishes/reappears when I remove/reinstall this mod on my install. When I click over to the advanced parts list in the VAB editor, this seems to break part filtering and make the advanced part list bug out. The regular parts list occasionally bugs out too, after a venture into the advanced list. This happening to anyone else, and anyone know a solution? RCS Build Aid is just too damn handy for building! Ugh. Disregard the above. Somehow when I reinstalled RCS Build Aid the third time this glitch stopped. I am very confused, but you don't need to worry about this unless other people are getting it.

I had something similar going on. I wound up doing two things, and in my case, that seems to have solved the problem. Might not work for you. I'm running an NVidia Card (1070), and updated my drivers for that. Secondly, I removed my old start up parameter to force starting KSP in directx11, to leave it to the default DX9. I'm sorry I can't be of any more help than that, but this has let me play around today with mods without weird inexplicable crashes, like I was getting yesterday.

Definitely an improvement, though there's still odd terrain clipping if I disable the suspensions, but no launch-into-the-sky-and-boom!

On mine, I deploy landing legs with g, the craft settles to the ground -- or starts on the landing pad with legs deployed -- the pads settle on the surface, a moment later fall through the surface. Then, I press G again to pull the legs up, and the entire ship leaps into the air as, I presume, it pulls the pads THROUGH the ground layer. This is deeply troubling. Are we making landing legs out of kraken-suckers?

I don't know that it's really a bug, since it lets you pilot your capsule down. The offset angles the capsule enough to produce lift by itself, rather than requiring you to turn it around. It's... pretty curious. I hope they add 'tilty' heatshields, like the present ones, and 'not-tilty' heatshields that act more like the old deadly re-entry ones, because it's a neat feature... it's just really hard to wrap your head around.

Hmmmmm. I will give these things a shot, and hopefully stop killing tourists. I don't have airbrakes unlocked yet, but I suppose I can do something similar manually with sets of flaps...

So. I'm struggling with this one - I'm guessing I should just try shallower re-entry angles and multiple aerobraking orbits, but, in case there's another option... My wings keep burning off my space planes on re-entry. Am I missing something? Any tips on avoiding having planes melt?

I'm guessing you'd have to start a new career.

Fingers crossed this gets updated -- another Saitek user who needs your aid! ;_;

Long story short, in general, the center of lift winds up behind the center of mass in flight, so if you have it like you do in your picture, your plane wants to go backwards, but your engines are pushing it forwards, and... that's not good. Long story long, there's a good illustrated guide here, though it's talking about KSP's old aerodynamics model. The new aerodynamics model is more like the improved FAR one talked about in the guide: http://forum.kerbalspaceprogram.com/threads/52080-Basic-Aircraft-Design-Explained-Simply-With-Pictures

Thirded. This would be brilliant.

Any chance of integrating the building unlocks with KER, so you get more advanced functionality as your buildings advance?

This mod makes me hugely excited. However. I use a Saitek X-55 system? And what's going on for me is that when I try to bind axes on the stick, it flares up with Button #16 or whatever -- tied to the mode switch on the throttle and constantly fired based on the mode switch's setting - and binds that plus axis #0 to whatever I'm trying to use. (Edit: Same deal on the Throttle, but with Button 31 - 33 ) D: Is there a way to get around this? Edit (for solution): !!! Okay. I switched to 'Old presets editor'? The flaring up with the mode switch buttons issue is no longer an issue. Hurrah! <3 Thank you so much!

I think running things through vJoy and UJR have a very similar effect. But all in all, I think joystick support needs to be improved by both the joystick manufacturers and the Unity/KSP devs.

For what it's worth, I've sort of found a solution, but I'm not quite expert enough to start offering a guide: displays the 'Roll' axis mapped through vJoy, and the 'Yaw' axis mapped through Saitek's drivers, to the same left-right movement of the stick. The lag is obvious.

And KSP's support said: --- Hi, Sorry, we are aware of this, but it's currently not a priority in development, we'll get to this issue in time and fix it, but we currently are busy doing other things with higher priority. Best regards, KSP Support

For those interested, this was the support ticket as it stands: [MyName] User Posted on: 04 September 2014 08:32 AM Hi, I'm experiencing input lag while playing Kerbal Space program -- there's a delay of up to a half second when making any input, be it stick control or pushing a button. This is apparently a known problem which is more or less exclusive to Saitek sticks, and specifically when running Saitek drivers - apparently one fix for the problem is to use generic joystick drivers but, obviously, with something like the X-55 that's kind of pointless. This may or may not be related to the Unity platform. Relevant links follow: http://forum.unity3d.com/threads/joystick-lag.115807/ http://bugs.kerbalspaceprogram.com/issues/762 http://forum.kerbalspaceprogram.com/threads/92614-My-Saitek-x52-Joystick-isn-t-performing-as-it-should As a new customer who specifically purchased the X-55 with playing Kerbal Space Program in mind (it's a game with a lot of fiddly controls, great for binding to all these switches!) this is especially disappointing. If you could please provide a fix, work-around, or perhaps get in touch with the Kerbal Space Program developers or Unity developers to try and work out what the problem is, that would be fantastic. Mad Catz Support Staff Posted on: 08 September 2014 02:45 AM Dear [MyName], Thank you for your e-mail. In regards to your enquiry, can you tell us which is the OS your pc is running at the moment? Also, please go to Start, in the Search bar, type joy.cpl and press Enter. In Test window, do you notice the same delay? Which store did you buy the controller from? Best regards, Cristina Toma Technical/Customer Support Rep [MyName] User Posted on: 08 September 2014 03:44 AM Hi, the delay doesn't occur in the test window, or in any other similar games. I purchased the X-55 directly from the EU MadCatz store. I'm presently running Windows 7. This specific problem also appears on an older Cyborg Fly 5 I own while playing Kerbal Space Program, but not while using a generic X-Box 360 joypad's thumb sticks or a similar logitech joypad's thumb sticks. Other users have reported problems with the Cyborg V1 ( http://steamcommunity.com/app/220200/discussions/0/648814843500619980?l=english ) and the X52 Pro ( http://www.reddit.com/r/KerbalSpaceProgram/comments/2ayg77/im_as_ready_as_can_be_for_024/cj05e5z ). Ticket Details Mad Catz Support Staff Posted on: 11 September 2014 12:47 PM Dear [MyName], In this case, since the controller doesn't register the same behavior in Windows, you might need to check the settings inside the program you are currently using with the device. At this point, we cannot say that the issue lies with the product itself. Best regards, Cristina Toma Technical/Customer Support Rep [MyName] User Posted on: 12 September 2014 03:56 AM Hi, I've made alterations to all user settings available within Kerbal Space Program, and, as stated, non-Saitek products (such as an x-box controller) do not suffer the same issue with the game, and there are reports that by disabling Saitek drivers the issue disappears, strongly implying that there's a problem within the Saitek drivers in relation to the game. What next steps do you suggest I follow? Are there any contact details I can provide for Saitek/MadCatz when contacting the developers of Kerbal Space Program/Unity, or could I request that Saitek/MadCatz's driver developers get in touch with the Kerbal Space Program developers to try and resolve the issue? Ticket Details Mad Catz Support Staff Posted on: 15 September 2014 06:37 AM Dear [MyName], What we advise you to do is to contact directly thr Kerbal Space Program manufacturer and ask for further information regarding this issue. Best regards, Cristina Toma Technical/Customer Support Rep

So I just got a Saitek X-55 HOTAS setup. ... It still has the Saitek lag problem. I'm opening a support ticket with them, for reals.

I'm getting the 'right click, no scale tweaking happens' thing. Tried updating all the KSPAPI things I could find, no good. Output log here --> https://dl.dropboxusercontent.com/u/13415207/output_log.txt Edit: Fixed it by deleting my installation of MSI: Robotics and reinstalling it from the new version. My bad!

FWIW, given the recent aggrivation and bugs, allow me to just say that I really enjoy RealChutes, and thanks for putting in the time to make it, stupid_chris!

Okay. I am having trouble with quicksaves, I think it's the Center Of Mass bug? Maybe? I am unsure. The quick fix I have sorta-found by blundering around is to edit, in my quicksave, the name of the parachute part on the ship from: parachuteName = RC_triple_canopy to parachuteName = canopy Then, instead of going crazy with the center of mass and camera zooming away, or occasionally the parachute not working at all, things work as expected. To try fixing it, I went into the mod files for Realchutes, and found two instances of 'parachuteName = RC_triple_canopy' in Parts/cone_chute.cfg and cone_double_chute.cfg, which I switched to 'canopy', and I did the same with transform names in materials/texturelibrary, and this totally didn't work at all. The part I was using/this was happening with was a stock mk16 parachute (tiny nosecone). Hope that helps in the bug-hunting!

For those wondering, seems to be broken with .24, or at least I can't get it to work at the moment.

Seems to be working with my installation of .24. YMMV