R-T-B

Not sure it's the cause of your error, but Kopernicus BE is mothballed / severely outdated now due to it not being updated. Use stable.

It's just a config and art really (AFAIK?), so it's all up to the dependencies. The Kopernicus parts should work fine with latest, I'm unsure what the status of the KopernicusExpansion Regional PQS portions are. It's possible it'll just work, though. Not sure.

R-T-B released this now release-86 New in this latest version release-86: 1.) Revert the KSC-sinking on load fixes, as they were causing camera issues. The KSC now sinks sometimes on quicksave load again, as a result (lesser of two evils in this case). To work around this, reload save, same as always. The KSC never sinks permanently. Known Bugs: 1.) Not exactly a bug, but worth mentioning: The Kopernicus_Config.cfg file is rewritten when the game exits. This means any 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 navbal furthermore sometimes behaves oddly. We are working on this and nmonitoring all the interstellar bugs actively. 4.) 1.) 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 for 1.8.x. 2.) Mutlistar Solar panel support requires an additonal config file, attatched to release. 3.) If you use the "AddWatchdog.cfg" file, A fake celestial body isthen used to fix the distant landing-gear sinking bug. This body is called "KopernicusWatchdog" and will a.) intentionally keep it's distance from you at all times and is b.) invisible. The body is usually hidden from in game processes, but this is new territory having to use another moving celestial to correct a bug, so there may be side effects. Also, Principia does not work with this fix at this time, unfortunately. Those users may try "MakingLessHistory" mod, the old workaround. 4.) When using the ultra/atlas shader, ocean effect customization (color etc) is unreliable. Please use only high shader level (shader level 2) or lower if working with stock ocean effects. This does not effect scatterer or other ocean rendering mods.

Just a heads up to everyone, we are tracking an emerging bug from the last camera change that happens on occasion at high altitude (1000m+) launch sites. In this case, the camera is elevated about 1000m about the KSC, which is a bit more problematic. Working on a fix (or alternatively just a revert) soon. In the meantime if effected Release-83 does not have this issue.

"I'm still ALIVE!" Roman Emperor Caligula, after being stabbed repeatedly by the Praetorian guard, and likely having said plenty. That one will always stick with me. A software dev (maybe me?) releasing a cutting edge new feature everyone is sure to love...

I see. It seems the first load loop is the problem. It raises the elevation slightly on first load and that sticks. As you said, it's slight, but it's there. I think I can actually fix that. It's minor as you said, but no sense leaving it if it is fixable... I'll take another stab at it soon. EDIT: Actually, I'm just going to leave it as it is if no one else cares, because that code is a rats nest I don't want to poke right now... lol. It works and doesn't affect gameplay? Sounds good to me.

Well there are two sinking bugs... the first is the bad one on distant bodies that can actually affect gameplay. The one I am talking about here only happens on quickloads at the KSC, and it results in the KSC sinking into the ground about 5m or so. It too is cosmetic, as a reload fixes it, but... not ideal. Anyways, am I understanding you correctly that it's still bugged for you? As in the elevation change still happens? Hmm. Odd. I could've sworn that would at least change the behavior somewhat... oh well. What is the exact procedure you follow to produce an elevation change like that, to be clear and enable proper replication? I don't think a clean install is needed, this should work basically the same in most any install or circumstances. I appreciate the feedback. May look into making this fix "opt-outable" in the near future (probably via the config file) but for now, it's not that bad, so I'll probably wait for a bit more feedback.

I would note a lot of the bugs with the stock alarm clock are due to it not respecting some mod variables. I still think this alarm clock is better/more reliable but if you want to use the stock one, I believe KSPCommunityFixes addresses at least a few of it's bugs. It is possible to hide it but I think it requires changes to the stock code, unsure if KAC wants to go that route. Maybe KSPCommunityFixes would be willing to add that as an option (hiding the stock alarm clock). I'd ask them as they do those kind of mods for "QOL" fixes regularly.

QFT. This is true of pretty much every mod that is free. People forget it too easily. The only small difference is some mods are lucky enough to have a (almost always small) team of beta testers. Those beta testers are also free-time unpaid peoples who may or may not have time that day of the week though. So same end result. You often end up being the beta tester. Be patient with us, please. We do our best. FWIW, I believe Kopernicus, which an absolute metric ton of mods depend on, has like 3 beta testers and I'm usually lucky to get one of their attentions before a release. Often the Q&A team is the dev in question, and you, the user. Be a team player. PS: Keep in mind, these statements are general in nature and apply everywhere, not just to Lisias. He's as susceptible to "borking" as he calls it as any lone dev, though.

An attempt at a compromise re-the camera angle bug. Try it out and advise. R-T-B released this now release-85 New in this latest version release-85: 1.) Attempt to correct a bug where the game camera would respawn at the KSC sometimes at an incorrect angle or elevation. Needs testing, but seems improved and more stock-alike. Known Bugs: 1.) Not exactly a bug, but worth mentioning: The Kopernicus_Config.cfg file is rewritten when the game exits. This means any 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 navbal furthermore sometimes behaves oddly. We are working on this and nmonitoring all the interstellar bugs actively. 4.) 1.) 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 for 1.8.x. 2.) Mutlistar Solar panel support requires an additonal config file, attatched to release. 3.) If you use the "AddWatchdog.cfg" file, A fake celestial body isthen used to fix the distant landing-gear sinking bug. This body is called "KopernicusWatchdog" and will a.) intentionally keep it's distance from you at all times and is b.) invisible. The body is usually hidden from in game processes, but this is new territory having to use another moving celestial to correct a bug, so there may be side effects. Also, Principia does not work with this fix at this time, unfortunately. Those users may try "MakingLessHistory" mod, the old workaround. 4.) When using the ultra/atlas shader, ocean effect customization (color etc) is unreliable. Please use only high shader level (shader level 2) or lower if working with stock ocean effects. This does not effect scatterer or other ocean rendering mods.

yeah I play at 10x rescale and the angle change is present there, just barely detectable. I think at stock scaling you'll notice it more. I'm still trying to think up a "best of both worlds" option, hoping for a last minute epiphany (they happen, albeit infrequently). There"ll be a patch of some sort for this by tomorrow for sure though. In the meantine, anyone really bothered by it can just go back one version.

I believe this is a side effect of the change that fixed the "sinking KSC bug." I'm not sure I can fix it without restoring the sinking KSC on quicksave-load. Thoughts? Which is worse?

If you have a log from this, I'd very much appreciate it. I suspect a floating point error of some kind... but don't know for sure. Yes shadows are an ongoing issue. I would suggest scatterer with long distance shadows on until I figure out how to fix them. On that note, new release: R-T-B released this release-84 New in this latest version release-84: 1.) The bug where quickloads would sometimes cause the KSC to sink, requiring yet another quickload to fix, has been patched (finally). Known Bugs: 1.) Not exactly a bug, but worth mentioning: The Kopernicus_Config.cfg file is rewritten when the game exits. This means any 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 navbal furthermore sometimes behaves oddly. We are working on this and nmonitoring all the interstellar bugs actively. 4.) 1.) 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 for 1.8.x. 2.) Mutlistar Solar panel support requires an additonal config file, attatched to release. 3.) If you use the "AddWatchdog.cfg" file, A fake celestial body isthen used to fix the distant landing-gear sinking bug. This body is called "KopernicusWatchdog" and will a.) intentionally keep it's distance from you at all times and is b.) invisible. The body is usually hidden from in game processes, but this is new territory having to use another moving celestial to correct a bug, so there may be side effects. Also, Principia does not work with this fix at this time, unfortunately. Those users may try "MakingLessHistory" mod, the old workaround. 4.) When using the ultra/atlas shader, ocean effect customization (color etc) is unreliable. Please use only high shader level (shader level 2) or lower if working with stock ocean effects. This does not effect scatterer or other ocean rendering mods.

I believe the JNSQ problems are resolved. They were primarily a stock bug, that occured when JNSQ was combined with Galaxies Unbound, IIRC. They should be fixed if you install KSPCommunityFixes. Fixing stock bugs is beyond the scope of Kopernicus, so I regularly punt stock issues over to that project and advise everyone install it to avoid known pitfalls. As for this report, the logs are pretty messy, but I'll see if I can't make any sense of them. If so, I'll edit this. EDIT: No, I'd need the full Logs folder to make heads or tails of that, I'm afraid. Maybe you can zip that?

This is handy. It beats my KOS countdown script that just beeped at me. Thanks!

As a Kopernicus dev, I try to stay mostly neutral re planet packs but I have to just state for being "in development" I have always found your work quite impressive. Keep it up.

Saying I fixed this in any capacity is generous, just FYI. I reported it but was busy with work beyond that. @Gotmachine did the actual fix and I just hooked him up with some beta testers. Still, a good fix and I know at least GU users will benefit from it.

FYI The KSPCommunityFixes with this fix is now out. The fix is called "ROCValidationOOR" and is on by default.

Kopernicus can be set to enforce a shader quality, however it will inform you with big text if it is doing so. It does not by default, and if RSS is using this, you should get a big text message about it.

That's probably the same as a bug I noticed. The "Generator" is when you run your engines, a generator makes power. It's short lived (only working when engines fire), and apparently the planner not only includes this power, but inverts it, making it negative. Fortunately in gameplay the output is positive, as it should be.

In one of the other videos they commented that it's now a character trait. Some kerbals do, some don't!

Well just because it's not my fault doesn't mean I won't try to help. I've pinged a few people. Start with updating SigmaDimensions and seeing if that helps though. I think you can find it here: https://github.com/Sigma88/Sigma-Dimensions Also, you do have an up to date Kopernicus? If not that never hurts. https://github.com/Kopernicus/Kopernicus/ Grab them from "releases" under each projects main page. EDIT: This error here suggests Kopernicus needs reinstalling as well, it seems to be missing Kopernicus.parser.dll [ERR 19:38:15.890] AssemblyLoader: Exception loading 'SigmaDimensions': System.Reflection.ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown. at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes(System.Reflection.Assembly,bool) at System.Reflection.Assembly.GetTypes () [0x00000] in <9577ac7a62ef43179789031239ba8798>:0 at AssemblyLoader.LoadAssemblies () [0x000e6] in <cd473063d3a2482f8d93d388d0c95035>:0 Additional information about this exception: System.TypeLoadException: Could not resolve type with token 01000014 (from typeref, class/assembly Kopernicus.IParserEventSubscriber, Kopernicus.Parser, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null) System.TypeLoadException: Could not resolve type with token 0100003c (from typeref, class/assembly Kopernicus.Configuration.BaseLoader, Kopernicus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null) Maybe there are two conflicting Kopernicus.Parser.dlls? If you find it still doesn't work after reintalling those, try removing any duplicates. You only need one. (You can just do a file search for "Kopernicus.Parser" in your gamedata)

You got the right logfile, that should be enough. I'll take a look right now and edit this with what I find. EDIT with findings: These are the main errors that seemingly start an error cascade: [EXC 19:38:17.636] ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown. System.Reflection.Assembly.GetTypes () (at <9577ac7a62ef43179789031239ba8798>:0) KSPe.IO.Hierarchy`1+<>c[T].<calculateTypeRoot>b__10_0 (System.Reflection.Assembly assembly) (at <9f7cd9a529194dc4a60f3cf218f8503b>:0) System.Linq.Enumerable+<SelectManyIterator>d__167`3[TSource,TCollection,TResult].MoveNext () (at <351e49e2a5bf4fd6beabb458ce2255f3>:0) System.Linq.Enumerable+WhereSelectEnumerableIterator`2[TSource,TResult].MoveNext () (at <351e49e2a5bf4fd6beabb458ce2255f3>:0) System.Linq.Enumerable.TryGetFirst[TSource] (System.Collections.Generic.IEnumerable`1[T] source, System.Boolean& found) (at <351e49e2a5bf4fd6beabb458ce2255f3>:0) System.Linq.Enumerable.FirstOrDefault[TSource] (System.Collections.Generic.IEnumerable`1[T] source) (at <351e49e2a5bf4fd6beabb458ce2255f3>:0) KSPe.IO.Hierarchy`1[T].calculateTypeRoot () (at <9f7cd9a529194dc4a60f3cf218f8503b>:0) KSPe.IO.Hierarchy`1[T].CalculateTypeRoot () (at <9f7cd9a529194dc4a60f3cf218f8503b>:0) KSPe.IO.Hierarchy`1[T]..ctor (KSPe.IO.Hierarchy hierarchy) (at <9f7cd9a529194dc4a60f3cf218f8503b>:0) KSPe.IO.Hierarchy`1[T]..cctor () (at <9f7cd9a529194dc4a60f3cf218f8503b>:0) Rethrow as TypeInitializationException: The type initializer for 'KSPe.IO.Hierarchy`1' threw an exception. KSPe.Util.SystemTools+Assembly+Loader`1[T].TryPath (System.String path, System.String[] subdirs) (at <9f7cd9a529194dc4a60f3cf218f8503b>:0) KSPe.Util.SystemTools+Assembly+Loader`1[T]..ctor (System.String[] subdirs) (at <9f7cd9a529194dc4a60f3cf218f8503b>:0) DistantObject.Startup.Awake () (at <e30ec9083ad44f3d8c362bd51ed054ea>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.GameObject:AddComponent(Type) AddonLoader:StartAddon(LoadedAssembly, Type, KSPAddon, Startup) AddonLoader:StartAddons(Startup) <LoadObjects>d__90:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) <CreateDatabase>d__71:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) GameDatabase:StartLoad() <LoadSystems>d__11:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) LoadingScreen:Start() [EXC 19:38:58.580] Add to mod list threw an exception in loading SigmaDimensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null: System.Reflection.ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown. at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes(System.Reflection.Assembly,bool) at System.Reflection.Assembly.GetTypes () [0x00000] in <9577ac7a62ef43179789031239ba8798>:0 [EXC 19:45:13.893] [ModuleManager] Post run call threw an exception in loading SigmaDimensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null: System.Reflection.ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown. at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes(System.Reflection.Assembly,bool) at System.Reflection.Assembly.GetTypes () [0x00000] in <9577ac7a62ef43179789031239ba8798>:0 at ModuleManager.PostPatchLoader+<Run>d__16.MoveNext () [0x00538] in <a0f9d7e5c0864d32839c501c53536c2a>:0 From that, we can infer that something is wrong with either KSPe (unsure what that is, I think something from @Lisias?) and SigmaDimensions. If I had to guess, I'd say something is out of date, and I'd start by making sure SigmaDimensions is up to date. Either way, it's not Koperncius. Kopernicus is simply reporting that you've got instability that may affect the mods ability to operate. I've pinged KSPe's author above in case they know more.

Don't worry about it. Glad you got it fixed!

You knew it had to be wrestling for control. It was the right word that got me there. I just had to look for the places computers might wrestle (code-wise, people).