Jump to content

OrbitalManeuvers

Members
  • Posts

    1,610
  • Joined

  • Last visited

Everything posted by OrbitalManeuvers

  1. I think it's safe to say I don't know what I'm doing with these parts ... but they're fun anyway
  2. It's not. I have a very minimal install where this is happening to me, too. Here are some things I'm extremely confident about: - there are no modifications of cfg files happening. The mod remains binary identical to the distribution files whether the game starts up and works, or whether it starts up and fails. This is easily confirmed by observing that MM doesn't recreate the cache on startup. - I cannot deny that although it completely defies logic, there does appear to be a cyclic nature about the failures. In other words, it will work for a few starts, and then not work for a few starts, rinse, repeat. These are restarts where identical keystrokes/mouse clicks are performed at every start, and different results are observed after loading the same game every time. I'm also doing identical keystrokes/clicks to exit, since I know KSP can write things at exit that change the next startup. I'm the first to say that this observation sounds insane, but something is causing this, and it's not a cfg change. - The one glimmer of hope that I had for a brief moment was a difference I found in the persistent.sfs file that had to do with KK's initialization. After further testing, the difference seems to not affect the actual outcome of the issue. In other words, it can fail or work with or without this initialized flag being set. I've spend a lot of time restarting KSP over and over and don't really have the drive to pursue this much farther. Hopefully someone will discover what's up with this.
  3. huh, am I misunderstanding what this mod is? It says this is a fork. That means it's all of the Katniss files, plus TruthfulGnome's changes. So we shouldn't be installing this over top of the original Katniss version any more, right? Looking at the Katniss folder "earthConfig" and this mod's "Patches" folder ... they contain pretty much the same patches, so it seems like you wouldn't want to have both. Unless it's Confused Thursday, which is always possible.
  4. You don't want or need BoulderCo. Those are configs for eve/scatterer, but KSRSS has all that built-in, so they're possibly conflicting. edit: whoops didn't refresh - same answer already given. womp.
  5. There's something else up with this file, too - because I don't have one anywhere on my F: drive, and there are 6 KSP installs there (1.12.2 and .3). I've actually never had a player.log file and I've been playing KSP since 1.7.
  6. Thanks for the reply. Am following the thread so I'll keep an eye out. Just in case you ever need this: https://gitlab.com/ksrss/KSRSS. But if all you need are some grep outputs I'd be happy to help.
  7. Hi - wanted to share an observation I've been having and see what role DOE plays in this. Here's a screenshot: (It probably needs to be expanded to full size to see the issue I'm asking about) So this is an atmospheric probe descending into Saturn's atmosphere. The issue I have here is Earth, Mars, and Venus. They are perfect little textbook-colored dots, whereas the rest of the starfield has been dimmed as expected since we're looking right into the sun. Does starfield dimming not apply to planets as well?
  8. Do you have any interest in adding a KSRSS @ 2.5x scale to your app? It's a pretty common setup these days and I'd love to give your stuff a try. If you need any data from a working install, I have several, and would be happy to help out.
  9. I clipped this out of NASA's RFC video. It's the "30-day stay" version of a Mars trajectory. I thought it was interesting that the video said this trajectory "may" include a Venus fly-by. Obviously that would add another constraint to the launch window, but it's an interesting trajectory. Neat to see a trajectory completely outside the standard Hohmann Transfer window. They do have an alternate that uses minimum energy, but the stay at Mars like is 500 days, and they're currently thinking that the 30-day plan is more attainable. I feel compelled to attempt this in KSP, naturally. Here's the rest of the mission architecture for anyone interested:
  10. The slightest inclination difference will cause the stock planner to wait forever. It gave me a transfer window from Kerbin to Mun weeks in the future. That was my last time using it - it's not good. This, plus Kerbal Alarm Clock, is still the best solution, especially for custom planet packs. I use this on both KSRSS and JNSQ.
  11. I had this problem as well. You didn't mention if the antenna is having an issue, too - but I think you'll find that if you place the core, then the antenna, then save it, then re-open it, the antenna will have lost its support struts, and the node it's attached to is now broken. If you take off the antenna you won't be able to attach it again. This was in addition to the verniers randomly moving around as you noted. I found something that fixes it on my machine, and I can share it with you with the normal caveat: it's not a good idea to change a mod's files directly. I didn't know how to do this with an external patch, so here's the brute force method that works on my installs. Idk if it will work for anyone else, and I don't recommend following my advice . But this is what makes it work for me:
  12. There is a node there for me, however, it's not visible. I think its positioning is juuuuust a smidge too high and that prevents KSP from showing it maybe? Anyway, an engine will attach there, and if you clip your camera into the part you'll see the center node.
  13. Some info here maybe: https://github.com/CobaltWolf/Bluedog-Design-Bureau/issues/1096#issue-997948637 unless you mean in flight?
  14. Hello, I've run into something on a new install that I haven't seen before. In the first screenshot, there are 10 snacks which show as 3 days. In the 2nd screenshot, there are 15 snacks, and now it's a year. The snacks/days progresses like this: 5=1d, 10=3d, 15=1y1d, 20=1y2d,25=2y36h ... 50=4y72h I've included a log file below, but this is running on GEP Primary, scaled 2.5x. Here's my log file: https://drive.google.com/drive/folders/1tcbYyhCIizhvwCWfi2jzt-r4q14vZM22?usp=sharing Thanks for any help!
  15. I was kinda aiming for a launch that did include a launch stand, but didn't include anything that MAS would get involved with, just to see if that helped.
  16. So, you have megabytes worth of NullRefs from MAS components. What happens if you launch just a probe core on a launch stand? edit: now that I think about it, MAS probably inserts itself there, too.
  17. Hope this helps a little. It's not perfect but it's close... I got this position on the pad: Using this position in the VAB:
  18. What is it you're trying to do? KSRSS comes with everything you need for both Eve and scatterer. You don't need to move anything or put anything anywhere, it's already inside the (correctly installed) KSRSS folder, and you just need to install Eve and scatterer.
  19. Actually, I think there is a problem currently. This began when the white paint scheme was introduced on the Centaur. I notice the patch says specific things about the orange subtype but nothing about the white. Removing the patch fixes the startup error. Any ideas?
  20. in my experience, the back wheels likely don't need to be motorized, or steerable for that matter. You can always re-enable the back wheels motor for slopes/etc.
×
×
  • Create New...