• Content count

  • Joined

  • Last visited

Community Reputation

803 Excellent

1 Follower

About Kobymaru

  • Rank
    Sr. Spacecraft Engineer

Recent Profile Visitors

3901 profile views
  1. It seems to me people aren't really believing me, so I made a Video: https://youtu.be/P2ADq1CVm0o I created a fresh (not stale) Flight plan, a creating a fresh (not old, and only one) maneuver node. When the time for the burn came, the node jumped. After the Burn Time, the maneuver disappeared. This is not the case. There is only one maneuver in my flight plan, and it's the one that is currently produced by the "Show on Navball" option. My issue is that it jumps at the beginning of the Burn. Also, switching to stability assist doesn't work well with nodes that aren't inertially fixed, does it?
  2. Nope, I triple-checked that. Recreated the flight plan, recreated the maneuver node, checked the reference frame of the burn, checked the plotting/navball reference frame, all should be correct. Still, when I start the burn, the maneuver node just jumps away. In another burn, I just tried to follow the node "for fun" and it jumped 3 times during one burn. I'm slowly but surely getting getting turned off from this Mod. While numerical stuff and the premise of N-Body gravity is amazing, the inability to execute even the most basic of flight plans makes this whole thing very un-fun to actually play. BTW, I have both situations as quicksaves, but they do require the whole Realism Overhaul suite, unfortunately. I did, this didn't change anything.
  3. It's already updated on CKAN? Neat. I'm afraid I have no idea what causes that, and we will be having a hard time debugging that. The trajectory drawing code is black magic to both me and PiezPiedPy, and I think even the original author Youen copy-pasted it from RemoteTech or something. I guess one day we should replace that code, but today is not that day. Sorry. You could create an issue here though, so we don't forget: https://github.com/neuoy/KSPTrajectories/issues It's hardcoded at the moment, but we can totally put it in the config. Please create a GitHub issue here: https://github.com/neuoy/KSPTrajectories/issues NP, we get this a lot. And I would need it in my own game too, but unfortunately it's just a bit too hard at the moment. If some nifty hacker wants to take that on, be my guest.
  4. OK, I still can't figure out how to do maneuvers using Principia. I created a flight plan with a burn. I engaged "show on navball". I aligned my ship. I am waiting for the "ignition" timer to count down to zero. As soon as the timer counts down to zero... the maneuver jumps! I am suddenly misaligned, ship starts spinning around, burn went all over the place. What did I do wrong? Performance and Polynomials are fun and all, but it's getting a bit hard to enjoy them when I can't execute basic maneuvers.
  5. Do you happen to have blizzy's toolbar? I believe the old versions didn't show an icon unless you "created" it in the Toolbar. If that's not the issue, make sure that the Trajectories.dll is there. If it is, please show me a Log File.
  6. Ok, do that. You could uninstall Trajectories and see if they still happen.
  7. Could you provide me with a quicksave file that I can load with only stock parts? Note that GitHub might prevent you from uploading the .sfs file directly, but you can rename it to .sfs.txt and it should be fine.
  8. OK, I get that. Still, why does the Node have to jump 90° when Principia thinks I'm done burning? That's just mean, honestly. Thanks, that helps a bit. Just tried it and it doesn't tick down, it keeps getting overwritten. I briefly considered kOS, but KSP is still a hobby and not my dayjob. I really don't want to start a whole software development project for each lander, and if RO supported it, I'd use the Stock Antenna system and role-played that I'm a Probe computer myself. Several hours over a 10-day period. I'll have to see what the in-game clock says, but what's for sure is that they are not agreeing. Thanks for the trick, I'll try that. Whoopsie, really? I've been wondering why my 8 GB system starts swapping after half an hour of play, but that would explain it. I doubt that the time difference is because of the memory, though. Feels more like principia does it's own time integration and doesn't synchronize it to the KSP clock. I do, and I still think the mod is amazing. I just think that it makes things harder than it has to. Why does it do that, though? Did somebody create a GitHub issue yet or have the devs mentioned anything about it?
  9. I had version 1.5, because I thought that's the last version compatible with KSP 1.2.2. This one still had the error regardless of reinstalling. Version 1.8 seems to work for me, and looks like it's also 1.2.2 compatible although it's marked as 1.3.0.
  10. [1.2.2] Realism Overhaul v11.5.1 - 06/12/2017

    @ILikeIke To add to that, after downgrading you should copy the whole install to a different location. KSP doesn not have DRM, so it's no problem, on the other hand you avoid problems whenever there is an update.
  11. So I have been trying to use the flight planner of Principia, and I have to say... it's a bit of a mess. It's especially hard to get it to work with RemoteTech, which is kind of a "must" for a realist experience with Realism Overhaul. The reason why Maneuver Nodes exist in KSP in the first place is not only for flight planning, but also as an Aid for Maneuver execution. Now Principia cripples this aid, and seemingly for no reason: Maneuver nodes disappear after the burn time is supposedly over. That wouldn't be too bad, except RemoteTech and Principia don't seem to agree on the passage of time (Did you happen to implement relativity? ) and over the course of a few days, the RemoteTech clock is a few minutes behind, starts the burn too late and then tries to chase a maneuver node that doesn't exist anymore. Why does this have to be deleted? Wouldn't it be better to just leave the maneuver node there? It seems that when checking "Show on Navball", Principia is constantly trying to overwrite the Maneuver Node. This seems like an OK idea until you actually try to do a Burn with it: first, you have no idea how much error you made and where to point the ship to correct it. Second, the timer and the Delta-V countdown is constantly stuck at the initial position. So how am I supposed to know when the burn is over? Do I have to use a stop watch? After a maneuver has been executed, the flight plan is null and void, because the real trajectory and the flight plan will never match up. That means, you have to Delete all maneuvers except the first, one by one by one Delete the flight plan Create the flight plan Recreate all maneuvers, one by one by one As you can see, this is is not particularly user-friendly. Couldn't there be a button with "refresh flight plan" or something like it? And maybe a readout that the flight plan is "stale"? Because it happened 3 times to me already that I executed a maneuver that was based on a stale flight plan accidentally, and ended up in a pretty useless Orbit. In the middle of the burn, about when my eccentricity went above zero, the maneuver node jumped to a different location, wrecking my burn. I checked both the Maneuver frame and the Plotting Frame, and both were on "non-rotating fixing center of the earth", with the Navball displaying ECI I'm kind of curious how people actually execute maneuvers, and whether I am the only one with RemoteTech. I understand that many things with Principia change and therefor not all concepts of the Stock game apply. But it just seems that Principia makes it unnecessarily difficult. For example, I absolutely don't understand the fight with maneuver nodes. Here, the Stock game has simple, intuitive concepts that could be wonderfully put to use in Principia. Why doesn't it? Instead of "Show on Navball", why can't there be a button that simply places a maneuver node exactly at the right time with the right burn vector? Then users could very easily execute the burn either manually (stock-style) or by slaving known tools such as the RemoteTech flight compuer or MechJeb to the maneuver node.
  12. [1.2.2] Realism Overhaul v11.5.1 - 06/12/2017

    Thanks, I found the setting and it was indeed enabled by default. Unfortunately, it does not seem to apply when the RemoteTech flight computer itself jacks up the the throttle: I get a failed ignition every single time and no attempt to perform ullage automatically. I also tried to program it into the flight computer by throttling up with main engines disabled and RCS enabled, but even then, the RCS blocks don't fire (they do when I put the throttle up manually). Do I understand correctly that my only option now is to CHEAT and manually perform ullage using the RCS controls that magically aren't locked down and have no signal delay?
  13. You could also just create an issue here: https://github.com/neuoy/KSPTrajectories/issues