Warezcrawler

Now that KSP has finally reach the end of endless updating, it is time to ensure compatibility with the lastest version of KSP. However, I haven't upgraded yet, as I am in the middle of a playthrough and updating mods is a mayor task. So my question is, is the latest version of my mod (this thread) compatible with latest ksp (1.12.1), or do I need to update it as it is? Regards

Interesting. It seems that DeployableEngines manipulated the engines, resulting in all the modes being activated. It seems that deployable engines manipulates the engines after my mod have initialized and disabled the engines that are not active. It seems from the source code that deployable engines handles stock multimode enignes, but the ones from this mod. From https://github.com/ChrisAdderley/DeployableEngines/blob/master/Source/DeployableEngines/ModuleMultiStateEngine.cs#L40 multiController = this.GetComponent<MultiModeEngine>(); I first guess would be to get Deployable Engines to recognise the "GTI_MultiModeEngineFX". They are very similar, so I would expect it to be easy enough, when it already handles stock multi mode.

go back into the posts and you can find an unofficial update by jbudda that work as intended :o)

Last does not take an argument. It is just ":LAST". I think that is simply the problem :o) Try looking at this

You write "EVE currently unsupported (it is not yet available for KSP 1.9+)" in the OP. Does that mean there is a known incompatibility? Or just that because EVE is not updated any issues must be unsupported?

Or minor because the game is still completely playable, and still much improved by this mod, yet it has some minor glitches...

What makes you think it is KSP that is right? How did you do the math?

I upgraded from 1.9.0 to 1.9.1, but suddenly several of my mods seemed broken, like CapCom and Contracts window. Both worked fine in 1.9.0. I expected this upgrade to be at least as simple as from 1.8.1. So my question is --> Is this something you have experienced in upgrading from 1.9.0? I'm thinking if this is not something everybody else is experienceing, then I probably did something wrong. So I like to know if that is the case.

thanks! That is much better...

I just downloaded from spacedock, but the zip file contains Kerbin Space Station contract pack! I think you must have zipped the wrong directory....

Well that depend on your perspective. Compared with Scatterer this is very minor - scatterer gives black sky, and no ocean, and probably more! Hence, mods could be much more broken, defective... I think this is a minor visual bug, that only show up in certain situations, so the game is still improved a lot by EVE, even with these bugs. --> That is why I see this as minor.

just use it as is.... The problems are very minor....

@jrbudda I just noticed that Stock KSP cannot calculate burntime correctly when using my mod "GTIndustries", while Kerbal Engineer Redux does that no problem. Thank you for that --- KER for the win!

THANKS!!!! How in the world I missed that I will never know! You are the best! Based on what blowfish pointed out I don't think this was the issue - furthermore this does actually do what I expect based on the MM cache. breakdown @PART[*]: HAS[ @MODULE[ModuleCommand]:HAS[#minimumCrew[>0]] <--- only when the part has ModuleCommand which has minimumcrew that is non zero ,!MODULE[ELWorkshop] <--- and the part does not have ELWorkshop ] -- i.e. intentional --- But thanks for your response. All help is always appreciated

I have a MM patch which yields a warning, but I cannot figure out what the source is in the patch. KSExpSeatMap { SeatTasks { name = ELWorkshop default = Workshop } } @PART[*]:HAS[@MODULE[ModuleCommand]:HAS[#minimumCrew[>0]],!MODULE[ELWorkshop]] { MODULE { name = ELWorkshop ProductivityFactor = 4 IgnoreCrewCapacity = false } } @PART[mk2LanderCabin,Large_Crewed_Lab]:HAS[!MODULE[ELSurveyStation]] { MODULE { name = ELSurveyStation } } @PART[crewCabin] { MODULE { name = ELWorkshop ProductivityFactor = 4 } } @PART[MK1CrewCabin] { MODULE { name = ELWorkshop ProductivityFactor = 4 } } @PART[mk4CrewCabin] { MODULE { name = ELWorkshop ProductivityFactor = 4 } } @PART[mk3CrewCabin]: { MODULE { name = ELWorkshop ProductivityFactor = 4 } } @PART[Large_Crewed_Lab] { MODULE { name = ELWorkshop ProductivityFactor = 7 } } Can anyone see the issue in the MM patch above? Thanks!

I for one am happy with MM, which is better than what you find in most games out there where modding is easily accessible. Can it be improved - probably - but I must say it gives a lot of info already. ------------ I'm unhappy with this post merge --------- Try something like @STATIC[*]:HAS[#pointername[KS_TaxiLarge]] { @Instances { @Orientation = 90.959137,100.041763,-0.000703487894 } } When Has point to a value different than name, you use # for has or ~ for has not, also see the documentation on that. Then you need to edit the Instances node. In the code above I only edit the first "instance" of instances, use ",*" after for all.

nope

It will always do that until updated, because it does a simple version comparison. It does not mean it cannot work, which it seems to do as far as I can see.... So just ignore the message for now - just means you cannot report it as a bug if it does not work.

Maybe, something as simple as putting a single MM log into the KSP log pointing to these two files would enable you to remove the copy of the logs - that way people like me does not need to know beforehand / or remember it for that matter. We as players / modders would find this info, and go to the referenced files when needed. Furthermore, you could consider keeping the errors in the KSP.log so as to making them visible, while keeping everything else in these separate files. I like them, because they make it very clear that this is what MM is doing.

Thanks... Don't think those have always been, have they? Don't remember them from 2 years ago when I was playing last.... But thanks, they are great.

I get 1 warning from module manager when loading the game - while the rest 10000 changes loads just fine. How can I identify the cfg file, which has the problem? There are so many lines in the log, so finding the correct note when not knowing what is would say is kind of hard.

I just want to let you now of an NRE I just got. I'm not sure if anything is broken by this. I have included the surrounding messages. It seems to be related to receiving science?! EDIT: It seems to happen when the "new" ground experiments transmit science to KSC in the background, which is a different behaviour than normal science which would come from current vessel or when recovering. Maybe there is something in this specific instance that is not handled in Tarsier at this moment.

Ok, I just got the latest one again. Noticed that I had to go to the section for older versions, since the main link get's the old 1.13.0 version - now I have the 1.13.3 version for 1.8.1. However, it seems it is maybe not loading correctly? I just noticed in the mod section of the log, it is not listed - which could explain why modulemanager fail when it tries to add it to the mod list....??? I wonder what could do this... It is compiled against the right version right? (guessing it is a stupid question...) Regarding the Structural, this always worked in the past though... Are you sure is should here? EDIT: Just tested against a clean install. Only my MM and Interstellar... Same result, so it should not be a mod incompatibility thing. EDIT 2: I found it. I had not installed the "999_Scale_Redist.dll" file..... My bad! Thanks for your help!

@FreeThinker I just returned to KSP, have not been playing since version 1.4.5.... I have a personal mod, which add's fuel switch to all kinds of different tanks, but it does not seem to work anymore. As far as I can see, the "InterstellarFuelSwitch" node is applied to the parts - go MM - but I get no switching feature in game. I guessing that something in InterstellarFuelSwitch has changed since I used it last, and am hoping you could point it out to me. My MM @PART[*]:HAS[@RESOURCE[LiquidFuel],@RESOURCE[Oxidizer],!RESOURCE[MonoPropellant]&!MODULE[InterstellarFuelSwitch]&!MODULE[FSfuelSwitch]]:NEEDS[InterstellarFuelSwitch]:FOR[GTI] { %LF = #$RESOURCE[LiquidFuel]/maxAmount$ %OX = #$RESOURCE[Oxidizer]/maxAmount$ %totalCap = #$RESOURCE[LiquidFuel]/maxAmount$ @totalCap += #$RESOURCE[Oxidizer]/maxAmount$ %LFORE = #$totalCap$ @LFORE *= 3 @LFORE /= 5.7 %ORELF = #$totalCap$ @ORELF *= 2.7 @ORELF /= 5.7 %LFDG = #$totalCap$ %DGLF = #$totalCap$ @DGLF /= 8 MODULE { name = InterstellarFuelSwitch tankSwitchNames = LiquidFuel,Oxidizer;LiquidFuel;LiquidFuel,Ore;LiquidFuel,DarkGoo;MonoPropellant;Structural resourceGui = LiquidFuel, Oxidizer;LiquidFuel;LiquidFuel, Ore;LiquidFuel, Dark Goo;MonoPropellant;Structural resourceNames = LiquidFuel,Oxidizer;LiquidFuel;LiquidFuel,Ore;LiquidFuel,DarkGoo;MonoPropellant;Structural initialResourceAmounts = #$../LF$,$../OX$;$../totalCap$;$../LFORE$,$../ORELF$;$../LFDG$,0;$../totalCap$;0 resourceAmounts = #$../LF$,$../OX$;$../totalCap$;$../LFORE$,$../ORELF$;$../LFDG$,$../DGLF$;$../totalCap$;0 //basePartMass = 2 availableInFlight = true availableInEditor = true inFlightSwitchingTechReq = highPerformanceFuelSystems displayCurrentTankCost = false hasGUI = true showInfo = true hasSwitchChooseOption = true } } The result in the config file (example) MODULE { name = InterstellarFuelSwitch tankSwitchNames = LiquidFuel,Oxidizer;LiquidFuel;LiquidFuel,Ore;LiquidFuel,DarkGoo;MonoPropellant;Structural resourceGui = LiquidFuel, Oxidizer;LiquidFuel;LiquidFuel, Ore;LiquidFuel, Dark Goo;MonoPropellant;Structural resourceNames = LiquidFuel,Oxidizer;LiquidFuel;LiquidFuel,Ore;LiquidFuel,DarkGoo;MonoPropellant;Structural initialResourceAmounts = 45,55;100;52.6315789473684,47.3684210526316;100,0;100;0 resourceAmounts = 45,55;100;52.6315789473684,47.3684210526316;100,12.5;100;0 availableInFlight = true availableInEditor = true inFlightSwitchingTechReq = highPerformanceFuelSystems displayCurrentTankCost = false hasGUI = true showInfo = true } Or the full example of the FL-T100 Fuel Tank I do get an exception which might be related, but I can't tell KSP Log if needed: Log File

Recompiled for v1.8.1