Ezriilc

Members
  • Content Count

    1,363
  • Joined

  • Last visited

Everything posted by Ezriilc

  1. @Nightside: Yes! HyperEdit 1.5.8 works well with KSP 1.4.5. I've updated the note on the HyperEdit page.
  2. Yes, I believe so. I will do a test and then post back here and update the note on my site.
  3. Sorry, I'm just now seeing this. I appreciate your encouragement, even if it's misplaced. I will take a look and try my best, but I'm betting I'll need some help. Specifically, which method should be used in place of the one that doesn't exist any longer. I've created an issue for this in our GitHub repo. EDIT: https://github.com/Ezriilc/KSP-Graphotron/issues/12
  4. Have you tried Graphotron with the latest version of KSP? It may actually work. I now believe that I had thought this was my other mod's thread. Sorry for the mix-up! @Drew Kerman is correct. There isn't/wasn't a BETA. I apologize. To be honest, I haven't done any testing with the new version(s) of KSP recently. Any input ya'all might have is more than welcome.
  5. That's great, and congrats! Even though using HyperEdit is the epitome of ... ahem... cheating. I wonder, though, what actually fixed your issue? If you can describe it here, it may help someone else down the line. Regardless, thanks for coming back here to follow up with us! Feel free to let us know about any other adventures you have.
  6. Firstly, welcome to the forums! I'm sorry you're having trouble, and I'm here to help. Also, you may find this thread useful: We've not had any other reports like yours, and all my tests work fine. To figure this out, I'll need more information. Please try all these things and let me know if anything fixes it. Which version of KSP are you using? Which version of HyperEdit? Where did you get each? Try holding the ALT key while pressing H. Try running KSP with only HyperEdit installed and no other mods. Try looking in the log files for references to HyperEdit. I hope this helps, but if not, then please contact me again - here or on my site.
  7. On further study, it appears the problem I had was with auto-strut and/or rigid attachment on the bottom set of engines (KE-1 Mastadon) touching the pad. So far, I'm not using any launch clamps, but I will do more testing to determine if using clamps fixes it. EDIT: I've learned that using clamps to keep the ship well off the pad seems to avoid the problem. I believe that auto-strut and rigid attachment were somehow attaching the ship to the pad. I'm very relieved about this, as I thought it was something with the Making History expansion.
  8. I've been doing some messing around with HyperEdit v1.5.8, and the new Making History expansion with KSP 1.4.4, and the results are... not ideal. In fact, the Lander seems to be totally borked. It doesn't move the ship, and just makes view shake and confuses me. I will do more testing soon, and I would appreciate any input from everyone here. Thanks in advance!
  9. I'm sorry if you're having trouble, and I promise to do my best to fix it. The error you've reported is not caused by network issues, and my hosting provider hasn't suffered any significant outage since I started the Kerbaltek site in 2013. If you continue to have problems, please contact me directly, so I can help. You can PM me here, on my site, and in IRC via EsperNet (#KSPofficial & #KSPmodding) and FreeNode.
  10. That means you're either trying to hotlink to my files (a no-no), or your browser is misbehaving due to plugins or some such. Please try it again with a different browser and/or with all plugins disabled.
  11. Good news everyone! I've just published a new release of HyperEdit v1.5.8, built for KSP v1.4.4. It also works for 1.4.1, 1.4.2, and 1.4.3. As always, please let me know if there are any issues. Thanks to the community for helping me get this done. http://www.Kerbaltek.com/hyperedit
  12. Sadly, The Creator is no longer part of the project, so it is left to me to care for it. Because I'm not fluent in C# enough to properly update the code, I'm somewhat stuck. Most times, someone in this great community saves me by volunteering new code, and/or testing. I don't mind anyone asking for an update - especially when you say "please". It's fine. Just understand that there may be quite a long wait. I would ask that you try our latest BETA-3 version with KSP 1.4.4 to see if it works, and report back to us here if you can. Your assessment could lead me to a fix that I can handle, or inspire someone to jump in here and help. Please, everyone, feel free to contact me any time.
  13. Please try with a different browser and/or disabling any browser plugins. If you still need help, please copy the exact and full error message you're getting.
  14. I understand, and I'd bet that is a good plan. Oddly enough, I don't really use mods, so I'm no expert in that regard.
  15. Thanks for the report. I've added the coords thing as an issue here: https://github.com/Ezriilc/HyperEdit/issues/54
  16. Yes, and I apologize for the long delay. But also, I've been told that our latest BETA-3 works in KSP 1.4.3.
  17. Instructions are on our site: http://www.kerbaltek.com/hyperedit Just put the .dll file inside the Kerbaltek folder (inside GameData; make it if you don't have it), and remove any other copies of HyperEdit.
  18. I apologize for the long delay. I'm hoping to have the full release published soon. When that happens, the update to CKAN will also happen shortly after.
  19. I'm having a... workflow issue. To be honest, I could use some help.
  20. Practice makes perfect, and HyperEdit definitely helps me with new craft designs and mission plans. My favorite craft builds are on my site (Craft Kitchen), please help yourself. "Kolsys" is my best ship.
  21. Yes, eventually. I'm having some IDE issues. In the meantime, you can use the BETA-3 we have up, as it seems to also work in KSP 1.4.2. EDIT: I think I was conflating this thread with my other mod's. I'm not currently aware of any problems with Graphotron on the latest version of KSP, but then I haven't done any testing. This doesn't mean I don't intend to, I simply overlooked it and didn't get any support requests.