Jump to content

taniwha

Members
  • Posts

    3,958
  • Joined

  • Last visited

Reputation

2,577 Excellent

Profile Information

  • About me
    Construction Gingerbeer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It'll be fixed next time I upload a release, as I don't actually maintain the file at all: it's all automated (and when I do a release, the file that's in the zip gets uploaded with the zip, so they're always in sync (except now).
  2. I sort of thought I had (or thought of it then forgot). Done now, though. Good for 1.8 through 1.12.99.
  3. This has been fixed in git, but I don't know when I'll be able to get out a release. You'll find the info you want in section 2.5.3 Micro Pad. But in brief, the colored arrows follow the RGB standard of XYZ, with inverted colors for negative axes. and +X on a part with default placement points to the VAB door.
  4. Nothing should have been broken. If so, I'd count that as a bug.
  5. Thanks. I'll take a look, but I can't promise when I'll get it done.
  6. Oh, dear.I goofed in my instructions, sorry. You DO need the UI (style cfg and pngs) and probably Texture (app buttons etc) directories. Oh, however, if you edit the paths in UI/DefaultSkin.cfg, you can move that into SC's directory.
  7. I do not. However, I believe CKAN uses the .version file when available, which is known to be wrong (I keep forgetting to fix it).
  8. Ahhhhhh, just as I was beginning to suspect (which is why I came to check this thread). If you are using SC, I suspect you do not need all of EL, just its Launchpad.dll, which you can put in SC's directory (overwriting the Launchpad.dll there), and removing any ExtraplanetaryLaunchpads.version from SC's directory.
  9. This is most odd. Please send me your KSP.log file (entire file, but you need only load KSP and exit).
  10. I'm sure they do, but EL itself works on all "recent" versions of KSP, and mod patches to EL are unaffected by the KSP version (and, for the most part, even EL's version). As I implied earlier, it's most likely the ExtraplanetaryLaunchpads.version file in EL's Plugins directory because MiniAVC.dll (which many mods include) uses that file to test for compatibility. Thus removing (or editing) that file will fix the "Launchpad not supported" problem. Don't worry that removing that file will break something as doing so cannot break anything.
  11. No, that's what whatever is saying is not supported, not what is saying that "Launchpad" is not supported, but I guess my question may not have been clear enough. Anyway, I asked because there are two mechanisms I know of for the "not supported" test: the original version checker created by Majiir and used in several mods (Kethane, FAR (in the past, at least), and EL included), and [Mini]AVC. [Mini]AVC uses the .version file I mentioned, the original version checker is hard-coded in each relevant mod, and I very carefully made sure EL's was happy with 1.12.
  12. What says it's not supported? If it's AVL (or whatever it's called), edit or remove ExtraplanetaryLaunchpads/Plugins/ExtraplanetaryLaunchpads.version (it does say 1.9.1, which is not correct. need to figure out the correct fix for that).
  13. That looks very much like you are trying to use EL 6.8.x in KSP 1.12 (which I've heard is a no-good combination). You should probably try grabbing 6.99.0, which I have tested in KSP 1.12.2.
  14. Seems to work nicely in 1.12.1, too.
  15. Maybe you'll come up with better style defs
×
×
  • Create New...