R-T-B

Yeah, that's one way to do it... I've never heard of the sun not illuminating though (wow!), only solar panel performance bugs. That happened to you?

Are you running Kopernicus in any form? If so, it's possible it's the culprit. There may be a bug in the stock release that only manifests itself in extremely strange edge cases (still not sure what exactly causes it to appear, but I think I know the origin of the bug). At any rate, if it's what I think, bleeding edge Kopernicus should have it fixed. Could you kindly test with that build instead of stable? Right now, it's in a pretty stable state, and should not bite (it will probably be a stable patch in just a few days, actually):

This is not the case anymore with my bleeding edge builds and hasn't been for some time, just FYI. I'm playing JNSQ on bleeding edge personally now. It's been mostly bug free, but no promises. I at least manage. I think I fixed the "farm patch" bug too. Bleeding edge is NOT release grade but it seems good enough right now for JNSQ.

I believe that is the case.

Keep in mind, I'm aware of at least a few bugs with it, but it does basically work. It's usable, if sometimes annoying.

The latest release may do even more to improve the issue. But it's good to hear even the first stab at it (Release 23) had a fair impact.

No, just download the other zip for your version, not the source code. We can look at optimizing them some, the new multistar math is probably to blame. Can I get your actual CPU just so I know what we are dealing with? No shame. You can turn off the new solar panels with a small cfg bit. Just throw the following in a cfg file in gamedata. This will restore stock behavior, which is fine for singlestar systems. @PART:HAS[@MODULE[ModuleDeployableSolarPanel]]:FINAL { useKopernicusSolarPanels = False }

A few more release dropped (we are at 25 now) with under-the-hood changes, and something kinda big happened as a result: https://github.com/R-T-B/KittopiaTech/releases Yep, a KittopiaTech release that actually works with 1.10.1 and stuff. Requires bleeding edge build 25 or greater (basically the latest to date). It will work with both 1.9.1 and 1.10.1 without fuss. Report bugs, of course. It will have issues with a Kopernicus Bleeding edge lower than 25, or the present stable build. We hope to test and promote this to stable as rapidly as is reasonable.

Believe me, I'm glad to be back too.

I may need more caffeine to read that. I'll be back later.

FWIW I think the latest bleeding edge finally fixed this bug, needs testing though. It's the first real time I've been able to play longterm without it at any rate. @OrbitalManeuvers

While all that testing was going on, I fixed another something. Feel free to test, maybe? This one is more relevant to planet pack authors. Kopernicus R-T-B Unified "Bleeding Edge" Edition Release 22 R-T-B released this 1 minute ago This is R-T-B's "Bleeding Edge" branch of Kopernicus, intended to support the latest features, KSP editions, and also the latest bugs. Please keep in mind this branch may be more buggy than Prestja's mainline Kopernicus branch, but it also supports more KSP versions and has more features implemented for testing reasons. Many features that make it into mainline Kopernicus are born, tested, and trialed by fire here. This is release 22. It contains the following changes: 1.) Experimental fixes for broken atmospheric fog-ramp, and some contrast/albedo settings. Known Bugs: 1.) Right now? Nothing big! Famous last words? Please download the right output zip for your version. "191" zips are for 1.9.1, "1101" for 1.10.1, etc. Thanks and as always, report bugs! -RTB EDIT: And, a wild hotfix appeared! Kopernicus R-T-B Unified "Bleeding Edge" Edition Release 23 R-T-B released this now This is R-T-B's "Bleeding Edge" branch of Kopernicus, intended to support the latest features, KSP editions, and also the latest bugs. Please keep in mind this branch may be more buggy than Prestja's mainline Kopernicus branch, but it also supports more KSP versions and has more features implemented for testing reasons. Many features that make it into mainline Kopernicus are born, tested, and trialed by fire here. This is release 23. It contains the following changes: 1.) Less experimental fixes for the fogramp (old ones did not work). Known Bugs: 1.) Right now? Nothing big! Famous last words? Please download the right output zip for your version. "191" zips are for 1.9.1, "1101" for 1.10.1, etc. Thanks and as always, report bugs! -RTB

I see. I honestly have no idea, was just a stab in the dark.

Are you using windows or linux? If windows, you may try paint.net. If Linux, well, you already tried GIMP... so dunno.

I'd like some testers for the above release, specifically the section I bolded. I really want to know if i finally fixed that. Also potential performance improvements, it would be nice to see some numbers. This may make it into stable if it proves solid.

Kopernicus R-T-B Unified "Bleeding Edge" Edition Release 21 R-T-B released this now This is R-T-B's "Bleeding Edge" branch of Kopernicus, intended to support the latest features, KSP editions, and also the latest bugs. Please keep in mind this branch may be more buggy than Prestja's mainline Kopernicus branch, but it also supports more KSP versions and has more features implemented for testing reasons. Many features that make it into mainline Kopernicus are born, tested, and trialed by fire here. This is release 21. It contains the following changes: 1.) Experimental performance improvements, possible fix for JNSQ "farm patch" bug. Try it? Known Bugs: 1.) Right now? Nothing big! Famous last words? Please download the right output zip for your version. "191" zips are for 1.9.1, "1101" for 1.10.1, etc. Thanks and as always, report bugs! -RTB

We are the new Kopernicus maintainers. Feel free to reach out to me and/or Prestja with any questions you may have.

I just made one and compared and the logs are actually the same, so don't sweat it. Just get me a log with the standard build.

I just PM'd you the build, don't really want it on the public git page on second thought so people don't get confused about 1.10 vs 1.10.1 (even though that'd be extremely dumb, I can see it happening). I also enabled debug mode in the build so it might log more verbosely (that's a might, I'm not sure that really does anything).

Oh wow you are here, yeah, just gimme 5 minutes to put it up lol. I forget 6am PST people actually start waking up all over the country. It's only really early for me.

That SHOULD be fixed, but it would not surprise me if it crops up for some odd configurations or something. Just because it can. Oh yes and I'm finally back. I got done with my reinstall post-motherboard arrival, which took way longer than it needed to (I didn't expect to have to do a reinstall at all, but at least it's done now). I'm going to work on the bleeding edge to smash some bugs. Once we have some good bug smashing done there, we'll probably drop another stable release on the 1.9 branch and maybe, if we're really lucky, we can talk about promoting 1.10.1. But that's a ways off. This is the safest route. But if you want to diagnose with me, you can always play that game too, just send me a log file from when it happens if you could. I shook each component before inserting it, listening for rattling metal. lol I'm paranoid now. But hey, what's a little component shaking vs an exploding computer? I think I'll do it from now on.

Sorry I just got my system reinstalled. Aparently switching motherboard brands was a BAD idea as it neccessitated a complete reinstall of windows before I could get everything stable again. But I'm back baby and hunting for bugs, and this seems as good a place to start as any... @etmoonshade, I will begin investigating your issue by making a one-time 1.10.0 build of build 20. I'm curious if that fixes it (it would confirm something changed in the .1 release). I'm building it now, care to test? Download from the usual link when you read this.

Board is here... yes late in the day but at least it arrived. Barring any issues should be hard at work tomorrow, next day worst case.

We don't really know what causes it other than maybe ksps shaders don't do so well with larger-than-stock worlds, but yes we are aware of this bug. Unfortunately I now have seen it as well and my suggested fixes do nothing. Sadness.

dlls can spread viruses. Don't doubt that ksp will not happily run viral code for a second. Unity does not really know how to distinguish. That said, I agree. If there is no clearcut license violation, there is no need to report.