The White Guardian

Thanks! I've been having trouble with getting some clouds to show up though... I suppose layerVolume is unsupported on gas giants? Update: the layerVolume is NOT the problem. Could anyone lend me a hand here? For some weird reason EVE downright refuses to load clouds on a specific gas giant. Even with the in-game GUI, no matter what I do it won't do anything. And yes, I added the deactivateDistance PQS. If I need to supply any logfiles just tell me which ones. So frustrating when something refuses to work for no apparent reason.

Don't forget an atmosphere temperature curve that is separate from the atmosphere maxAltitude value

1. Nope, sorry. However, you can find & copy stock scatter configurations here. 2. I'm trying myself. I tried a .obj wavefront once but it made KSP puke. I'm currently trying to run the model through Unity and add a collision mesh in the process. I'll let you know once I figure it out.

Just a quick question - is it possible to disable the shadows on clouds? Not the shadows they cast themselves, but the shadow the planet casts on them? I'm trying to simulate glowing cloud layers.

I second this, thank you so much for uploading these @Sigma88!

Here you go.

I can explain this. It's because you put it in a folder named 'PluginData', KSP doesn't look inside these folders when loading, which is why they are used for Kopernicus' OnDemandLoading. The game itself doesn't load the textures, Kopernicus does. EVE has no such loader and uses textures already picked up by KSP, therefore don't place them in a folder named PluginData and they should work.

How long the travel time from Kerbin to Cerillion would be, I think.

Let me plan some transfer windows real quick. ... Done. Here's a plot showing transfer windows:

It's not used right now, but I might use it in the future. I'm trying to see if I can give the Sun a new texture as a Cyran expansion.

Consider it done. Worlds I can offer for the algorithm: - Cyran (Planet Cyran) - Sennim (Planet Cyran) - Protorin (Planet Cyran) - Cerillion (Planet Cerillion) - Kallahan (Total Rebuild) For Cyran, being a brown dwarf like object, I'll also supply some alternative textures to use so the planet becomes less repetitive. I'll also code some custom, procedural worlds for TBG if credit is given.

Could work, I'll look into it. Though I won't give the quicksand a sandy texture then, more like mud. I'll mostly take inspiration from Aridia from Ratchet & Clank, one of my favorite series:

Glad to hear it worked, and nice screenshot! By the way, everyone, I have an announcement to make. I'm working on several expansions for Cerillion, moons and mods (like replacing Kerbin with Cerillion). These won't be done anytime soon, but should freshen up the Cerillion experience.

@MalevolentNinja I think I know what the problem is. Looking at your mods list you use @Galileo's amazing work with SVE as clouds. The thing is that Cerillion uses textures from the default EVE cloud configurations, namely the detail, noise and particle textures. Here's what to do: 1. Go to the following page: https://github.com/WazWaz/EnvironmentalVisualEnhancements/releases 2. Download the file 'AnyCPU-Configs-Release.zip' 3. Go to your KSP's directory (the folder containing the KSP.exe file) 4. In the KSP directory, you should find a folder named 'GameData'. Open this folder. 5. Open the downloaded ZIP-file with any program. Inside is a folder named 'GameData', open this folder up as well. Inside is a folder named 'BoulderCo'. Drag and drop this folder into the 'GameData' folder in your KSP's directory. 6. To avoid unwanted cloud interaction with SVE, you can delete all files save for the following: BoulderCo/Atmosphere/Textures/detail1 BoulderCo/Atmosphere/Textures/uvnoise1 BoulderCo/Atmosphere/Textures/Particle/rgb BoulderCo/Atmosphere/Textures/particle/particle_NRM Make sure that these four files aren't deleted or moved, and are present on startup. All other files can be deleted, as long as these four are present. @Waz can I actually bundle those textures (given proper credit of course) in future versions of this mod to avoid this problem?

Scatterer is probably one of the most memory-consuming mods out there if everything is enabled. First thing you should try is reducing it to just the atmosphere shaders. If that doesn't do the job, reduce the texture resolution in KSP's settings.

Oh... oops Anyhow, it seems to be calculated internally, the SOI is larger the further an object is from it's referenceBody, and the lower the mass of the referenceBody compared to the object in question. There seems to be a function embedded in the game's codes doing this, but I don't see that much reason for knowing the exact function.

This is why I don't support CKAN myself, I have no idea what to do if something goes wrong. Could you check your KSP's GameData folder? Add to that, do the clouds appear in the map view?

I don't think so. I used the formula you provided and here are the results: Eve hillsphere provided by Kittopia: 185949494.965972 Eve hillsphere calculated using formula: 85109364.738244 A significant difference there, as the Kittopia version is about ten times as large. Therefore I think Squad uses an edited version of the formula for it to apply better to KSP's scale.

Yeah, I'll write a patch for that real quick. Give me a moment. Hmm, could you keep an eye on the altitude meter when descending? I have a gut feeling that I know what's going on. I was gonna give Glacia a redesign anyways, it's much too similar to Dres in my opinion.

@A Kerbal Engineer all necessary files seem to be in place. It could also be a mod incompatibility, try removing all mods but Cerillion, Kopernicus, ModularFlightIntegrator and ModuleManager. @A Kerbal Engineer Wait a minute... The KSP folder reads 'V1.2.0.1586' Hmm... I have a gut feeling that you installed Kopernicus for 1.2.2 or 1.2.1 while you in fact have version 1.2.0. Try the following Kopernicus version: https://github.com/Kopernicus/Kopernicus/releases/tag/release-1.2.0-3

Did you install ModularFlightIntegrator along with it? It comes bundled with Kopernicus as it is a dependency. Also, are you certain you are using KSP 1.2.1 and not KSP 1.2.2? If so, here's the last version for 1.2.1: https://github.com/Kopernicus/Kopernicus/releases/tag/release-1.2.1-3 Otherwise, use this one for 1.2.2: https://github.com/Kopernicus/Kopernicus/releases/tag/release-1.2.2-2

Yes, but the most convenient way would be the following: 1. Make an Imgur account (or login with another account like Google) 2. Upload the image there 3. Click on the image, and copy the link that ends with the filetype, for example .png or .jpeg. 4. Post the link in a message here and it'll automatically turn into the image. The KSP forums automatically does this with any image link that ends with a filetype extension, including Google Images searches. For example: LINK: http://i3.kym-cdn.com/photos/images/original/000/670/809/842.jpg And pasted in normally:

I think the problem was that you got to work on the ScaledVersion before even providing a template planet. Try to do that first from now on and see if the issue appears again.