R-T-B

I was unaware JNSQ had a setting requirement, it's been so long since I installed it. This is indeed probably his issue then. His settings file appears to be using standard (non-JNSQ) low terrain quality. Thanks for clarifying. And FWIW, the shader setting can be lowered, I've done it before. It's the terrain quality setting that seems to matter the most. Oh, and while I'm here, there is a new Stable Kopernicus that works wonders on JNSQ performance with land scatters, if anyone is interested. Just a shout out to that:

Wow. Ok, so here's what I'll need from you next. KSP.log from your ksp install directory root. settings.cfg too please, just to double check something. Send them to me in PM, so we don't clutter this too much since this is not a common issue. I will do my best to develop some kind of fix for you, worst case, or tell you what's causing it in simple terms, best case. Also if anyone else is having this issue with JNSQ, please speak up.

Yeah. Your issue is really odd and certainly not one I'm familiar with. Do let me know. If it doesn't work, the next step would be to ask your hardware configuration, because maybe it's a bug related to your particular hardware? If so we can likely develop a work around, but we need to know the parts that are affected by this.

It's here: Direct link to latest release: https://github.com/Kopernicus/Kopernicus/releases/download/release-1.9.1-10/Kopernicus-1.9.1-10.zip I fear it may not help you though, as stable is really just bleeding edge right now with a few less experimental features, none of which should cause that. I hate to go down this road, but have you tried reinstalling KSP completely to rule out a corrupt install? If you have steam, maybe validating game cache (under right click game in library -> properties) may help?

Oh, it sounds like you have an old save. We did do some solar changes in the latest Kopernicus for 1.9.1 forward (mainly to support multiple stars in some planet packs properly). In flight vessels may be affected, as will old designs if not reloaded and resaved. You can ignore the warnings while doing so. Let me know if that helps your issues. Keep in mind vessels affected by this bug in flight basically need to land before they can be fixed, or edited in the savegame .sfs in some way (I don't really know how you'd go about it, but basically you need to replace the ModuleDeployableSolarPanel and/or KopernicusSolarPanelsFixer to KopernicusSolarPanels A simpler work around if you are using a pack with only one star is to disable the multistar support entirely. This can in theory be accomplished by putting the following in a .cfg file in your Kopernicus/Config folder. Here's what you'd need to do, more or less: Open notepad, paste the following in it: @PART:HAS[@MODULE[ModuleDeployableSolarPanel]]:FINAL { useKopernicusSolarPanels = False } save it as type "all files" in GameData/Kopernicus/Config. File name can be anything that ends in .cfg, example: SolarPanelSingleStarFix.cfg If windows doesn't let you save it there, save it to your desktop first, then move it.

I am unsure what would cause your scenario. You could try stable 1.9.1, or the latest bleeding edge (in case you are out of date or something). I just tested both and at least for a fresh game, they are working for me. It's almost like your save is corrupted or something.

I can only say that's not a common bug if it can't be fixed by a reload, and if one reload fails, the second usually succeeds. Quite odd, sorry I can't offer more help. EDIT: Looking at your modlist, I see you have Tweakscale. You aren't resizing the bodies by chance, are you? That might lead to this behavior (unfamiliar with TweakScale in general but know it resizes... things).

This is a big release to the stable branch people, for both planet devs and players. I strongly advise updating! Highlighting some of the chief improvements below! Kopernicus 1.9.1-10 R-T-B released this now New in this version (1.9.1-10) 1.) Added a culling range to land scatters, by default at 10km, configurable by the Kopernicus_Config.cfg parameter ScatterCullDistance. This massively improves performance in scatter-heavy planet packs with land scatters on. 2.) We now support "Breaking Ground" anomalies out of the box, eliminating the need for "MyRocksAreBiggerThanYours." 3.) Material names have been simplified. You can still use the old ones, but there are simpler alternatives now. You can see https://github.com/R-T-B/Kopernicus/pull/28/files for details, or simply wait for the wiki to update. Remember, the old names still work and we have no plans to change that, this is just for usability. New in major release (1.9.1) 1.) Planet pack authors (or you) may now specify the packs target shader level by by setting config/Kopernicus_Config.cfg EnforcedShaderLeve. 3 = Ultra/Atlas, 2 = High, 1 = Medium, and 0 = Low. Planet pack authors may use this via modulemanager module if needed as well. Note that we encourage of the KSP Parallax shader project over use of Squad's ATLAS shader. It is both equally performant and more flexible. 2.) The longstanding ringshader bugs have been fixed. 3.) Performance Optimization and bugfixes enabling KittopiaTech support. 4.) JNSQ & other large world "Farm patch" bug fixed. 5.) Particle support restored. 6.) All 1.9.1 bugs that are known fixed. Full support for 1.9.1 7.) Multistar support. The math on ECs in single star may be slightly different than stock in some situations, but it should be similar in most and not enough to matter. 8.) Added GameData\Kopernicus\Config\Kopernicus_Config.cfg file, with options to configure shader warnings and enable or disable shader locking, as well as set preferred shader level. Easy to edit, just look inside!

I've seen that (and also an underground KSC). Usually a reload will fix the bug. Have you tried that? It seems to be some stock bug with the load routine and larger planetary bodies. Unfortunately, short of a reload which almost always works, I don't know of any fix. Have you tried eliminating other mods one by one to rule out mod interference of some kind, if the reload trick is not working?

Kopernicus R-T-B Unified "Bleeding Edge" Edition Release 41 R-T-B released this 6 minutes 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 41. It contains the following changes: 1.) Added a culling range to land scatters, by default at 10km, configurable by the Kopernicus_Config.cfg parameter ScatterCullDistance. Please test performance benefits and also, if the culling is working properly. Known Bugs: 1.) None known as of now, however that does not mean there is none! Report if you find any! 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 haven't changed anything with the solar code recently (just patcher config files but they should not be an issue). What was the last release this worked on for you, and can you provide your KSP.log please? (from game root directory).

Sounds about right. The optimizations are working then. They don't have a major impact, and only really affect it in near scatter scenarios, but I will take what I can get, and continue to whittle away at it. I don't think the glitchy terrain was Kopernicus either but interesting all the same. Let me know if you experience it frequently. Sounds sort of like stock weirdness.

Kopernicus R-T-B Unified "Bleeding Edge" Edition Release 40 R-T-B released this 5 minutes 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 40. It contains the following changes: 1.) Another attempt at the experimental optimizations for land-scatters in release 37. I believe they are now ready for primetime. Known Bugs: 1.) None known as of now, however that does not mean there is none! Report if you find any! 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

There was one report of performance degradation from those changes/optimizations that initially seemed quite real, but I do now think that user was having unrelated issues. I now doubt there is any reason to avoid brining it back. There are some more optimizations I’d like to test too for scatters. Will test them together likely next release on BE.

This is mainly what I was seeking to eliminate, the near terrain scatter (surface object) lag. It looks like it worked, more or less? Maybe removing this optimization was the wrong way to go.

Can people who are willing to test for me try a quick bench of the following? Take bleeding edge latest release, and JNSQ. Run with land scatters enabled scatters 100%. You WILL lag. See how bad (in FPS). report. Then compare with this old optimization release, Release 37 of the bleeding edge. If you get a good result (net gain in FPS to Release 37), please compare then more standard packs with Release 37 vs the modern Bleeding Edge. I'm trying to gauge whether or not reverting the optimizations in Release 37 was the correct thing to do.

I've been investigating this issue with JNSQ. It seems the collision detection it does on scatters is very very expensive. The best thing you can do is turn down scatterer percentage. I'd advise nothing higher than 25%. I tried to improve the performance of this section of Kopernicus in the code. My best result was fairly good in release 37 of the bleeding edge. But I had to revert it because it hurt some other performance scenarios outside of JNSQ. If you are only using JNSQ, you may still try it. It may give you a nice uplift. Some day I hope to bring those optimizations back.

Kopernicus R-T-B Unified "Bleeding Edge" Edition Release 39 R-T-B released this 7 minutes 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 39. It contains the following changes: 1.) Contributions to SolarPanels.cfg from forum user hemeac to help avoid errors in third party packs. Known Bugs: 1.) None known as of now, however that does not mean there is none! Report if you find any! 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

Kopernicus 1.9.1-9 R-T-B released this 1 minute ago · 1 commit to master since this release New in this version (1.9.1-9) 1.) Contributions to SolarPanels.cfg from forum user hemeac to help avoid errors in third party packs. New in major release (1.9.1) 1.) Planet pack authors (or you) may now specify the packs target shader level by by setting config/Kopernicus_Config.cfg EnforcedShaderLevel. 3 = Ultra/Atlas, 2 = High, 1 = Medium, and 0 = Low. Planet pack authors may use this via modulemanager module if needed as well. Note that we encourage of the KSP Parallax shader project over use of Squad's ATLAS shader. It is both equally performant and more flexible. 2.) The longstanding ringshader bugs have been fixed. 3.) Performance Optimization and bugfixes enabling KittopiaTech support. 4.) JNSQ & other large world "Farm patch" bug fixed. 5.) Particle support restored. 6.) All 1.9.1 bugs that are known fixed. Full support for 1.9.1 7.) Multistar support. The math on ECs in single star may be slightly different than stock in some situations, but it should be similar in most and not enough to matter. 8.) Added GameData\Kopernicus\Config\Kopernicus_Config.cfg file, with options to configure shader warnings and enable or disable shader locking, as well as set preferred shader level. Easy to edit, just look inside!

Yeah, we switched to asteroid defined nodes, so Galaxies Unbound must be set up that way in it's config. Before, it was only spawning around Kerbin/the homeworkd, which while convenient, was not technically correct behavior. This would be up to the pack author to fix now.

The current fix is more a fallback to old behavior. It won't cover all cases but it will function as it did before for at least near future solar and most major mods. I obviously botched the first patch and was just looking for quick fix (still a modularmanager noob in terms of understanding syntax). I was planning on looking at it in more detail tomorrow but I appreciate you beating me to it. That will likely ship to bleeding edge tomorrow and then to stable very soon thereafter. I just need to test it, which I will probably do tomorrow morning. Thanks. You'll get credit in next release's release notes.

Yep, it'll be the first time in a long time if we beat SQUAD to KSP 1.11 with our stable 1.10.1 release, but we're on target to do so if all goes well!

Kopernicus 1.9.1-8 R-T-B released this 41 minutes ago · 1 commit to master since this release New in this version (1.9.1-8) 1.) Bugfix for third party solar mods caused by syntax errors in Solarpanels.cfg. (Thanks for the report, @vagabond77). This is also available on bleeding edge. New in major release (1.9.1) 1.) 2.) Planet pack authors (or you) may now specify the packs target shader level by by setting config/Kopernicus_Config.cfg EnforcedShaderLeve. 3 = Ultra/Atlas, 2 = High, 1 = Medium, and 0 = Low. Planet pack authors may use this via modulemanager module if needed as well. Note that we encourage of the KSP Parallax shader project over use of Squad's ATLAS shader. It is both equally performant and more flexible. 2.) The longstanding ringshader bugs have been fixed. 3.) Performance Optimization and bugfixes enabling KittopiaTech support. 4.) JNSQ & other large world "Farm patch" bug fixed. 5.) Particle support restored. 6.) All 1.9.1 bugs that are known fixed. Full support for 1.9.1 7.) Multistar support. The math on ECs in single star may be slightly different than stock in some situations, but it should be similar in most and not enough to matter. 8.) Added GameData\Kopernicus\Config\Kopernicus_Config.cfg file, with options to configure shader warnings and enable or disable shader locking, as well as set preferred shader level. Easy to edit, just look inside!

@Gordon Dry, try this build with a more conservative optimization for land scatters, should be on CKAN-Bleeding edge as well: Kopernicus R-T-B Unified "Bleeding Edge" Edition Release 38 R-T-B released this 7 minutes 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 38. It contains the following changes: 1.) The previous performance optimizations only worked well in synthetic testing, and actually hurt FPS in many situations. More conservative ones have been applied that should work better globally. 2.) Corrections to the syntax of SolarPanels.cfg have been made, enabling better compatibility. Known Bugs: 1.) None known as of now, however that does not mean there is none! Report if you find any! 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

Ah, gotcha. That's odd too but in a different way.