Jump to content

King Something

Members
  • Posts

    146
  • Joined

  • Last visited

Everything posted by King Something

  1. Probably not, due to Unity 5 wheel shenanigans. Wheels from KSP 1.0.5 and earlier (Unity 4) do not work in KSP 1.1.0 and later (Unity 5).
  2. @Sigma88 has a few mods for OPM, including one which changes the colors of the new planets so that they're NOT the same color as their real-life counterparts. Check out the links in his signature for details. He's also got a mod which changes Jool's color to a Jupiter-esque golden brown.
  3. As the moderator said, it'll be ready when it's ready. In the meantime, check out the unofficial release in @Flashblade's signature, just above your post. That one works in 1.2.1, but make sure your plugins are up to date.
  4. It'll get here when it gets here. For future reference, please refrain from asking for updates to mods -- it's against the rules, and is impolite to the modders. The answer to the question "When is the update of $MOD for $KSP_Version gonna come?" is always "Soon™", so don't bother asking. There's an unofficial release of B9 for 1.2.x in @Flashblade's signature (the second post yours), but no official release until all the dependencies are updated.
  5. That's the HX parts pack. It should be available in the OP and elsewhere in this thread.
  6. That's the HX parts pack, separate from the main pack.
  7. The MechJeb For All patch isn't made by the same guy who makes MJ. It is a MM patch, and will work as long as you have MJ installed. MJ proper has the two probe cores I mentioned and the Mech Jeb module, which is what has those fancy windows that tell you the orbit info and the remaining DV and whatnot. The patch adds the module to all command parts, manned and unmanned, so that you can use it in a B9 cockpit.
  8. Someone made a patch for Mechjeb that makes it work with all command modules and probe cores, instead of just the two parts that come with Mechjeb (one is a conical probe core with landing legs, which has catastrophic results as soon as the vessel loads on the launchpad in 1.1.x; the other is a radially-attached probe core... chip... thing... which cannot be the first part on a vessel and cannot be places in such a way as to prevent navball shenanigans) I'm not sure if Mechjeb has been updated for 1.2.0 yet, but once it's available the patch I mentioned should work.
  9. Given the inherent nature of PC games (and computer software in general), this dream is unlikely to ever become reality, though the absence of a bug-free KSP is not because of a lack of trying on Squad's part.
  10. Possibly worth noting, but the mod (and bundled IFS and MM) are in a folder called Gamedata instead of GameData. This may result in frown-upon-able shenanigans for users who extract directly to their KSP install folder without paying attention to the capitalization.
  11. The good news is that MM and IFS have been updated for 1.2.0, so Blowfish's job of updating B9 has become that little bit easier. It should be ready for release Soon™.
  12. Take as much time as you need. If it isn't ready by the end of the month, then don't release it by the end of this month. Keep in mind that the latest version of KSP is 1.2pre, not 1.2 proper -- it's very unlikely, but Squad may make some changes from 1.2pre to 1.2 proper that could break mods built for the former. Hopefully everything progresses well.
  13. The bad news is that this means we'll (well, YOU'LL) have to wait for Firespitter to get updated before further tests can be done. The good news is that the wheels no longer summon the Kraken with their mere presence on a vessel.
  14. If K.Yeon is so inclined, then perhaps. Depending on the presence or absence of Unity wheel shenanigans in KSP 1.2 proper, we might be fortunate enough to also see the return of the OPT landing gear (and B9 landing gear, and Adjustable Landing Gear, and....)
  15. Call Gallagher. See if he can lend the Spacedock admins his watermelon hammer so that they can fix their servers.
  16. You'd have to ask stali about that. I haven't looked at the coding for the various versions of OPT (partly because I'm not a modder) but I would imagine that he has a reason for changing that part's name (perhaps because there are other parts in the various OPT releases with that name?). And in any case, he said weeks before releasing 1.8.5 that he was changing the names of all the parts and that that change would break all vessels with OPT parts. I don't think that this change should come as a surprise.
  17. LOUD NOISES!!!!3.14159! If you were paying attention over the past few months, or reading the past dozen or so pages, you would have known that the latest community maintenance update would break all previously built OPT vessels. You would also know that the fact that OPT 1.7 is not compatible with OPT 1.8 is a major reason why the community maintenance version exists in the first place -- name changes and various other under-the-bonnet changes have been made to the parts from the various official OPT releases so that they could all be used together in a single parts pack. It's a large project and by no means an easy one. We should all be thankful that @stali79 et al put forth the effort to put it all together. Constructive criticism is welcome, but I don't think the modders would very much appreciate you complaining that the update would break all pre-existing vessels when they themselves said that it would happen weeks before actually releasing that update. Oh, and the OPT landing gear from earlier versions, designed to work in KSP 1.0.x, have been temporarily removed due to incompatibility with KSP 1.1.x.
×
×
  • Create New...