R-T-B

Oops. Fixed, lol.

Kopernicus release-42 R-T-B released this 1 minute ago New in this latest version (release-42): 1.) Hopefully the final, proper fix for incorrectly vertically elevated land scatters. Will have a performance impact, but should not be more than the culler can handle for most configs. Known Bugs: 1.) 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. 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 navbal furthermore sometimes behaves oddly. We are working on this and all the interstellar bugs actively.

You might try turning off landscatters, they perform poorly in Kopernicus on the best days.

Kopernicus release-41 R-T-B released this now New in this latest version (release-41): 1.) Hazbod is now functional. It has been for a bit actually. Note: Kerbal stock game parts are extermely heat tolerant and may take time to burn! 2.) Experimental fixes for landing gear sinking in distant bodies, worth testing. May/may not work but won't hurt either way. Known Bugs: 1.) 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. 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 navbal furthermore sometimes behaves oddly. We are working on this and all the interstellar bugs actively.

Then I honestly don't know what would cause that. That's very odd. Are you using scatterer or anything else that may be playing with the scenery in some way? I have seen some behavior like that with scatterer but usually disabling distant shadows will fix it.

I described it on Kopernicus Discord. Copying it here for reference: "Anouncement: I have cracked the issue with square tiles on Joolian Moon templates. It is not a Kopernicus bug so much as an improper use of configs. Most configs (JNSQ included) are using AtmosphericTriplanarZoomRotation as their PQS material. This DOES NOT WORK on the following bodies as they don't implement that shader: Laythe (1.9.1 only), Tylo, Bop, Pol, Eeloo. You must use AtmosphericBasic/AtmosphericOptimized or Vacuum on these bodies or you will get the tile bug! It's that simple!" Note some of those moons gained that material since I posted that, but it depends on which KSP you are running. 1.11 has it on a lot more moons.

I would suggest a reinstall as something in your game must be corrupted. The checkerboard bug is caused by a config issue, not really a bug. It happens when you use the 1.8+ shader on a planet without support for it. That said I don't really see it that strongly in your screenshot. I honestly am unsure on this, and would suggest experimentation. I literally just imported MyRocksAreBiggerThanYours code with the help of it's author, and it should behave identically. Nah, he's kind of right frankly. But a lot of this is squad syntax we are just exposing. Thus, not my fault... lol. Plus at this point my main aim is to keep it running, that's really the big goal here. It's annoying but worth it. Of course, it COULD BE much worse. Trust me. We have it easy compared to some systems I've seen. Humanity can come up with truly awful things sometimes when too many programmers try to get clever in their own secret code/language... Kopernicus itself is an amazing and terrifying project, so for that part, yes. It's very time consuming AND very hard to fit in with a real life job. But we try.

Nothing should have changed with regards to b9partswitch for quite some time. How long did you have between updates? It is possible if you had not updated for some time that the new solar math deployed around Febuaryish is interacting badly with something. Do you happen to know the last version that worked?

I found the bug. It was introduced by small error in casts in last release. Oops. @Juba @emiliofloris Here is the fix. Unfortunately hazbod is still broken but hey, at least the sky and day/night is working again.: Kopernicus release-40 R-T-B released this now New in this latest version (release-40): 1.) Fixed a day/night cycle/KSP lights on/off bug caused by faulty star detection code, introduced in last release. Known Bugs: 1.) 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. 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 navbal furthermore sometimes behaves oddly. We are working on this and all the interstellar bugs actively. 4.) Hazardous Body object is presently broken, and has been for some time aparently. We are working on this for a near future release. Don't go driving in lava you shouldn't drive in, now...

I will spend some time checking into this now. Can anyone else confirm/deny if this is an issue? It may be just the above user, but before work tomorrow would be best to be certain. Also a logfile if you experience this may help. Will look into this as well. Stand by for my findings. EDIT: Log file does not show anything amiss. Will try to test by hand here shortly.

A quick release with my existing bugfixes plus that one, since it seems fairly important for users to get. More will follow with any luck: Kopernicus release-39 R-T-B released this now New in this latest version (release-39): 1.) added numerous nullchecks to the "nearest/brightest" star detection routines. This might help with some strange atmorim behaviors. 2.) Added a nullcheck to prevent logspam that was producing lag when using 3dorbit forcing (thanks Al2Me6). Known Bugs: 1.) 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. 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 navbal furthermore sometimes behaves oddly. We are working on this and all the interstellar bugs actively. 4.) Hazardous Body object is presently broken, and has been for some time aparently. We are working on this for a near future release. Don't go driving in lava you shouldn't drive in, now... I'm alive. Just overworked lol. A quick note; I won't be updating bleeding edge right now. Until things get "back to normal" workload irl wise, I just don't have time to maintain a seperate beta branch. So this is the only branch for right now. I will try to keep it to the same quality standards though. The next big bug to fix right now is hazbod not working. I hope to fix that soon.

Thanks for the PR! Since it's memorial day I finally have some time. I will get it merged before the weekend is over with a few other fixes.

Yeah, it seems I didn't implement collisions right. You can download the fix linked above. I will probably release a patch for my work sometime soon too. Certainly.

That catches a few people. Thanks for updating us!

I'm going to try to treat your problems as similar since you are experiencing similar symptoms, and you have provided a log where the other user has not. It looks like the issue is being caused by JNSQ's old implementation of ROCs. You can fix this by finding and deleting the "MyRocksAreBiggerThanYours.dll" file from your JNSQ install. This should have no side effects. Report back if you still have load issues after that. There are also some EVE errors. I'm unsure why. What version of EVE are you using?

There is. It's an optional cfg that is downloaded only if needed that implements the Kopernicus multistar module. Otherwise it falls back to pure stock logic. I can see how that might be problematic for mods actively searching for the module if Kopernicus is present.. I did not think of that scenario. Apologies. Advice on how to make this better is welcomed.

Appreciate the insight.

I had similar issues with the latest nvidia drivers, oddly. Seems to be some kind of new bug. I fixed it by using their "studio" drivers, which despite the name, game fine. Hope your issue is similar / this helps. To the other posters, I will get back to you soon. Posting from a cellphone so can't look at logs now.

I have seen this before, and it's not usually Kopernicus (installing it alone won't do it, at least not the stable version which you should be using), but a "Firespitter.dll" being outdated that can cause this. Unsure what that is or what it does but it's nearly always present when this bug happens. We are working on making this not needed, but the most I can do is make it autoadapt to minor updates. Obviously major updates are going to need work. It's because of how deep we "cut" into KSP to make this mod work, basically. Sorry for missing this so long. You need to download the optional .cfg linked with a release to enable multistar tracking, and put it in your config folder. There is a multistar-associated performance penalty, which is why it's "opt-in" now.

Hello all. I'm sorry I have not been more attentive here. Work has been playing "catch up" AKA "Work until you die" with me since the reopening of the pandemic. I hope the workload lessens soon but we'll see. I will try to answer some support requests now. I am alive and well though, know that. Hello. That Player.log is huge! Let's start with something more basic. Can you delete your KSP.log file from your main KSP directory, run the game, and post the rebuilt resulting file? Also please post your mod list. I tried to discuss this and phase it in with a warning on bleeding edge. I'm surprised it surprises anyone as months of notice were given. I even pinged major users to discuss the change... did I miss you? If so I apologize. There is a compatibility layer in the sense that the old module is removed and the new module added for save game pipelining. I'm not sure what more you would want me to do. I would advise you to just go with the latest naming convention (the module behaves the same but is per panel not per vessel). I do not support old builds anyways, and I target old KSP builds so there is aboslutely no reason to run an obsolete build. Also, this logic is not enabled by default even now (partially due to lack of testing). It is opt in for multistar systems only, by explicitly downloading a .cfg file. This is partially because I know it's not an ideal situation. My apologies. I just don't have like, any testers right at this time willing to test things like that, and my personal time is more limited unfortunately.

It does. You can reenable them by installing a custom asteroid spawner, or enabling the stock one (only good for the stock-based system, like this). This is done by setting Kopernicus_Config.cfg option UseKopernicusAsteroidSystem = Stock. The options are normally UseKopernicusAsteroidSystem = False, True, or Stock. False is for a completely separate mod to take over, True is for Kopernicus to just do it's thing without comets, and Stock is the stock generator without customization.

No, he's right. The reason for the rename is the core module code is changed from one per vessel (which did not work, basically) to one per panel. I apologize for not being more responsive. My work has been at my heels with the reopening in washington state because we're doing well with the pandemic... which of course is great news! For everything but modding... lol.

It has really small bodies by nature, correct? It may run up against this kopernicus bug which to date I haven't found a fix for: https://github.com/Kopernicus/Kopernicus/issues/460

To show how performance has improved in 10x rescales with the new culler: Here is an absolutely huge draw-distance forest that is being distance culled to 5000m. Unfortunately the act of culling nearly 20km of trees (KSP tries to draw that much, don't ask me why, probably some kind of rescale bug/thing) is kind of heavy, but it's even worse to draw them. FPS without the culler is around 20FPS. FPS with is below, quite a bit more playable (~54FPS at 4K on a RTX 2080): No, it's not ideal (a lot of the trees that are lagging us are hidden from view behind that hill and could use some kind of z-culling to hide them too), but 1080p should be better, and I'm still working on it. At least rescale 10x is finally for the first time in history approaching playable numbers with scatters at 100% density. What a novel idea, right? PS: Colliders were enabled for all scatters in this test, which probably further hindered performance, so keep that in mind too.

Kopernicus release-38 R-T-B released this New in this latest version (release-38): 1.) Yet more landscatter optimizations and bugfixes. 2.) Restored the distance culler with a default cull distance of 5000m, because large system rescales need it. Known Bugs: 1.) 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. 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 navbal furthermore sometimes behaves oddly. We are working on this and all the interstellar bugs actively. 4.) Hazardous Body object is still presently broken, and has been for some time aparently. We are working on this for a near future release. Don't go driving in lava you shouldn't drive in, now...