phoenix_ca

It's not exactly good forum etiquette, repeatedly bumping a thread in close succession. If your post is last, you should be fine editing it. Four posts is...excessive.

You'd have to be crazy to make a pancake rocket in FAR.

LoadOnDemand is boss. Except when you're in the VAB/SPH. Then you need to treat KSP veerrrry gently.

Hrmph. Even that doesn't work right. Can someone see what I'm doing wrong here? @PART[*]:HAS[@MODULE[ModuleCommand],!MODULE[SCANsat]]:FINAL { MODULE { name = SCANsat sensorType = 0 fov = 0 min_alt = 0 max_alt = 0 best_alt = 0 power = 0.05 scanName = Eyeball Scan } } The part will drain power at a rate of 0.05, but the toolbar buttons won't be visible, and the command part doesn't have any SCANsat controls via the GUI.

Ran into a crash. Looking over the exception in the LoD log, looks like something wacky happened handling a Near Future Propulsion texture. https://dl.dropboxusercontent.com/u/5296507/NearFuturePropulsion-LoD-CrashLogs.7z See! I'm doing better now! MOAR LOGS! I should also mention that this doesn't happen all the time. In fact that was very much a random occurrence.

Alllright. What on earth did I do wrong? When I try to add the toolbar buttons, they aren't visible. If I try to add them to a new toolbar, they make that toolbar disappear. O.o Edit: 'Tis something to do with my MM config. I added the MapTraq modules to all parts with a command module. Apparently, that's not working so well. MOAR EDIT: You added parameters! >.< I'm going to guess that new "scanName" value has something to do with supporting Kethane and...other mods. >.>

No. Even if they could output enough power (which they can't unless they're close to the sun), EC cannot be converted to MJ locally. That's slated for the next release.

And ORS support is right after that, riiiight? Riiiiiight?

FAR does that, more or less (no weird shenanigans with the reentry effects required).

Stock aerodynamics are dumb. Dumb dumb dumb dumb dumb. The only people that could probably answer that question adequately is Squad.

Yes, a working version of B9: http://forum.kerbalspaceprogram.com/threads/79611-B9-Aerospace-interim-maintenance-pack KSPI if you feel like really changing things. Docking Port Alignment Indicator for sure.

Herpity derp derp. I'll remember that.

Bah. The human brain can also spew a lot of crap. The Internet is evidence enough of that. People are stupid.

Miner Wars, and every other permutation of that that came after it. It was all pretty crap. What was worse is that they made a complete piece of crap, advertised it as something very different (think Aliens: Colonial Marines level of lies), and then did nothing to repair the damage with those people who got suckered. I was one of those people, and that means I point-out just how bad of a developer they are every chance I get. It's my payment back to them for yoinking $60 from me. If you're looking at games to buy, avoid Keen Software House as if it were Ebola virus. As I've said, Squad are practically saints in the indie dev scene. At least they are delivering on their promises. Not super-fast, sure, but they are delivering.

The problem is that that's exactly what the wording of the license tries to restrict; dependency. In effect, trying to reserve a right that was never the author's right to reserve in the first place. Yes, but we aren't talking about redistribution of anything here. We're talking about making a piece of code (say, a config file) that is dependent on KAS. Restrictions on that kind of use are unreasonable. To draw another analogy (which I'm stuck with until I manage to dig-up some legal cases that apply; remarkably difficult since words like dependency are primarily used in the context of juvenile law, not software ), it would be unreasonable for Adobe to dictate to its users what art they may create with their software. The PSD file that is created from that is dependent on Photoshop for it to be interpreted and used correctly, but that does not mean that Adobe can apply arbitrary standards like "no da-da art may use the pen tool". Similarly, Adobe has no ability to restrict software extensions that anyone may create. As long as they aren't redistributing Adobe's property, there is nothing they could do via a license agreement to prevent, say, Topaz Labs from operating. Can a word processor claim ownership of the words written with it? No offence, but both you (DYJ) and RoverDude are talking about something completely different and irrelevant to the point I originally brought up. This isn't about redistribution, it's about dependency. Furthermore, the license agreement is between the creator and the user, it is not between the creator and any other person out there writing code for KSP. If that were actually the case, then I could just release a mod that made a tiny edit to how every API call worked with KSP and say in the license "You may not distribute any parts that use the modules in this mod" and instantly take-over complete control of the KSP modding community. KospY made a mistake writing those license terms, adding invalid restrictions (or possibly not understanding what he was actually saying) and it should be corrected. Majiir should have the right to adjust the license, assuming he took ownership of the code.

It is indeed. And it works stupendously well.

That sounds exactly like what Rover is trying to do (and succeeding at doing).

The annoyance with Windows is that there is no hard standards enforced by Microsoft about where programs must put their crap. Things are different on Linux, and wildly different on OS X. Linux has some modicum of standards for where supporting application data must go, while OS X has two folders, only one of which is usually relevant. There's ~/Library/Application\ Support/ and /Library/Application\ Support/ . And that's it really; anything outside of that is into non-standard land. This makes managing an OS X (or other Linux/BSD) system way, way easier. Windows, is a hot mess. Programs will put themselves wherever they please. There isn't even a standard place for binaries. Instead of a single /Applications/ folder there are two folders that don't provide useful separation. And then there's the blasted registry, and finally the quagmire of folders that is the \Users\ folder on Windows where various applications may or may not store their data. It's not stored in a standard way (Application Support data is stored in OS X by application name), meaning there's no predictability for the user. One can't actually look in those folders and expect to find user data for an application. It could be held in the registry (barf) or somewhere else entirely. All those inconveniences add up, enough that simply wanting the damn program all in one place is understandable. If Microsoft did a better job of establishing a coherent and unified standard for devs to use, and devs would actually follow it, this wouldn't be such a headache.

Such excellence.

:< You didn't understand.

Well, that puts my uses of PWings to shame.

Everything was SO MUCH BETTER. That isn't nostalgia, that's truth! All this crap we have now, making the game easier. Like manoeuvre nodes! Who asked for those?

Looks like I got an LoD crash in the VAB, so here's an output log (which also seems to confirm my suspicions).

Not really, no. I guess I need to question my sanity when it comes to still playing this game.

That's what Kerbal Alarm Clock is for!