TheGatesofLogic

Trying to figure out how to patch this myself, but struggling, any update on when the problem with OPM might be addressed?

The real issue is quite apparent: Fast, Cheap, Good You may pick two of these.

This is not purely correct. From a marketing standpoint, nobody will take you seriously if some data is not provided. Since none actually is, it's safe to assume the worst.

Well, alpha-emitters make terrible dirty bombs. There's a reason Co-60 is the favored dirty bomb material, and that's because it is a beta and gamma emitter.

Okay, please keep in mind, Pu-238 is NOT fissile and neither are its decay products. It really wouldn't be targeted.

Yeah, not really all that surprising, let alone dangerous. Alpha-emitters are extremely dangerous when ingested or in very large quantities, but otherwise they atmre harmless, especial if they have a casing like they would in a pacemaker. As for whether it would be risky in that it could be accumulated, that isn't an issue either, as Plutonium 238 is non-fissile.

Unfortunately ippo that isn't entirely correct. OSX will not handle executables directly in any fashion. They simply do not recognize it as capable of running internally. As a result it does require some sort of conversion framework to run it on a mac. which is rather inconvenient for mac users.

Regardless of the degree to which that engine can vector, it can only vector in one dimension so it provides absolutely no yaw control. Engine yaw control requires two of those engines and the ability to adjust the thrust on those engines individually, which is only possible with a plugin that I forget the name of. Alternatively you could rotate that engine sideways, but that would remove the pitch authority the engine gives

Well, the flavor might be unknown, but the smell would entirely depend on the frequency of reactions between the water ice and the organic molecules. It will almost certainly smell more like glue and nail-polish than most anything else save for a few nitrogen based esters whose scents I am unfamiliar with. I expect predominantly nitrillic ester formation. Edit: now that i think of it... Nitrate esters would be extremely common on the surface if there is ANY significant reaction between the water ice and organic nitriles. Titan's surface would be covered with explosives!!! We clearly need this in KSP

I don't think you get it. When you make coffee YOU usually boil it correct? If you order coffee from a restaurant do you expect it to be served less than 5 degrees C under boiling? Nobody does. If you take even a small sip of coffee that hot it would cause severe burns to your tongue, which may cause you to involuntarily spill the coffee over yourself. Such a substantial mistake on McDonald's part is a serious hazard, regardless of the way in which it was discovered, which is REALLY what the lawsuit was about.

There's also a new mod that replaces treeloader and works with tree.cfg files, it's called TechManager and it fixes this problem entirely, including adding the new nodes and everything.

not a stock issue i can tell you that much, it only happens with these parts, and only happens when you move them after adjusting them

This seems to have been buried, anyone have a fix for this? I keep running into the same issue

I was referring to relativistic forces, despite the period of time of the passing appearing to decrease due to spatial contraction coupled with relativistic dilation forces should act at a faster rate in accordance (IIRC). Also, as said before, electromagnetic forces are not discrete, so no matter how fast you travel through the planet there will still be SIGNIFICANT scattering. After rereading a bit on relativistic forces I was in fact correct, passing time would be countered by a force proportional to the momentum of the object based on its relativistic mass over the invariant mass, which means that a high amount of interaction is essentially unavoidable. (Maybe)

Knowing this, I am honestly impressed, this part is beautiful

Since TreeLoader's license is all rights reserved it is obviously not possible to distribute a patched version of treeloader. This does not mean, however, that Treeloader cannot be patched. I'm curious as to whether it would be acceptable to distribute a plugin that would patch treeloader after it has already been downloaded in the original format very similar to the way module manager patches config files. I'm curious as to the legality of this and whether this is even possible, as I have not delved into plugin development thus far, but knowing what I do I feel as though this wouldn't be difficult at all, and I have heard that treeloader really only needs minor modifications to fix it for .25. Is this true? Or would the extent of the changes fall into the category of the patcher essentially already having a modified version within it? Where is the line drawn?

Well, the problem here is relativity, it limits the passing period in exchange for accelerating the rate at which the interactions proceed (I think). So you end up with a major interaction regardless of how fast you go (maybe).

Unless node locations are the basis for model scaling, which I am not sure is the case, as I believe it is the other way around, where model scaling effects node location, the configuration patch given in the past few pages for the magnetic nozzles SHOULD NOT WORK. Am I wrong or does it actually not work, it's very unclear.

well, generally speaking, you WANT your radiators to be as cold as possible (increases efficiency of energy conversion) however are you certain that you're turning your reciever on as a reciever? if it's activated as a transmitter this should happen, but not when it's activated as a reciever...

The MM config "fix" i found a few pages back doesn't look like it should do anything to fix the rescale problem. Sure if you move the nodes you might be able to get the parts to attach to other parts, but the engines are still smaller than they are supposed to be. The part has to be rescaled, the nodes can't just be shifted around...

I think my post was lost, so I'll repeat it. I'm still having scaling issues with the magnetic nozzles, is anyone else also having this issue? It seems like people are not so I'm not sure what the issue is.

When it says "compatible with type-1 docking nodes" this is referring to the 1.25 meter stock docks, yes? I assume then that the extendable docking probe is an aesthetic piece, and lacks a collision mesh? Also, it appears as though the pod does not have deadly reentry heat shielding, is there a config someone has put out somewhere for this?

I'm still running into issues with the scaling of the magnetic nozzles. Anyone able to help with this or having the same issue? The nozzles appear to be scaled down just slightly so the nodes float above the model and they are slightly smaller than the part size they should be.

Dude, seriously? this is like a 5 month necro...

I personally favor the idea of intracellular manipulation via nanorobotics which alter the cellular and genetic structure of an individual such that the individual is optimized for things which normal humans cannot do. This would allow crying a to actually be feasible.