Ph34rb0t

Nice to see my stuff is still being used! Cheers!

Does anyone (still) have Freeman's FAR/Spaceplane patches? All the links I've tried are dead. I would also take any alternatives. - Edit: I'm dumber than dumb. Tried middle-clicking the spoiler tags and wondered why I didn't get a download. For reference: http://forum.kerbalspaceprogram.com/entries/1770-FAR-NEAR-DRE-etc-Support-for-KSOS-by-helldiver

The updates for the utilities and GF still don't show up on CKAN, but I guess it's just a matter of time before they will. Manual download from your server works.

Thanks for fixing the SAS bug!

The FF savegame kraken has finally swallowed all my Kerbal's progress or garbled it. No chance for recovery from a S.A.V.E. backup. Any way to hack the .sfs file to at least get some rough flight and EVA time back (don't care much about any ribbons)? - E: Same bug as sjohnson's, probably.

This has an IVA model now? Sold, sold, sold! And I have the perfect companions for it! http://forum.kerbalspaceprogram.com/threads/32456-0-25-Hot-Beverage-Inc-Scalding-Hot-Parts-%2810-10-New-shipment!%29

Note to self: Check own threads more often. As the dangerous furry thing above me posted, the parts should still work in 0.90. I've only tested the fuel cells so far and they worked as well as they always did.

Thanks! (Fortunately, I could burn all of the excess money on ConstructionTime build points. )

I already have SBFM installed. Maybe it's the source for some problems...? In that case, thanks to you both. I've tried it with or without "Use stock SAS". It doesn't make a difference. But Mechjeb doesn't seem to be the culprit as I also get this behaviour whitout MJ being installed at all. What about implementing a single SAS toggle cycle into the Ascent AP whenever the "Engage Autopilot" button is pressed? It wouldn't harm people who do not have this problem, but it would provide an easy fix for those who have. - - - Updated - - - - Edit: It seems to be caused by AFBW 1.4.4! http://forum.kerbalspaceprogram.com/threads/95022-0-90-AFBW-v1-4-6-%28Joystick-controller-mod-SAS-bug-fixed!%29?p=1639637&viewfull=1#post1639637 Well, case closed, I guess. Sorry for the stir-up here!

I've disabled every mod that could influence on flight behaviour or auto-flight (including MJ) and still get SAS-like behaviour after starting a flight, but without an illuminated SAS indicator. Pressing "T" once does nothing visually, pressing "T" a second time puts me into default SAS mode. Must be a stock bug after all... Yup. 2.5.6. Your config is much nicer than mine, so it's time for an upgrade, I guess. Thanks for posting it!

I can't seem to make negative payments (i.e. pay back money) in the current version of Government Funding. If I put in, say, "-1" in the "Pay or get paid" box, I receive 1 Credit instead of paying one.

Ah, I think I have the source for the weird SAS behaviour pinpointed: Pilot Assistant. It does enforce its own stablization algorithm by default and subsequently clashes with Mechjeb. Nope, it wasn't Pilot Assistant. This is still happening. Does MechJeb clash with 0.90's pilot experience stuff? I'm also not using the cumbersome AR202, but a MM config file that adds MJ to any "command" type part. My test vessel from the sceenshots also "only" uses a probe core. The MM config file looks like this and has been working perfectly until...well, I don't know...the 0.90 upgrade?

Yup. 10char

MiniAVC - provided it still works as it's supposed to - does not complain about the installed RPM version. They're included in the download from https://github.com/Mihara/RasterPropMonitor/releases . (Folder: JSI\RPMPodPatches)

The RasterPropMonitor download on CKAN doesn't include the ModuleManager patches for the stock command pods or MoarDV's updated .dll files. Might be worth adding both as dependencies?

CKAN has version 18.3 sans the ModuleManager patches for the stock command pods, so it needs to be manually updated with MoarDV's .dlls and the patches from Mihara's regular pack. Ah, that actually makes sense.

The version from CKAN does not include the patches for the default pods. You'll have to install them manually (just the "RPMPodPatches" folder). I found that out the hard way. That doesn't work for me. RasterPropMonitor.version reads and KSP still complains.

Well you ninja'd me. - Edit: I've tried to take a peek into the debug menu and output_log.txt to see if I can find something related to MechJeb there, but without any success. If this bug isn't caused by another installed mod, can't Mechjeb simply be made to automatically toggle SAS on and off in future versions as a safety measure?

Click the box next to "Automatic Altitude Turn"... (This is standard behaviour for quite a while.)

Without tapping "T": http://i.imgur.com/eaosclK.png With tapping "T": http://i.imgur.com/taR1V51.png Modlist (only those including .dlls or relevant to MJ): - Edit: Regarding the solar panels: The autodeployment stopped after I disabled the option in the Ascent Autopilot. The panels would deploy whether I had the AG AP enabled or not.

Does anyone else have problems with the Ascent Guidance mode and gravity turns? I'm using dev build 385 with FAR 14.6 and the latest MJ FAR plugin build. The rocket will only start its gravity turn after I hit the "T" (SAS) key while the AG autopilot is engaged. This makes the "SAS" icon flash for a split second and after that, everything works as it should. Without hitting the "T" key, the rocket will do a vertical ascent and then simply pick up its entire orbital velocity near the apoapsis. It's almost as if MJ is fighting against SAS for control unless I intervene... - Edit: Does MJ automatically check for stage deltaV and can it override user input into AG mode if it detects that a weak stage sould better be fired outside of the atmosphere?

I see that this info was right in your v1.1 announcement post. Sorry for asking again and thanks for the reply!

So I've thinned out KWRocketry to 10% of its original content. What will happen when I install an update for KW? Will I have to re-disable all the parts that I don't need or will CKAN auto-apply my previous selections? In any case, thank you. One more thing that I (probably) won't have to install by hand ever again. P.S: A "Disable All" button would be nice to have.

Layouts are stored in "advanced_flybywire_config_v21.xml" in the AFBW folder. - Edit: Regarding the deadzone problem: It doesn't happen in 1.4.4.

Confirming extreme slowdowns with 1.4.5 when the configuration menu is open. KSP 0.90 x86, Win 7. Also, my controller's (Top Gun Fox 2 Pro Shock) coolie hat isn't recognized anymore. Reverting to version 1.4.4 breaks my config file. I can reinstate a backup from 1.4.5, but it will be wiped clean as soon as I enter a flight scene. Can you make the config file handling a bit more robust? Also, there are cases in 1.4.4 and 1.4.5 in which the movement (or dead zone) of my throttle slider is not correctly recognized. Throttling up works, but after throttling down into the dead zone makes the ship throttle up again after a few seconds. I have to fight the input with repeated "throttle down" movements. Scratch that, it was hardware related. I'm not sure if this has always been broken or if this is a new bug, but I'm only noticing now that the available dead zone settings actually don't make any sense for a throttle slider. You'd need a user-adjustable zone extending from 1.0 toward 0.0 and a zone from -1.0 to 0.0 and not a zone from 0 to 1.0 and 0 to -1.0. After all, what use is a dead zone smack dab in the middle of the slider? I mean, it could be useful for, say, enabling translation forward or backward in docking or EVA mode (by moving the slider forward or backward from a safe middle position) or for use with gamepad sticks, but it surely isn't useful for throttling a ship's engine with a throttle slider on a flightstick. As a workaround, I can set my positive deadzone to 0.99999 for now and only use the upper 50% of the slider, but this isn't very useful for precise throttle settings. I'd appreciate if there could be a possibility to mark an axis with "Is slider" or "no center position" in future versions and have an appropriate dead zone handling.