ultrasquid

Boating is certainly possible, but the dynamics are not well optimized. Travel over "water" is invariably noisy and splashy. Some work will have to be done in the game engine to improve that, and I don't think it's a priority at this stage of development. The Firespitter mod (mentioned above) provides many of the things you'll need, though, including electric propellers, floatation pontoons, and high-capacity batteries.

I feel you there. Apart from a few splashes like we get in this kit, much of KSP is rather drab, ranging from galvanized steel to brushed aluminum. Some more bright paint and gold metalized mylar would be wonderful, not just for Firespitter, but among all the parts. Now, to do so would make maintaining a cohesive aesthetic more difficult (even the current not-quite-matched grays can be troublesome), but it wouldn't be impossible.

I found a small animation bug with the radial parachute. If you mount the chute pod in a rotated position, the parachute will deploy the direction in which the pod is rotated rather than the direction of travel. Once the animation completes the chute snaps to the correct direction, but when it's time to fully open the canopy, the chute snaps back to the rotated orientation until the animation completes, then it snaps to the normal velocity vector again. I haven't tested this with the stock radial chutes, just the one from this kit. I'll try to get you some screenshots of this if my description doesn't make sense.

You'll have to get the Firespitter mod for one of those. There's even a folding prop for packing into a tight rocket fairing. I find it odd that stock KSP aviation jumps straight in with jet engines. Like many things in KSP, that doesn't make a lot of sense in terms of technical progression, though it might be explained by game mechanics.

The science system as it is, while a valid game mechanic (the diminishing returns for performing the same experiment in the same environment) isn't very sciency. Reproducible results are nearly as important as new discoveries, and are far more useful. And, if performing the same experiment gains different results, it would tend to indicate that there is an external variable that the experiment hadn't controlled for, and is worthy of further investigation.

Due to system performance issues, I keep my KSP window below maximum size for my monitor. As a result of the increasing sophistication of parts, and the verbosity of some (especially mod) developers, the information included has become more lengthy in many cases, and the information windows that appear at mouseover in the parts catalog sometimes get cut off on the top and bottom. These mouseover popup windows need to be sensitive to the game window height and become wider when necessary to fit the text within the available height and not get cut off. I can see instances where this wouldn't work, such as descriptions that make use of several line breaks that push the window height. There might be some way to impose a rule in the developer guidelines to prevent this from happening, too.

No worries, take your time. Just trying to say that your work is appreciated.

I hope about two months of inactivity isn't too much to alert the necro-cops. KSP could really use small parts like these updated for the 0.22 tech tree/career mode. They fill a gaping hole in the existing collection of parts. @Nuke: I hope you'll be able to get back to them soon.

I'd been using the dodecahedron balloon as a lifter for atmospheric probes in previous versions. It never seemed to fly high enough, though, and without wind it never went far from the KSC. A weather balloon would be a nice addition for this purpose. Looking forward to your improvements.

I found some very interesting constellation maps at http://www.davidrumsey.com/luna/servlet/view/search?os=0&q=6900.000&pgs=100&sort=Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No It will take some time to crop and format them properly, but I think a skybox like this could be a lot of fun.

My understanding is that in Sandbox mode there should be no substantive change, but there may be compatibility glitches as there can be between them any other release. In order for mod parts to work in the new Career mode, they'll have to be rewritten to connect to the tech tree node structure. There are a few nodes left unused by the stock game that are reserved for mods that don't fit neatly into existing nodes.

Consider that all the apparently cylindrical fuel tanks out there actually would have hemispheric, or at least ovoid domed ends on them, concealed by an outer shroud. Compressed gases would force flat-ended cylinders out into such a shape anyway, so containers for compressed gases are given that shape to avoid fighting the natural forces. It's similar to the reason plastic soda bottles are shaped the way they are. It took decades of engineering for Coca Cola to produce their trademarked curved bottle in plastic, because the CO2 dissolved in the liquid would cause it to bulge out without special reinforcement. Up until then, and still now with other brands, the basic domed cylinder remains the standard. You could argue that an exposed truss of some kind might give a weight advantage over a cylindrical shroud over the domed end of the tank, and that certainly might be the case with very large ones, but aerodynamic drag would be substantially increased, likely negating the effect of any weight advantage at launch. I still like the spherical tanks. They look cool, and hemispheres have more fuel capacity than similar conical adapters.

Plants emit CO2 during respiration, just like other living things with aerobic chemistry. For this to work, of course, one has to assume the green pigment in kerbal skin is chloroplasts. This does not necessarily mean the kerbals are plants. Their skin may be inhabited by symbiotic algae or similar. And, bringing this back on topic, those algae could produce psychotropic alkaloids under certain conditions, and give explanation to a whole range of kerbal behavior.

Wouldn't photosynthesis allow kerbals to extend their food and oxygen supplies, so long as they keep a window pointed sunward?

These will be fun

A few requests: Over-under style Mk1 cockpit mount and jet intake to Firespitter oblong fuselage adaptor or something, like so: Mk1 cockpit mount with side jet intakes to Mk2 fuselage adaptor, a little bit like this: Firespitter oblong cockpit mount with side jet intakes to Mk1 fuselage adaptor kind of like this: Firespitter Oblong to Mk2 fuselage adaptor

Are these parts meant to replace or complement Nuke's Half-Meter parts and other useless crap?

Did you ever get close to finishing the IQ-9 Analyzer head for MechJeb 2? A nice thing about original MechJeb was there were so many modules to choose from, including your R2-D2 unit. The new version, while many features are greatly improved, only comes in the plain old gray box with a couple lights. It would be nice to have a choice again.

Small rockets like these are also good for sub-orbital missions e.g. telemetry experiments, functionality tests, etc. The stuff NASA shoots off from Wallops, Va. is like this.

That's not what happens. Holding the Option key while dragging and dropping a file or folder from one window to another will copy the file into the new window, leaving an identical copy in its original place. If there is an existing item with the same name as the one you are copying, a dialog will appear asking if you want to replace it, but it will overwrite the thing. Only when you select multiple files (not folders and certainly not nested folders nor the files therein) and drag them into a window with similarly named files do you get the option to swap in only the newer files, and the option key doesn't even come into play there..

What is in the included folders other than GameData/B9_Aerospace/ and why are those items necessary for B9 Aerospace to work? If those other folders are already there in my KSP/GameData folder, how do I prevent this bunch from overwriting them (which would be the usual drag-and-drop folder moving behavior on MacOS X)? I'm reasonably sure this was explained somewhere, but it really should be appended to the first post. The warning there without explanation is enough to keep me away from this mod and others with similar invasive folder schemes like Ferram Aerospace Research.

I still miss the other MJ modules. All there is now is the AR202 box. I guess it'll have to do.

Oh woe! Almost 2 months without an update from a free and voluntary mod hobbyist! Give the guy a break! The new KSP version just came out and it's darn near miraculous any mods at all have been updated for it. v0.20.x has barely been around for a blink. I have a Pong machine from 1974 that still works just fine without any updates.

Are your wheels now using the same control scheme as the stock wheels? If not, how would I edit one or the other so they all operate consistently according my (or someone else's) preference? (this may have been answered, but I haven't tracked back enough in the thread to find an answer yet. If I do find it, I'll edit this post with what I find out)

Here's what I got this time $ mono /Applications/PartGen\ 2.2.2\ by\ Lando/KSP_PartGen.exe Unhandled Exception: System.ArgumentException: The requested FontFamily could not be found [GDI+ status: FontFamilyNotFound] at System.Drawing.GDIPlus.CheckStatus (Status status) [0x00000] in <filename unknown>:0 at System.Drawing.FontFamily..ctor (GenericFontFamilies genericFamily) [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Drawing.FontFamily:.ctor (System.Drawing.Text.GenericFontFamilies) at System.Drawing.FontFamily.get_GenericSansSerif () [0x00000] in <filename unknown>:0 at System.Drawing.Font.CreateFont (System.String familyName, Single emSize, FontStyle style, GraphicsUnit unit, Byte charSet, Boolean isVertical) [0x00000] in <filename unknown>:0 at System.Drawing.Font..ctor (System.String familyName, Single emSize, FontStyle style, GraphicsUnit unit, Byte gdiCharSet, Boolean gdiVerticalFont) [0x00000] in <filename unknown>:0 at System.Drawing.Font..ctor (System.String familyName, Single emSize, System.String systemName) [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Drawing.Font:.ctor (string,single,string) at System.Drawing.SystemFonts.get_DefaultFont () [0x00000] in <filename unknown>:0 at System.Windows.Forms.Theme.get_DefaultFont () [0x00000] in <filename unknown>:0 at System.Windows.Forms.Control.get_DefaultFont () [0x00000] in <filename unknown>:0 at System.Windows.Forms.Control.get_Font () [0x00000] in <filename unknown>:0 at System.Windows.Forms.Form..ctor () [0x00000] in <filename unknown>:0 at KSP_PartGen.Form1..ctor () [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) KSP_PartGen.Form1:.ctor () at KSP_PartGen.Program.Main () [0x00000] in <filename unknown>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.ArgumentException: The requested FontFamily could not be found [GDI+ status: FontFamilyNotFound] at System.Drawing.GDIPlus.CheckStatus (Status status) [0x00000] in <filename unknown>:0 at System.Drawing.FontFamily..ctor (GenericFontFamilies genericFamily) [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Drawing.FontFamily:.ctor (System.Drawing.Text.GenericFontFamilies) at System.Drawing.FontFamily.get_GenericSansSerif () [0x00000] in <filename unknown>:0 at System.Drawing.Font.CreateFont (System.String familyName, Single emSize, FontStyle style, GraphicsUnit unit, Byte charSet, Boolean isVertical) [0x00000] in <filename unknown>:0 at System.Drawing.Font..ctor (System.String familyName, Single emSize, FontStyle style, GraphicsUnit unit, Byte gdiCharSet, Boolean gdiVerticalFont) [0x00000] in <filename unknown>:0 at System.Drawing.Font..ctor (System.String familyName, Single emSize, System.String systemName) [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Drawing.Font:.ctor (string,single,string) at System.Drawing.SystemFonts.get_DefaultFont () [0x00000] in <filename unknown>:0 at System.Windows.Forms.Theme.get_DefaultFont () [0x00000] in <filename unknown>:0 at System.Windows.Forms.Control.get_DefaultFont () [0x00000] in <filename unknown>:0 at System.Windows.Forms.Control.get_Font () [0x00000] in <filename unknown>:0 at System.Windows.Forms.Form..ctor () [0x00000] in <filename unknown>:0 at KSP_PartGen.Form1..ctor () [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) KSP_PartGen.Form1:.ctor () at KSP_PartGen.Program.Main () [0x00000] in <filename unknown>:0 I can't say for sure, but it seems to be hanging on not finding a font that it wants.