OrbitalDebris

Awesome

Quick bug report, the KW procedural fairings no longer fit the 0.25 scaling compatible KW Rocketry parts.

I thought that auto-struts were in there already? or am I thinking of a different mod? BTW thanks for the update, e-dog. This is one of my must-install mods

I thought KW parts had a problem with 0.25? I've been using the fairings from AIES, the mod seems to be working well.

IIRC that means that KSPAPIExtensions isn't working correctly. It may need updating for 0.25

@Enthalpy

Waves hands mysteriously... "Abra-ka-Sarbian!" (poof!) @PART[W485_Surface*Light] { @MODULE[ModuleLight] { %lightR = 1.00 %lightG = 0.93 %lightB = 0.78 } } @PART[W485_Surface4WayLight] { @MODULE[ModuleLight],1 { %lightR = 1.00 %lightG = 0.93 %lightB = 0.78 } @MODULE[ModuleLight],2 { %lightR = 1.00 %lightG = 0.93 %lightB = 0.78 } @MODULE[ModuleLight],3 { %lightR = 1.00 %lightG = 0.93 %lightB = 0.78 } }

The color of the emitted light is a tweakable, you can just right-click on the parts in the VAB and change it to any hue you like. Unfortunately the texture on the part stays that same yellowish color, so it can look a bit weird. Maybe playing with transparency in the 3d models can help?

Yeah, me too... that and RealChutes. MJ can land on a dime using stock chutes, but it doesn't support RC (last I tried it doesn't even open them) and that mod has some pretty cool parts I'd love to use.

Works great here on 64 bit windows. I have an issue report, although I suspect it's not easily fixable... when you use the new docking port and try to use the RPM docking cam, there's a big silver hexagon in the display which is probably the back of the prong that sticks out of the docking port.

Wow, I completely missed that. Yep, you're right. I guess I'm so used to seeing ads all over the place my brain just edits them out

Actually I don't think the toolbar's breaking the rules, because the donation button is not in the toolbar itself, it's in the download page. (emphasis mine)Speaking of the new rules, I really like this one: That will make plugins that depend on other plugins a lot more stable.

@Biotronic They just added it in 0.24.1

Not sure if that's the case... I just tested it and it does have a pretty puny decoupling force, but if you look at the part description in the VAB it says it has a ejection force of just 100. If you look at the other, smaller decouplers they are a lot more powerful - for example, the 1.25M decouplers have an ejection force of 250 and the 2M decoupler's force is 600. I suspect they goofed on the part and it was supposed to have an ejection force of 1000. If that's the case, it should be pretty trivial to patch with a MM script.

Thank you Vendan for adding the privacy info in the OP. And thank you SirCmpwn for maintaining a server that cares about its users privacy. This is how it starts, individual modders show they care about this stuff, and eventually it will become the normal and expected thing to do. This is incidentally also what happened with free software licenses, initially everyone just said "it's a free program, why do you care?" and now posting and complying with licenses is normal and expected.

That's the thing - his code is sending data from a computer he doesn't own to somewhere else. The privacy statement is there to inform the owner of the computer what's happening to this data (to fully inform the user he'd need to link both his privacy statement and KerbalStuff's). In this case (a free mod for a computer game) it's a pretty trivial thing so it's a storm in a teacup, but in the bigger picture this is the kind of thing that large companies get fined billions for.

Thanks for a great mod, Vendan. About privacy, this is why commercial software that does this sort of thing comes with a privacy statement. This is a short text that describes what data is sent, how it's used and stored, and after how long it's deleted. It gives users peace of mind (and for companies that sell their stuff in the EU, it also prevents very large fines...) With a privacy statement, users can make an informed decision of whether they want to use a given program or not. I imagine that the statement for this mod would read something like "This mod sends its version number over unencrypted HTTP to my server at www.blah.com; this information is used to determine whether a new version of the mod must be downloaded and it's not stored at the server. This behavior is opt-in and can be disabled at any time by editing the config file called blah.cfg that's in the mod's folder". Bam, no ambiguity and no need for strong words. Note that the statement must be truthful, so the first version of this mod would have had to state that the behavior is not configurable by end users.

w00t! 0.24 is now officially done

Awesome stuff! Thanks Sarbian!

.net code is just like Java in that the binaries are bytecodes that will work on any CPU, unless the dev deliberately does something that will only work on one specific CPU type. That is something that's rarely needed and actually a pain in the butt to get right, so it's very unlikely to be done accidentally. I think it's safe to say that most plugins will just work on 64 bit.

Yeah, that's unfortunate. I write software for a living, and our privacy guy would have a cow if I did that in production code

Ah, interesting. Thanks!

Yep. As far as I'm concerned, KWR is what stock should have been And with 64 bit KSP, I'll be able to enjoy the textures at full-res!

I think I may have a bug report... I'm using the latest (released on the 17th) builds of MJ and module manager, with the above MM script, and all functionality is enabled on my pods in career mode even though I just have the first couple of tech tree nodes unlocked - I was expecting to get the delta V window and maybe one or two others, but I have everything available. I'm playing the full 0.24 career mode, with funds. Can anyone confirm?

Uh-oh. Decoupler bug?