Starseeker

Using the 1.4.2 version, I was seeing the same ad-filled map problem. Went to the Kerbal Maps link, and it appears the domain expired.

Ah, I see. Would be nice to see more space-combat support, but if that's not what this mod is about, then I understand.

Forgive me if this has been asked before, but what broke with the HE-KV-1 vacuum-capable missile?

This is truly amazing work.

The gyrotron is labelled as being needed for microwave power transmitters, but the massive dishes are the only ones not labelled as not needing the gyrotron. Also, there seems to be very few dedicated transmitters. In addition, how is the free electron laser used? Does it have standalone transmit capability, or do you need to attach a transmitter?

Once the problem with nukes' blast radii is fixed, it would be awesome to see a selection of proper self-assembled ballistic missile warhead components instead of one pre-made MIRV warhead. There are three components of a ballistic missile's warhead that are currently missing from KSP: the conical heat shield, the fuzing (not a typo) mechanism, and the "physics package" (the nuke itself). The heat shield protects everything from reentry, the fuze tells the nuke when to go off, and the nuke - well, we all know what it does. Here's my concept of how this weapon system would play out: The physics package: The fuze: The heat shield: Of course, there may possibly might could be a better way to do this, but I can't think of one. ---unrelated post below--- Also, does this add a "ballistic" mode to the Modular Missile Guidance part?

What's this I've heard about a Procedural Explosive?

I guess I meant a station or such that used something like Extraplanetary Launchpads to build vessels from shipped-up parts. It was kind of a offhand idea anyway.

Tentative idea for a new category: Constructor Vessel: A vessel capable of assembling another vessel.

How would I go about removing the racing stuff from the mod (on my end)? I'll never use it, and I feel that it would give a (small) performance boost. Should I just delete the files/folders for the relevant statics, or is it more complex than that?

Is it normal for the W88 to detonate mid-air after being "fired"? EDIT: After looking through event logs, I've found that it surpasses it's g-limits and detonates. Will experiment with turning part g-limits off.

It would be nice to see some non-MIRV (similar in operation to the existing BDA explosive warhead) nuclear warheads. I'd think .625m, 1.25m, and 2.5m would be good sizes. In addition, the fixed warheads could have configurable yield, with corresponding variable cost & mass, as well as a thermonuclear option (which would be even more costly) for the 1.25m and 2.5m. Also, some conical re-entry shields, in 2.15m, 2.5m and 3.75m sizes, would work well. The re-entry shields would look something like this (dark segment is shield, white is base): EDIT: Something I noticed: in the VAB or SPH action group editor, there's an option on the various nuclear bombs of "detonate". However, when this is assigned to an action group, and then said action group is triggered, nothing happens. I've also noticed that the "detonate" feature is absent from the RMB menu in-flight.

And PartTools allows one to do that by...

How does one use this IN their IVAs? All the models in the dl are .mu, which can't be loaded into unity.

I've sent the PM

k. Thanks for helping me and being patient!

Even with a cuboid, the error persists.

Niether of those seemed to work. I'll try a different model.

I'll get the screens

I'm trying to dip my toe into making mods, but I'm being hindered by a big problem: KSP refuses to load my parts. Looking in the debug window, it seems to be because my collider's tricount is above 255. I say seems because this error occurred even when I used a default box collider, which has 12 tris. Any idea why this may be occurring?

Immiburn(1) n. A burn that is combination ascent and orbital insertion; typically due to a low second-stage TWR. Immiburn(2) v. To perform an immiburn.

My game consistently crashes while loading with an out-of-memory error. I installed ONLY RO and RSS (and dependencies) via CKAN on a 1.0.5 KSP install. Example log: Any support on this would be appreciated. If more information is needed, please ask. NOTE: A 1.0.4 install running RO, RSS, and additional mods works fine.

Any plans for RPM support in the pods? Check if you have the pumps enabled.

Naughtblammer n. A part, such as a Cubic Octostrut, that has no fuels (or, indeed, capacity of any kind) that nevertheless explodes violently upon overheating. Also refers to a non-essential or leftover part that exploded. Naughtblam v. To be a naughtblammer. Naughtblam n. The moment when a naughtblammer naughtblams. Also refers to any explosion of a part that is vestigal or unneeded.

Nevermind, download progressing nominally. Tried running as Administrator, might have fixed issue. That, or it was temporary.