The White Guardian

It's the cloud texture getting deformed a bit, as you can see the texture seems to have some kind of noise filter applied to it. I'm wondering if I can increase or decrease the strength of the effect. But it doesn't really matter anyway, it's a new EVE feature to reduce pixel-clouds iirc, so I might as well make use of it and apply a new cloudmap that better utilizes this new feature.

Alright, before I sign off for today, here's some last eye candy for you all. Also, this is probably going to baffle you all: the screenshot is Cyran + EVE + full-res textures, max-detail KSP. Guess my PC's specs. Thus, expect both quality and performance. I might even push out some sweet 8K graphics before release!

I've already informed Capt about this issue. I even told him how to fix the problem. I'd give it a maximum of ten hours before this mod is updated. To fix it yourself, you need to edit the files Sarnus.cfg, Urlum.cfg, Neidon.cfg, Thatmo.cfg and Tekto.cfg. In those files, find the value Atmosphere -> lightColor. Copy and paste the value of this entry elsewhere. Next, delete the lightColor value entirely and replace it with AtmosphereFromGround { waveLength = X } Next, replace the X with the value of the lightColor. Keep in mind that you should always use the same color in the same config, ergo, a value optained from Urlum's config should be used in Urlum's config only. I know, it may sound a little confusing, so if you'd rather wait (Just download Sigma's patch, it should be in the post above mine. Trust me, this guy's a Kopernicus ninja.) take comfort in the knowledge that it should be fixed very, very soon. I actually already fixed the issue in the configs, tested them in-game, then sent them to Capt, now I only have to wait for him to read it.

Big news: EVE support and FF ribbons inbound! Because of the sheer amount of different combinations however, you'll have to assemble the ribbons yourself. For that, you'll need GIMP for now, maybe I'll extract all of the textures so they can be added with other image-editing software later, but for now, GIMP's the way to go. Besides, it's free! (I could also add a version of Photoshop, problem is I don't have it so no way to save it in Photoshop's format...)

Hey, first off, congratz on the release! But now to my question, I'm trying to add cloud compatibility to Arkas:DevEdition for the next version, which is set to release this week. Problem is, the clouds look a bit... 'funky'. And that's only a mild case, in some cases it looks much worse. Any ideas as to what values could be the cause of this? I'm quite new to all those new features of EVE, you see.

Just delete lightColor and ensure the waveLength value has the same... well... value. I tested it with OPM (also broken) and it worked like a charm, I already messaged Capt about this. Now I'm thankful I haven't pushed out the updates for Arkas: DevEdition and Cyran yet, otherwise they'd require a hotfix.

Did you also revert the changes made to lightColor? Because it basically broke every Kopernicus mod out there that adds a custom-colored atmosphere, every atmosphere will have to be updated to AtmosphereFromGround{waveLength} otherwise.

The causer of the 'warp glitch', the planet I was orbiting suddenly warping a bunch of degrees in the direction it's rotating (imagine Earth suddenly skipping from 12:00 to 14:00, just POOF and the planet's rotated a few degrees further), the causer is HyperEdit. Don't ask me why or how, but it's HyperEdit. So, shoutout to all Kopernicus modders who, like me, use HyperEdit to check out their planets in-game for testing purposes, beware that this problem may occur. KSP 1.2 now has a budget HyperEdit however, found in the cheats menu. BTW, I'm getting the same logspam, according to the in-game logger. I kicked out the color values entirely in the config file of the planet I was talking about earlier, so that it now uses Laythe's default color settings, and it's STILL bugging my planet. What the hell is your problem, KSP?! Full .body logfile: Config: ---wait (checks) I'm such a big bloody imbecile. I altered the atmosphere twice in the same config.

Another edit: game works, planet does not, same error in the logfile. If I wasn't too lazy I'd paste in the link I posted earlier a second time... I was going for a blue atmosphere anyways, and because the planet was using Laythe as a template I just kicked out the color values, let's see what happens. As for the warping issue I talked about earlier, EVE wasn't the problem, now trying if HyperEdit is the culprit.

Hmm. After adding that glitching config the game started breaking, strangely enough it didn't with other planets that also used lightColor, only when I added the config of the planet in question the error started appearing in their log files as well. Or, at least, the game started breaking because of it. Yep, I totally get why you hate AtmosphereFromGround, @Thomas P. Alright, I commented out lightColor and added the same color value to AtmosphereFromGround{waveLength}, testing it now. Game works again, thanks, @Thomas P. Strangely enough, it worked fined with lightColor before I installed the last Kopernicus. No offense, but I think whatever you tried made it worse. Though, regarding atmospheres, there is only one word that comes to mind and only one man who can say it perfectly.

Use what now? Where do I need to place that value? Like this? Atmosphere { atmosphereFromGround { waveLength = x } } EDIT: I'm such a scrub. Looked at some Kittopia exports, found the answer right away.

Does that mean it was an internal error of some kind? Update: error persists. Same error.

Before I could stress-test I got a black screen at the space center. I removed my own planet mod, game loaded fine. I started adding configs back in until I found the culprit: [LOG 19:43:56]: Parsing Target ambientColor in (Kopernicus.Configuration.AtmosphereLoader) as (Kopernicus.Configuration.ColorParser) [LOG 19:43:56]: Parsing Target lightColor in (Kopernicus.Configuration.AtmosphereLoader) as (Kopernicus.Configuration.ColorParser) [LOG 19:43:56]: Exception Was Recorded: Exception has been thrown by the target of an invocation. at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0 at System.Reflection.MonoProperty.SetValue (System.Object obj, System.Object value, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] index, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0 at System.Reflection.PropertyInfo.SetValue (System.Object obj, System.Object value, System.Object[] index) [0x00000] in <filename unknown>:0 at Kopernicus.Configuration.Parser.LoadObjectMemberFromConfigurationNode (System.Reflection.MemberInfo member, System.Object o, .ConfigNode node, Boolean getChilds) [0x00000] in <filename unknown>:0 at Kopernicus.Configuration.Parser.LoadObjectFromConfigurationNode (System.Object o, .ConfigNode node, Boolean getChilds) [0x00000] in <filename unknown>:0 at Kopernicus.Configuration.Parser.CreateObjectFromConfigNode (System.Type type, .ConfigNode node, Boolean getChilds) [0x00000] in <filename unknown>:0 at Kopernicus.Configuration.Parser.LoadObjectMemberFromConfigurationNode (System.Reflection.MemberInfo member, System.Object o, .ConfigNode node, Boolean getChilds) [0x00000] in <filename unknown>:0 at Kopernicus.Configuration.Parser.LoadObjectFromConfigurationNode (System.Object o, .ConfigNode node, Boolean getChilds) [0x00000] in <filename unknown>:0 at Kopernicus.Configuration.Loader.Kopernicus.Configuration.IParserEventSubscriber.PostApply (.ConfigNode node) [0x00000] in <filename unknown>:0 [LOG 19:43:56]: Inner Exception Was Recorded: Object reference not set to an instance of an object at Kopernicus.Configuration.AtmosphereLoader.set_lightColor (Kopernicus.Configuration.ColorParser value) [0x00000] in <filename unknown>:0 at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (object,object[],System.Exception&) at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0 I'm gonna experiment a little further, but there was nothing out of the ordinary with the lightColor value. Could it be because the values had five decimals after the dot? (for example 0.74713 or something)? Ergo, if anyone recognizes this error, let me know what in the world I did wrong. Here's the atmospere part of the config.

I am experiencing a weird issue with the planets I'm developing, in KSP 1.2. Time Warp warps stuff quite literally, the planet or moon my spacecraft is orbiting suddenly rotates a certain amount of degrees in a certain direction, I couldn't quite see how much and in what direction, this behavior seems to be the result of timewarping. Mods installed: Kopernicus (1.2.1 release 1) EVE (the new 1.2.1 version) HyperEdit I've installed the latest Kopernicus and deinstalled EVE to test what the cause of the problem is, if it's Kopernicus or a conflict. I will also try without Hyperedit if the problem persists.

A-yup! Since I've given the pack one heck of an art pass, I need to update the entire OP as well. Ooh boy, this is gonna be a lot of work.

Alright, development has now shifted to the bugfixing phase. All left to do now is test the system and ensure that everything works as intended. And add a crap load of science defenitions of course. Really not looking forward to that massive task.

Exactly my plan: HD eyecandy for better computer systems, and less HD, yet still good-looking textures for machines with less power. Kinda. It still takes a good 30 minutes though.

Because of the new texture, a new biome map has been made, which also reduced the number of biomes from 16 to 10. Don't worry though, there will still be plenty to expore, you might even find a surprise hidden somewhere on Iltan...

Do you use any launch options? OpenGL, DirectX, or anything? Also, could you provide the following file: in your KSP directory, go to logs-> kopernicus and paste the contents of one of the .body files in a message here. It must be the .body file of one of the planets that is giving you the white ball syndrome. Also, for everyone who may be interested, a dev screen of in-game Iltan 2.0

@JadeOfMaar There is one problem however, the image I sent you is of a planet with 8K textures, and I don't want to blow up people's computers. Therefore it'll take a while for me to get things looking just as amazing in 4K.

Alright, I'll get to work on providing some amazing visuals.

Update: I've gotten Arkas itself to work on 1.2. No moons yet. I have to fix some minor issues and it'll be good to go. Expect an update next week!

Hmm... no, the preview image is an in-game screenshot, but as I said, I could alter it. Colors are easy to do, it's editing the surface layout that I do not want to do. I'll check SVE and SVT to see what you mean, and try and see if I can make the pack look more like that. @JadeOfMaar looking at the SVE and SVT threads, I wonder, is this more like what you are looking for? Because in that case, I'd be more than happy to provide.

Zerto has been remade, let's say it's a rather... strange world now. It also has 9 unique biomes to explore. Nope, that's not true. I just want to maximize exploration. I have no plans to change Iltan as is, though I may do so in the future. For now I just want to provide more content to explore. But I am curious, who did you mean by 'epic planet makers'? And what did you hope Iltan would get to qualify for 16 biomes?

Remade Dres: from 4 to 8 biomes. I'm now going to remake Zerto. "Putting in there to justify that"? What do you mean?