Lisias

Duuude…. Your KSP.log is littered with problems! Let's try to fix them one by one. By first, you have multiple copies of ModuleManager installed, and by some reason the OLDER one was selected to be run! [LOG 16:20:14.200] [ModuleManager] version 4.1.4.0 at C:\Kerbal Space Program 3\GameData\ModuleManager.4.1.4.dll won the election against Version 4.1.4.0 C:\Kerbal Space Program 3\GameData\Benjee10_Orion_v1.2.0\GameData\ModuleManager.4.2.2.dll Version 4.1.4.0 C:\Kerbal Space Program 3\GameData\CoriolisSpaceSystems_v1.0.0\GameData\ModuleManager.4.1.4.dll Version 4.1.4.0 C:\Kerbal Space Program 3\GameData\IFS\ModuleManager.4.1.4.dll Version 4.1.4.0 C:\Kerbal Space Program 3\GameData\ModuleManager.4.2.1.dll Version 4.1.4.0 C:\Kerbal Space Program 3\GameData\ModuleManager.4.2.2.dll Version 4.1.4.0 C:\Kerbal Space Program 3\GameData\Shuttle-Orbiter-Construction-Kit-master\GameData\ModuleManager.4.1.4.dll Please remove GameData/ModuleManager.4.1.4 and GameData/ModuleManager.4.2.1 files from your rig. You are being exposed to MM bugs that were already been fixed. Additionally, it's usually a good idea to have ZeroMiniAVC installed. Some add'ons distribute an older version of MiniAVC that is known to cause problems and getting rid of it is usually the easier way out of the problem. If you use CKAN, you don't need MiniAVC at all, and if you don't use CKAN, KSP-AVC (the full package) is way more convenient. You also have ShadowWorks installed in a completely weird place. You are using Windows, but somehow some MacOS artefacts leaked into your GameData. You have it installed on a directory called GameData\__MACOSX\ShadowWorks_Stockalike_SLS_2_0_5_1\ShadowWorks , but you need to install it on GameData\ShadowWorks . Completely remove the __MACOSX directory from your rig, and reinstall ShadowWorks properly. You also have yet some more ModuleManager DLLs on your rig: [LOG 16:20:13.644] Load(Assembly): Benjee10_Orion_v1.2.0/GameData/ModuleManager.4.2.2 What hints that you also installed Benjee10's Orion wrongly. Completely remove the directory GameData\Benjee10_Orion_v1.2.0 and reisntall Benjee10's Orion correctly. And also, [LOG 16:20:13.659] Load(Assembly): CoriolisSpaceSystems_v1.0.0/GameData/ModuleManager.4.1.4 [LOG 16:20:13.659] AssemblyLoader: Loading assembly at C:\Kerbal Space Program 3\GameData\CoriolisSpaceSystems_v1.0.0\GameData\ModuleManager.4.1.4.dll And also: [LOG 16:20:13.688] Load(Assembly): IFS/ModuleManager.4.1.4 [LOG 16:20:13.688] AssemblyLoader: Loading assembly at C:\Kerbal Space Program 3\GameData\IFS\ModuleManager.4.1.4.dll [LOG 16:20:13.692] AssemblyLoader: KSPAssembly 'ModuleManager' V2.5.0 And also: [LOG 16:20:13.767] Load(Assembly): Shuttle-Orbiter-Construction-Kit-master/GameData/ModuleManager.4.1.4 [LOG 16:20:13.767] AssemblyLoader: Loading assembly at C:\Kerbal Space Program 3\GameData\Shuttle-Orbiter-Construction-Kit-master\GameData\ModuleManager.4.1.4.dll [LOG 16:20:13.768] AssemblyLoader: KSPAssembly 'ModuleManager' V2.5.0 All these add'ons are badly installed. You need to completely remove the following folders GameData\CoriolisSpaceSystems_v1.0.0 GameData\IFS GameData\Shuttle-Orbiter-Construction-Kit-master And then reinstall properly these add'ons! You may want to consider using some package manager as CKAN or CurseInstaller to help you on your rig... I expect some of the problems littering your KSP.log to be vanished by doing this. I also found the following fatal problem: [EXC 16:28:26.028] FileNotFoundException: Could not load file or assembly 'ToadicusTools, Version=0.22.4.4, Culture=neutral, PublicKeyToken=null' or one of its d PartModule.Awake () (at <39c0323fb6b449a4aaf3465c00ed3c8d>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.GameObject:AddComponent(Type) Part:AddModule(String, Boolean) Part:AddModule(ConfigNode, Boolean) PartLoader:ParsePart(UrlConfig, ConfigNode) <CompileParts>d__56:MoveNext() UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr) You need to install this ToadicusTools (I don't know what it is, but it is needed by TweakableEverything - so you may want to seek further help with its maintainer!), or nothing in your rig will work properly - including TweakScale. It's nonsense to try to further diagnose your KSP.log, because at this point you have so many problems on it that is more than likely that the TweakScale one is a consequence of these problems, and not a problem affecting specifically TweakScale! Please implement the fixes above and try again. Send me the new KSP.log if something else borks on you! Good Luck! I need the full KSP.log published on DropBox or something in order to diagnose your issue. Patches are never the cause of this problem, it's 99% of the time another add'on that borked being loaded and triggered a nasty bug on a thingy called Assembler Loader/Resolver. Send me the full KSP.log (don't try to post it here on Forum, it will not work and will harm Forum) and I will find the problem.

So… Someone with more than enough money wanted a new Ventador Lambo, but by some reason he likes water more than asphalt. So this crazy dude did this: Yeah. The dude built a high performance catamaran (180MPH!!!) with Lamborghini look and feel (and parts!!). More : https://yachting.entropia.mc/?post_type=portfolio&p=1488

Hi! I need the full KSP.log, and not only the error messages, as the rest of the log have the information I need to pinpoint who is borking on us. Additionally, given the nature of the problem, I may need the ModuleManager.ConfigCache too. See the OP, on the hidden section called Support, to see where you can find these files. Zip them and publish them using dropbox or something similar - or, if you have a github account, you can drag and drop them on a comment on this link. Paste a link to your post here so I can connect the dots!

Try to mangle the "minimumTargetRelativeAngle" thingy to see if anything changes. In in the middle of a <piii>storm at dayjob, I don't know when I will have spare time to tinker with the Poodmund's skybox - probably on the weekend. But I'm guessing that this setting may help you on the matter. Cheers!

Found it! [ERR 15:17:24.641] [AssemblyLoader] Exception when getting assembly attributes: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown. Additional information about this exception: System.TypeLoadException: Could not load type of field 'JanitorsCloset.JanitorsClosetLoader:Log' (0) due to: Could not load file or assembly 'KSP_Log, Version=0.1.1.7, Culture=neutral, PublicKeyToken=null' or one of its dependencies. assembly:KSP_Log, Version=0.1.1.7, Culture=neutral, PublicKeyToken=null type:<unknown type> member:(null) signature:<none> You need to install this thing, it's a missing dependency for JanitorsCloset. Interesting enough, I found no warning about missing dependencies on your KSP.log...

This is truly demonic. I would had made a hell of a fuss on my neighbourhood with one of these when young!! Put one of these on my hands and I will show you… (after leaving jail ) I think I would have company doing my time!

Send me screenshots of the problem, your KSP.log and a link for the Skybox you are using Let's see if I manage to reproduce the thing here on the week end! It's not drawing some parts on distant vessels. I need to study what changed on some ReStock parts and try to code something to convince DOE to draw them.

Hi! The (more or less) current list of Companions can be found here: https://github.com/net-lisias-ksp/TweakScaleCompanion Anything else is a trial-and-miss , as you have realised. The reason is that as 3rd party PartModules are added, I need to inspect them in order to understand how they work, and then be able to cook a recipe teaching TweakScale how to scale them (and then write a MM patch). Sometimes it's really easy, sometimes not at all! You will find some comprehensive (but somewhat messy) tutorials here.

A ramp will do. As a matter of fact, is how boarding parts were implemented on AP+! The problem I see is doing a ramp that would fit a size1 or size1.5 tail cone without being too steep for a Kerbal to use when extended. The MD-85 stairs is more or less 45 to 50º degrees, and I don't think a Kerbal will climb it without some kind of help. On the other hand, you can extend the ramp to allow it to be less steep, trading angle for length. It~s how the AP+ ramp were implemented, by the way. It will not be exactly as the MD-85 you want to mimic, but it may be near enough! Cheers

This kind of stairs on KSP is tricky, because on KSP the crafts use ladders, that relies on a different code to do the job. So you will need to do a stair with the step large enough to induce KSP physics ot think it's something like a ground stairs, like the stairs on the top of the VAB - and, then, I don't think such device would fit on a 1.5 or even 2.0 bulkhead profile as I would use on a MD-87. I think this is exactly the reason the "Size 1.5 Air Ramp" is a ramp, by the way.

As far as I understand, this is already happening - if you are on the surface of the Mün, you will not see the stars while on the bright side. The stars are dimmed when your eyes are receiving direct or indirect sunlight (it's the reason you don't see the stars on the surface of the Moon at the bright side, the sunlight being reflect by the sand is reaching your retina). Same thing while orbiting Earth - if you can see the Earth while being illuminated by the Sun, then the light bring reflected by the planet will prevent you from seeing the stars the same. However if give your back to both Sun and Earth, when you will be able to see the stars alright because there will be no direct or indirect sunlight reaching your eyes (there's no scattering on Space). Are you sure this is not happening for you? I just fired up my test bed and the stars became visible once Kerbol is occluded by Kerbin! I think there's something else playing a role on this issue. Are you guys using a custom skybox or any other visual enhancement? More or less. When startuping the game, DOE checks if there's no customized values on the KSP/PluginData. If none are found, it tries to read the Default values from a "hidden" file on its plugin data. If the file is found, the default values are read, if not the values hardcoded on the DLL are used. Once you customize the settings, the new values are stored on the KSP/PluginData. BUT… As I said, I failed to prevent that the new customisations settings would be needed by 3rd parties, so the whole model will be reworked. It will will not change dramatically, but it will change a bit. https://github.com/net-lisias-ksp/DistantObject/issues/25

For obvious reasons (I burned the midnight oil half the week!), Midnight Syndrome by Lebowski.

Don't bother, it's screwed up. I just realised that I added customisation settings intended to be eventually used by 3rd parties on Planet Packs, but didn't provided a way to allow them to patch the damned things, forcing the user to do it manually!! I will tackle it down on Issue #25.

Hi! You got bitten by a nasty KSP bug on a thingy called "Assembly Loader/Resolver", this is what loads DLLs to be used by KSP and so any problem on it is pretty nasty. The problem is triggered when something fails to be loaded by any reason, what breaks something inside the thing and from that point, anything else trying to load somethings fails no matter what - even when everything is right. Since TweakScale cannot allow a savegame to be loaded when it is not on a consistent state (as this would destroy all scaled parts on the savegame!!), TweakScale checks if everything is allright after being loaded and, if not, yells about so you can do something about - like asking help here. On the KSP log you sent, the problem appears to be unrelated to USI at all… Apparently it's EnvironmentalVisualEnhancements! [ERR 17:55:41.210] ADDON BINDER: Cannot resolve assembly: Utils, Culture=neutral, PublicKeyToken=null [ERR 17:55:41.213] AssemblyLoader: Exception loading 'CelestialShadows': System.Reflection.ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadExce ption' 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 <39c0323fb6b449a4aaf3465c00ed3c8d>:0 Additional information about this exception: System.IO.FileNotFoundException: Could not load file or assembly 'Utils, Version=1.11.6.1, Culture=neutral, PublicKeyToken=null' or one of its dependencies. File name: 'Utils, Version=1.11.6.1, Culture=neutral, PublicKeyToken=null' It's trying to load a thingy called Utils, but this thing is not being found. This is that triggers the Assembly Loader/Resolver bug - from this point, everybody else is being screwing - as DOE. Even Recall is being caught indirectly by this mess! [LOG 17:55:51.764] Calling KSP-Recall.ModuleManagerSupport.ModuleManagerAddToModList() [EXC 17:55:51.775] Add to mod list threw an exception in loading CelestialShadows, Version=1.11.6.1, Culture=neutral, PublicKeyToken=null: System.Reflection.ReflectionTypeLoadExce ption: 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.ModListGenerator.GetAdditionalModsFromStaticMethods (ModuleManager.Logging.IBasicLogger logger) [0x00021] in <410b7909691747c78c895491c954d2a4>:0 I think that USI was just an innocent bystander that had the bad luck of stepping on the mine, triggering this cascade of events. Perhaps whatever installed USI updated EVE too, and then you got the impression that USI was the problem! In a way or another, your best line of action is to reach EVE maintainers and ask for help about the missing "Util" thingy. You may want to uninstall EVE until they fix the problem, otherwise you will not be able to startup your game! (Removing TweakScale will only remove the one yelling about the problem, the problem will be still there, screwing up silently everybody else!)

It's a pretty counter-straightforward formula and the new parameters trim it in a equally counter-straightforward way. minimumSignificantBodySize is simple: if defines the smaller body (in visible pixels) that will be considered on the sky dimming. It helps to make things faster on Potatoes by ignoring bodies with an apparent size smaller than the threshold. In pixels. minimumTargetRelativeAngle is the relative angle between Camera and the current body being calculated in which the dimming will happen. You can trim the point of the screen the current body will trigger dimming the sky. Given the other parameters, it ended not being that useful in the end because more than one body can trigger the sky dimming (and, when this happens, the "stronger" one will prevail, and not the one you may thinking of). In degrees from 1 to 180. not only size, but distance matters on the formula! referenceBodySize the size of the reference body (usually the Sun). The size of all the bodies are floored and then normalised with this parameter before being fed into the formula. This one will be useful on custom Star Systems where the Sun (always the brightest body in the visible sky) is smaller than Kerbol. I don't have the slightest idea about the unit of this thing!! That's really great news. I'm currently facing some difficulties to test this on visuals add'ons because I'm essentially using mobile GPUs (and the really crappy ones!). I'm still fighting to buy a nice GPU card, but things are still incredibly expensive around here due import taxes (really, really expensive - the final tax is 115% the price you paid for the good, shipping and insurance included! it's plain nuts!). Buying a second hand one (what would help save a bit of money) is out of question due the cripto-mining breakage flooding the market with badly beaten GPUs - it would worth the risk if the card would be being sold by 25 to 30% of the MRSP, but at 80% to 100%? Now and then I find a offer on eBay for a brand new one cheaper that some second hand ones! Thanks for the help!!

Well, without more information, I can only guess. Send me the KSP.log after reproducing the problem so I can check for some Exception or any other weirdly. But, back to the guess: apparently you had diagnosed the mishap yourself - something on the new BDArmory Plus is reseting something, and TweakScale is being caught with its pants down. Since some time TweakScale ceased to force its weight on 3rd parties (see this post for more information), and started to rely on a sane KSP runtime (exactly to prevent TweakScale from doing this to 3rd parties, by the way). Problem is that once TweakScale started to rely on the KSP runtime (what was made possible by Recall), it became vulnerable to being screwed by 3rd parties. Apparently it was what happened to you. Since I had problems with Procedural Parts myself (see this post for more information), I think I know why BDA+ guys did things this way (again, assuming it's really DBA+): in a nutshell, Procedural Parts neglects correct data to KSP on OnLoad, and so someone else needs to update it by brute-force later. The way I solved it for TweakScale was to write a patch on KSP-Recall to scavenge the correct data and fill the empty spaces while loading KSP, what for all effects solves the root problem without screwing up anybody else. You can find the patch here. And I did it on Recall because fixing 3rd parties is completely out of scope for TweakScale, Recall is the place where I choose to fix these problems. This removes TweakScale from a problem in which it's completely innocent, and centralizes my fixing efforts on a single place where it's easier (or less hard) to have everything synchronised. What I suggest you to do is: Be absolutely sure it's the BDArmory Plus the source of the misbehaviour: Revert BDA+ to the previous release. If the problem goes away, you have confirmation. Once you had confirmed the problem is BDArmory Plus, reach the maintainers explaining the problem and pinpointing the patch I linked above (or just link this post to them and call it a day!) With this information, they will be able to decide if they add a dependency on KSP-Recall (and activates the patch for themselves too) or if they try to fix the problem themselves on a custom patch (and remove whatever clutch they hypothetically did on code). Both ways will work, it's the nice thing about fixing things using patches. Assuming the problem is really on BDArmory Plus, the maintainers ideally should take proper measures to fix the problem on their side on a way that respects the KSP's PartModule's life cycle (as I did on Recall), otherwise they will be screwing up any 3rd parties that need tp trust the PartModule's info (and not only TweakScale). Cheers!

Da Vinci… The Kerbal among Humans!!!! You see… Building a Da Vinci's Bridge would do a nice KSP Challenge, this game physics should be able to handle a small to medium bridge. One would need to use the longer Beams to minimize a bit the part count, but it appears to be doable to me! The Seamaster and the MBR are some of my favorites concepts ever - with the Beriev being slightly more Kerbal! (see the OP of this thread!) At the time I was toying with hydrofoils, I came to the same conclusion: it's way easier to takeoff from water with them! Sounds like a mission for the BDArmory guys! (it's KSC bombing season again!! )

Distributin betas on CKAN is hardly a good idea! There were some changes on the road map that need to be implemented first, anyway.

Hi. The fastest way to get in contact with me is to post your questions about TweakScale on the TS' Forum! But now and then a kind Kerbonaut hints me, so no harm is done. Let's see your case.. Humm. You got bitten by a nasty KSP bug. There's a thingy called Assembly Loader/Resolver on KSP that it's in charge of loading DLLs and bind its contents into the game. Unfortunately, this thing is utterly bugged since forever, and the bug is triggered by something failing to load a needed DLL. When this happens, everything trying to load something after gets screwed by the bug and ends up being falsely flagged as a problem. In your case, the real problem is: [ERR 17:55:41.213] AssemblyLoader: Exception loading 'CelestialShadows': 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 <39c0323fb6b449a4aaf3465c00ed3c8d>:0 Additional information about this exception: System.IO.FileNotFoundException: Could not load file or assembly 'Utils, Version=1.11.6.1, Culture=neutral, PublicKeyToken=null' or one of its dependencies. File name: 'Utils, Version=1.11.6.1, Culture=neutral, PublicKeyToken=null' The `CelestialShadows` thingy is trying to load an Assembly (the thingy that a DLL loads into KSP) called `Utils`. But it was not found, triggering the bug and, later, when TweakScale tries to load its own DLLs, it gets screwed and yells because it can't allow you to load a savegame without that DLLs loaded (or your savegame will get screwed too). `CelestialShadows` is a thingy from EnvironmentalVisualEnhancements. You will need to reach EnvironmentalVisualEnhancements maintainers , as I don't know how to fix it. Alternatively, you may want to remove EnvironmentalVisualEnhancements from your KSP in order to be able to play until the EVE maintainers are able to help you! Cheers!

Software Development is nothing more than stacking layers of abstractions, multiplying the failure points.

The Burning Man 2022. (we need a Burning Kerbal Festival around here!!)

The Zeppelin could be boarded by passengers by the Mooring Mast. I was not commonly used, tough. Can't imagine why! Of course, this didn't prevented Americans to try it that way! (in the end, the high winds prevented boarding the vessel on the Empire States)

Yes, there were some discussions in the past - but as the time gone by (and the bugs blew up), I ended up forgetting about this subject! Well, I will not forget it again: https://github.com/net-lisias-ksp/TweakScale/issues/264 Let's see how the remaining of this year behaves - so I can find time to give some care to TweakScale! Most of Serenity parts are already supported, including Science. The only parts I'm reticent to publish are the robotics, because they are pretty buggy and unstable as they are, what to say after scaling them. But, as long you understand that things may blow up horribly in your savegame by trying it, there are two ways in which you can try your luck and scale them: By editing this file and removing the "//" from the patches: https://github.com/net-lisias-ksp/TweakScale/blob/master/GameData/TweakScale/patches/SquadExpansion/Serenity/Robotics.cfg By downloading the latest TweakScale BETA and then creating a directory called "TweakScaleExperimental" on your GameData: https://github.com/net-lisias-ksp/TweakScale/releases/tag/PRERELEASE%2F2.5.0.49 Both approaches will work, but the BETA has improved support - and both will be risky nevertheless. Please make constants backups of your savegames, and don't risk anything you don't want to loose by using these stunts. Feel free to report any misbehaviours you find, but please understand that they will not be considered "bugs" and probably I will not be able to work on them for some time.

ANNOUNCE Release 1.9.0.9 is on the wild, featuring: Adds pt-br Localization Prevents pumping resources not meant to be transferrable Closes issues: #28 GPOSP is trying to pump non pumpeable resources! #25 Brazilian Portuguese (Português Brasil) <pt-br.cfg> See OP for the links — — — — — 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 that I'm wasted, and I prefer to avoid the risk of making yet more mistakes while publishing the thing - and I could use the time to have some feedback from early-adopters. — — POST EDIT — — A mysterious time anomaly happened, wiping out 1.9.0.8 from existence! Please download 1.9.0.9!

Hey, very interesting info! I'm unsure I should use it on the flares problem because I would have to mangle with the game camera (assuming, of course, I could cook something for my problem with this info), and it will risk screwing up things with people using Camera add'ons. On the other hand, this will solve for sure another problem on another add'on of mine! Life saver! Thanks!