gnivler

Members
  • Content Count

    27
  • Joined

  • Last visited

Community Reputation

3 Neutral

About gnivler

  • Rank
    Elon Musk fanboy

Recent Profile Visitors

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

  1. Is there an issue tracker being used anywhere? It looks like Github is out of date despite the mod being updated (and thanks for that @pizzaoverhead!) It's a loaded question, and may not be a bug and I haven't thoroughly tested it, but it I'm hearing the sounds persist for a while after throttle cutoff (with zero monopropellant being consumed).
  2. Can you please upload a craft file to test against?
  3. My suggestion is try stock + RT to see if they persist. If you can replicate them, open issues on the tracker https://github.com/RemoteTechnologiesGroup/RemoteTech/issues. There are some problems with the FC on Windows at least, where old instances remain visible and functional but essentially fail. Closing the FC window and opening it again is the only workaround I'm aware of there (see https://github.com/RemoteTechnologiesGroup/RemoteTech/issues/578) I'm interested to test the manual burn and warp problem if it holds up. Sorry, I'm not sure about the slave status offhand... new to RT. Is it possibly an indicator of a relay(ed) connection?
  4. Thank you!!! I was incorrectly assuming that my current orbit would have a suitable intersect with the other 2 but I was too high up. I could have found it if I did a couple orbit+ clicks but didn't think I needed to. Once I lowered the orbit I was able to dial in a maneuver that put me behind the trailing satellite and saved me from going to bed grumpy.
  5. Hoping someone can point out my mistakes, I'm at a loss with something very basic... I'm working from the tutorial http://remotetechnologiesgroup.github.io/RemoteTech/tutorials/c16network/ and have built this around Kerbin 3 times. Now I'm trying to do it for Mun and have 2 satellites up with good separation and sync (altitude 1700 with separation 2545.58KM) but every attempt I make to set up the 3rd results in it being on top of one of the other 2. My process is targeting the previous satellite, setting the apoapsis marker at the target altitude and with that separation to target. I can use either satellite as the target but the other is always waiting at Ap. I've tried eyeballing 90 degrees but the separation values don't make much sense. I'm assuming this is a simple mistake but I'm too stupid to figure it out.. so please, any help would be appreciated!
  6. That's what I was thinking. There are both sets though... egg/conic fairings that both decouple and don't, and interstate fairings that both do and don't decouple. I think.. not at my PC. I need to build bigger rockets.
  7. I'd rule out my system... validate Steam files.. go back to stock + PF, new sandbox career. See what happens. Since the build for 1230 i haven't had any problems.
  8. @TK421d maybe you're using the structural fuselage parts instead of the aerodynamic fairing parts? The prior don't decouple by design.
  9. @edog300 I'm not sure if you want issues reported (at all, or here). It appears that in some cases, the fairings will reset to the first stage if you click Reset in VAB. Minor issue obviously (if it's not just me). I love this mod, thank you.
  10. That method of burning from LKO to hang Ap over the AN/DN is awesome. Thanks!
  11. Thanks for the post, very good info. I was doing some quick searching trying to figure out if there was another way to do this... you're fairly sure you have to eyeball it? I have OK results by lining up the AN/DN on the launch pad, rotating to the desired inclination etc, but it's not as accurate as I'd like.
  12. Thank you for working on this! I noticed that Steam has a pre-release branch (build 1228) as well as the regular branch being 1.1 with build 1230. I've got the latest PF release on build 1230. I can't resize the base or attach fairing walls. Figured you already know this, but just in case not.
  13. Is that what would be required for the warp button? I have no idea. That does sound like overkill if so. I don't agree that it's with the counter-intuitive or that (most) people couldn't figure it out. The usage guide for this mod would be succinct so there's that as well. Alternatively It could be an option.
  14. I like this as well another idea.. 'warp to next node' as provided by stock, just as a button on the UI and the smallest possible correction, in grammar. On the key bindings window it says "Show less trajectories" but the proper wording is 'fewer'.