Benneb

Does changing the order of the nodes change where the game considers the CoM to be though? Test 2 (which I have noticed is actually a terrible picture) extends off into the distance so should not be the CoM. Or rather does it change what the game considers to be the 'top' and 'bottom' nodes? Test 1 for example, the top and bottom nodes do not work but they are the ones closest to the CoM. Only by putting them at the bottom of the list as in Test 3 do they work. Its actually not that much work. The nodes for the root part typically get placed at very the top of the list making it easy to find and move them to the bottom.

I just spent a day pulling my hair out trying to work out why I could not get a part I had made to attach to my ship. I think we all know the bug by now. You place the parts but they remain greyed out: I discovered that although the top node would not work, the nodes at the ends of the struts would: Hummm says I. Why would the sides work but none of the others... Cue about 4 or so hours of me making more welded parts and playing with the files trying to figure it out. Eventually I have worked out how to get the node I want to use to work: If we look at the files I can kinda explain what is going on... (I'll paste only the relevant sections here, the actual files ill attach to this post if I can seems I can't so I have pasted one file at the bottom which you can paste the node_stack parts into to test if you so wish.) Test1: node_stack_backstationHub0 = 0,0.6122528,0.9372894,0,0,-1,1 node_stack_topstationHub0 = 0,1.524406,0.02513594,0,-1,0,1 node_stack_bottomMk1FuselageStructural2 = 0,-4.0749,0.02513594,0,-1,0,1 node_stack_toptrussPiece3x4 = -4.922832,0.6122526,0.02513594,-1,0,0,1 node_stack_toptrussPiece3x6 = 4.922832,0.6122526,0.02513594,1,0,0,1 Test2: node_stack_right01 = 4.922832, 0.6122526, 0.02513594, -1, 0, 0, 1 node_stack_left01 = -4.922832, 0.6122526, 0.02513594, 1, 0, 0, 1 node_stack_top01 = 0, 1.524406, 0.02513594, 0, -1, 0, 1 node_stack_bottom01 = 0, -4.0749, 0.02513594, 0, 1, 0, 1 node_stack_back01 = 0, 0.6122528, 0.9372894, 0, 0, -1, 1 Test3: node_stack_backstationHub0 = 0,0.6122528,0.9372894,0,0,-1,1 node_stack_toptrussPiece3x4 = -4.922832,0.6122526,0.02513594,-1,0,0,1 node_stack_toptrussPiece3x6 = 4.922832,0.6122526,0.02513594,1,0,0,1 node_stack_topstationHub0 = 0,1.524406,0.02513594,0,-1,0,1 node_stack_bottomMk1FuselageStructural2 = 0,-4.0749,0.02513594,0,-1,0,1 Basically what we have here are 3 identical welded parts. Yes the names are a bit different but please ignore that as I have discovered it really does not matter what they are called. The important part is the node on the bottom of the list. Test1 will only attach via the struts: Test2 will only attach via the back node on the hub: Test3 will only attach via the top and bottom nodes: I think you can see where this is going; the node one the bottom will always work but the others will not. I do not know why this is working like this but it does. Whilst I said the others will not work, there are exceptions. Test1 will attach via either strut and Test3 will attach via the bottom or top. The only thing I can see is that they share the same plane? The remaining nodes work just fine once the part is attached so using this method means you can have as many as nodes as you like. Anyway, I hope this helps someone work out what is happening, I am off to make a useable version of Colonel_Panic's amazing OASIS station The file: PART { name = Test module = Part author = UbioZurWeldingLtd rescaleFactor = 1 PhysicsSignificance = -1 node_stack_backstationHub0 = 0,0.6122528,0.9372894,0,0,-1,1 node_stack_topstationHub0 = 0,1.524406,0.02513594,0,-1,0,1 node_stack_bottomMk1FuselageStructural2 = 0,-4.0749,0.02513594,0,-1,0,1 node_stack_toptrussPiece3x4 = -4.922832,0.6122526,0.02513594,-1,0,0,1 node_stack_toptrussPiece3x6 = 4.922832,0.6122526,0.02513594,1,0,0,1 CrewCapacity = 0 TechRequired = sandboxWeld entryCost = 0 cost = 2760 category = Structural subcategory = 0 title = Test manufacturer = UbioZur Welding Ltd description = Warranty void during re-entry. attachRules = 1,1,1,1,0,0,0 mass = 3.65 dragModelType = default maximum_drag = 0.2242188 minimum_drag = 0.2265625 angularDrag = 0.7695313 crashTolerance = 154.3515 breakingForce = 342.627 breakingTorque = 342.627 maxTemp = 4139.063 fuelCrossFeed = True MODEL { model = Squad/Parts/Structural/stationHub/model position = 0,0.6122528,0.02513594 scale = 1,1,1 rotation = 0,0,0 } MODEL { model = Squad/Parts/FuelTank/MK1FuselageStructural/model position = 0,-1.237401,0.02513594 scale = 1.25,1.25,1.25 rotation = 0,0,0 } MODEL { model = Squad/Parts/FuelTank/MK1FuselageStructural/model position = 0,-3.1249,0.02513594 scale = 1.25,1.25,1.25 rotation = 0,0,0 } MODEL { model = Squad/Parts/Structural/trussAdapter/model position = -1.322984,0.6122528,0.02513594 scale = 1,1,1 rotation = 0,0,90.00001 } MODEL { model = Squad/Parts/Structural/trussPiece3x/model position = -3.447593,0.6122528,0.02513594 scale = 1,1,1 rotation = 0,0,90.00001 } MODEL { model = Squad/Parts/Structural/trussAdapter/model position = 1.322984,0.6122528,0.02513594 scale = 1,1,1 rotation = 0,0,270 } MODEL { model = Squad/Parts/Structural/trussPiece3x/model position = 3.447593,0.6122528,0.02513594 scale = 1,1,1 rotation = 0,0,270 } MODEL { model = Squad/Parts/Utility/dockingPort1/model position = 0,0.6122528,-0.8923258 scale = 1,1,1 rotation = 270,0,0 } MODULE { name = ModuleDockingNode deployAnimationController = 1 nodeType = size1 } MODULE { name = ModuleAnimateGeneric animationName = dockingring startEventGUIName = Open Shield endEventGUIName = Close Shield } }