Jump to content

Galileo

Members
  • Posts

    7,298
  • Joined

Everything posted by Galileo

  1. I’m not sure what you are trying to say, and your logs don’t have any errors.
  2. You have SVT installed, not SVE. This is not an EVE issue. Post your issue on the Kopernicus thread.
  3. Or start a new career. Adding a Kopernicus to an existing career with vessels in orbit, will break the solar panels. All newly created vessels will be fine, but the existing orbiting ones will be broken.
  4. You can continue once kopernicus is update, which it already is OPM is compatible with 1.4.3 as well. I just need to update the OP when I get some time
  5. That is an issue with how the plane was saved in whatever 3D program it was made in. Whoever made it didn’t apply the correct settings to the shadow options in blender or they never intended for flags to have transparency. It’s not really an EVE issue. If it’s squads flag model, then they would need to change that and I doubt that they will. My suggestion is to recreate the flag with an opaque background.
  6. Well, Kopernicus is version locked and doesn’t work I’m newer versions until it is updated for that particular version. Nothing we can do about that. It’s never recommended to update KSP when using a planet pack. At least you know for next time to make a back up of your ksp install. Lessons learned
  7. You really believe many people don’t use them? SVT is used A LOT and improves performance. It raises the scatter amount, provides higher res textures, and enables colliders on all objects that aren’t grass. So I would suggest taking a look at it. Not having boulders, trees and grass is depriving users and yourself from an immersive experience in my opinion. I’m kind of surprised you don’t have them in your planet packs
  8. You just need to use the old bundled kscswitcher from a previous version.
  9. No. KK is broken with the current SigmaDimensions and KKtoSD.
  10. It’s a lot to look over. The fix for you implemented with @SpaceCenter won’t work because there is not a SpaceCenter node in the template, so it doesn’t change anything. The landControl cfgs I use are straight from Squad. If they have an extra color parameter, then so do I. I chose not to use BumpedDiffuse. All that does is allow the textures to use a normal map. This can slow performance. Diffuse is easier for potatoes It’s odd that your cfg for colliders doesn’t get errors. It accomplishes exactly what my cfgs do, just in a slightly different way. I also didn’t delete the old colliders parameter from the cfgs, which shouldn’t hurt anything. I’ll have to try out your cfg for myself. Thanks for the testing and the reports.
  11. It’s a bug in kopernicus. The dev knows and is working on a fix.
  12. Yeah that change would need to come from their end unfortunately, or fortunately depending on how willing the dev is.
  13. OPM Galileo can be removed completely. The new OPM should also be available for 1.3.1, so any old instance of “ OPM Galileo” should be wiped.
  14. @HebaruSan is there anything that can be done to just remove the old “OPM Galileo” from ckan?
  15. If you mean the orbit lines are jittery, then yes, that’s normal. It’s a bug in KSP. Bodies were not meant to be placed outside of Eeloo, and when they are, you get that issue.
  16. I don’t think QA is what you think it is OP. It’s not a fun gig.
  17. It is scatterer related is and is caused by a bad cfg. Do you happen to disable scatterer eclipses? i used to have an issue like this with SVE and it turned out to be people disabling the eclipses. I forget what parameter needs to change. It’s been so long since I have seen the issue.
×
×
  • Create New...