Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by OhioBob

  1. Certainly. Go right ahead and add it. Thanks.
  2. Unfortunately only Galileo can edit the OP since he's the one who created it. And he's not around anymore.
  3. I don't know much about the KK stuff. @JadeOfMaar might have to look into the problem for us.
  4. In Kerbin's properties, try setting solarRotationPeriod = False. I don't know if that will fix it or not, but it's worth giving it a try.
  5. There should be. Ceti is suppose to have some Breaking Ground stones and boulders.
  6. Transfer Window Planner and Trajectories work fine with JNSQ, or any other planet pack for that matter. I don't know anything about [x] Science. JNSQ is not configured for Parallax, thus Parallax is not recommended for JNSQ . However, since Parallax is designed to modify the stock celestial bodies, and since JNSQ uses the same names as the stock bodies, Parallax will modify JNSQ. However, those modifications are designed specifically for the stock celestial bodies and not the JNSQ's version of those bodies. Therefore there is no guarantee those changes will look right or work right. There's nothing stopping you from using Parallax with JNSQ, but since neither product is designed to work with the other, don't ask for help if you have problems. Also note that Parallax will not do anything to the additional bodies that JNSQ adds that do not share names with the stock bodies.
  7. The atmosphere multiplier stretches the existing atmosphere curves, while atmoTopLayer extrapolates them. For example, let's use your mulitplers and the stock Kerbin atmosphere, which is 70 km in height. The atmosphere multiplier stretches the existing curves to a height of, 70 * 1.1 = 77 km. The temperature and pressure at the bottom, middle and top of the atmosphere is exactly what it was before. It has just been stretched out to a new height. The atmoTopLayer multiplier then extrapolates the atmosphere from where it left off up to a new height of, 77 * 1.18 = 91 km. Sigma Dimension computes a rate of change from the existing pressure curve, and then uses that rate of change as a basis for the extrapolation. In the 77-91 km range the atmospheric pressure should decay exponentially so the pressure at the top of the new atmosphere is much lower than it was at the top of the old atmosphere. Regarding MechJeb, I know nothing about that. I have no idea why you seem to be experiencing drag above where the atmosphere ends. That shouldn't happen. But since it's apparently not a Realistic Atmopheres issue, it's not my concern.
  8. This is likely due to the kerbal renamer and possibly kerbal replacements, both of which have been known to be buggy. I recommend deleting the folders GPP_Renamer and GPP_Replacements. That should fix the problem.
  9. The only way I know to figure out what objects are available is by looking configs for the celestial bodies and see what they are using. You can find that here: kittopia-dumps/Configs at master · Kopernicus/kittopia-dumps (github.com) As far as accessing the hidden files, I don't know anyway to do that. Perhaps there's a way to decompile files, but I don't know anything about that. That's not my area of expertise.
  10. The Kopernicus Wiki gives much of that type of information. Scatters specifically are placed using a PQS mod called LandControl.
  11. You're probably thinking of Explodium Breathing Engines. There are no plans to add anything like that to this mod because that mod still exists.
  12. UPDATE Version 3.0.2 Changelog Fixed Eve optimized options on Reliant and Swivel engines for KSP 1.12.2+ Deleted old deprecated parts. See opening post for download link and instructions.
  13. 16 km is Hale's computed SOI at 2.5x scale. Likewise, 58 km (as seen in the screenshot) is Ovok's computed SOI at 2.5x scale. So what is apprently happening is SigmaDimensions is resizing the planets, then the SOIs are being computed using KSP's internal formula. The sphereOfInfluence parameter is not being used at all. I have no idea what would cause such a thing to happen. @tmccreight651, obviously you are using SigmaDimension to do the rescaling, but what configs are you using? Are you using Rescale, Rescale Continued, your own custom configs, or something else? (edit) I just ran a test in a minimum install with OPM and SigmaDimensions. The only settings I changed where the Resize and Rescale multipliers to 2.5. SigmaDimensions correctly rescaled the SOIs of Hale and Ovok. So that tells me SigmaDimensions is doing what it is suppose to do. The bug is most likely due to some unusual mod interaction.
  14. I doubt you'll get a response. Sigma88 (maker of all the Sigma mods) hasn't been around for a long time. As far as I know, he has stopped maintaining all of his mods.
  15. The renamer and replacements mods have been a source of occasional complaints and bugs since the beginning. I've therefore decided to strip GPP of all the unnecessary frills and extras and just get down to the basics of providing a planet pack. I just don't want to have to deal the the maintenance of all those extras.
  16. You're going to have to do what Poodmund said and take up the issue with the maker of whatever rescale mod you're using. The SOIs shown in your screenshots are actually smaller than what they are in the OPM configs -- Ovok's SOI at normal scale should be 94 km and Hale's 41 km, yet the screenshot shows them as 58 and 16 km. So clearly something is screwing up the SOIs, making them smaller rather than larger. This is not an OPM problem. (edit) I've figured out what's happening, but I don't know why. For some reason the sphereOfInfluence parameter is being ignored and you're getting the KSP computed SOI values for Hale and Ovok. I suspect this is some sort of a problem with the rescale mod or Sigma Dimensions. Certainly not an OPM issue.
  17. Are you sure you applied the patch correctly? You should take the text that Leganeski gave you, save it as a plain text file but with a .cfg extension, and then place the file inside your GameData folder. I see no reason why it shouldn't work.
  18. I've never used any of the replacement stuff, so I don't know how it is supposed to work, or even if it does work. All the replacement stuff is scheduled to be removed from the next GPP version.
  19. I also recommend KSPCommunityFixes. It repairs a bug that interfers with the correct placement of ground scatters.
  20. @SpudNutimus, adding to what Jade said, if you need to reselect your terrain detail settings, be sure to first delete the settings.cfg file in your KSP folder. The next time you start KSP after deleting the file, KSP will rebuild it. You'll have to go into settings reselect everything.
  21. Aside from being incompatitble with 0.08+ versions of scatterer, I think SVE still works fine.
  • Create New...