Jump to content

Galileo

Members
  • Posts

    7,298
  • Joined

Everything posted by Galileo

  1. Can you send me your output log and a screenshot of the inside of your EVE folder?
  2. You didn't follow instructions. Only use the Kopernicus, MM and module flight integrator included in the download.
  3. Well, for starters, you are trying to run a bunch of mods on x32 bit. you are likely running out of memory. use the x64 bit version.
  4. that is a known bug with scatterer in 1.3. Scatterer is not updated for 1.3 and causes floating terrain tiles. Disable the ocean shaders
  5. No biggie! it doesn't bother me that it happens and its really to fix, just a little inconvenient is all. I just thought I would help try to get to the bottom of it.
  6. I looked at your output log and you are on 1.3, which is good, but you have Module Manager 2.7.6 in your gamedata, which is for 1.2.2, which is bad. Remove it, and see if the issues go away. Also, delete the MM cache before you start the game again.
  7. SVT works perfectly with 1.3 btw. I just havent updated the version file or thread
  8. @EspenB89 please provide the required trouleshooting items: Output log screenshot of your GameData folder
  9. Nothing will be broken really, unless you have a ton of bases on the surface of bodies. KSP changed the PQSMods library so the new terrain features I added last update were destroyed. I had to rewrite them all again, multiple times. So the terrain will be different once more, but closer to what is was prior to 1.2.3. we also decided to move ahead and delete the CareerSaver cfg from the download, so if you are playing a career that started pre- GPP 1.2, you will have to use the CareerSaver from the older versions. But any vessels in route some where or in orbit will be fine.
  10. there isn't a solar panel issue. If you are using mods that change solar panels at all, like Kerbalism or amp year, things will not work. Or, you can try going into the kopernicus config folder and adjust the solar panel cfg to not use kopernicus solar panels.
  11. It may not happen with the stock system. It may be an conflict between hyperedit and kopernicus. The best way for you to replicate the issue is to install kopernicus and hyperedit to anywhere. Sometimes it does it, other times it does not, but most of the time it does. With how popular kopernicus and planet packs are, I'd say it's definitely worth looking into.
  12. I guess it may be good to mention that I pretty much exclusively use hyperedit along side kopernicus. As hyperedit is invaluable while editing bodies
  13. @Norcalplanner it will be soon. Slowly but surely, dependencies are updating and we are updating as quickly as we can to catch up to the changes. Some guys are on hiatus and some are busy with RL so the going has been a little slower than usual, but it's getting done
  14. So, you made a kopernicus cfg, not a plugin. If you aren't including an actual plugin (.dll file) then you don't really need a source as your cfg is the source. Now, if you include a .dll from another mod or you make one yourself, you have to include a source. This to to ensure you aren't including a plugin that could harm someone's computer
  15. Ok cool, I'll look into it when I get a chance, but I'll be pretty busy for the next week or so
  16. does the update work with the new kopernicus solar panel stuff? Or is this just a 1.3 maintenance update?
  17. Does it cause the game to be unplayable at any point or does it break the mod in any way?
  18. I talked to nathenkell about this recently and you can actually put height maps and biome maps inside a PluginData folder. Only normal maps and color maps needs to be outside of the PluginData folder that way your load time isn't as bad
  19. Sounds like you downloaded Stock Size Real Solar System.
  20. Because the game recognizes Earth as kerbin due to kopernicus favoring displayName over cnNameLater. Not a bug.
  21. If nothing is changing, then you have definitely not replaced the SVE sunflare.
  22. That is something that only happens with hyperedit. My guess is hyperedit is too fast, and the celestial bodies do not have time to fully load the planet. It doesn't break anything and a quick trip to the tracking station and back to the vessel fixes the issue, but it happens quite often and can sometimes destroy a vessel if you run into one of the not-so-fully-loaded sections of the body. It indeed has something to do with hyperedit though. It been like that since 1.2
  23. Well, because Squad does not want to change its minimum requirements to play the game. It wants to keep the players with crummy pcs and Macs playing. I assume for fear of loosing potential monies.
×
×
  • Create New...