NathanKell

Please follow the guidelines. They're there for a reason; we need the info in them.

Updated version of ialdabaoth's (who is awesome) ModuleRCSFX. ModuleRCSFX *fixes the major known issues with the stock RCS Module (ModuleRCS) *Supports some advanced features (axis restriction, full thrust, scaling). *Supports EFFECTS (well, it will--currently broken) Installation: Extract to GameData (creating a ModuleRCSFX folder, and inside that, Plugins and the readme. Download GitHub License: CC-BY-SA (with the ialdabaoth proviso, that all forkers must remark upon his awesomeness...which I'd do anyway). From the readme: ModuleRCSFX is a fixed version of the stock RCS module. It is derived from ModuleRCSFX by ialdabaoth (who is awesome). It supports a lot of configuration, as well as fixing stock bugs. ** RCS Part Controls ** useZaxis defaults to false. If you set it to true, the RCS will fire along the Z axis of the given transform(s). This means you can use engine part models as RCS parts (like using the ion engine model as an RCS part). ** RCS Axis Control ** enablePitch enableYaw enableRoll enableX enableY enableZ All these default to true, but if one is set to false in the MODULE, the RCS part will not fire for that input. These can be toggled in the VAB/SPH. useThrottle which, when set to true, means that RCS will fire forwards with the throttle. ** RCS Thrust Control ** fullThrust defaults to false. Set it to true and if the thrust ratio is > fullThrustMin (default: 0.2) RCS will fire at full thrust (or 10% thrust in precision mode), rather than the less-than-full-thrust, dependent-on-angle they do stock. useLever defaults to false. When it's false, fine controls will make RCS fire at 10% (default) power only. When it's set to true, stock behavior returns (i.e. fine controls means lever arm compensation). precisionFactor is the multiplier to use when useLever is false (as it is by default). precisionFactor defaults to 0.1 (10%). ** RCS Input Controls ** EPSILON defaults to 0.05. That means a control actuation of less than 5% is ignored. This is because Unity is bad at joysticks and ignores deadzones. ** RCS Effects ** Currently disabled pending rework. Changelog: v4.2 * Fixed bug where inputs were being improperly normalized (thanks Starwaster!) * Fixed a bug in applying useThrottle (was being done in global Y not local Y; ditto). v4.1 * Fixed bug in thrust calculation (was 2% what it should be...) * When in fullThrust mode, don't switch to full thrust unless thrust ratio already starts out at fullThrustMin (configurable).

Are you sure that's the whole log? Also, can you zip the file and upload it? It looks like it got converted to richtext or something. (It cuts off while KSP appears to still be going strong) As it stands you've got plenty of exceptions, but it's unclear which is the one that happens right before the problem. Please launch KSP, *just* replicate the problem, then *immediately* quite KSP, then zip and upload the player.log. Thanks!

wasmic: if no info can be added, no help can be given. That guideline is there for a reason; we can't just zap a magic wand, we need info.

BLUESHADOW125: Try here. NINJA'D: or, yeah, Read the OP.

Wow. Just wow.

Does control from here work correctly for the stock linear port?

HoneyFox: ah, sorry! I must have missed your ping. To use that mask, move it 2048 pixels left then flip it horizontally. That'll make it work for 7-3.

If you get a crash in a modded install, please follow the guideline in the sticky. It'll make it much easier to diagnose.

Lucid Hills: it helps because that vastly decreases memory usage, which brings KSP under the threshold at which the errors occur.

Moved a couple posts. Let's stay on the topic of TreeLoader, please! If you have Minecraft-related business, please hash it out in Minecraft-related fora.

Also, you should read that post of HarvesteR's that Rowsdower linked. His original proposal was a 2D game without real orbital mechanics, because real orbital mechanics are too tough for people. And yet here we are.

Please post in the Modded Support forum, and follow the "how to get help" guidelines.

The error you get from your OS has nothing to do with what crashed Unity. Check the output_log.txt (in KSP_Data) and go to the bottom. Scroll up until you see Crash!!! and right above it should say what made it crash. If what made it crash is you being out of memory, then ATM can help.

The config file for the stock solar system is "no config file" -- you only put *changes* in the config file

Geschosskopf: nobody's forcing you to get offended, either. As I read it, this thread has thus far been a fairly civil discussion about what various people want to see in KSP. I suggest everyone keeps it that way, rather than suggesting those who disagree with them about the direction KSP should take should leave.

http://forum.kerbalspaceprogram.com/threads/29932-Mysterious-Projects-Falcon-IVA-HUD

Lack got busy, and distracted by OOH SHINY. Check the dev thread.

Well, the shuttle was going to make payload to orbit dollars a pound! Actually, the absolute best resource AFAIK is The Shuttle Decision.

CDK: Read the last couple pages (in particular, this)

Also, many of us use github; you can subscribe to our repos and get notification on releases.

I sit corrected

Procedural Fairings has an interstage. You place the base (attaching the "floating" node to your engine, or, if clustered, the central node), set the base width and top width and height appropriately, and, if extra height is needed, set that. Then add fairing sides, and build your next stage below the interstage. It's by far the most versatile part in PF, since you can *also* use it to make payload fairings (just place a nosecone on the floating node).

Well, maybe not the worshipping bit. Modders are all human too (don't we know it). But a little patience, when someone's having a busy time in RL (*and* just got tons of abuse heaped on him re: ModStats) would be in order.

MBM 2 PNG v7: https://www.dropbox.com/s/txthm7h5jwqgnz5/mbm2png7.zip?dl=0