Lisias

You also have the feeling that pellinor is way too happy?

First Post! (ok, it's unfair) In the next few days, a proper TweakScale release will be issued. The current "unofficial" of mine, by being… unofficial… , it's full of crazy ideas that still need to be proven. Eventually some of them will be merged into the 'mainstream', but until there, I'll keep the official releases the more orthodoxically as possible. Welcome aboard. Fasten your seat belts and sit tight.

Hi, Guys. I'm the new guilt..., I mean, responsible for keeping your craft's parts explod… I mean, scaling on KSP. I want to thank @pellinor for the confidence, and want to say to all that yes, it will blow up for sure. Specially on landings. New thread: https://forum.kerbalspaceprogram.com/index.php?/topic/179030-141-tweakscale-under-new-management/&tab=comments#comment-3469313

As from 2018-1016 and under @pellinor agreement, I'm the New Management for TweakScale. From now on, it's all officially my fault! (well, not everything... ) In a Hurry: Help Wanted! See this post. Current Release: 2.4.8.8 for KSP >= 1.3 (2024-1117) It works from KSP 1.3.0 to KSP 1.12.5! Seriously! How to check Compatibility on CurseForge. IMPORTANT Users of KSP 1.12.x need to install KSP Recall. Users of KSP 1.11.x need to install KSP Recall also. Users of KSP 1.10.x need to install KSP Recall too. Users of KSP 1.9.x need to install KSP Recall too. Users of KSP 1.8.x need to install KSP Recall also. Users of KSP 1.7.x need to install KSP Recall also. Users of KSP 1.6.x need to install KSP Recall too. Users of KSP 1.5.x need to install KSP Recall as well. Users of KSP 1.4.3, 1.4.4 and 1.4.5 need to install KSP Recall. Am I detecting a pattern here? read this post before updating! Announce for 2.4.8.0. 2.4.8.1 was ditched. Announce for 2.4.8.2. Announce for 2.4.8.3. Announce for 2.4.8.4. Announce for 2.4.8.5. Announce for 2.4.8.6. Downloads on CurseForge. Soon™. on SpaceDock (for CKAN users). Soon™. on GitHub (for manual and/or KSP-AVC users). TweakScale Companion Program Third Party support is being implemented into Companions, and all legacy patches are going End Of Life on TweakScale 2.4.4. Most of them are unusable anyway Check the TweakScale Companion Program's Thread for more information. New Companions are being released on a regular basis. Or get the ÜberPaket from: CurseForge. SpaceDock (for CKAN users) Github (for manual and/or KSP-AVC users). Relevant Notes Kraken Food (unholy interactions between Add'Ons) is detected on startup, and a proper (and scary) Warning is shown when appropriated. Pay attention to that message, and reach me here for help! Overrules and HotFixes can be issued to workaround the problems if needed. See this post. A PhD thesis about the current problems can be found on this post. An article about how new patches will be handled is here. For users of Infernal Robotics: The Classic Infernal Robotics has a showstopper bug. See this post for details. TweakScale strongly advise using Infernal Robotics/Next where these issues were solved. Description: TweakScale lets you change the size of a part. Not just that, but it will figure out how much fuel is in the resized part. And if it's an engine, it will become more powerful by scaling it bigger, or weaker by scaling it smaller. (Pictures are eternal work in progress! ) Credits: Contributions From: Goodspeed and Biotronic. [original release thread] Pellinor [previous release thread] And future new features/bugs/mishaps from yours truly. Support: I need help in order to proper help you. Open the spoiler for instructions about how to get support: Scale Safe!

From which Galaxy are you from? https://www.easeus.com/data-recovery/restore-lost-documents-after-windows-10-forced-update.html Long time Windows user here. Every major Windows update broke half my productivity tools. I'm now (for while at least) a MacOS user. Let me tell you something: it's even worse.

Probably never. The development model used by KSP is more as Operating System than a shelve product. You can't have the cake and eat it too. You want a Star Citizens development model? It came with a Star Citizens pricing model attached. :-) What I do is to stick with a Version the most I can. I know people considering migrating from 1.3.1 just now. ;-)

Yep, but did you realized that it was your word that triggered these ones, didn't? Sometimes, all what people need is a kick in the... back to start pushing back their changes.

How about "pull requests seasons"? Regularly announcing that you are receiving pull requests, anticipating your time window to give Firespitter some care? This appears to be working reasonably well.

Sure thing.

I don't remember the files, but I did it in every sound file that had thrown an exception on loading. So I presume yes. I choose not to change what it's working. Renaming the texture would break any hypothetical mod that would try to reuse it. Sometimes, it's better to live with the mistake than trying to fix it.

I have some of these and some more fixes on a fork of mine. My worst nightmare at the moment is exactly the wheels, but I think I get a insight due a mess-up on EditorExtensionsRedux - autostruts. Every landing gear must be autostrutted to the root part, IIRC. I still have to check this on firespitter, however. https://github.com/net-lisias-kspu/Firespitter/blob/master/CHANGE_LOG.md

There're a lot of appliances (commercial, industrial and even agricultural) that still relies on 32 bits CPUs. These things just don't die. :-) What it's a good thing for Microsoft, as their replacement will hardly run Windows 10.

Probably older versions of dependencies. Install this mod, then reinstall the latest versions for Pathfinder, overwriting everything. Heisenberg should be left untouched, but everything else will be updated.

Leaking abstractions happens. And once your artifacts became dependent of that abstraction, solving the leak can incur on colateral effects that would demand a full recertification of every single component of your product to prevent a blow on yours users' machines. If the cost of fixing such leak is way higher than the cost of leaving things as they are, it's nonsense (and even dull incompetence) fixing such a leak. One could think it would be a good idea to mask the problem - an initialization code that would run after the leak to undo the undesired behaviour, so nobody would notice and so, nobody would bother. That, my friend, would be a "meshuga". Currently, this is just an annoyance. It would be better (mainly to save face) that this would not had happen, but if a proper fix is not feasible with a proper cost/benefit ratio and without causing undesirable collateral damages, I say left it alone. At least, for now. There're way more serious problems to be fixed or at least properly workarounded.

EXCELLENT question. ARR mods should not accept pull requests from anyone. The pull request's author is also an author too, and usually it's accepted that the code being pulled has the same license of the target codebase. The mod is GPL2? Your pull request should be licensed under the GPL2. If the codebase is ARR, your code being pulled is ARR. TO YOU. So it's a license violation to accept such pull request without a formal, written and traceable explicit permission from the pull request author. And no, the mere existence of the pull request is not enough. Any novel writer would be in hell if any scoundrel could claim copyright infringement because the latter snail mailed him an addendum to his work. If the mod is ARR, it should not accept pull requests. It will be a copyright hell having to trace the explicit authorization from every single commit that it's not their own. Unless the committer explicitly grants the repo owner a perpetual authorization to his works, what would be nonsense and demand a legal contract between the parts. — — — — — Merged unrelated message — — — — — I thought of something that can be of use to people in need to embed CC-ND works on their package. If every single file being embedded (including the DLL) is being published also in a unpackaged form, the original package is not the only "copy" of the Work! So, if I can download the DLL, I can redistribute it in the very same way I would do with the ZIP file. So, embedding such a mod into your's own mod package is not creating a derivative. It's just redistributing the Work into a new medium (your package). And since it's usual practice to commit the DLL on the GameData folder on Github, that settles the matter IMHO.

I have an 16Gb macmini and sometimes it is'nt enough. :-) we need the KSP.log from the folder were you run KSP. "Right Click / Show Original" on the launching icon will reveal were it is.

Yes. SpaceDock, ChangeLog. https://spacedock.info/mod/557/Near Future Propulsion#changelog

Valentina: __ Jeb, I'm worried. I'm not certain I can fly this monster to Mün! It's too mu... Jebediah interrupts abruptly: __ Val, I trust you. And I trust Bill. If he built her, she flies. And if she flies, you fly her home. Tales From Kerbol / Kerbinautenlied / Das KSCgold / Tome 3 To be published soon. Not too soon,…

Se alguém ainda não percebeu, eu tô tentando fazer uma brincadeira com o Anel de Nibelungo, do Wagner. Serão 4 "Atos", cada "Ato" dividido em "Tomos". Mas ok, eu acho que já perceberam sim. Mas agora eu tô com dois problemas: Botei um Kerbal masculino na tripulação e só percebi semanas depois. #facepalm Tomzer trocará de lugar com uma Kerbalette da Estação. Vou atualizar o texto ainda neste FdS. Closed/Fixed. Tô tentando "kerbalizar" o termo "Anel de Nibelungo", mas não sai nada que preste. Minha melhor idéia foi, lembrando dos "Snacks" que os Kerbals tanto apreciam, usar "O Anel de Kibelungo", fazendo uma pegadinha com Quibe, que é um 'Snack'. Mas na segunda vez que repeti isso em voz alta, eu saquei que não será uma boa idéia…. Vasta margem para piadinhas de quinta-série ou musiquinhas tipo Mamonas Assassinas. Hummm… Isso pode render alguma coisa lá no site, hein? Closed/Fixed : Pesquisei a origem das histórias do Anel de Nibelungo, e uma delas tinha um título adaptável sem dar margem para os problemas mencionados! Pelo lado positivo, finalmente eu consegui não só ajustar uma Kolúmbia "montada às pressas com as partes que conseguiram", como também dar cabo de uma pancada de exceções e problemas que estavam me lascando a vida não só durante a construção como nos lançamentos da nave. Então, segue uma colher de chá. :-) Valentina: __ Jeb, estou aflita. Não estou segura que vou levar esse monstro até a Lua! É muito... Jebediah corta Valentina antes que termine a frase: __ Val, eu confio em você. E confio no Bill. Se ele construiu, voa. E se voa, você traz de volta. Por outro lado, Wernher ainda tem algum trabalho por fazer….

I can only speculate that mods that do PInvoke to libraries compiled in 32 bits would be the issue. I can't imagine a pure C# choking by running in 64 bits. Right now, the X-Input.dll came to my mind.

As far as I know, nope. There are two models set for Kerbals: "ships" (Kerbals on EVA are a "walking/flying ship") and scenario (workman on VAB/SPH). The formers are irreplaceable (or at least, nobody managed to do this stunt yet), and the later are unaccessible by mods. I am one that have some crazy/stupid ideas that would need this feature, so I second that. (not sure if I helping saying that! Hehe)

Hi. To everyone that running this on KSP 1.4, there's a forgotten ModuleManager dll in the package that needs to be deleted: Missing method UnityEngine.Texture2D::LoadImage(byte[]) in assembly /Users/lisias/Applications/Games/KSP/Exodus/KSP.app/Contents/Resources/Data/Managed/UnityEngine.CoreModule.dll, referenced in assembly /Users/lisias/Applications/Games/KSP/Exodus/GameData/PrakasaAeroworks/parts/Mk2Thruster/ModuleManager.2.6.8.dll It now and then floods my KSP.log with this message, and today KSP found it was a good idea to just CTD on me after logging this on output.log from Unity.

You have a point. I need to organize me better - I didn't expected having to properly maintain the Unofficial forks.

I'm on that bug hunting mood this week, so I though on give this a peek. Well, I found this on your log: [ERR 08:21:28.757] ADDON BINDER: Cannot resolve assembly: KIS, Culture=neutral, PublicKeyToken=null [ERR 08:21:28.758] ADDON BINDER: Cannot resolve assembly: KIS, Culture=neutral, PublicKeyToken=null [ERR 08:21:28.759] AssemblyLoader: Exception loading 'SuperKerbal': System.Reflection.ReflectionTypeLoadException: The classes in the module at (wrapper managed-to-native) System.Reflection.Assembly:GetTypes (bool) at System.Reflection.Assembly.GetTypes () [0x00000] in <filename unknown>:0 at AssemblyLoader.LoadAssemblies () [0x00000] in <filename unknown>:0 Additional information about this exception: System.IO.FileNotFoundException: Could not load file or assembly 'KIS, Version=1.7.6496.29316, Culture=neutral, PublicKeyToken=null' or one File name: 'KIS, Version=1.7.6496.29316, Culture=neutral, PublicKeyToken=null' System.IO.FileNotFoundException: Could not load file or assembly 'KIS, Version=1.7.6496.29316, Culture=neutral, PublicKeyToken=null' or one File name: 'KIS, Version=1.7.6496.29316, Culture=neutral, PublicKeyToken=null' So, something on your installment wants to load KIS, but since it is not installed, it capsizes. And God knows what it should had done in order to keep things working thigh. WBI supports KIS, and if it thinks KIS is installed when it's not, such things can happens. I also found Scatterer and Kopernicus on your installment. If they are not needed to reproduce the problem, my best advise is to delete them from the test bed. They just add loading time and expand the exposing area without adding any value to the bug hunting. I think you should delete the ModuleManager cache and try again. I usually do it every time I delete, add or update a mod on my installment. It's not always necessary, the cache consistency code usually works - but now and then, it miss something and give me some headaches until I realize what's happened. By deleting the cache manually when changing something, my migraine medicine consumption dropped a lot.