Proot

I use a program called "Cubethesphere". My skybox is also generated with that program from my texture base.

I have an update really close to be ready. Lighter in memory but with better look, and with much better fps performance. I've improved the clods (textures and particles) in almost all planets, some terrain textures too. The hugest clouds has been converted to the EVE cubemaps, wich looks much better than the old system. I've overhauled the terrain scatters in all bodies and I've added that scatters in some bodies where before there hadn't. Now you can climb or hit the trees, rocks, cactus.... there are rocks and sea weed in the oceans. And well, wait to see the crags at Duna... We just need and update in EVE to solve a gap in the clouds, and I need to solve an inconsistency in the terrain scatter collisions (I guess is my fault somewhere in my Kopernicus configs, but its hard to find it). Then it will be released.

Rbray is pretty bussy lately with Dynamic Texture Loader, but I bet he gonna fix this as soon as he can. Anyways +1: IMHO is better to wait for a fix than just try to avoid it (if this were avoidable would not be an issue).

Ugh, I've spent a month precisely working in avoid the stock gap in the change from SS to PQS. That solution would make the change even more harsh than stock. Don't seem suitable for me. Anyways I'm not requesting a solution right now, I just want to report the issue and help to solve it. Many thanks for your help anyways!

I've tried the last github master version, but I still have the problem with the clouds altitude. Is this known? The clouds (not the shadows) dissapears in the change from Scaled Space to the PQS scales. So in Kerbin, as example, we have a gap in the clouds from the 160000 meters (end of scaled space) to the 55000 meters (PQS complete "deploy"). I've tried to change the heigths with Kopernicus. Changing the fade of ScaledVersion to 159000-160000 (instead 55000 to 60000) you can avoid the clouds gap but -obviously- then you have a gap where the terrain dissapears in the range of 60000 to 130000 meters (which is the fading of the PQS scale). This doesn't seem to left any error in the debug but I'll try to leave you here my logs ASAP.

I've been using the experimental version for a while. I must say that works very, very well, looks great and is truly perfect for a stock install. But for heavy-environmentally-modified installs (like with KSPRC), where the scenes become more complicated, the experimental version does a visible impact on frame rate. A similar thing happens with particles systems in Kopernicus and with Texture Replacer Relfections (which works in a similar way to your experimental version but generating a small cubemap of the scene). The fps drop is completely logical: if we stack several shaders (EVE+Scatterer and so on), particles (EVE+Kopernicus), huge textures (clouds, details and so on)... at the end we have a bottleneck. It's not your fault at all, maybe with Unity5 we will see an improvement in all this aspects but, meanwhile I want to do a humble request: would be possible to maintain both ways? I mean the current color config system and the experimental version, to be able to use one or other as needed?

I'm turning the biggest textures to the cubemap system and I must say this: congrats @rbray89, looks much better than the old system and with a sightly less memmory usage. The terminators and the colours of the clouds seem much more nice and accurate (not so dark at the sunsets/sunrises as with the "base" system"). Also, as you pointed time ago, the map look less deformed and "clean" with an equivalent texture quality. Very well done!

That is the smoke you see around in the launchs and landings.

Mainly caused by the normalmaps compressed in DXT, yes. And I don't know if you can change that behaviour but... despite that bc3 compression of the DDS/DXT format is quite bad in quality terms... something in the way where GIMP saves that format makes the results to be much better than with any other software. It uses some writing way whose artifacts are not so noticeable (those normalmaps get a pink aspect, instead the usual grey aspect). Recommended!

@rbray89, could be possible in the future to have light over the clouds until the terminators of a planet? Maybe even a bit of "tint" like in the previous EVE? And BTW, I was thinking in try again with the cubemaps, to avoid deformations and save a bit of memory, but I've seen that you are not using them in the last master update. May I know the cause?

Multiple lights/reflections is like finally put KSP at the graphical height of SpaceEngine. Congratulations Blackrack, is a truly remarcable hit!!

What honour! Many thanks!

Textures are generated and sized to look the better they can do it, related to the size of the bodie/object and the memory cost. That is usually the double of stock. Going to higher sizes don't add very much: will be not related to the PQS scales and color heightmaps are blurried by default, so you only get a bit of sharpness in scaled space, with an excessive cost of memory. The problem is not the texture, are the stock changes between PQS and scaled space, and I'm working on that, to avoid the "gap" effect and set the scaled space at more "correct" heights. I don't have the textures at higer resolutions, but I'll do it in the future, with the unity5, the official 64 bit windows version and the multithreading support. Just not for the moment.

In fact I appreciate the favor, a lot. If I dedicate my time to solve all this "small" things, with my crappy and slow english, all would be much more slow and worse... But seriously, I wait anxiously the update to Unity 5, basically with the expectation of send to the oblivion most of the memory problems... This thread has much more messages related to the memory usage than with the mod by itself. Anyways, as I've said many times in past pages: atm is hard to play this in dx9/windows without "tweaks" in your install; dx11/windows does it better but has some problems (as black Jool)... so the best choice, in memory saving and in general terms, -imho- is to force OpenGL in windows. I play with several mods (not parts), forcing OpenGL, without memory crashes. For me the only problem with OpenGL is the lack of antialiasing, but I can force it in the GPU options, so is not a problem at all.

Is not a "problem". The Ocean Shader in Scatterer is simply not finished yet. I've talked about this gap with @blackrack he will work on it, but he not even has a GPU right now... So if you want this detail "finished", sadly you need to wait. Of course, if you want/can lend him a hand to get a new GPU, probably the work will be done sooner: http://forum.kerbalspaceprogram.com/index.php?/topic/103963-wip-scatterer-atmospheric-scattering-v002182-24122015-ocean-shaders-get-them-while-theyre-hot/&page=1

I'm tweaking all those details and doing much more things. Feeling like... Please be patient.

Textures are like they are, no by caprice but to fit with everything else. You can add a lot of thing to the texture, but at the end it will not be in the surface, so imho that have no sense. I don't have as goal to add just eye candy to the game, I have as goal to enhance the stock game as much as possible. That means that what you see in the KSPRC texture is exactly what you have in the surface. With the Unity5 enhancements I have the hope of have more memory room to add PQS details to Kerbin with Kopernicus, wich could do similar changes, but at all levels. But is not possible atm, imho, with the current memory management/limit.

Yup. I'm pretty poor, lol, so I just can donate a bit from time to time. But there is projects here that totally deserve it. So when I can do it, it's not hard to find one to contribute.

I've done a contribution, to thank you for your efforts and to push for the continuity of this awesome project. Hope more people do the same to help if needed. Many thanks for your work!

Another great video! I love those overflights! You mind if I put these videos in the OP?

Procedural clouds are not fully compatible with rings (yet).

And he is over it... BTW, a very cool video DaZeInBok!

One small step for a man, one giant leap for kerbalkind. Happy year 2016!

It can't be compatible. WS uses the reflection plugin from Texture Replacer. KSPRC aswell, for his own textures. Please, be a bit patient. An update is coming with performance improvements and this time the reflections will be an optional feature. For those who want to use other textures mods, and so on.

May I know how you did to get the stock data about the land classes for this?