Nils277

Thanks Created a bug report here: https://bugs.kerbalspaceprogram.com/issues/25153

@DMagic This difference in the log file will definitely have something to do with the update they did in KSP 1.9 In the release note of 1.9.0 we can find: It seems they changed to system so that the KSPedia entries do not clog the RAM all the time, but did not consider/test the KSPedia entries from mods that were created with the latest PartTools

Will add images to the OP when i get some time This is an intended behaviour. The laboratory should be a bit inferior to the Stock one because it is smaller and leighter. Seems that the conversion for OSE Workshop are not added to the ISRU. Will add some (reasonable) converters to it. Will have a look at this

Sorry for the veeery late reply...Do there parts still disappear? They should not vanish when launched. They should work like any other part and not need KIS/KAS and/or Breaking Ground to be usable. Will test this too Do you have any mods instaled that change things about the heat? I was not able to reproduce this bug yet There are patches for MKS which are linked in the first post. I don't know it they are up-to-date however. I do not really use MKS in my playthorughs and simply do not have enough knowledge about the complex game mechanics of MKS Will be added in the next release i'm working on right now

Buenas tardes (hope this is correct ) Thanks, glad to be back, home office does have its benefits sometime. Yeah, we are fortunately all well until now. Hope you and your family too!

Hi, i tried to update the KSPedia entries of my mods to work in KSP 1.9.1, but never got them working. Basically i tried to follow the workflow i posted here: For KSP 1.8.X this worked without problems. So i tried to do the same with the Parttools for 1.9.X. At first it seems sucessfull, because the KSPedia files compiled without error messages and created the *.ksp files, which also had the correct size. The log from KSP also does not show any errors about an outdated KSPedia entry. But still the KSPedia entries are not showing in KSPedia. The only warning i see in log is however, this is also logged when no mod or secondary KSPedia entry is installed. Does anyone already had success at updating the KSPedia entries to work in 1.9.X? Maybe @Nertea, @linuxgurugamer @Angel-125 ? PS: Making History is also installed in the latest version.

Update to 1.2.11 ~Still alive~ Changelog: Download:  In fact there have been plans for a smaller rover/bike/tricycle like addition i had in mind, but i never really had time to add it...maybe some day

Can you tell me, what happens when you dock or grap onto the trailer? I have tried and tested many options and really thought i had removed nearly all errors Edit: Even better, do you have a save (best without many other mods) where a Problem can be reproduced?

Which to storage boxed do you not find? Are they from a mod, or for the vanilla game? Will take a look what happends...sounds like a new issue with KSP 1.9 to me. You mean the joints and hitches right?

Oh, thanks for the hint with KSPedia, totally forgot these. Will prepare an update for them. Then the export option from Paint.net for dds is a bit misleading. I'm 100% sure i chose DXT3 for diffuse textures because it does not have an alpha channel. Well thats even better, so i don't have to change so much.

Hmm, will take a look into that. Ther is actually nothing special about the heat shield. Ita just a model that uses the mechanics that are already build into KSP. Maybe the update to 1.9 changed something about the modules and i have to update. What version of this mod and what version of KSP are you using?

@linuxgurugamer thanks a lot! Will merge the request asap and make a new release. @Bom-bombardier what issues do you have exactly? Are they directly related to KPBS?

To be honest, i did not There is one part that can be attached to a rover on the front, to create an unmanned rover, but never really how sized parts for an unmanned rover. Might take a look at it at some day

@million_lights I think i found what you were searching for: 1. You have so save every page you want to have for you KSPedia in one of the asset folders inside of Unity 2. Go inside of Unity into the folder you have you KSPedia Assets saved. In my case its just the folde KSPedia: 3. Select the page you want to assign an AssedBundle to. In the following image its the "Congiguration" page, marked in red. When selected, the AssedBundle option will appear at the bottom right (also marked in red) 4. When you now click on the drop down menu from (here with the text "planetarybaseinc" you will get the menu to create and assign asset bundles to the individual pages.

Hey, sorry for the late reply, the forum did not inform me there was a new post here...Unfortunately i do not know any new tutorial for the KSPedia. However I will take a look at where to find the section you mentioned and post it here. I'm not 100% sure about the unity version. I use 2019.2.2f1, because this is the version explicidliy stated in the PartTools. Your version should work nontheless as 2019.2.10f1 is just a bugfix update for all i know. The KSPedia assest work in KSP for me. Or was this directed at Million Lights?

Well soonTM, seems to be quite sooner than expected Update to 1.6.10 Changelog: Download:

@EngineerMartijn and everyone also having trouble building the KSPedia entries with the latest PartTools: I have found a working solution here:

A solution was found, see bottom of post To update my mods to KSP 1.8.0 i need to recompile all my KSPedia entries with the latest PartTools and Unity 2019.2.2f. For this purpose i made a fresh install of Unity 2019.2.2f, uninstalled preloaded TextMesh Pro, installed the TextMesh Pro specified and afterwards installed the latest Parttools. Exactly as explained here: However: It seems that compiling the KSPedia slides is impossible with the PartTools. After installing them i get the following message: Assembly 'Assets/Plugins/KSPAssets/KSPAssetCompiler.dll' will not be loaded due to errors: Unable to resolve reference 'TextMeshPro-2017.1-1.0.56-Runtime'. Is the assembly missing or incompatible with the current platform? Reference validation can be disabled in the Plugin Inspector As this message clearly states, it is not finding the runtime for TextMeshPro version 1.0.56 from 2017. The version that can be currently only downloaded from the Asses Store it version 1.2.2, which seems to not work. Disabling the Reference Validation does not solve the problem either. I have searched a lot but was unable to find any download of TextMeshPro that works with the KSPAssetCompiler. Has anyone found a solution to that problem or knows where i can find the TextMeshPro version needed to get the PartTools running again? Edit: Looking into the folders from TextMeshPro, it seems that the downloaded version is in fact 1.0.55, almost all .dlls have "1.0.55.2017.2.0b12" in their name so i'd guess its indeed version 1.0.55, so the Question is, why is it not downloading the later version 1.0.56? Edit 2: Found a solution: Uninstall any other TextMeshPro version you have installed in your Scene Download "TextMesh Pro Release 1.0.56 - Unity 2017.1" from https://forum.unity.com/threads/useful-information-download-links.458634/#post-3304434 and install it Disable "Validate References" for the KSPAssedCompiler.dll and KSPAssets.dll in the "Assets/Plugins/KSPAssets" folder Comment out line 12 from the "TextMeshProResolver.cs" file (its: the line with [InitializeOnLoad]) in the "Assets/Plugins/KSPAssets" folder Build your KSPedia file as always

Thats really nice to hear ...i thought that at least the textures are not working because KPS does not support DXT3 textures anymore and FUR still uses them for the diffuse textures. Hmm, that must have changed since i last looked at it. I really thought that update() will only be called after awake() and start(), that might really be the culprit

Yes, i'm already working on the update and try get have a running version soonTM

Thanks, thats a good find! Will take a look at it why the light settings can be null. Nontheless i will be able to at least test for that case in the log and stop the lpg spam. For all: I know that FUR might not work with 1.8.0. Will try to update soon(TM)

Okay, thanks for the hint, will take a look at if indicator lights does somthing. I think there should be also a patch file for indicator lights shipped with FUR, might be that something changed that i did not think of.

@draqsko I just tried with a fresh install of FUR with a nearly unmodded KPS (just KAS, CRP, CCK and KPBS) and i do not see any NREs (NullReferenceException) getting spammed after loading e.g. the parts from FUR. Actually a see no NREs at all. I found a bug for the drill that disables the lights when it is set to have the rear lights, which might be related to the logged errors you are seeing. Can you tell me which mods you have? Normally the multilights should not interact with any other mods, it is only there so you can have differend colored lights.

The problems are still present int 1.7.3 but for all i know they do not cause any harm. I'm back from my vacation now and will start to find and remove the problem

Thanks for the report, i will take care of this once i'm back from vacation