Cilph

Members
  • Content Count

    536
  • Joined

  • Last visited

Community Reputation

172 Excellent

About Cilph

  • Rank
    Codes using butterflies

Recent Profile Visitors

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

  1. Originally there were no cones, then planetary cones were added, and the satellite targeting was never adjusted to work with a cone. Not much effort to change it though. I think. I've rewritten that section three times since then and the official release is still using the first revision .
  2. About comparing distance to signal delay, there's currently an issue where the signal delay is calculated wrong and not only scales with distances, but with number of satellite hops. It's on the list of things to fix. *rolleyes*. Related, the project is definitely in need of more contributors. Some management positions have opened up and more help with coding wouldn't exactly hurt.
  3. 64-bit has strange issues with research, might even be related to stock rather than RT.
  4. If anyone is interested in joining the Remote Technologies Group, the group that now maintain the mod, just contact Erendrake, Starstrider42, Peppie23 or Warrenseymour. Even better: just start improving it and submit a pull request on GitHub. There's plenty of bugs to fix!
  5. With the default range model, if A's strongest dish is 50Mm, and B's strongest dish is 70Mm, you need to get within 50Mm of each other.
  6. I agree with Xiong on some points, but the best way to get your voice heard is to put in a feature proposal at the GitHub issue tracker. For example, I just wrote out this proposal: https://github.com/RemoteTechnologiesGroup/RemoteTech/issues/111
  7. Much thanks to Warrenseymour, Starstrider42, Erendrake for continuing the project!
  8. So it turns out Amaroq might not be present anymore. Would all parties interested in taking over the project contact me over PM so that we can sort something out over the coming week? Hoping to make this community developed, but it would require one or more people coordinating everyone. Of course, if Amaroq shows up and is willing, all is well.
  9. I put my source online: https://github.com/RemoteTechnologiesGroup/RemoteTech Handing over the reigns to Amaroq. I hope he can get a community developed continuation going. So if you're interested in contributing, go ask him. Not that I can make demands, but I'd prefer if the code was kept modular and testable, so that it can perhaps be used as an example for other future modders. RemoteTech 0.22/0.23 will not be on Curse as I don't approve of them, but do whatever you like for the next version. Putting the releases on github via either their release system or static webpage would be a nice way. Peace.
  10. Boycotting Curse by the way. RemoteTech will be spread via the GitHub repo. GitHub has an excellent release system these days.
  11. GitHub should have project transferring functionality. I'll handle it.
  12. As said, not entirely stepping down yet, I'd like to finish what I'm currently working on even though it might have a bit overkill architecture. Though perhaps I should let everyone in on that mess of a build instead of keeping it till it's done. I'd like to take a lead position still as it requires less time than coding the damn thing. For documentation, starstrider42 was working on a full user guide, and my go-to guy for modelling is Kommit, who did an amazing job on the KR-7 and KR-14 dishes. So, should we convert the project to a community effort then?