[0.23] Modulefixer

[qnistNAMEERF]

The link now directs to the homepage for KSP Curse

See one page back:

As the original license allows, here is uploaded the mod as downloaded originally from Spaceport:

Modulefixer.

[Taki117]

this doesnt seem to work with a couple of the fission reactors in KSPI-Lite

Try updating KSPI-Lite.

[JackCY]

YT video is dead, no idea what's this supposed to fix.

[therealcrow999]

I cant believe this problem is still around, lucky I had this .dll backed up on my HD.

[JackCY]

Download link dead, can you reupload it? Admins broke links to spaceport/curse.

And I'm not in the mood to figure out what it needs to compile the DLL. Might just smack Squad to fix this already instead if it's still persistent.

[therealcrow999]

Download link dead, can you reupload it? Admins broke links to spaceport/curse.

And I'm not in the mood to figure out what it needs to compile the DLL. Might just smack Squad to fix this already instead if it's still persistent.

Got to page 2 post #18, someone uploaded to a Drop Box.

[Hremsfeld]

What does this fix? The video in the OP is dead. It's recommended as part of Real Solar System, but I've got no idea why.

Edit: VVVVV Oh! Thanks.

Edited October 12, 2014 by Hremsfeld

[NathanKell]

It fixes the stock KSP bug (still here since .23) where a part that has three or more resources, but no module, will appear to blow up to infinite size when you mouseover it in the editor part list.

[NecroBones]

I'm running into this bug now too, with my fairings mod. The parts don't have any resources, but rather, I'm trying to consolidate the fairing bases and allow the player to choose which length of fairing to use by choosing which upper node to attach things to.

The thing is, these upper nodes are decoupler nodes, and I don't want to use an omnidirectional "MODULE" for the decoupler, so that the base and payload can be controlled separately.

So I'm hitting zoom-in bug with a config like this:

MODULE
{
    name = ModuleDecouple
    ejectionForce = 50
	explosiveNodeID = top01
}

MODULE
{
    name = ModuleDecouple
    ejectionForce = 50
	explosiveNodeID = top02
}

MODULE
{
    name = ModuleDecouple
    ejectionForce = 50
	explosiveNodeID = top03
}

THe suggested .dll doesn't do anything for having too many decoupler modules. Any ideas?

[NecroBones]

Showing the problem, with 3+ decoupler nodes:

[NathanKell]

Yeah, sounds like we need one that operates in reverse, adds an untweakable/invisible 0/0 ElectricCharge PartResource to such parts.

[NecroBones]

Yeah, sounds like we need one that operates in reverse, adds an untweakable/invisible 0/0 ElectricCharge PartResource to such parts.

Unfortunately, just adding that manually to my .cfg files doesn't seem to fix it, so we'd probably need a different approach. But when you said that, for a moment I had an "ahah!" moment and thought we were on to something. My test made me sad.

Edited November 2, 2014 by NecroBones

[Saint-Stanislas]

I'm having this issue again on 0.90 with U.S.I. survival pack - DEPT propulsion module.

I'm gonna try the fix to see if it still work for 0.90 probably tomorrow

[NecroBones]

The video in the OP doesn't seem to be there anymore.

Also, does anyone know of any fixes for 3+ decoupler nodes under 0.90? No dummy nodes in my testing in 0.25 made any difference.

[RoverDude]

Guys. Please do not apply this to any USI mods. You're just masking what is an install issue, and making my job a hell of a lot harder. It will not make your stuff work.

Personally, I am not a fan of this mod as it inflicts work on modders who are trying to provide support, and it masks issues. As a modder, it's better to just fix the problem

[Saint-Stanislas]

heard you !

I might have the time to reinstall everything one by one tonight (missed a flight so stuck in Airport )

And then see if another mod is breaking my install. Re-installing SrvPack alone was not sufficient to fix the issue for me.

RoverDude, I assumed that reinstalling meant the specific mod only... It's just unclear for me how can we corrupt an installation ? Either you're just reffering to me being unattentive and throwing files in the wrong place, or to some gamedata interaction that is breaking stuff. So, files in gamedata are writen by the game, or some mods are writing in them? Or it's just a loading process issues where ksp is able to corrupt files just by reading them under specific buggy conditions ?

[RoverDude]

Depends - stuff in the wrong place, old stuff in the right place, people using mods that 'work' but are not set up for the current KSP version, people ignoring warnings, people 'fixing' things, etc.

You are getting this because a part module is not loading. A part module is not loading because something is wrong with your installation (see points above). When people use this 'mod' it causes me headaches because it makes it harder for me to uncover the truth.

This 'mod' is a bad idea.

[rabidninjawombat]

heard you !

I might have the time to reinstall everything one by one tonight (missed a flight so stuck in Airport )

And then see if another mod is breaking my install. Re-installing SrvPack alone was not sufficient to fix the issue for me.

RoverDude, I assumed that reinstalling meant the specific mod only... It's just unclear for me how can we corrupt an installation ? Either you're just reffering to me being unattentive and throwing files in the wrong place, or to some gamedata interaction that is breaking stuff. So, files in gamedata are writen by the game, or some mods are writing in them? Or it's just a loading process issues where ksp is able to corrupt files just by reading them under specific buggy conditions ?

I know its time consuming. But sometimes best way to diagnose the issue is to start with a clean install then reload your mods one by one (start with the one you had the issue with) booting the game with each install and note which mod causing the conflict when added.

[CaptainKipard]

Is this fix still necessary?

[NathanKell]

No.

10char.

[khyron42]

NathanKell, then it should probably be removed from the list of mod "recommendations" in RO's OP.

[NathanKell]

RO wasn't updated for 1.0. Now it is.