Jump to content

Kerbal Attachment System (KAS) 0.4.7 - Pipes as fuel lines and even fewer explosions!

Majiir

By Majiir
in KSP1 Mod Releases

 Share

Recommended Posts

psyper

psyper

Posted
Posted
Thanks for that. Another resource I didn't know about :)

Looks like attachNodeName is what we want. Now to find out how nodes are named...

Looks like it - I'll have to see if its set up on the part cfg or if its hard coded in to the model itself. Also worth a try pressing ctrl+k while in eva and then ctrl+click on the part your playing with - its a debug mode that'll bring up the properties of the part and enable you to tweak them - not sure what it'll show as I never knew it existed until now. It might save you having to make the changes to the file itself and reload the game each time!

Link to comment
Share on other sites
Tex_NL

Tex_NL

Posted
Posted
last weekend I spent a long time stabilizing my Orbital yard with KAS struts. During EVA Bill placed 24 strut endpoints and connected them. It worked perfectly and the station was no longer shaking itself apart as soon as I turned on the SAS.

Now, a few days later I come back and guess what. The end points are still there but all the struts are gone. Please don't tell me I have to reconnect them each and every single time when I come back.

Are/were you using an outdated version of Kerbal Joint Replacement?

Kerbal Joint Replacement? I know, and use, Kerbal Joint Reinforcement but WTF is Kerbal Joint Replacement???

If you meant Kerbal Joint Reinforcement then no, I've got v2.0, the most recent version at the time of my original question (it was updated today to v2.1). But I can't see why this could be related in any way.

Link to comment
Share on other sites
GavinZac

GavinZac

Posted
Posted
Kerbal Joint Replacement? I know, and use, Kerbal Joint Reinforcement but WTF is Kerbal Joint Replacement???

If you meant Kerbal Joint Reinforcement then no, I've got v2.0, the most recent version at the time of my original question (it was updated today to v2.1). But I can't see why this could be related in any way.

It's a typo, is what the **** it is.

The previous version of KJR did cause issues with KAS struts, exactly as you described. The newest one should fix it.

Link to comment
Share on other sites
Tic-Tac

Tic-Tac

Posted
Posted

So...

I read a bit of the Wiki, it's not really well explained how to add new grabable/attachable/placableincontainers parts(for example I'd like to add some mod solar panels to them, and also batteries).

I saw this:

https://github.com/KospY/KAS/wiki/Part%20modules

Okay I got how that worked, but... Where do we put those lines? In a cfg in the kas folder? In the part's cfg? In gamedata?

And is there anything we have to add? Name?

Thanks.

Link to comment
Share on other sites
GavinZac

GavinZac

Posted
Posted
So...

I read a bit of the Wiki, it's not really well explained how to add new grabable/attachable/placableincontainers parts(for example I'd like to add some mod solar panels to them, and also batteries).

I saw this:

https://github.com/KospY/KAS/wiki/Part%20modules

Okay I got how that worked, but... Where do we put those lines? In a cfg in the kas folder? In the part's cfg? In gamedata?

And is there anything we have to add? Name?

Thanks.

It's best to use ModuleManager to add them. Majiir warns against touching the addModules.cfg.

I've got a small project going to add it to most things that a Kerbal should be able to carry, you can find it here.

Link to comment
Share on other sites
Sokar408

Sokar408

Posted
Posted

I made some small radiators attachable via KAS. However after attaching them to a satellite (you know what happened...), the waste heat doesn't seem to go down. Anyone else has tried this, or know what could be wrong? (the increase the radiators give to the wasteheat limit works though, so the part seem to be correct attached)

The way I did it was simply adding these lines in addModule.cfg;

///////// RadialRadiatorzzz2 ///////

GRAB

{

stockPartName = RadialRadiatorzzz2

evaPartPos = (0.0, 0.00, -0.35)

evaPartDir = (0,0,-1)

storable = true

storedSize = 10

attachOnPart = True

attachOnEva = False

attachOnStatic = False

attachSendMsgOnly = False

}

Is that the correct way, or what am I missing?

Link to comment
Share on other sites
Starstrider42

Starstrider42

Posted
Posted (edited)

Is there a way to edit the changes made by addModule.cfg using ModuleManager instead of editing the file directly? I tried both @PART[smallRadialEngine]:HAS[KASModuleGrab]:Final and @GRAB[*]:HAS[#stockPartName[smallRadialEngine]], but neither seems to work.

Specifically, I'm trying to remove the light engines and fuel tanks from KAS. But anything I try seems to have no effect.

EDIT: exactly what I'm doing for module removal:

@PART[smallRadialEngine]:HAS[KASModuleGrab]:Final
{
	!MODULE[KASModuleGrab] {}
}

!GRAB[*]:HAS[#stockPartName[smallRadialEngine]] {}

Neither works.

Edited by Starstrider42
Gave full code, for clarity
Link to comment
Share on other sites
Superfluous J

Superfluous J

Posted
Posted
Is there a way to edit the changes made by addModule.cfg using ModuleManager instead of editing the file directly? I tried both @PART[smallRadialEngine]:HAS[KASModuleGrab]:Final and @GRAB[*]:HAS[#stockPartName[smallRadialEngine]], but neither seems to work.

Specifically, I'm trying to remove the light engines and fuel tanks from KAS. But anything I try seems to have no effect.

I have never tried to remove a module using ModuleManager, but the documentation seems to say that this will work:

@PART[the_part_name]
{
    !MODULE[KASModuleGrab] {}
}

...but I've misread the documentation before so I'd not be surprised at all if I got something wrong.

Link to comment
Share on other sites
Tallinu

Tallinu

Posted
Posted

First, it could be that KAS is doing its adding of modules to stock parts after ModuleManager does its own work, in which case even :Final wouldn't let it strip the module off after it's been added. Don't know if this is the case or not.

Second, you can't delete any of those GRAB nodes entirely - they're root level, which KSP makes read-only. There's nothing ModuleManager can do at that level. But you should be able to search for a GRAB node that HAS a certain key/value pair and change or remove the keys from that node.

@GRAB[*]:HAS[#stockPartName[smallRadialEngine]]

(assuming the # is correct syntax) to find the right part, then

{

!stockPartName

!evaPartPos

!evaPartDir

!storable

!storedSize

!attachOnPart

!attachOnEva

!attachOnStatic

!attachSendMsgOnly

}

should remove all of the keys from that part. I don't know how KAS would handle a completely empty node - hopefully it would just gracefully ignore the node and not crash anything, but you never know. If that doesn't work properly, try something like:

{

@stockPartName = asdfasdfasdf123

}

That should create a situation much like where the player has removed the stock part KAS is looking for, and my guess is that KAS might be more likely to handle it gracefully.

Link to comment
Share on other sites
Justin Kerbice

Justin Kerbice

Posted
Posted

@Majiir: I have had today a very similar issue to my previous one with an evil winch (unhandled null exception which lead to block some game control): I have just a rover, with a winch and a magnet connected to it, I have extended it a bit, then retracted but magnet have some angle prevented a fully retract. Left the rover, do something nearby with a kerbal, going back to the rover... boom winch issue. Not sure of the exact actions done, seems these winches need more care :/.

I was able fortunately to recover vessel but going back to space center was not working, it's weird.

Link to comment
Share on other sites
a.g.

a.g.

Posted
Posted

In the current version, never leave a vessel with a winch in undocked mode, or it will mess up when loading it again. The fix will be in the next release.

Link to comment
Share on other sites
a.g.

a.g.

Posted
Posted

That's already fixed too, and as a bonus, the KAS pipes will have toggles to enable operating like the stock yellow pipes in the next release.

If you are interested in the technical details, the cause for the engine flow bug is that KAS didn't configure the surface attach node on the part, and only added it to the parent-child hierarchy. It turns out, stack fuel flow does use the nodes in flight - hardly anything else actually needs them. In the meantime, Scott mentioned editing the saves, and the way that you'd do it in this case is to copy the missing "srfN = ..." line from one of the engines that weren't moved.

Link to comment
Share on other sites
Kitworks

Kitworks

Posted
Posted

So, maybe I'm missing something, but do the attachable struts actually do anything to increase stability? For instance, if I dock two space station modules, and then attach them as well with several struts, will that reduce the wobble between them?

It seems like that's how they should work (like stock struts, but attachable), but whenever I try to use them this way, it seems not to make a difference...

Link to comment
Share on other sites
Tallinu

Tallinu

Posted
Posted

For anyone else who's tried to make the container bay storable, grabbable, and/or attachable...


@PART[KAS_ContainerBay1]:HAS[!MODULE[KASModuleGrab]
{
!mesh = containerBay1.mu
!scale = 1
!node_stack_bottom = = 0.0, -0.8050, 0.0, 0.0, 1.0, 0.0, 0

@rescaleFactor = 1
@node_stack_top = 0.0, -0.35625, 0.0, 0.0, 1.0, 0.0, 0
@node_attach = 0.0, -0.4025, 0.0, 0.0, -1.0, 0.0

MODEL
{
	model = KAS/Parts/containerBay1/containerBay1
	scale = 0.5, 0.5, 0.5
}

MODULE
{
	name = KASModuleGrab
	evaPartPos = (0.0, 0.10, -0.15)
	evaPartDir = (0,0,-1)
	storable = true
	storedSize = 8
	customGroundPos = True
	dropPartPos = (0.0, 0.2, -0.55)
	dropPartRot = (-10.0, 0.0, 0.0)
	attachOnPart = True
	attachOnEva = False
	attachOnStatic = True
	attachSendMsgOnly = False
}
}

This combines the config heralo came up with that fixes the model with some parameters I'd picked to position things better and make the racks storable.

According to a comment in the part.cfg for the container bay, there was some kind of bug with scaling that must have prevented the use of the model node. I tried to look it up, but there isn't any bug listed at the given URL (either open, closed, or anything else, as if it was deleted). However, everything *seems* to work just fine using this config.

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...