R-T-B

Ah. I thought that error sounded familiar. Yep, when you uninstall only part of parallax that can happen. Glad it's fixed now though!

I'd say you likely removed only one of the two folders it installs. That can cause issues. Anyways mod is legit if you have the specs to run it.

That is the idea, but I thought a ping may be appropriate "just in case." Best efforts is all I can offer, like most modders, so a heads up usually is wise. I can promise I will fix issues presented to me from this change to the best of my ability, and not punt it on you unless I have literally no other choice. This change itself is actually an attempt to finally close a rather ancient issue, in fact, so "unbreaking" is usually the goal.

As a heads up to some parts mods out there: I know this is kind of a "not again!" moment but Kopernicus is again planning to take control of the ModuleDeployableSolarPanel and replace it with a new module called "KopernicusSolarPanel" (note the lack of "s" on the end, which a previous generic fixer that was added to the vessel proper had. This one is per panel and replaces the actual panel module, hence the lack of "s"). Yes, this will eventually be in stable (it's already in bleeding edge). The reason? In short the other approach we tried (a single fixer module for the whole vessel) never really worked properly. We're going back to square one where the math at least added up and worked, frankly. If your mod does anything with these module names directly it should probably be updated to be aware of this. We aren't pushing it out immediately, instead testing it in the bleeding edge. We have a module manager config that attempts to adapt to any mods out there using b9partswitch, etc. That config is attatched to the bottom of this post in a pastebin post. This is purely informational, and intended to prepare people who need to know about this. Most mods probably don't need to do anything (even if I ping you you probably don't), but if you want to "test and see" you can grab the latest bleeding edge preview build here and try it yourself: https://github.com/R-T-B/Kopernicus/releases Relevant config patch (Would love @hemeac's input since a lot of that code is stuff I cut and pasted from his older Kopernicus work). Input welcome. I'll be pinging some major modders so they see this post. @CobaltWolf, @Poodmund, @Nertea, @blowfish If I missed anyone important, my apologies. I'm not the most socially aware modder at times, but I am trying to put the word out there.

Might be more usable now? Kopernicus R-T-B Unified "Bleeding Edge" Edition Release 80 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 80. It contains the following changes: 1.) A hotfix for a bug that prevented some panels from working with some modsets and even some stock panels from working under some situations has been issued. The release notes are otherwise the same as release 79. Known Bugs: 1.) At interstellar ranges, heat can sometimes behave strangely. It is best to turn off part heating when traveling far far away. 2.) When zooming out all the way in map view at interstellar ranges, the navbal sometimes behaves oddly. We are working on this and all the interstellar bugs actively. Please download the right output zip for your version. "LEGACY_18" zips are for 1.8.x, "UBE19+" for anything between 1.9 and 1.11.x. Thanks and as always, report bugs! -RTB

And on that note, I've already logged multiple bugs against this version in combination with other mods It may very well stay in bleeding edge at this rate. I would not use this on an important save, certainly not one with extensive mods.

It is sadly (the math is heavier due to being calculated per panel rather than the vessel as a whole). But I have compensated for it by reducing the rate at which it recalculates from every physics frame to once per second (configurable). It should balance out to about the same performance as such, but it's in bleeding edge for a reason.

New release I could use some testing on. Not being pushed to BE CKAN yet because savegame compatability issues exist, see below. Kopernicus R-T-B Unified "Bleeding Edge" Edition Release 79 R-T-B released this 16 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 79. It contains the following changes: 1.) New solar math that is both more accurate (100% accurate actually), and more performance intensive. 2.) Reduced solar math refresh rate to once per second by default to compensate for heavier math, in Kopernicus_Config.cfg (generated on first run) there is SolarRefreshRate = 1, this is how many seconds between refreshes. 1 is default. Must be an integer. Known Bugs: 1.) The new solar math does not work on current in flight vessels, they will generate no ECs. We are working on a save upgrade system for them, but it is not ready yet. This is mainly a testing release, but could be used in a fresh game. 2.) At interstellar ranges, heat can sometimes behave strangely. It is best to turn off part heating when traveling far far away. 3.) When zooming out all the way in map view at interstellar ranges, the navbal sometimes behaves oddly. We are working on this and all the interstellar bugs actively. Please download the right output zip for your version. "LEGACY_18" zips are for 1.8.x, "UBE19+" for anything between 1.9 and 1.11.x. Thanks and as always, report bugs! -RTB Also, @hemeac, maybe you can help with figuring out how to upgrade existing inflight vessels using a modulemanager config? I'd be most appreciative. Compare solarpanels.cfg now with previous release. We are basically reverting to the module replacement method because nothing else ever worked right. EDIT: Release 80 should do that now, upgrade existing vessels. Would still appreciate a lookover.

I thought "source" was odd too, but he admitted that he pulled Kopernicus out in that screenshot. I do also admit that limits our ability to diagnose. Still, the log isn't useless. I may be able to glean something from it. Looking now. EDIT: Nope, there is too much going on in there to rule anything conclusive. I'd start by removing those "source" and "texture" folders that are seemingly an incorrectly downloaded mod, and seeing what that does.

I appreciate the update. Replied there, thanks.

That's likely. Sorry for the slow replies here, busy work week. I think I'm going to need the KSP.log to diagnose this one properly. I'd ask that if you are having file size issues with that file, you delete it before running KSP (it will regenerate for just that run). That may reduce it's size. You can furthermore zip the resulting file. Then, if it's still too big, try to find a file hosting service like google drive or similar. Somewhere will surely let you upload it. EDIT: Also, what is in the "source" directory if I may ask? In GameData above?

Can I get a picture of your gamedata folder / a list of installed mods?

This is what Big Mun wants us to think!

Thanks for the quality screenshots. I've never made it past Mun/Minmus orbit personally (a bit ashamed to admit), but Duna does indeed look very nice.

That's a nice clue. Try putting the following in a config .cfg file (name does not matter), maybe? @Kopernicus:FINAL { useOnDemand = False } It WILL increase your ram usage. But it might fix the bug.

Just FYI everyone, I'm sure Linx will update this soon, but really, don't use bleeding edge except for testing. It's a beta release, and though once it was the only way to get 1.10+ support, stable has been out for some time now for 1.11.1 and 1.10.1. Bleeding Edge has got active, buggy experiments going on and is intended for testers.

Yeah, does it do the same on the stable branch (available here, now for all versions)? This is likely a new bug from the latest bleeding edge experiment to support multiple versions of KSP with one dll. What KSP version do you run? I'll note it all the same, but for your use case the likely best course of action is to go to stable branch. Thanks for the report.

Kopernicus release-34 R-T-B released this New in this latest version (release-34) 1.) Some additional fixes to the space center camera, which was occasionally appearing slightly too high up in elevation. Known Bugs: 1.) 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. 2.) 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.

Someone was displeased while I pushed to CKAN I take it? Interesting. This is just an experiment and if anyone is upset with it, they can speak up. Just don't use foul language obviously. Or I just missed something. Possible as well.

Big bombshell testing release. We are testing a new adaptable dll that dynamically tries to adjust to the version of KSP it runs on. This is basically "Kopernicus written once, run on many platforms." This is likely to be buggy. If you don't want that, you should probably migrate to stable. We are in tester ground again. The potential for this to reduce the workload in maintaining multiple versions is huge. It's not perfect yet (we still have to target a seperate build for 1.8, for example) but this allows us to work with subpatches (like 1.10.0) without increasing code complexity, and it just makes my life easier... If we can get it working well I'm all for it! Drawbacks as of now? Pretty much just that comet support in the Kopernicus asteroid generator had to be turned off for right now. CometPercentage does nothing, as such. Asteroids still work like usual. I'm working on that, it isn't necessarily permanent, and you can still get comets with an external generator or the stock one. Testers are advised to look for bugs at places versions changed: Gas giant shaders, camera issues, and version specific behavior are all worth investigating for bugs! Without further delay, here is the release. It will be on CKAN soonish. Kopernicus R-T-B Unified "Bleeding Edge" Edition Release 78 R-T-B released this 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 78. It contains the following changes: 1.) Bring up to speed with latest stable stuff. 2.) We are testing a new adaptable dll that dynamically tries to adjust to the version it runs on. This is likely to be buggy. If you don't want that, you should probably migrate to stable. We are in tester ground again. Known Bugs: 1.) At interstellar ranges, heat can sometimes behave strangely. It is best to turn off part heating when traveling far far away. 2.) When zooming out all the way in map view at interstellar ranges, the navbal sometimes behaves oddly. We are working on this and all the interstellar bugs actively. Please download the right output zip for your version. "LEGACY_18" zips are for 1.8.x, "UBE19+" for anything between 1.9 and 1.11.x. Thanks and as always, report bugs! -RTB

We have a fix for this and a few bug things with rescale (I'd know, I made the pull requests), but the binaries aren't updated yet. I imagine Linx will have a release fixing them soon. If you really need it "now" I suppose you can PM me as I have a working version for rescale based on present master sourcecode, but keep in mind, the binaries I'd give you are not official and you can't bug Linx about them. They'd be "inbetween versions" source code wise and he doesn't want to diagnose that. Hence them not being public. @Gameslinx if you'd rather I didn't offer this at all, that's cool too. Just speak up.

It's actually pretty clean code. @Thomas P. did excellent at commenting and documenting and keeping things reasonably understandable. It's just the project has a huge scope. So it's a huge pile of noodles, even if organized noodles. Yeah, the analogy breaks down a bit lol.

Bleeding edge is actually my eternal testing ground. People were advising it for a while because it was the only one to support 1.11.1, but now we have stable doing that as well, so you should really use it:

Map view and very high orbit yes. And no, It won't interfere at all with Spectra. Spectra provides no scaled version replacements.

I've been working on some space center side camera fixes, even though it's not my fault I may be able to work around whatever is going on with KSC switcher while messing with that code. Will look into it later.