R-T-B

This is what I was referring too. Already off though. Hmm. Something with Maxwell and the shaders I guess, shaders are not my best area of expertise but I'll see if blackrack has any ideas. In the meantime, try extacting just the "shaders" folder from a release before 1.30 and merging it with a modern release, maybe it'll work better for you.

Thanks for the report. I got a true linux rig running so I'll run some OpenGL test fixes through it soon. Thanks for this detail, good for testing to know all the different config changes.

If you have scatterer shadows enabled, turn them off. Otherwise, wow that is buggy and though I have no Maxwell nvidia hardware to test with, I will try and see if I can't do something about it. No promises though, just best effort. As a workaround, you may try one of the builds before we rebuilt the shaders. I think 1.30 was the last one. BTW, I am finally all the way better. Based on symptoms I think it was seasonal flu and not Corona, but being careful. It should work in any OS really. Linuxgurugamer tests it in Linux, pretty sure. By the way, my results with it were incredible. Like a 20FPS gain on average.

That's what my server box was showing me. The AMD built shaders were coming out weird or something. They would run fine on AMD though, Only place I could reproduce this bug was on my nvidia server, and not every time. It was hard because it only has a GTX 1060 3G but I could get it to do with just stock scatterer and decent enough FPS to not quit in frustration, so thanks for the report. Was pretty easy to figure out once I knew it was more than just one random user not setting the right settings.

That's a different bug than the one I was talking about, but good to know it at least is stock and something Squad can handle! I'm talking about the crazy bad flickering shadows some have reported on the ground at launch, even on other bodies like the Mun. Not the weird mountain poking through the atmosphere look... don't know how else to describe it, but that's the difference basically.

Hmmm. Weird. I wonder why I don't see it? Maybe I need to play the game more... lol. Sounds right though, because integrated graphics would be the first to do it you'd think. Intel is infamous for doing very little in their graphics "cards" (really just the CPU as you said). Yeah the water shader has always done that. Sharp angles mess it up sadly. I don't know how to fix that, been like that as long as i can remember. The only real option to fix it is to shut off the water shader and go back to stock there, which sucks. Unless blackrack can fix it, maybe? I'll ask him about it. More intertested in those who had flickering ground shadows, like on the Mun and such, etc.

Also offtopic but thank you for showing me this! At first I thought you misspelled "heatspreader" lol. I am totally going to try this now.

Sometimes I swear the physics break down at that point. I mean I know the game isn't supposed to let that happen, but it would explain some things. Anyways, yeah, please test my new hotfix everyone. I mean part count is the big thing we aren't considering. IF you fly in a 300 part count craft even in stock kerbal it's tough enough (I mean yes, WE can do it but I'm talking for an average potato PC). Game is just too singlethreaded to handle big part counts let alone graphics to go with them. Sadly my bigbad 8 core 9900k sits mostly idle while KSP suffers. I genuinely find it hard to justify upgrading the final level of the VAB sometimes. Totally offtopic, but it's the big thing I hope KSP2 fixes.

New release is out. It's simply a shader recompile, no actual code changes, so it has the same version number. Known as the "NVIDIA shadow hotfix," please try this if you have shadow issues and/or are using an nvidia card. Heck, if you are having any shadow issues even with an AMD card, maybe it's worth a try. (note scatterers own shadows setting does not count, it's broke right now) But do specify in bug reports you are using the "hotfix" please, so I can differentiate. Yep that's AVP. If you cross 300 parts it starts to progressively murder you. But very pretty.

Oh, that bug. Sorry, I'm waking up. Yeah, I looked at the screenshot. Same one. So here's what I see: The shaders I compiled on AMD work on AMD cards fine (tested with two), even in OpenGL mode where I normally get sun flickering issues. The shaders I compiled on an NVIDIA card (a GTX 1060 3G in my server system) work on all NVIDIA cards and all AMD ones EXCEPT on AMD Windows in OpenGL mode, where the sun experiences texture corruption. This leads me to believe we need to make two shader packs available, but it's not adding up. For right now, I'm just going to distribute with the ones built on nvidia because the sun glitch on AMD is minor and only occurs in OpenGL mode on Windows (open source drivers may fix it on linux, no idea). I think honestly I am just compiling the shaders wrong somehow on the AMD box (the files that come out are significantly smaller), but maybe there is something more to this. I don't really know as shader land is as I have always said, foreign to me. For right now, I am prepping a new release with nvidia built shaders in hopes it gets things working right for the majority of users.

I mean, what I use for "pretty dang epic" visuals is astronomers visual pack, at 8k textures. Be aware it is a GPU and CPU destroyer though. Your game will slow down a lot. But boy is it pretty. I can barely run it acceptably at the 8k texture version with my RX 5700 XT, which SHOULD be about 50% faster than a GTX 1080 (in truth it's a bit less because AMD drivers suck for KSP due to being largely singlethreaded in DX11), so if I were you, I'd try it but go for one of the lower res texture packs. Should still look pretty darn awesome. Feeling better today btw. Not all the way better but MUCH better than yesterday. This shouldn't be covid-19 if what I am reading is right as all I ever really got was a bloody nose and typical sinus grossness (no fever). Still I'm doing the whole self-isolation thing because who the heck knows? Heck maybe I'm one of the lucky few it doesn't hit hard but I sure don't want to share it! Anyways, should give me some time to work. I'm going to try to replicate the faulty shader bug today with the shadows. I have a GTX 1060 somewhere I can test with... Yes, it does. I think it may be a Pascal specific glitch, maybe since I compiled the shaders exclusively on AMD? I'm going to get in touch with blackrack and get his compiled shaders and see if they behave better. He doesn't have any for EVE, but hopefully scatterer is the only one bugging out right now.

Nah, I was saying I have no issue with it. If a mod does though, just listen to 'em. Makes it easier on everyone. Already feeling a bit better. Hope tomorrow it's gone. If so, it was nothing but a lil' cold and that'd be for the best.

Hmmm. The only thing I am noticing re the shadow bug is you are all using Pascal era NVIDIA cards. Then again those were really popular cards... Not sure if that means anything, but I (who can't reproduce the bug) am running an AMD Radeon 5700 XT card from the Navi lineup, which is quite a bit different (honestly, usually AMD is buggier, so this'd be a first for me, lol). Maybe that means something, no idea. Will look at this again soon. Right now just trying to get over this thing. To all concerned it has remained mild so far and is just slowing me down, nothing more. It's mainly just a PITA. If anything I think I am making forward progress not backwards re recovery. I personally see no rights issue with it... but not a lawyer. They look to be just the binaries with some configs and textures, no biggie. Maybe I'll regret this statement when my head clears, but looks fine to me.

Sorry for my absence as of late, I have the sniffles for lack of a better term, no fever yet, hoping it isn't that nasty covid 19 thing... It's mostly mild and just a lack of energy. Hope it stays that way. Still needless to say I'm in isolation, heh. It is lonely up here. This shadow artifact bug is weird. Could people experiencing it try falling back one or two versions and seeing if it goes away? Maybe EVE as well? There was a shader recompile there that may be messing with things. The goal would be to see where in that mess it happened... Or if it's unrelated to shaders and been there a while. Thanks. Also, since it appears stock is affected by it too, please post your GPU model in case there is a pattern. @StoneWolfPC @dtoxic @7pH

Good to see the RSS-hack I did performs as well as it does. It's not really the best way to handle it, because it breaks scatterer-shadows in a way that can't be fixed, so it probably will never make it into an official release, but I'll be happy to maintain a "patched' version for those purposes until we have a better way.

Also, if you have scatterer shadows on, turn them off. They do something very similar to that and are very broken... possibly for the same reason.

Yeah, that bug was not one it was designed to address. This new shader code deals with cloud clipping, issues with the clouds vanishing entirely at certain angles. Anyways, not saying this isn't a bug because it is, just that it wasn't fixed with this and probably won't be until offiical update by blackrack. See, it is something to do with the transition from local scenery to scaled space. Blackrack understands it better than I. I expect his official release to fix it properly, until then I can't do much about that one really unless he has an idea. It's not a bug I have a firm enough grasp of the root mechanics to really fix, I don't think. Gotta be honest there. As I said this is really blackracks baby at the end of the day. I'm sure he has ideas on what to do, but I don't for this one.

New release hotfixes of both EVE and Scatterer up with blackracks shader code, fixing the Jool visual-oddity bug. Please download them and test. I should note I personally tested these in the sense that at least Kerbin and Jool appear correctly in both map view and flight, as well as the other planets in standard map view were all 100% perfect... we need more testing than Kerbin and Jool in flight though, obviously. It should fix things more than break them, but lets do some testing. @stratvox I am particularly interested if this helps the OpenGL shoreline issue at all, or if we need to mess with clip planes a bit (that would be the case if you still see it). I have a feeling it won't do much being it's cloud code, but stranger things have happened...

Thanks, but since I have to patch EVE as well I may as well build them myself... I will use that fix though, rather than the hacky-sounding offset version (I really have no idea what I'm doing in shaderland anyways, so will defer to you).

I will try this today (each fix in the order listed). Next build will undergo some testing though before I push it out, I think. Probably better for all (even on the bleeding edge, lol). Will have it tested by about noon PST with any luck (my timezone).

Hm. That's very odd. Can you try it with just an older EVE and not an older scatterer, just to isolate if it's one that's faulty and not the other? EVE gave me a bunch of headaches while building, so i have a suspicion that's the origin of the issue. EDIT: Nope, just tested and the origin of the issue is blackracks new shader changes. @blackrack, unless I did something wrong your updated spherecloud shader breaks Jool. I will pull those builds for now. If you downloaded them please revert. They didn't do what we wanted, unfortunately. They won't hurt your game but they clearly have issues. Yep, I just remembered this. Thank goodness, I was about to partition my SSD and that seldom ends well. Plus Gentoo is a black hole someone can vanish into for weeks... lol

Only if RSSMode is toggled, which is for real solar system support. It's more of a hack really and I doubt that's what's causing this as that looks like Kerbin. No, not at all. I mean, yes, in concept it is, but.... The project in there is a really obsolete Unity Project that won't even import right. I'm setting up a Linux box to debug OpenGL. May be gone a few days, because my distro of choice is... Gentoo! But hey, I will be able to properly debug Linux afterwards.

New releases of both EVE and Scatterer this evening, finally including @blackrack's latest EVE-derived cloud shader code. Some notes on these releases: 1.) They do not fix scatterer shadows, yet. 2.) They are SUPPOSED to fix a ton of cloud based clipping issues. but, 3.) they are largely untested (blackrack knows what he's doing, usually ) If they cause any trouble, or more harm than good, reverting is never harmful. Otherwise, let's hope they fix a lot of bugs! Links in OP, as always. Replying to say it did. By the way, do you know the proper way of building EVE's shader code? Man, I had to resort to building it in scatterers build tree, and injecting it into an uncompressed unity bundle with an external tool, because the build system for the shaders is so strange and undocumented. At least it worked.

Hey, it's all good. I push out the fixes as soon as I get them, untested often times. I can see how some people might percieve that as a "lack of quality control" We get there in the end though. No need for that. I'm chill with criticism.

Thanks, I will try in a few hours. Wow, an OpenGL tester finally shows up. Thank you! Yeah, unfortunately I'm at a loss as to what might be causing that only on OpenGL (it should be running just like dual camera version), but I will take a look tonight. Any thoughts, @blackrack? A logfile might help too if you have time. Find it in the KSP install root, KSP.log I believe. Right now I'm going to wait on taking on anything new until I drop existing projects, because these ones are pretty heavy-duty ones code wise. But I'll put it on the list, Scatterer should be updated officially soon so maybe there'll be room.