Ezriilc

I'm sorry, but I don't know what to make of that. I'd need someone with more KSP API experience than I have, and possibly with experience on RSS and other planet packs. Hopefully someone here will have more insight.

As of today, Kerbaltek members' Ribbons have been served more than 6 million times since ~July of 2014! At one point, I was worried that my host may not like the bandwidth use, but I've never gotten any notices or slowdowns (that I know of), so I'm glad that I decided to host users' images in-house - it has worked out great. I'm pleased that users still like it after all these years, and I look forward to many more years to come. I've been thinking it's high time I got back into it and add to my own achievements. Getting all the devices and completing all my ribbons has been my goal from the beginning of the project. I encourage others to do the same, as KSP has only gotten better over time, and it's so much better a use of one's time than crushing candy or battling royals. Fly on, you magnificent, exploding krash-test dummies!

To be honest, I just don't know. I don't actually use that feature of HyperEdit, and I'm no expert in that area. I've inherited the mod from The Creator, and I didn't write that part of it. Sorry I'm of no help. Hopefully, some of the real experts will chime in here and help - they usually do.

Version 1.5.8 is the first item listed on that page, so I'm confused.

EDIT: All and none.

Where are you looking?

Sorry, I'm not fully understanding. Are you saying that KSP v1.5 reports that HyperEdit v1.5.8 is not compatible?

I've actually been meaning to post about a report I got saying that HyperEdit 1.5.8 (latest as of this post) works (at least partly) with KSP 1.5. So, my question is did you try it?

Welcome to the forum! There is no way to tell what's happening without complete details of what you're doing and how. First, remove all mods except HyperEdit and try it again. If you still have the same problem, please provide more information. What versions of everything you are using? Tell us exactly, step-by-step what you're doing and in what order. Include anything necessary for anyone else to reproduce the problem.

@Aeroboi, this is what I've found while testing my Windows 10 rig with 64-bit KSP 1.4.5, including the Making History expansion, and HyperEdit 1.5.8, in sandbox mode. EDIT: Oops! I had the issue numbers backwards, so I corrected them here and in the repo. I've confirmed this and commented created the issue on GitHub, with some detail. Please let me know if I'm off the mark (so to speak ), or if I've left anything out. https://github.com/Ezriilc/HyperEdit/issues/62 As for the "moving only East" problem with IJKL, I think that may be due to using the Lander to land on a different body. The user should orbit the body first with the Orbit Editor, then land on the body with the Lander. I noticed your screenie of the Lander has the warning: "Landing on a different body is not recommended.", which indicates this condition. This may be the work-around for the East-only problem. I've created commented the other issue for this. https://github.com/Ezriilc/HyperEdit/issues/44 Please also take a look at that and tell me if it feels right. I look forward to any and all input on this issue from anyone and everyone. Especially any code geniuses such as @Thunderous Echo, @linuxgurugamer, and @fronbow. But seriously, all input is welcome, from suggestions to pull requests. I hope this helps!

@Aeroboi, thank you for the excellent report and details. It does appear you're on to an issue that we've had in the past, but that I thought was at least partly fixed. https://github.com/Ezriilc/HyperEdit/issues/44 I have updated that issue with regard to the fact that the problem still exists. I realize this doesn't help you at all, and I'm sorry for that. I'm not an expert with KSP modding, so I don't know if I can actually fix it, but perhaps we can figure out a way around it. Also, someone seeing this may be able to help with the programming. I have been saved by this community many times so far. I plan to do some more testing of the specifics, and I will report back here in the next day or two. Please feel free to add any more input you may have at any time, here and/or in the GitHub issue.

Please try it without any other mods. You may need to install one mod at a time to determine which if any is the problem. Good luck and please let us know if you learn anything new.

Thanks for the follow-up. I feel your pain, but I'm glad it's working again. By all means, if you learn anything new, feel free to contact us again here, or on my site. Good luck! @Nightside, I just realized that I failed to answer your other question. I'm sorry for that, I must have been moving too fast that day. Please know that I don't intend to ignore you. It sounds like you're doing things properly, but if the Lander does nothing, then something is up, as it does work for me and other testers. I would need to know some more specific information about your setup and what steps you've taken. It's probably too late now, but if you still need help and/or have any questions, please let me know. I'm happy to help.

I've not heard anyone report this issue yet, and I cannot imagine how that could be related to HyperEdit, as it doesn't make any changes whatsoever to the terrain or buildings. That doesn't mean it's not happening, just that I can't see how. I recommend that you try a fresh install of KSP and HyperEdit, without any other mods. If you still have the same problem, I'd be happy to do some more testing, so please let us know what you find out.

Good news, everyone! I've updated my Craft Fixer tool (on the Craft Kitchen page), so it will recognize new (KSP v1.4.5) .craft files, as well as old ones. If you got the "Unrecognized file content" error, then this fix may help you. Please try it again, and report any issues you may find. http://www.Kerbaltek.com/craftkitchen

@Nightside: Yes! HyperEdit 1.5.8 works well with KSP 1.4.5. I've updated the note on the HyperEdit page.

Yes, I believe so. I will do a test and then post back here and update the note on my site.

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

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.

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.

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.

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.

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!

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.