Lisias

It's not TweakScale. These "tokens 0100006b and 010004f" means that something in your GameData was compiled to an older or a newer version of something that broke the ABI (Application Binary Interface). When this happens, a buggy thingy called Assembly Loader/Resolver inside KSP gets triggered, and from that point everybody that tries to load a DLL or to use a thingy called Reflection borks relentlessly, including (but not limited to) TweakScale. TweakScale is the only one yelling about the problem, but make no mistake, a lot of add'ons also get screwed by this problem - it only happens that most of them ignores the problem and let you get screwed later when you load your savegame with a borked installment. You didn't gave permissions to read the files you linked. Please set them to public and ping me here, and I will inspect the files. Make backup of your savegames. If you insist on keep going besides the TweakScale warning, your savegames will get corrupted for sure!

Hi! Not so long time ago, a new KSP release broke TS in a horrible way and caused some carnage in the field. Since that time I choose to warn the user when a untested KSP is in use with TweakScale to warn them about the (hypothetical) danger and so give them a chance to backup everything - just in case. Usually a new TS release follows a new KSP release in a few days - a new TweakScale release is currently available on the TS thread. Currently available on github and CurseForge. SpaceDock and CKAN will be updated Friday.

r2 justo solved the settings issue. I started to work on your issue, but I realised it would take more time than available, so I postponed it to the next weekend! What you are seeing is that Celestial Bodies had the correctly "duplicated supressor" code, but I didn't did it for Vessels, and it happens that Asteroids and Comets on KSP are implemented as "Vessels", being the reason that some "celestial bodies" (that are not really objects from the KSP type CelestialBodies, but Vessels in disguise) have the duplicated labels and others don't! Nice catch. The dimming code is somewhat simplistic - if you are looking into the Sun, or if you are looking into the Planet your are orbiting from a reasonable distance, the sky is dimmed. I don't remember seeing a code to check if you are on the dark side of the Planet, I will check it on the WeekEnd. https://github.com/net-lisias-ksp/DistantObject/issues/31

From the Steam Forums. Many players from many games are complaining about this in the last weeks, and I found this post about a guy saying it zeroed it on the Steamworks.NET. I don't know if this stunt is being pulled by someone at Steam, or if 3rd parties managed to inject malicious code on the Steamworks.NET on the user's machine (virii?) to do that - and I don't even know if this affects only Windows users or also Linux and MacOS. I decided to post this here because KSP is listed as one of the games using Steamworks.NET and people here is usually way savvier on this field than the community of most games I'm aware - so the chances of getting this settled/confirmed/whatever here is IMHO way higher than on Steam Forums. I did a quick search on the github repo for "survey" and "survey-smiles" but, obviously, didn't found anything. At least, yet.

This is not a bug at all. It's the normal logging while DOE looks for and loads its internal DLLs. The ERR ADDON BINDER are completely bogus, you should ignore them. Are you really sure DOE is the one screwing up the CommNet? It just doesn't mangles with anything related to it, and since the DLLs are loaded fine (see the DLLs stating their versions below the message saying "Found it"), DOE is not triggering the infamous Assembly Loader/Resolver neither. Publish the whole KSP.log on dropbox or something and post the link here. I will look into it.

Guys. Just came to my attention that Steams users, apparently, are susceptible to an attack to their privacy by Steam's games using Steamworks.net . As it appears, Steamworks.net is sending information to survey-smiles.com , currently under the IP 199.59.243.222 . I can't confirm this yet because, besides had bought KSP on Steam, I download my games using download_depot on the Steam Client's Console and install them manually. In the mean time, the best defense is to block the offending site (or its IP) on your firewall. Steamworks.net is open source, so it's possible to recompile it ripping of the offending code - but Steam will happily overwrite your changes as soon as you update the game or verify the installation - but if you are like me and install everything by hand, an alternative Steamworks.net binary without spyware could be a nice side project to someone with some time to burn! — EDIT — It came to my attention that, perhaps, Steamworks.net could be being compromised on the user's machine, perhaps by virii, perhaps by code injection! — — — — Cheers.

You know, I just didn't thought about it… And the fix is shamefully easy, it's just a matter of multiplying the font size by a value published by KSP's API with the size multiplier (I forgot the name, but a quick search on the KSP's API will do the trick). I will work on it. https://github.com/net-lisias-ksp/DistantObject/issues/30 — — POST EDIT — — As a matter of fact… https://github.com/net-lisias-ksp/KSPe/issues/43

@italon, @Caerfinon, Distant Object Enhancement /L 2.1.1.11r2 was just published with the fix! @Caerfinon, it was a pretty lame mistake on my KSPe.Light library. When I wrote that code, I was less experienced on KSP and ended up trying to reinventing the wheel with a somewhat embarrassing level of success. Once I overcome that 5 levels of grief on this #facepalm moment, by using an already existent ConfigNode method everything felt on their places by themselves. Libraries are a huge help to reuse code - and also to reuse borks. — — — @pmborg, I think I nailed the problem, but I didn't had time to confirm it properly. I will come back to this by night.

ANNOUNCE Release 2.1.1.11r2 is available for downloading, with the following changes: The very same 2.1.1.11 release, but with a yet another updated KSPe.Light with the #28 fix. This release is exactly the 2.1.1.11, but with the KSPe.Light.DOE library updated to fix the problem reported above by @Krazy1 and on this other thread by @italon and @Caerfinon (as well by a402245 on github). No screenshots this time, I'm in hurry. Again™… See OP for the links. — — — — — This Release will be published using the following Schedule: GitHub. Right Now. CurseForge. Right Now. SpaceDock. Right Now. Being a minor re-release, there's no reason to schedule the distribution as I usually do.

BY THE KRAKENS!!! Bill??? https://aviationhumor.net/now-thats-a-go-kart/

ANNOUNCE Release 2.4.6.19 is available for downloading, with the following changes: Bug fixes. States compatibility to KSP 1.12.5 Updates KSPe.Light with bug fixes and 1.12.5 support. Closes Issues: #246 New bug related to IVA and Cameras when TweakScale is installed. That pesky IVA bug is no more!! #hurray!!! Disclaimer By last, but not the least... This Release will be published using the following Schedule: GitHub, reaching first manual installers and users of KSP-AVC. Right now. CurseForge. Right now. SpaceDock (and CKAN users). Right Now. The reasoning is to gradually distribute a potentially Support Fest release in a way that would me allow to provide proper support if anything else goes wrong.

ANNOUNCE KSP Recall 0.3.0.8 on the Wild, featuring: Updates the thing to KSP 1.12.5 Updates KSPe.Light with bugfixes and support for 1.12.5 This is a minor release, aimed to be targeted as 1.12.5 compatible by the distribution channels. — — — — — This Release will be published using the following Schedule: GitHub, reaching manual installers and users of KSP-AVC first. Right Now. CurseForge. Right Now. SpaceDock (and CKAN users). Right Now. No functional changes were applied to this release, it's pretty unlikely that any problem would be detected on the field.

Humm… Gotcha! I probably need to replicate the fix I implemented on DistantFlare to DistantVessel! (Asteroids are "Vessels" on the Game Engine!). I will work on it tomorrow, I mean, this morning after waking. https://github.com/net-lisias-ksp/DistantObject/issues/29

I think this was fixed on July 22, last year and published on Release 2.1.1.9. Additionally, the mouse doesn't trigger the labels for celestial bodies being hidden by something else (unless you use ALT+RMB). At least I couldn't reproduce that misbehaviour now on 2.1.1.11. Are you experiencing this problem now?

Yep, I'm working on it right now. It was a stupid mistake on my KSPe library… I'm polishing some more details on the thingy, I think we will have a new release with this fixed by morning! https://github.com/net-lisias-ksp/DistantObject/issues/28

Confirmed. By exiting the game and reloading it, the alt+click behaviour is forgotten. Additionally, I was mistaken - KT is the one saving configurations on a savegame basis, DOE uses a "universal" settings on <KSP>/PluginData/DistantObject/ folder . I didn't migrated it to savegames yet . Since we are here, what you think is best for DOE, a Universal Setttings, or specific settings for each savegame? In a wat or another, the saving code is working, the settings.file is being update. The proeblem is that the specific settings, "showNames" is not being readed on game startup. Dang, probably a typo somewhere . And, as a matter of fact someone had already reported it and I missed it! https://github.com/net-lisias-ksp/DistantObject/issues/28 I'm will fix this tonight.

Humm… So apparently you found a bug, I will check this tonight! Are you using the latest DOE, right? This one? Are you launching from Steam? If yes, did you tried to bypass the PD-Launcher? As a matter of fact… Great idea! Thanks for the tip!

Parts using custom PartModules (as B9PS) need specialised code to be handled, it's one of the reasons 3rd party support was delegated to the Companion Program. Only parts relying solely on Stock PartModules can be scaled your way.

Ah, missed this one! The settings.cfg you find inside PluginData on DistanceObject's directory is a template used for new savegames. DOE's settings are saved on your savegame, so each savegame can have different settings. The only recommended way to set DOE's settings is by using its Setting's panel. Ah, now we are getting into something! Someone probably forced TweakScale on unsupported parts (had you installed All Tweak?), and so things gone down trough the tubes. Additionally, Forum's MM has a kinda of a bug (a too much optimistic heuristic, to tell you the true) in which in some occasions (unfortunately less uncommon that we would like) the cache is not rebuild and then there's a chance that you upgrade or downgrade something and the ConfigCache is not rebuild, and the aftermath is you using an inconsistent patchset in memory. This can also potentially screw up things, specially TweakScale that is very sensitive to the patching's healthiness. I will try again using All Tweak to see what happens.

I need to intervene and explain that TweakScale is not the cause of your problems. Lack of support for your preferred part is. TweakScale supports Stock and most of the DLCs (Robotics are not supported because they are terribly buggy themselves). If you want support for a 3rd party, you should check the TweakScale Companion Program, or install All Tweak. Thank you for your understanding.

That's the history: I reproduced your installation using the CKAN you provided, added KSP-Recall and TweakScale manually and then the damned thing refused to work! KSP plain didn't loaded the Main Menu scene, no matter what. KSP.log was clueless, but I found the following on the Player.log: By removing the following add'ons: Parallax-OuterPlanetsMod Parallax-StockScatterTextures Parallax-StockTextures I managed to fire up KSP with success, but by then, I could not reproduce the problem! Even by downloading the craft you pinpointed above! First, I loaded the stock Aero Equus. Saved it, loaded it and no problem detected - it even launched without a fuss. Then I enabled TS Chain Scale, scaled up the root part (and the whole craft was scaled up too), saved it, loaded it, launched it - and absolultely no Exceptions were logged nor a misbehaviour was detected. Then I downloaded your robot_3.0.7.craft, did exactly the same (of course not all parts were scaled, as not all parts had TS support), and everything gone fine the same. I want to suggest to you and to @italon to remove Parallax (and anything related to it) and check if things start to work for you. Since I could not reproduce the problem on my rig, it's for sure something on your rigs - perhaps Parallax, perhaps something else screwing up with Parallax that so somehow screwed up TweakScale or, more probably, anything that should be being called its IPartCostModifier by TweakScale - as the point of TS that is borking suggests that the problem may be on that something else, and not on TS itself.

Nope, your KSP is suffering from many issues - what's happening is that TweakScale is the one complaining about, where the others go silent about the failures, letting them to screw you up later on the game. You have lots of problems with ModuleWheels: [EXC 22:17:08.422] NullReferenceException: Object reference not set to an instance of an object ModuleWheels.ModuleWheelSubmodule.OnAwake () (at <4b449f2841f84227adfaad3149c8fdba>:0) PartModule.Awake () (at <4b449f2841f84227adfaad3149c8fdba>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.GameObject:SetActive(Boolean) DragCubeSystem:SetupPartForRender(Part, GameObject) <RenderDragCubesCoroutine>d__31:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) <SetupDragCubeCoroutine>d__46:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) <CompileParts>d__56:MoveNext() UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr) And you have also this pretty weird problem bugging ModuleManager: [EXC 22:12:09.517] [ModuleManager] Post run call threw an exception in loading f4b7b4c6-f092-4f75-909e-8ba42c13cadc, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null: System.Reflection.ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown. at System.Reflection.Emit.AssemblyBuilder.GetTypes (System.Boolean exportedOnly) [0x0012d] in <9577ac7a62ef43179789031239ba8798>:0 at System.Reflection.Assembly.GetTypes () [0x00000] in <9577ac7a62ef43179789031239ba8798>:0 at ModuleManager.PostPatchLoader+<Run>d__16.MoveNext () [0x00538] in <ac37db06097f4706b70066f555f86981>:0 MechJeb is also being screwed by something: [LOG 22:12:12.252] [MechJeb2] Starting the Dispatcher [ERR 22:12:12.282] MechJeb moduleRegistry creation threw an exception in LoadComputerModules loading f4b7b4c6-f092-4f75-909e-8ba42c13cadc, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null: System.Reflection.ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown. at System.Reflection.Emit.AssemblyBuilder.GetTypes (System.Boolean exportedOnly) [0x0012d] in <9577ac7a62ef43179789031239ba8798>:0 at System.Reflection.Assembly.GetTypes () [0x00000] in <9577ac7a62ef43179789031239ba8798>:0 at MuMech.MechJebCore.LoadComputerModules () [0x0002d] in <26f1f8c6d2ae4d2d8ccc568248027be7>:0 And a lot more affecting different add'ons that I quit to count in the middle of the log file. At least but not at last, obviously, TS - the only one trying to inform you about something really, really wrong on your rig: [LOG 22:00:25.605] [KSPe.Binder] Looking for Scale.PartDB.19x.dll on GameData\TweakScale\Plugins\PluginData\... [LOG 22:00:25.606] [KSPe.Binder] Found it on C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\GameData\TweakScale\Plugins\PluginData\Scale.Pa rtDB.19x.dll. [LOG 22:00:25.607] [TweakScale] Support for KSP 1.9.0 to 1.12.4 Version 2.4.6.18 /L [LOG 22:00:25.636] [TweakScale] ERROR: System.Reflection.ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown. at System.Reflection.Emit.AssemblyBuilder.GetTypes (System.Boolean exportedOnly) [0x0012d] in <9577ac7a62ef43179789031239ba8798>:0 at System.Reflection.Assembly.GetTypes () [0x00000] in <9577ac7a62ef43179789031239ba8798>:0 at KSPe.Util.SystemTools+Type+Finder.FindByQualifiedName (System.String qn) [0x00039] in <e78b6736d2e9431a9ef12ef81cc2a206>:0 at TweakScale.Startup.Start () [0x000a3] in <8ce57831e5584c899d8e7b205eefdb07>:0 at error:0 By previous experience, when TS borks with a System.Reflection.ReflectionTypeLoadException it's due some TS DLL really missing from your GameData or due some 3rd party triggering a bug on the KSP guts, more specifically, a thingy called Assembly Loader/Resolver. Since the log above says that it had found the DLL TS wants, the conclusion is that we have some 3rd party screwing up the already buggy Assembly Loader/Resolver. Digging on your log, I found: [LOG 21:59:22.245] [AddonLoader]: Instantiating addon 'PQSModCreator' from assembly 'KopernicusExpansion.RegionalPQSMods' [EXC 21:59:22.993] ArgumentException: Duplicate type name within an assembly. System.Reflection.Emit.ModuleBuilder.DefineType (System.String name, System.Reflection.TypeAttributes attr, System.Type parent, System.Type[] interfaces, System.Reflection.Emit.PackingSize packingSize, System.Int32 typesize) (at <9577ac7a62ef43179789031239ba8798>:0) System.Reflection.Emit.ModuleBuilder.DefineType (System.String name, System.Reflection.TypeAttributes attr, System.Type parent, System.Type[] interfaces) (at <9577ac7a62ef43179789031239ba8798>:0) TriAxis.RunSharp.TypeGen..ctor (TriAxis.RunSharp.AssemblyGen owner, System.String name, System.Reflection.TypeAttributes attrs, System.Type baseType, System.Type[] interfaces, TriAxis.RunSharp.ITypeMapper typeMapper) (at <fd18e0ef899946d5b101c3255bfcbde8>:0) TriAxis.RunSharp.AssemblyGen.Class (System.String name, System.Type baseType, System.Type[] interfaces) (at <fd18e0ef899946d5b101c3255bfcbde8>:0) TriAxis.RunSharp.AssemblyGen.Class (System.String name, System.Type baseType) (at <fd18e0ef899946d5b101c3255bfcbde8>:0) KopernicusExpansion.RegionalPQSMods.PQSModCreator.Awake () (at <f5e1172978524a599c9056aa1686da11>: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() And this appears to settle the question: PQSModCreator is apparently broken (or perhaps is being induced to break by yet someone else?). In a way or another, you will need to remove Kopernicus from your rig in order to have all that other Add'ons above to work (TS is only one of them!). I suggest you to reach Kopernicus Maintainers for further help on fixing Kopernicus, because I don't know it enough to even give you a educated guess about how to fix it! Send them the same KSP.log you sent me, and you can pinpoint this post as a source of information. I can try to help if someone that knows Kopernicus' guts is available to guide me on the debugging! Good Luck!

Do you use CKAN? If yes, can you send me a export of the mods installed? I had looked into your KSP.log, and there's a ton of AddOns!

My experimental fork of MM I NOT PUSHED to anyone, and everything I publish aims to be fully compatible to Forum's MM. The ModuleManagerWatchdog aims to detect potential problems with Forum's MM, as my experimental fork had fixed them in a way or another. That said, the advice is still valid. Reaching me first is usually the best way to fix something around here.

Hi! It's not TweakScale! [ERR 18:16:27.283] Coroutine couldn't be started because the the game object 'ServiceBay.250.v2' is inactive! [ERR 18:16:27.283] Exception handling event onEditorShipModified in class CostWidget:System.NullReferenceException: Object reference not set to an instance at TweakScale.TweakScale.IPartCostModifier.GetModuleCost (System.Single defaultCost, ModifierStagingSituation situation) [0x0000e] in <8ce57831e5584c899d at Part.GetModuleCosts (System.Single defaultCost, ModifierStagingSituation sit) [0x00046] in <0435390348b6470d8166bd1c53b4b100>:0 at ShipConstruct.GetShipCosts (System.Single& dryCost, System.Single& fuelCost, VesselCrewManifest vcm) [0x0003d] in <0435390348b6470d8166bd1c53b4b100>:0 at CostWidget.onShipModified (ShipConstruct ship) [0x00000] in <0435390348b6470d8166bd1c53b4b100>:0 at EventData`1[T].Fire (T data) [0x000b0] in <0435390348b6470d8166bd1c53b4b100>:0 TweakScale is asking for its Module Cost. And since TweakScale only asks for the module cost on an attached part, but the target Module is borked somehow and this is screwing up things. TweakScale is the screaming victim of the problem, by uninstalling TweakScale you still have the problem lingering around waiting for the next victim. It's a long time since I get this by the last time, but when it happened was due B9PS deactivating itself due the presence of another Fuel Switch, and so behaving wrongly when someone asks for its GetModuleCost - but your stackdump is different, if B9PS is involved, then it's a different kind of misbehaviour. Can you send me the craft that triggers this problem? I need to check the parts and then check the patches to see what's happening. That "ServiceBay.250.v2 is inactive' thingy is bothering me, by the way. The craft you was editing uses it?