Jump to content

OhioBob

Members
 View Profile  See their activity

  • Posts

    3,934

  • Joined

  • Last visited

 Content Type 

Everything posted by OhioBob

  1. OhioBob
    If you have scatterer installed but have deleted SVE_Scatterer, then you are getting scatterer's default configs and textures. That might be OK for your purposes, but it's not SVE. If you want SVE's scatterer configs and textures, then you should reinstall SVE_Scatterer and revert to the older version of scatterer. The dust storms in SVE have been turned off. I don't know the reason for this, but I'm guessing they either didn't work properly or were causing some problem. If you want to try turning them back on, you can find the config for them in the file StockVisualEnhancements/SVE_Configs/SVE_Clouds.cfg. If you scroll down you'll find the config for Duna-DustStorms, It hasn't been removed, just commented out so it doesn't execute. If you want to reenable it, just remove the comment tags // to the left of each line. I make no promises about what will happen if you do this.
  2. OhioBob
    @Vphurple Izumi, SVE hasn't been updated in years and is likely not compatible with the latet versions of its dependencies. I know for certain that scatterer v0.08+ can break stuff that's has been updated for it. I recommend reverting to scatterer 0.0772. I don't know if the current EVE works or not. You might have to roll back to an earlier version of it as well. I also see you have SVT installed. I strongly recommend against that. SVT was made for a very old version of KSP that had pretty poor terrrain quality. Stock KSP now comes with improved terrain that is far better than what you can get with SVT.
  3. OhioBob
    OPM requires Kopernicus, and Kopernicus turns comets off. If you want comets you need to use the stock asteroid generator (which supports comets), rather than the Kopernicus asteroid generator (which does not support comets). Find the file Kopernius/Config/Kopernicus_Config.cfg. Open the file and find the setting UseKopernicusAsteroidSystem. Change UseKopernicusAsteroidSystem from equal to True to equal to Stock and save.
  4. OhioBob
    We have no current plans to do that. If somebody else wants to write and release Parallax configs for JNSQ, they are welcome to do so.
  5. OhioBob
    I don't understand. But JNSQ is not configured to use Parallax. You should not be using it with JNSQ.
  6. OhioBob
    Why are you posting this in the JNSQ thread?
  7. OhioBob
  8. OhioBob
    Any unopened saves will be unaffected by the installation of RSS. After installing RSS, you should start a new game just for RSS. If at some point you want to go back to your old saves, you'll need to remember to uninstall RSS before opening them. Opening a non-RSS save with RSS installed could mess up your old save, possibly deleting some of your vehicles.
  9. OhioBob
    It use to be Kerbin sized, but 1/9 scale works better mathematically, so it has been changed. The mod is apparently retaining the old name because it is familiar. It's not unprecidented to keep a traditional name (why is the Big 10 called the Big 10 when the conference has 14 schools).
  10. OhioBob
    Yes, about 2500 m/s at an altitude of about 80 km. About 2400 m/s at 150 km, and about 2300 m/s at 220 km. Because at 1/9 scale, orbital periods are exactly 1/3 what they are at real scale. So Earth can be given an 8-hour day, and all the planets will retain their familiar real life orbital periods when measured in days. That is, Mercury will orbit in 88 days, Venus in 225 days, Earth in 365 days, etc.
  11. OhioBob
    Yes. If you use Sigma Dimensions and Rescale, the OPM planets will be rescaled along with the stock planets.
  12. OhioBob
    Interesting. I would have thought @*,* would have worked. Although JNSQ uses "Class", not all planet packs do. Some use "Value", though it really doesn't matter name is used, it can be anything. The first asterisk is suppose to be a wildcard that will work with any sub-node name, and the second asterisk is suppose to apply the change to all instances where that sub-node name appears. @R-T-B, has @*,* ever been tested to assure that it works? Perhaps you should do something like this just to cover all the bases: @landClasses { @*,* { @color = 0,0,0,0 @noiseColor = 0,0,0,0 } @Class,* { @color = 0,0,0,0 @noiseColor = 0,0,0,0 } @Value,* { @color = 0,0,0,0 @noiseColor = 0,0,0,0 } } I think I may have seen other posts where people have reported ColorFix.cfg not working, though I could be getting confused with something else.
  13. OhioBob
    I've never seen anything like your first screenshot. That being said, ghosting can occur when rescaling if you don't refresh the cache, though it usually doesn't look like your screenshot. If you haven't already done so, I recommend deleting the .bin files located inside the GPP/Cache folder, and restarting.
  14. OhioBob
    Logs might as well be written in Egyptian hieroglyphics for all the good they do me.
  15. OhioBob
    I'd like @JadeOfMaar to give his oppinion on this. As far as I'm concerned, it can all go. None of it is worth keeping if it has the potential to cause problems. The only possible exception that I wouldn't mind keeping is the Skybox**, but only if we can be certain it is working bug free. The rest of it I've never really been a big fan of, and I certainly wouldn't be broken hearted if the skybox goes as well. Generally speaking, I don't like frills and extras that do little to enhance the game. The maintenance and risk of bugs isn't worth it. ** GPP has it's own sky box, assuming it is working. Honestly, I haven't really noticed if it is or not.
  16. OhioBob
    Yeah, I really don't want to lose HeatShifter. Sounds like something is going to be broken no matter what I do.
  17. OhioBob
    It looks like there's an error in the config. GPP adds BG surface features to the GPP planets only when GPP is installed in its normal primary mode. But then it removes all BG surface features not added by GPP regardless of whether it is installed primary or secondary. It should remove those features only in primary mode, not secondary. Or else it will strip the stock planets of all their surface features. I think the fix is to add a no GPP_Secondary condition to the removal. Try this... Find the file GPP/GPP_Configs/GPP_ROCdefinitions.cfg, and change the first line to the following: !ROC_DEFINITION:HAS[~Mod[GPP]]:NEEDS[!GPP_Secondary]:LAST[GPP] {} I've been made aware that Sigma Renamer has been causing crashes, but this is the first I've heard of any issues with Sigma Replacements. I've already decided to delete the Renamer from the next release. I might have to delete the Replacements as well.
  18. OhioBob
    What is "eva science kit"? Are you referring to the deployable science parts that came with Breaking Ground?
  19. OhioBob
    @Wilds, while it is OK to modify Realistic Atmospheres for your own personal use, be advised that distributing your modifications is a violation of the Realistic Atmosphere's license. Specifically, the NoDerivatives clause. Creative Commons — Attribution-NonCommercial-NoDerivatives 4.0 International — CC BY-NC-ND 4.0
  20. OhioBob
    I really don't understand what the problem is. You're going to have to describe it in more detail.
  21. OhioBob
    That's something I'm going to look into for the next release. But presently I don't have a solution.
  22. OhioBob
    The renamer is going to be deleted from the next release.
  23. OhioBob
    I don't know.
  24. OhioBob
    That's good. I'm going to try to fix it for the next release.
  25. OhioBob
    I've never tried it, but it looks to me like the GPP Research Bodies settings are intended for primary mode. Though it makes no distinction between primary and secondary, so the same settings will likely work in secondary mode as well, even though those settings may not really be appropriate for secondary. It could probably use some tinkering. Also note that the Research Bodies settings uses the name "Kerbin", which applies only to primary. In secondary it is named "Gael".
×
×
  • Create New...