R-T-B

and just like that, a hotfix. Hopefully the last one! Kopernicus release-145 New in this latest version release-145: 1.) Hotfix for broken heightmap exporting, introduced in release-143 accidentally. Known Bugs: 1.) The particle system is hopelessly broken and will likely remain that way. It will probably be removed entirely in the future. This happened around release 1.10 when squad removed more stock methods, but no one really noticed. 2.) Not exactly a bug, but worth mentioning: The Kopernicus_Config.cfg file is rewritten when the game exits. This means any manual (not in the GUI) edits made while playing the game will not be preserved. Edit the file only with the game exited, please. 3.) At interstellar ranges, heat can sometimes behave strangely, sometimes related to map zoom (be careful zooming out). It is best to turn off part heating when traveling far far away. 4.) When zooming out all the way out in map view at interstellar ranges, the navball furthermore sometimes behaves oddly. We are working on this and monitoring all the interstellar bugs actively. 5.) Very Old craft files may complain about a missing module. This is a cosmetic error and can be ignored. Reload and re-save the craft to remove the error. Known Caveats: 1.) The 1.12.x release series works on 1.12.x. The 1.11.x,1.10.x,1.9.x and 1.8.x releases are deprecated 2.) Multistar Solar panel support requires an additional config file, attached to release. 3.) As of release-107, scatter density underwent a bugfix on all bodies globally that results in densities acting more dense than before on some select configs. Some mods may need to adjust. Normally we'd not change things like this, but this is technically the correct stock behavior of the node so... if you need the old behavior, see config option UseIncorrectScatterDensityLogic. 4.) As of Release-119, LandControl createColors is no longer obeyed, it is forced on to avoid another bug. Very few mods to my knowledge use this parameter, but a few do (JNSQ for example). We work around this in game now, but if you need createColor colors, turn option "EnableColorFix" to false. 5.) The "collider fix" as it's called, which fixes the event in which you sink into the terrain on distant bodies, is now on by default. If you really need distant colliders, turn this off, but you'd best have a good reason (I can't think of any).

I'm always more partial to forums, but if I have to ask on the discord, I'm gonna ask on the discord. But if they close the forums it would be a major loss.

What about important community modders? It'd be nice if we could get a heads up build to start porting some of our work.

Heads up everyone! This is probably the last bugfix before KSP2, should cover most things... Kopernicus release-144 New in this latest version release-144: 1.) Kopernicus Asteroid Generator performance improvements via github user TuckMeIntoBread, should reduce in game stutter on asteroid spawning. 2.) The old "ColorFix.cfg" file is now baked into Kopernicus, and can be turned off with an ingame/config file option called "EnableColorFix." Setting it to false disables it, but it defaults to true for obvious reasons (few packs need it off, many need it on). 3.) Changed default for "DisableFarAwayColliders" is now true instead of false. The feature has yet to cause a major issue, and several larger planet packs rely on it, so... 4.) Fixed some insignificant but still relevant memory leaks, and changed Kopernicus_Config.cfg loader to load earlier to prevent race conditions with some configurations. Known Bugs: 1.) Not exactly a bug, but worth mentioning: The Kopernicus_Config.cfg file is rewritten when the game exits. This means any manual (not in the GUI) edits made while playing the game will not be preserved. Edit the file only with the game exited, please. 2.) At interstellar ranges, heat can sometimes behave strangely, sometimes related to map zoom (be careful zooming out). It is best to turn off part heating when traveling far far away. 3.) When zooming out all the way out in map view at interstellar ranges, the navball furthermore sometimes behaves oddly. We are working on this and monitoring all the interstellar bugs actively. 4.) Very Old craft files may complain about a missing module. This is a cosmetic error and can be ignored. Reload and re-save the craft to remove the error. Known Caveats: 1.) The 1.12.x release series works on 1.12.x. The 1.11.x,1.10.x,1.9.x and 1.8.x releases are deprecated 2.) Multistar Solar panel support requires an additional config file, attached to release. 3.) As of release-107, scatter density underwent a bugfix on all bodies globally that results in densities acting more dense than before on some select configs. Some mods may need to adjust. Normally we'd not change things like this, but this is technically the correct stock behavior of the node so... if you need the old behavior, see config option UseIncorrectScatterDensityLogic. 4.) As of Release-119, LandControl createColors is no longer obeyed, it is forced on to avoid another bug. Very few mods to my knowledge use this parameter, but a few do (JNSQ for example). We work around this in game now for most all mods, but if you find you need createColor colors, turn option "EnableColorFix" to false. 5.) The "collider fix" as it's called, which fixes the event in which you sink into the terrain on distant bodies, is now on by default. If you really need distant colliders, turn this off, but you'd best have a good reason (I can't think of any).

I have launched KSP in that install several times, with and without KSPCF. That's why I believe something else is at play here. Not sure what though... the whole thing seems exceptionally odd.

Not to dismiss rmaine's concerns, but I can't repro this either on a clean install. I think it must be a external mod or corruption issue somehow. Not sure how though. When you delete your steam install, delete the ksp folder from windows explorer too btw. Steam will not remove modified files. For reference, here's my config from my stock game: PART { url = Squad/Parts/Utility/parachuteMk1/parachuteMk1/parachuteSingle DRAG_CUBE { cube = PACKED, 0.1569,0.6557,0.4137, 0.1569,0.6557,0.4137, 0.2765,0.6423,0.3861, 0.2765,0.8647,0.1765, 0.1612,0.6491,0.6308, 0.1612,0.6762,0.669, 6.735E-06,0.1034,0.01848, 0.6307,0.3626,0.6124 cube = SEMIDEPLOYED, 7.477,0.2763,0.5794, 7.477,0.2764,0.5794, 0.5275,1.225,4.172, 0.5275,1.124,14.99, 7.54,0.2753,0.5646, 7.54,0.2743,0.5325, 6.557E-07,8.838,1.147E-05, 0.826,17.83,0.821 cube = DEPLOYED, 72.79,7.568,4.943, 72.79,7.567,4.943, 52.78,8.568,4.172, 52.78,6.533,14.99, 73.5,7.509,4.551, 73.5,7.472,4.551, 6.676E-06,8.838,0.0001245, 8.26,17.83,8.21 } }

1x is HARD. My 3090 based rig can just barely do that at 1080p and 60FPS... Fortunately, 4x is nearly visually identical at up to like 1440p in practice. The only real difference between it and 1x is very minor motion artifacts. 8x is also close, and very reasonable as a default for a wide range of cards. As I told blackrack, this is a masterpiece and he's fully earned every patreon for his efforts on the preview. Gratz man.

I'd need an example game to check. What games feature PDLauncher right now? That might be possible.

A modern potato. As in, the latest in potato technology. It's a lowend 2023 PC. Not meant to be mean or judgemental at all to other potatoes.

For those wondering: Can my potato PC run this? I tried it on a modern potato, loaded it up with all my mods, and the result is described below in a post I made to blackrack: FPS in top corner. Planet is a rescaled 2.5x Kerbin. No, it's not great, but it does run ALMOST playably and that's with parallax and a ton of other mods maxed out. Reduce my modset some and I'd say it could be usable. That's on an igpu with a 25W power budget, roughly equal performance wise to a very low clocked AMD RX 570 or faster version of a GTX 1050 type card. Not bad at all!

The error is coming from KopernicusExpansion, not Kopernicus. I don't dev that mod, though the names are quite similar. If you remove KopernicusExpansion I expect you can still use Kopernicus. Try reaching out to the dev of the mod there.

At the moment, you subscribe to his patreon page and download the early access. They will eventually be available for free though.

I play 2.5x rescale for reference. Lookin' pretty good blackrack, at first glance. Note the rescale does skew the visual effects slightly. The FPS are on a 3090 with a 8x temporal settings. AMD 5950x as well. This is heavily modded 4k, so don't panic, you can do 1080p at 60FPS way way way easier (like sqrt(x) of hardware requirements lol) I can safely say blackrack is making excellent use of my dev gpu gift.

To answer this, the stock generator does not work well with complete system replacements. It only works properly with systems that have Dres and Kerbin both present, so basically stock-alike systems. At one point I was going to properly support comets. It will still happen someday, but like most of us, I'm going to be looking at what needs KSP2 has first, most likely.

Yep, release incoming to address that and some small other things: https://github.com/Kopernicus/Kopernicus/releases/tag/release-143 New in this latest version release-143: 1.) Removed a warning that was incorrectly displaying on build 1.12.5 about the build being beta (seems fine). 2.) a minor fix for exported height maps from Kittopia. 3.) allowedBiomes may now contain spaces. Known Bugs: 1.) Not exactly a bug, but worth mentioning: The Kopernicus_Config.cfg file is rewritten when the game exits. This means any manual (not in the GUI) edits made while playing the game will not be preserved. Edit the file only with the game exited, please. 2.) At interstellar ranges, heat can sometimes behave strangely, sometimes related to map zoom (be careful zooming out). It is best to turn off part heating when traveling far far away. 3.) When zooming out all the way out in map view at interstellar ranges, the navball furthermore sometimes behaves oddly. We are working on this and monitoring all the interstellar bugs actively. 4.) Very Old craft files may complain about a missing module. This is a cosmetic error and can be ignored. Reload and re-save the craft to remove the error. Known Caveats: 1.) The 1.12.x release series works on 1.12.x. The 1.11.x,1.10.x,1.9.x and 1.8.x releases are deprecated 2.) Multistar Solar panel support requires an additional config file, attached to release. 3.) As of release-107, scatter density underwent a bugfix on all bodies globally that results in densities acting more dense than before on some select configs. Some mods may need to adjust. Normally we'd not change things like this, but this is technically the correct stock behavior of the node so... if you need the old behavior, see config option UseIncorrectScatterDensityLogic. 4.) As of Release-119, LandControl createColors is no longer obeyed, it is forced on to avoid another bug. Very few mods to my knowledge use this parameter, but a few do (JNSQ for example). You can work around this if affected by setting your LandControl color to be all zeroes. See attatched cfg for a mod that does this. 5.) The "collider fix" as it's called, which fixes the event in which you sink into the terrain on distant bodies, is off by default. If you have a system larger than stock, please see Kopernicus_Config.cfg option DisableFarAwayColliders, read about the fix/workaround, and set it as you feel appropriate.

Kopernicus release-142 R-T-B released this now release-142 New in this latest version release-142: 1.) Removed a warning that was incorrectly displaying on build 1.12.4 about the build being beta. Known Bugs: 1.) Not exactly a bug, but worth mentioning: The Kopernicus_Config.cfg file is rewritten when the game exits. This means any manual (not in the GUI) edits made while playing the game will not be preserved. Edit the file only with the game exited, please. 2.) At interstellar ranges, heat can sometimes behave strangely, sometimes related to map zoom (be careful zooming out). It is best to turn off part heating when traveling far far away. 3.) When zooming out all the way out in map view at interstellar ranges, the navball furthermore sometimes behaves oddly. We are working on this and monitoring all the interstellar bugs actively. 4.) Very Old craft files may complain about a missing module. This is a cosmetic error and can be ignored. Reload and re-save the craft to remove the error. Known Caveats: 1.) The 1.12.x release series works on 1.12.x. The 1.11.x,1.10.x,1.9.x and 1.8.x releases are deprecated 2.) Multistar Solar panel support requires an additional config file, attached to release. 3.) As of release-107, scatter density underwent a bugfix on all bodies globally that results in densities acting more dense than before on some select configs. Some mods may need to adjust. Normally we'd not change things like this, but this is technically the correct stock behavior of the node so... if you need the old behavior, see config option UseIncorrectScatterDensityLogic. 4.) As of Release-119, LandControl createColors is no longer obeyed, it is forced on to avoid another bug. Very few mods to my knowledge use this parameter, but a few do (JNSQ for example). You can work around this if affected by setting your LandControl color to be all zeroes. See attatched cfg for a mod that does this. 5.) The "collider fix" as it's called, which fixes the event in which you sink into the terrain on distant bodies, is off by default. If you have a system larger than stock, please see Kopernicus_Config.cfg option DisableFarAwayColliders, read about the fix/workaround, and set it as you feel appropriate.

Added a new bug (bold above) to the update. Basically, please use 1.12.x, as I can't be bothered to fix older issues now that KSP isn't a moving target anymore. I will update CKAN metadata for this in next release (even though it technically does load).

Kopernicus release-141 R-T-B released this 2 minutes ago release-141 New in this latest version release-141: 1.) Deactivated some buggy thermal flux code that should not have shipped yet (it won't hurt your kerbals, but should not be shipping yet). Basically a hotfix. Known Bugs: 1.) Not exactly a bug, but worth mentioning: The Kopernicus_Config.cfg file is rewritten when the game exits. This means any manual (not in the GUI) edits made while playing the game will not be preserved. Edit the file only with the game exited, please. 2.) At interstellar ranges, heat can sometimes behave strangely, sometimes related to map zoom (be careful zooming out). It is best to turn off part heating when traveling far far away. 3.) When zooming out all the way out in map view at interstellar ranges, the navball furthermore sometimes behaves oddly. We are working on this and monitoring all the interstellar bugs actively. 4.) Very Old craft files may complain about a missing module. This is a cosmetic error and can be ignored. Reload and re-save the craft to remove the error. 5.) Ring shaders are broken on 1.11.x and lower. Please use 1.12.x if possible and consider older builds basically as is. You might get the ring shaders working by using older builds shader bundles, but I am really just focusing on 1.12.x now. Known Caveats: 1.) The 1.12.x release series works on 1.12.x,1.11.x,1.10.x, and 1.9.x. The 1.8 release is deprecated 2.) Multistar Solar panel support requires an additional config file, attached to release. 3.) As of release-107, scatter density underwent a bugfix on all bodies globally that results in densities acting more dense than before on some select configs. Some mods may need to adjust. Normally we'd not change things like this, but this is technically the correct stock behavior of the node so... if you need the old behavior, see config option UseIncorrectScatterDensityLogic. 4.) As of Release-119, LandControl createColors is no longer obeyed, it is forced on to avoid another bug. Very few mods to my knowledge use this parameter, but a few do (JNSQ for example). You can work around this if affected by setting your LandControl color to be all zeroes. See attatched cfg for a mod that does this. 5.) The "collider fix" as it's called, which fixes the event in which you sink into the terrain on distant bodies, is off by default. If you have a system larger than stock, please see Kopernicus_Config.cfg option DisableFarAwayColliders, read about the fix/workaround, and set it as you feel appropriate.

A few users reported this on the new release. Try the former release if you have this, be aware it may need you to install some .net framework stuff (will prompt you) but it should work just as well.

Kopernicus release-140 Latest New in this latest version release-140: 1.) Fixed several bugs in the ringshader on non-windows platforms, as well as added some additional features (dual texture support, wiki will be updated soon, thanks WarriorSabe). This is considered experimental code on Linux and Mac, but still should be better than what you had. Please report any bugs, all the same. 2.) Fixed a Kopernicus SolarPanel localization "Direct Sunlight" error (sometimes would be stuck on english). 3.) This release deprecates 1.8.x support. Past releases will still work, but the extra ringshader features there were too maintainence intensive to port and you won't get future releases going forward. Given the limited user base of 1.8.x, and our limited manpower, we had to drop support for it to keep the project going. Known Bugs: 1.) Not exactly a bug, but worth mentioning: The Kopernicus_Config.cfg file is rewritten when the game exits. This means any manual (not in the GUI) edits made while playing the game will not be preserved. Edit the file only with the game exited, please. 2.) At interstellar ranges, heat can sometimes behave strangely, sometimes related to map zoom (be careful zooming out). It is best to turn off part heating when traveling far far away. 3.) When zooming out all the way out in map view at interstellar ranges, the navball furthermore sometimes behaves oddly. We are working on this and monitoring all the interstellar bugs actively. 4.) Very Old craft files may complain about a missing module. This is a cosmetic error and can be ignored. Reload and re-save the craft to remove the error. Known Caveats: 1.) The 1.12.x release series works on 1.12.x,1.11.x,1.10.x, and 1.9.x. The 1.8 release is deprecated. 2.) Multistar Solar panel support requires an additional config file, attached to release. 3.) As of release-107, scatter density underwent a bugfix on all bodies globally that results in densities acting more dense than before on some select configs. Some mods may need to adjust. Normally we'd not change things like this, but this is technically the correct stock behavior of the node so... if you need the old behavior, see config option UseIncorrectScatterDensityLogic. 4.) As of Release-119, LandControl createColors is no longer obeyed, it is forced on to avoid another bug. Very few mods to my knowledge use this parameter, but a few do (JNSQ for example). You can work around this if affected by setting your LandControl color to be all zeroes. See attatched cfg for a mod that does this. 5.) The "collider fix" as it's called, which fixes the event in which you sink into the terrain on distant bodies, is off by default. If you have a system larger than stock, please see Kopernicus_Config.cfg option DisableFarAwayColliders, read about the fix/workaround, and set it as you feel appropriate.

I know the mod is developed on an RTX 2080 Super (because said development card was once mine, before I posted it to him during the GPU shortage), but I'm pretty sure his target "playability" point is well below that. I'd say 1080ish performance is a good bet.

I just patched release-139 to work with 1.12.4 with no warning. No other changes & no new release for this, just download the old one which has now been patched. A new release with much more features will be coming soon. https://github.com/Kopernicus/Kopernicus/releases/tag/release-139

This has been done. See: https://github.com/R-T-B/KSSL/releases

I can make a special build for that. When I next recompile this in the next few days, I'll do so.

Kopernicus at least, as a mod project, is very much so. I'm holding things together and working on one final release, but I am very much downgrading my efforts there in anticipation of all the KSP2 work I will likely have to recreate.