politas Posted May 31, 2017 Author Share Posted May 31, 2017 13 hours ago, gerishnakov said: I have, but now if I touch anything in cKan I get the error I mentioned. I'm pretty sure that a Clean & Reinstall will sort that out 20 hours ago, Warsoul said: MaErDa Beta Tester Pack V0.95 I edited the tech tree, i need a checkup if ive done it correctly please : Reveal hidden contents //=========================================================================================== // MaErDa Techtree Nodes //=========================================================================================== @RDNode:HAS[#id[MaErDaT0]] { @hideEmpty = False pos = -2625,1199,-1 } //--------------------0.625m---------------------------------------------------------------- @RDNode:HAS[#id[MaErDaT1]] { @hideEmpty = False pos = -2900,1199,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT1a1]] { @hideEmpty = False pos = -2975,1300,-1 } @RDNode:HAS[#id[MaErDaT1a2]] { @hideEmpty = False pos = -2975,1400,-1 } } @RDNode:HAS[#id[MaErDaT1a3]] { @hideEmpty = False pos = -2975,1500,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT1b1]] { @hideEmpty = False pos = -2825,1300,-1 } @RDNode:HAS[#id[MaErDaT1b2]] { @hideEmpty = False pos = -2825,1400,-1 } } @RDNode:HAS[#id[MaErDaT1b3]] { @hideEmpty = False pos = -2825,1500,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT1c1]] { @hideEmpty = False pos = -2975,1100,-1 } @RDNode:HAS[#id[MaErDaT1c2]] { @hideEmpty = False pos = -2975,1000,-1 } } @RDNode:HAS[#id[MaErDaT1c3]] { @hideEmpty = False pos = -2975,900,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT1d1]] { @hideEmpty = False pos = -2825,1100,-1 } @RDNode:HAS[#id[MaErDaT1d2]] { @hideEmpty = False pos = -2825,1000,-1 } } @RDNode:HAS[#id[MaErDaT1d3]] { @hideEmpty = False pos = -2825,900,-1 } //--------------------1.25m---------------------------------------------------------------- @RDNode:HAS[#id[MaErDaT2]] { @hideEmpty = False pos = -3200,1199,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT2a1]] { @hideEmpty = False pos = -3275,1300,-1 } @RDNode:HAS[#id[MaErDaT2a2]] { @hideEmpty = False pos = -3275,1400,-1 } } @RDNode:HAS[#id[MaErDaT2a3]] { @hideEmpty = False pos = -3275,1500,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT2b1]] { @hideEmpty = False pos = -3125,1300,-1 } @RDNode:HAS[#id[MaErDaT2b2]] { @hideEmpty = False pos = -3125,1400,-1 } } @RDNode:HAS[#id[MaErDaT2b3]] { @hideEmpty = False pos = -3125,1500,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT2c1]] { @hideEmpty = False pos = -3275,1100,-1 } @RDNode:HAS[#id[MaErDaT2c2]] { @hideEmpty = False pos = -3275,1000,-1 } } @RDNode:HAS[#id[MaErDaT2c3]] { @hideEmpty = False pos = -3275,900,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT2d1]] { @hideEmpty = False pos = -3125,1100,-1 } @RDNode:HAS[#id[MaErDaT2d2]] { @hideEmpty = False pos = -3125,1000,-1 } } @RDNode:HAS[#id[MaErDaT2d3]] { @hideEmpty = False pos = -3125,900,-1 } //--------------------2.5m---------------------------------------------------------------- @RDNode:HAS[#id[MaErDaT3]] { @hideEmpty = False pos = -3500,1199,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT3a1]] { @hideEmpty = False pos = -3575,1300,-1 } @RDNode:HAS[#id[MaErDaT3a2]] { @hideEmpty = False pos = -3575,1400,-1 } } @RDNode:HAS[#id[MaErDaT3a3]] { @hideEmpty = False pos = -3575,1500,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT3b1]] { @hideEmpty = False pos = -3425,1300,-1 } @RDNode:HAS[#id[MaErDaT3b2]] { @hideEmpty = False pos = -3425,1400,-1 } } @RDNode:HAS[#id[MaErDaT3b3]] { @hideEmpty = False pos = -3425,1500,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT3c1]] { @hideEmpty = False pos = -3575,1100,-1 } @RDNode:HAS[#id[MaErDaT3c2]] { @hideEmpty = False pos = -3575,1000,-1 } } @RDNode:HAS[#id[MaErDaT3c3]] { @hideEmpty = False pos = -3575,900,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT3d1]] { @hideEmpty = False pos = -3425,1100,-1 } @RDNode:HAS[#id[MaErDaT3d2]] { @hideEmpty = False pos = -3425,1000,-1 } } @RDNode:HAS[#id[MaErDaT3d3]] { @hideEmpty = False pos = -3425,900,-1 } //--------------------3.75m---------------------------------------------------------------- @RDNode:HAS[#id[MaErDaT4]] { @hideEmpty = False pos = -3800,1199,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT4a1]] { @hideEmpty = False pos = -3875,1300,-1 } @RDNode:HAS[#id[MaErDaT4a2]] { @hideEmpty = False pos = -3875,1400,-1 } } @RDNode:HAS[#id[MaErDaT4a3]] { @hideEmpty = False pos = -3875,1500,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT4b1]] { @hideEmpty = False pos = -3725,1300,-1 } @RDNode:HAS[#id[MaErDaT4b2]] { @hideEmpty = False pos = -3725,1400,-1 } } @RDNode:HAS[#id[MaErDaT4b3]] { @hideEmpty = False pos = -3725,1500,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT4c1]] { @hideEmpty = False pos = -3875,1100,-1 } @RDNode:HAS[#id[MaErDaT4c2]] { @hideEmpty = False pos = -3875,1000,-1 } } @RDNode:HAS[#id[MaErDaT4c3]] { @hideEmpty = False pos = -3875,900,-1 } //------------------------------------------ @RDNode:HAS[#id[MaErDaT4d1]] { @hideEmpty = False pos = -3725,1100,-1 } @RDNode:HAS[#id[MaErDaT4d2]] { @hideEmpty = False pos = -3725,1000,-1 } } @RDNode:HAS[#id[MaErDaT4d3]] { @hideEmpty = False pos = -3725,900,-1 } //------------------------------------------ //=========================================================================================== // MaErDa Techtree Defs //=========================================================================================== RDNode { id = MaErDaT0 title = MaErda R&D Partnership description = While researching alone is never a good idea; MaErDa Corp give you the opportunity to access to their new prototypes in exchange of some of your exploration's research and your money of course ! cost = 50 hideEmpty = False nodeName = node1_maerdat0 anyToUnlock = False icon = maerdat0 pos = -2625,1199,-1 scale = 0.6 Parent { parentID = start lineFrom = LEFT lineTo = RIGHT } } RDNode { id = MaErDaT1 title = MaErda 0.625m Form Factor description = 0.625m Branch of MaErDa R&D cost = 65 hideEmpty = False nodeName = node1_maerdat1 anyToUnlock = False icon = maerdat1 pos = -2900,1199,-1 scale = 0.6 Parent { parentID = MaErDaT0 lineFrom = LEFT lineTo = RIGHT } } RDNode { id = MaErDaT1a1 title = MaErda 0.625m pods description = 0.625m Branch of MaErDa Pods cost = 65 hideEmpty = False nodeName = node1_maerdat1a1 anyToUnlock = False icon = maerdat1a pos = -2975,1300,-1 scale = 0.6 Parent { parentID = MaErDaT1 lineFrom = LEFT lineTo = RIGHT } } RDNode { id = MaErDaT1a2 title = MaErda High-Tech 0.625m pods description = 0.625m High-Tech Branch of MaErDa Pods cost = 250 hideEmpty = False nodeName = node1_maerdat1a2 anyToUnlock = False icon = maerdat1a pos = -2975,1400,-1 scale = 0.6 Parent { parentID = MaErDaT1a1 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT1a3 title = MaErda 0.625m pods Prototypes description = 0.625m Branch of MaErDa Pods Prototypes cost = 500 hideEmpty = False nodeName = node1_maerdat1a3 anyToUnlock = False icon = maerdat1a pos = -2975,1500,-1 scale = 0.6 Parent { parentID = MaErDaT1a2 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT1b1 title = MaErda 0.625m Utils description = 0.625m Branch of MaErDa Utils cost = 65 hideEmpty = False nodeName = node1_maerdat1b1 anyToUnlock = False icon = maerdat1b pos = -2825,1300,-1 scale = 0.6 Parent { parentID = MaErDaT1 lineFrom = RIGHT lineTo = LEFT } } RDNode { id = MaErDaT1b2 title = MaErda High-Tech 0.625m Utils description = 0.625m High-Tech Branch of MaErDa Utils cost = 250 hideEmpty = False nodeName = node1_maerdat1b2 anyToUnlock = False icon = maerdat1b pos = -2825,1400,-1 scale = 0.6 Parent { parentID = MaErDaT1b1 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT1b3 title = MaErda 0.625m Utils Prototypes description = 0.625m Branch of MaErDa Utils Prototypes cost = 500 hideEmpty = False nodeName = node1_maerdat1b3 anyToUnlock = False icon = maerdat1b pos = -2825,1500,-1 scale = 0.6 Parent { parentID = MaErDaT1b2 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT1c1 title = MaErda 0.625m Tanks description = 0.625m Branch of MaErDa Tanks cost = 65 hideEmpty = False nodeName = node1_maerdat1c1 anyToUnlock = False icon = maerdat1c pos = -2975,1100,-1 scale = 0.6 Parent { parentID = MaErDaT1 lineFrom = LEFT lineTo = RIGHT } } RDNode { id = MaErDaT1c2 title = MaErda High-Tech 0.625m Tanks description = 0.625m High-Tech Branch of MaErDa Tanks cost = 250 hideEmpty = False nodeName = node1_maerdat1c2 anyToUnlock = False icon = maerdat1c pos = -2975,1000,-1 scale = 0.6 Parent { parentID = MaErDaT1c1 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT1c3 title = MaErda 0.625m Tanks Prototypes description = 0.625m Branch of MaErDa Tanks Prototypes cost = 500 hideEmpty = False nodeName = node1_maerdat1c3 anyToUnlock = False icon = maerdat1c pos = -2975,900,-1 scale = 0.6 Parent { parentID = MaErDaT1c2 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT1d1 title = MaErda 0.625m Engines description = 0.625m Branch of MaErDa Engines cost = 65 hideEmpty = False nodeName = node1_maerdat1d1 anyToUnlock = False icon = maerdat1d pos = -2825,1100,-1 scale = 0.6 Parent { parentID = MaErDaT1 lineFrom = RIGHT lineTo = LEFT } } RDNode { id = MaErDaT1d2 title = MaErda High-Tech 0.625m Engines description = 0.625m High-Tech Branch of MaErDa Engines cost = 250 hideEmpty = False nodeName = node1_maerdat1d2 anyToUnlock = False icon = maerdat1d pos = -2825,1000,-1 scale = 0.6 Parent { parentID = MaErDaT1d1 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT1d3 title = MaErda 0.625m Engines Prototypes description = 0.625m Branch of MaErDa Engines Prototypes cost = 500 hideEmpty = False nodeName = node1_maerdat1d3 anyToUnlock = False icon = maerdat1d pos = -2825,900,-1 scale = 0.6 Parent { parentID = MaErDaT1d2 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT2 title = MaErda 1.25m pods description = 1.25m Branch of MaErDa Pods cost = 125 hideEmpty = False nodeName = node1_maerdat2 anyToUnlock = False icon = maerdat2 pos = -3200,1199,-1 scale = 0.6 Parent { parentID = MaErDaT1 lineFrom = LEFT lineTo = RIGHT } } RDNode { id = MaErDaT2a1 title = MaErda 1.25m Rocket description = 1.25m Branch of MaErDa Rocket cost = 125 hideEmpty = False nodeName = node1_maerdat2a1 anyToUnlock = False icon = maerdat2a pos = -3275,1300,-1 scale = 0.6 Parent { parentID = MaErDaT2 lineFrom = LEFT lineTo = RIGHT } } RDNode { id = MaErDaT2a2 title = MaErda High-Tech 1.25m Rocket description = 1.25m High-Tech Branch of MaErDa Rocket cost = 500 hideEmpty = False nodeName = node1_maerdat2a2 anyToUnlock = False icon = maerdat2a pos = -3275,1400,-1 scale = 0.6 Parent { parentID = MaErDaT2a1 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT2a3 title = MaErda 1.25m Rocket Prototypes description = 1.25m Branch of MaErDa Rocket Prototypes cost = 1000 hideEmpty = False nodeName = node1_maerdat2a3 anyToUnlock = False icon = maerdat2a pos = -3275,1500,-1 scale = 0.6 Parent { parentID = MaErDaT2a2 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT2b1 title = MaErda 1.25m Utils description = 1.25m Branch of MaErDa Utils cost = 125 hideEmpty = False nodeName = node1_maerdat2b1 anyToUnlock = False icon = maerdat2b pos = -3125,1300,-1 scale = 0.6 Parent { parentID = MaErDaT2 lineFrom = RIGHT lineTo = LEFT } } RDNode { id = MaErDaT2b2 title = MaErda High-Tech 1.25m Utils description = 1.25m High-Tech Branch of MaErDa Utils cost = 500 hideEmpty = False nodeName = node1_maerdat2b2 anyToUnlock = False icon = maerdat2b pos = -3125,1400,-1 scale = 0.6 Parent { parentID = MaErDaT2b1 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT2b3 title = MaErda 1.25m Utils Prototypes description = 1.25m Branch of MaErDa Utils Prototypes cost = 1000 hideEmpty = False nodeName = node1_maerdat2b3 anyToUnlock = False icon = maerdat2b pos = -3125,1500,-1 scale = 0.6 Parent { parentID = MaErDaT2b2 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT2c1 title = MaErda 1.25m Tanks description = 1.25m Branch of MaErDa Tanks cost = 125 hideEmpty = False nodeName = node1_maerdat2c1 anyToUnlock = False icon = maerdat2c pos = -3275,1100,-1 scale = 0.6 Parent { parentID = MaErDaT2 lineFrom = LEFT lineTo = RIGHT } } RDNode { id = MaErDaT2c2 title = MaErda High-Tech 1.25m Tanks description = 1.25m High-Tech Branch of MaErDa Tanks cost = 500 hideEmpty = False nodeName = node1_maerdat2c2 anyToUnlock = False icon = maerdat2c pos = -3275,1000,-1 scale = 0.6 Parent { parentID = MaErDaT2c1 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT2c3 title = MaErda 1.25m Tanks Prototypes description = 1.25m Branch of MaErDa Tanks Prototypes cost = 1000 hideEmpty = False nodeName = node1_maerdat2c3 anyToUnlock = False icon = maerdat2c pos = -3275,900,-1 scale = 0.6 Parent { parentID = MaErDaT2c2 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT2d1 title = MaErda 1.25m Engines description = 1.25m Branch of MaErDa Engines cost = 125 hideEmpty = False nodeName = node1_maerdat2d1 anyToUnlock = False icon = maerdat2d pos = -3125,1100,-1 scale = 0.6 Parent { parentID = MaErDaT2 lineFrom = RIGHT lineTo = LEFT } } RDNode { id = MaErDaT2d2 title = MaErda High-Tech 1.25m Engines description = 1.25m High-Tech Branch of MaErDa Engines cost = 500 hideEmpty = False nodeName = node1_maerdat2d2 anyToUnlock = False icon = maerdat2d pos = -3125,1000,-1 scale = 0.6 Parent { parentID = MaErDaT2d1 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT2d3 title = MaErda 1.25m Engines Prototypes description = 1.25m Branch of MaErDa Engines Prototypes cost = 1000 hideEmpty = False nodeName = node1_maerdat2d3 anyToUnlock = False icon = maerdat2d pos = -3125,900,-1 scale = 0.6 Parent { parentID = MaErDaT2d2 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT3 title = MaErda 2.5m Form Factor description = 2.5m Branch of MaErDa R&D cost = 250 hideEmpty = False nodeName = node1_maerdat3 anyToUnlock = False icon = maerdat3 pos = -3500,1199,-1 scale = 0.6 Parent { parentID = MaErDaT2 lineFrom = LEFT lineTo = RIGHT } } RDNode { id = MaErDaT3a1 title = MaErda 2.5m pods description = 2.5m Branch of MaErDa Pods cost = 250 hideEmpty = False nodeName = node1_maerdat3a1 anyToUnlock = False icon = maerdat3a pos = -3575,1300,-1 scale = 0.6 Parent { parentID = MaErDaT3 lineFrom = LEFT lineTo = RIGHT } } RDNode { id = MaErDaT3a2 title = MaErda High-Tech 2.5m pods description = 2.5m High-Tech Branch of MaErDa Pods cost = 500 hideEmpty = False nodeName = node1_maerdat3a2 anyToUnlock = False icon = maerdat3a pos = -3575,1400,-1 scale = 0.6 Parent { parentID = MaErDaT3a1 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT3a3 title = MaErda 2.5m pods Prototypes description = 2.5m Branch of MaErDa Pods Prototypes cost = 1000 hideEmpty = False nodeName = node1_maerdat3a3 anyToUnlock = False icon = maerdat3a pos = -3575,1500,-1 scale = 0.6 Parent { parentID = MaErDaT3a2 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT3b1 title = MaErda 2.5m Utils description = 2.5m Branch of MaErDa Utils cost = 250 hideEmpty = False nodeName = node1_maerdat3b1 anyToUnlock = False icon = maerdat3b pos = -3425,1300,-1 scale = 0.6 Parent { parentID = MaErDaT3 lineFrom = RIGHT lineTo = LEFT } } RDNode { id = MaErDaT3b2 title = MaErda High-Tech 2.5m Utils description = 2.5m High-Tech Branch of MaErDa Utils cost = 500 hideEmpty = False nodeName = node1_maerdat3b2 anyToUnlock = False icon = maerdat3b pos = -3425,1400,-1 scale = 0.6 Parent { parentID = MaErDaT3b1 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT3b3 title = MaErda 2.5m Utils Prototypes description = 2.5m Branch of MaErDa Utils Prototypes cost = 1000 hideEmpty = False nodeName = node1_maerdat3b3 anyToUnlock = False icon = maerdat3b pos = -3425,1500,-1 scale = 0.6 Parent { parentID = MaErDaT3b2 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT3c1 title = MaErda 2.5m Tanks description = 2.5m Branch of MaErDa Tanks cost = 250 hideEmpty = False nodeName = node1_maerdat3c1 anyToUnlock = False icon = maerdat3c pos = -3575,1100,-1 scale = 0.6 Parent { parentID = MaErDaT3 lineFrom = LEFT lineTo = RIGHT } } RDNode { id = MaErDaT3c2 title = MaErda High-Tech 2.5m Tanks description = 2.5m High-Tech Branch of MaErDa Tanks cost = 500 hideEmpty = False nodeName = node1_maerdat3c2 anyToUnlock = False icon = maerdat3c pos = -3575,1000,-1 scale = 0.6 Parent { parentID = MaErDaT3c1 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT3c3 title = MaErda 2.5m Tanks Prototypes description = 2.5m Branch of MaErDa Tanks Prototypes cost = 1000 hideEmpty = False nodeName = node1_maerdat3c3 anyToUnlock = False icon = maerdat3c pos = -3575,900,-1 scale = 0.6 Parent { parentID = MaErDaT3c2 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT3d1 title = MaErda 2.5m Engines description = 2.5m Branch of MaErDa Engines cost = 250 hideEmpty = False nodeName = node1_maerdat3d1 anyToUnlock = False icon = maerdat3d pos = -3425,1100,-1 scale = 0.6 Parent { parentID = MaErDaT3 lineFrom = RIGHT lineTo = LEFT } } RDNode { id = MaErDaT3d2 title = MaErda High-Tech 2.5m Engines description = 2.5m High-Tech Branch of MaErDa Engines cost = 500 hideEmpty = False nodeName = node1_maerdat3d2 anyToUnlock = False icon = maerdat3d pos = -3425,1000,-1 scale = 0.6 Parent { parentID = MaErDaT3d1 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT3d3 title = MaErda 2.5m Engines Prototypes description = 2.5m Branch of MaErDa Engines Prototypes cost = 1000 hideEmpty = False nodeName = node1_maerdat3d3 anyToUnlock = False icon = maerdat3d pos = -3425,900,-1 scale = 0.6 Parent { parentID = MaErDaT3d2 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT4 title = MaErda 3.75m Form Factor description = 3.75m Branch of MaErDa R&D cost = 375 hideEmpty = False nodeName = node1_maerdat4 anyToUnlock = False icon = maerdat4 pos = -3800,1199,-1 scale = 0.6 Parent { parentID = MaErDaT3 lineFrom = LEFT lineTo = RIGHT } } RDNode { id = MaErDaT4a1 title = MaErda 3.75m pods description = 3.75m Branch of MaErDa Pods cost = 375 hideEmpty = False nodeName = node1_maerdat4a1 anyToUnlock = False icon = maerdat4a pos = -3875,1300,-1 scale = 0.6 Parent { parentID = MaErDaT4 lineFrom = LEFT lineTo = RIGHT } } RDNode { id = MaErDaT4a2 title = MaErda High-Tech 3.75m pods description = 3.75m High-Tech Branch of MaErDa Pods cost = 500 hideEmpty = False nodeName = node1_maerdat4a2 anyToUnlock = False icon = maerdat4a pos = -3875,1400,-1 scale = 0.6 Parent { parentID = MaErDaT4a1 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT4a3 title = MaErda 3.75m pods Prototypes description = 3.75m Branch of MaErDa Pods Prototypes cost = 1000 hideEmpty = False nodeName = node1_maerdat4a2 anyToUnlock = False icon = maerdat4a pos = -3875,1500,-1 scale = 0.6 Parent { parentID = MaErDaT4a2 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT4b1 title = MaErda 3.75m Utils description = 3.75m Branch of MaErDa Utils cost = 375 hideEmpty = False nodeName = node1_maerdat4b1 anyToUnlock = False icon = maerdat4b pos = -3725,1300,-1 scale = 0.6 Parent { parentID = MaErDaT4 lineFrom = RIGHT lineTo = LEFT } } RDNode { id = MaErDaT4b2 title = MaErda High-Tech 3.75m Utils description = 3.75m High-Tech Branch of MaErDa Utils cost = 500 hideEmpty = False nodeName = node1_maerdat4b2 anyToUnlock = False icon = maerdat4b pos = -3725,1400,-1 scale = 0.6 Parent { parentID = MaErDaT4b1 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT4b3 title = MaErda 3.75m Utils Prototypes description = 3.75m Branch of MaErDa Utils Prototypes cost = 1000 hideEmpty = False nodeName = node1_maerdat4b3 anyToUnlock = False icon = maerdat4b pos = -3725,1500,-1 scale = 0.6 Parent { parentID = MaErDaT4b2 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT4c1 title = MaErda 3.75m Tanks description = 3.75m Branch of MaErDa Tanks cost = 375 hideEmpty = False nodeName = node1_maerdat4c1 anyToUnlock = False icon = maerdat4c pos = -3875,1100,-1 scale = 0.6 Parent { parentID = MaErDaT4 lineFrom = LEFT lineTo = RIGHT } } RDNode { id = MaErDaT4c2 title = MaErda High-Tech 3.75m Tanks description = 3.75m High-Tech Branch of MaErDa Tanks cost = 500 hideEmpty = False nodeName = node1_maerdat4c2 anyToUnlock = False icon = maerdat4c pos = -3875,1000,-1 scale = 0.6 Parent { parentID = MaErDaT4c1 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT4c3 title = MaErda 3.75m Tanks Prototypes description = 3.75m Branch of MaErDa Tanks Prototypes cost = 1000 hideEmpty = False nodeName = node1_maerdat4c3 anyToUnlock = False icon = maerdat4c pos = -3875,900,-1 scale = 0.6 Parent { parentID = MaErDaT4c2 lineFrom = RIGHT lineTo = RIGHT } } RDNode { id = MaErDaT4d1 title = MaErda 3.75m Engines description = 3.75m Branch of MaErDa Engines cost = 375 hideEmpty = False nodeName = node1_maerdat4d1 anyToUnlock = False icon = maerdat4d pos = -3725,1100,-1 scale = 0.6 Parent { parentID = MaErDaT4 lineFrom = RIGHT lineTo = LEFT } } RDNode { id = MaErDaT4d2 title = MaErda High-Tech 3.75m Engines description = 3.75m High-Tech Branch of MaErDa Engines cost = 500 hideEmpty = False nodeName = node1_maerdat4d2 anyToUnlock = False icon = maerdat4d pos = -3725,1000,-1 scale = 0.6 Parent { parentID = MaErDaT4d1 lineFrom = LEFT lineTo = LEFT } } RDNode { id = MaErDaT4d3 title = MaErda 3.75m Engines Prototypes description = 3.75m Branch of MaErDa Engines Prototypes cost = 1000 hideEmpty = False nodeName = node1_maerdat4d3 anyToUnlock = False icon = maerdat4d pos = -3725,900,-1 scale = 0.6 Parent { parentID = MaErDaT4d2 lineFrom = LEFT lineTo = LEFT } } //=========================================================================================== // MaErDa Techtree End //=========================================================================================== Ok, I'd closed the PR so it won't get added to CKAN. As far as the TechTree config, I'm not sure where to get help for that, but this thread is probably not the best for it. Link to comment Share on other sites More sharing options...
Olympic1 Posted May 31, 2017 Share Posted May 31, 2017 24 minutes ago, ItsSeanBroleson said: for my own curiosity, is there any delay on the CKAN end when authors complete their work on an update? Like, do they submit it and then CKAN indexing takes system/developer action or is it pretty instant after an author sends it out to be indexed? Depends on where CKAN gets the releases from. CKAN can pull from SpaceDock, Github, Curse, Jenkins or other websites. When releasing on SpaceDock, that release is immediately (max 1min) added to CKAN. Releases on other platforms however (see above), get added when our bot detects it (max 3 hours). Link to comment Share on other sites More sharing options...
Devan kerman Posted May 31, 2017 Share Posted May 31, 2017 I have a small problem with the new ksp 1.3 release... The mod Devs who upload there mods to curse can't choose the option to upload for 1.3 and some other websites are also having this problem. I'm playing on ksp 1.2 and I don't want to update yet, and CKAN is downloading mods that are meant for 1.3 and causing all sorts of problems. Even if you do fix this can you add an option to downgrade all your current mods to the correct version? -Thanks Devan Link to comment Share on other sites More sharing options...
politas Posted May 31, 2017 Author Share Posted May 31, 2017 5 hours ago, Devan kerman said: I have a small problem with the new ksp 1.3 release... The mod Devs who upload there mods to curse can't choose the option to upload for 1.3 and some other websites are also having this problem. I'm playing on ksp 1.2 and I don't want to update yet, and CKAN is downloading mods that are meant for 1.3 and causing all sorts of problems. Even if you do fix this can you add an option to downgrade all your current mods to the correct version? -Thanks Devan Once the mods are fixed on Curse and the CKAN metadata updates, a Clean & reinstall will get the correct versions on all mods installed. (Or you can just uninstall and reinstall the specific mods) If the metadata is controlled by us rather than the mod author, we can also add an override to force the correct mod compatibility util Curse gets around to fixing it, and you can force installation of a particular version of a mod using the command line by saying: ckan.exe install <Modidentifier>=<version> (Make sure you get the full version string and the mod identifier from the mod details) Link to comment Share on other sites More sharing options...
Devan kerman Posted May 31, 2017 Share Posted May 31, 2017 Thanks! -Devan Link to comment Share on other sites More sharing options...
felcas Posted June 1, 2017 Share Posted June 1, 2017 On 2017-5-30 at 2:09 PM, HebaruSan said: It's not the same as having it in CKAN itself, but try sorting this page by "Last Indexed": http://status.ksp-ckan.org/ Thanks HebaruSan, I didn't see this because the software does not have that colum. I didn't knew about the link you sent to me. I will use it but I still think that adding a colum like I described would be very handy. Link to comment Share on other sites More sharing options...
ss8913 Posted June 1, 2017 Share Posted June 1, 2017 so.. raster prop monitor updated to 1.3 a couple days ago, yet CKAN still shows 1.2.2 as the max supported version... moarDV says to ask here if there are CKAN issues, so... I'm asking here... is there a problem with this mod or its metadata? Link to comment Share on other sites More sharing options...
blowfish Posted June 1, 2017 Share Posted June 1, 2017 25 minutes ago, ss8913 said: so.. raster prop monitor updated to 1.3 a couple days ago, yet CKAN still shows 1.2.2 as the max supported version... moarDV says to ask here if there are CKAN issues, so... I'm asking here... is there a problem with this mod or its metadata? Latest release is marked as a prerelase on Github. Prereleases will not be indexed for CKAN. Link to comment Share on other sites More sharing options...
KSPNoob Posted June 1, 2017 Share Posted June 1, 2017 So with the launch of 1.3 I decided to give Ckan a try on my fresh install of KSP. I deleted my old KSP folders and started a new however when I downloaded my mods through CKAN they still show up as AD as if I manually installed them. Not sure whats going on, anyone have an idea? Link to comment Share on other sites More sharing options...
felcas Posted June 1, 2017 Share Posted June 1, 2017 On 2017-5-30 at 2:09 PM, HebaruSan said: It's not the same as having it in CKAN itself, but try sorting this page by "Last Indexed": http://status.ksp-ckan.org/ HebaruSan, I just played a bit with the link you sent me, there are a lot of recently indexed mods that are not available in CKAN software. I also found a solution to the problem. I post here for other users reference. If you are in CKAN and want to know the latest additions you can just click on the FILTER BUTTON in the side of the blue arrows buttons, once you click in there you will find some interesting options being one of them the NEW IN REPOSITORY option. Link to comment Share on other sites More sharing options...
Rafael acevedo Posted June 1, 2017 Share Posted June 1, 2017 Anyone experiencing slow download speed on ckan when getting mods from spacedock. I tested my connection and it is not on my end. Link to comment Share on other sites More sharing options...
TheRagingIrishman Posted June 1, 2017 Share Posted June 1, 2017 1 hour ago, Rafael acevedo said: Anyone experiencing slow download speed on ckan when getting mods from spacedock. I tested my connection and it is not on my end. Spacedock is a community ran site so it occasionally has low connection speeds. You can check to make sure it's not ckan by going to spacedock.info and trying to download something. Link to comment Share on other sites More sharing options...
Rafael acevedo Posted June 1, 2017 Share Posted June 1, 2017 30 minutes ago, TheRagingIrishman said: Spacedock is a community ran site so it occasionally has low connection speeds. You can check to make sure it's not ckan by going to spacedock.info and trying to download something. tried it downloaded in 1 second versus 2 hours through ckan. I also reported the issue on spacedock Link to comment Share on other sites More sharing options...
politas Posted June 1, 2017 Author Share Posted June 1, 2017 6 hours ago, Rafael acevedo said: Anyone experiencing slow download speed on ckan when getting mods from spacedock. I tested my connection and it is not on my end. Have you got the latest CKAN 1.22.3? 19 hours ago, felcas said: Thanks HebaruSan, I didn't see this because the software does not have that colum. I didn't knew about the link you sent to me. I will use it but I still think that adding a colum like I described would be very handy. Yep, it would be useful, but given the way that our automatic indexing of new updates works, that information is just not available for the client. We'd need to maintain a whole separate data structure in order to compare the new repo data with past repo data, and then the client would need to spend time comparing every mod's current release with what it last knew as the current release, working out what to do with that information,... We'd basically need to program an AI to do what we do keeping the repo up to date so that it can understand some changes. I know that it seems like an easy thing to do, but trust me, it really isn't. If it was easy, we'd have done it by now. 15 hours ago, KSPNoob said: So with the launch of 1.3 I decided to give Ckan a try on my fresh install of KSP. I deleted my old KSP folders and started a new however when I downloaded my mods through CKAN they still show up as AD as if I manually installed them. Not sure whats going on, anyone have an idea? If you have deleted everything in your GameData folder (other than the Squad folder, obviously), then you shouldn't be getting any AD mods. I know I sound like a broken record, but try a Clean & Reinstall. (Or the relevant parts of it) It really does solve most problems in the CKAN client. Link to comment Share on other sites More sharing options...
HebaruSan Posted June 1, 2017 Share Posted June 1, 2017 22 minutes ago, politas said: Yep, it would be useful, but given the way that our automatic indexing of new updates works, that information is just not available for the client. We'd need to maintain a whole separate data structure in order to compare the new repo data with past repo data, and then the client would need to spend time comparing every mod's current release with what it last knew as the current release, working out what to do with that information,... We'd basically need to program an AI to do what we do keeping the repo up to date so that it can understand some changes. I know that it seems like an easy thing to do, but trust me, it really isn't. If it was easy, we'd have done it by now. What about tracking the timestamp when a new version was added? Solving the 100% case of same-version updates with full metadata checking would be AI-level processing and lots of storage, but I think that the date of the latest release is all that anyone actually cares about. Doesn't the crawler know when the version it downloaded wasn't already indexed? registry.json:available_modules/<modname>/module_version/<version>/initial_timestamp? Link to comment Share on other sites More sharing options...
politas Posted June 1, 2017 Author Share Posted June 1, 2017 (edited) 16 minutes ago, HebaruSan said: What about tracking the timestamp when a new version was added? Solving the 100% case of same-version updates with full metadata checking would be AI-level processing and lots of storage, but I think that the date of the latest release is all that anyone actually cares about. Doesn't the crawler know when the version it downloaded wasn't already indexed? registry.json:available_modules/<modname>/module_version/<version>/initial_timestamp? No, it doesn't, from my understanding. If you have some code experience, and can think of a way to do it without breaking what it does, we welcome contributions! https://github.com/KSP-CKAN/NetKAN-bot is the specific repo. I don't know Perl at all, so I only know how it works by what I've been told. Edited June 1, 2017 by politas expand Link to comment Share on other sites More sharing options...
Rafael acevedo Posted June 1, 2017 Share Posted June 1, 2017 53 minutes ago, politas said: Have you got the latest CKAN 1.22.3 Yes, I do Link to comment Share on other sites More sharing options...
ss8913 Posted June 2, 2017 Share Posted June 2, 2017 20 hours ago, KSPNoob said: So with the launch of 1.3 I decided to give Ckan a try on my fresh install of KSP. I deleted my old KSP folders and started a new however when I downloaded my mods through CKAN they still show up as AD as if I manually installed them. Not sure whats going on, anyone have an idea? If you start over, you need to delete the old CKAN folder as well, since CKAN keeps track of what it's installed... basically to do a KSP reset: 1. delete CKAN GameData Ships (from your KSP install dir) 2. ensure ckan.exe is in the KSP install dir 3. have steam verify local files to restore GameData and Ships 4. run CKAN 5. install mods Link to comment Share on other sites More sharing options...
ferretpl Posted June 2, 2017 Share Posted June 2, 2017 On 5/21/2017 at 8:56 PM, loppnessmonsta said: Hey all! Sorry if this has been covered before and I missed it, but it's been driving me nuts for a while now and I can't find anything to fix it. All of Sarbian's mods give an error when installing, including ModuleManager. His are the only mods I have noticed doing this. This is the error I get: Failed to download "https://ksp.sarbian.com/jenkins/job/ModuleManager/126/artifact/ModuleManager-2.7.6.zip" - error: The request was aborted: Could not create SSL/TLS secure channel. I have done a clean install, which resolved all the other errors I'd been getting, but this one is proving stubborn. Just in case you didn't solve your problem, firewall andor antivirus software is the cause, in my case it was FSECURE blocking connections with invalid/outdated/unsure certificates Link to comment Share on other sites More sharing options...
eragon333 Posted June 2, 2017 Share Posted June 2, 2017 Is it possible to make in local files in CKAN folder, history of all Status Logs? It would help to detect mods that're causing game crash or when we want to find mods we uninstalled. Link to comment Share on other sites More sharing options...
felcas Posted June 2, 2017 Share Posted June 2, 2017 21 hours ago, politas said: Yep, it would be useful, but given t Hhe way that our automatic indexing of new updates works, that information is just not available for the client. We'd need to maintain a whole separate data structure in order to compare the new repo data with past repo data, and then the client would need to spend time comparing every mod's current release with what it last knew as the current release, working out what to do with that information,... We'd basically need to program an AI to do what we do keeping the repo up to date so that it can understand some changes. I know that it seems like an easy thing to do, but trust me, it really isn't. If it was easy, we'd have done it by now. Hy Politas, thanks for the reply and yes I believe in you. After that I discovered the option FILTER > NEW IN REPOSITORY However I would like to point out some discrepancies. 1-HebaruSan sugested I check the new indexed mods in this link http://status.ksp-ckan.org/ , it was a good solution, I found some mods I was looking for but and headed for CKAN for the upgrade but I didn't found them there. I tried several other recently indexed mods and searched for them in CKAN, again they was not listed. APPEAR to not working properly 2-The option FILTER > NEW IN REPOSITORY, was working nicely, until I noticed yesterday that there was no new mods (zero), however I also noticed the number of compactible mods rised. I just finished going thru 337 of them and indeed found some new stuff I was waiting for, and others I didn't see before. Soo this filter also APPEAR to not be working properly. When I say APPEAR is really that, because I am also considering I am doing something wrong and I will apreciate if you can correct me. Thanks Link to comment Share on other sites More sharing options...
KSPNoob Posted June 2, 2017 Share Posted June 2, 2017 17 hours ago, ss8913 said: If you start over, you need to delete the old CKAN folder as well, since CKAN keeps track of what it's installed... basically to do a KSP reset: 1. delete CKAN GameData Ships (from your KSP install dir) 2. ensure ckan.exe is in the KSP install dir 3. have steam verify local files to restore GameData and Ships 4. run CKAN 5. install mods Thnx but I got it working with earlier advice (to clear and reset) however I put my Ckan.exe simply on my desktop and it works fine. Link to comment Share on other sites More sharing options...
Slaver0110 Posted June 2, 2017 Share Posted June 2, 2017 (edited) Just a quick question. I was wondering if there is any way to set CKAN to only download mods for a certain KSP version. I'm still using KSP 1.2.2 until all the mods that I use have been updated to 1.3. Problem is, my install was borked yesterday and I had to do a clean install (KSP 1.2.2), and CKAN seems to insist on installing mods that are updated to 1.3 (which kills my saves). Is there any way to set CKAN to install the mod version that are 1.2.2 compatible only, excluding 1.3 versions ? Thanks in advance, and cheers! Edited June 2, 2017 by Slaver0110 Edited for clarity Link to comment Share on other sites More sharing options...
HebaruSan Posted June 2, 2017 Share Posted June 2, 2017 13 minutes ago, Slaver0110 said: Just a quick question. I was wondering if there is any way to set CKAN to only download mods for a certain KSP version. I'm still using KSP 1.2.2 until all the mods that I use have been updated to 1.3. Problem is, my install was borked yesterday and I had to do a clean install (KSP 1.2.2), and CKAN seems to insist on installing mods that are updated to 1.3 (which kills my saves). Is there any way to set CKAN to install the mod version that are 1.2.2 compatible only, excluding 1.3 versions ? CKAN is supposed to do this already. It can tell which version of the game you have, and it tracks which versions of each mod are compatible with which versions of the game. By default it should only be showing you mods that are compatible with your KSP version. If it's showing you incompatible mod versions, the most likely cause is incorrect metadata for those mods. The most likely cause for that is the fact that Curse has not added a 1.3.0 version option to their web site, but modders are uploading updated mods anyway and selecting 1.2.2 instead, which incorrectly marks that mod as 1.2.2 compatible. No, there's not much you as a user can do about that; it might get straightened out once Curse adds a 1.3.0 option and modders start using it, or it might not. Link to comment Share on other sites More sharing options...
Slaver0110 Posted June 2, 2017 Share Posted June 2, 2017 11 minutes ago, HebaruSan said: CKAN is supposed to do this already. It can tell which version of the game you have, and it tracks which versions of each mod are compatible with which versions of the game. By default it should only be showing you mods that are compatible with your KSP version. If it's showing you incompatible mod versions, the most likely cause is incorrect metadata for those mods. The most likely cause for that is the fact that Curse has not added a 1.3.0 version option to their web site, but modders are uploading updated mods anyway and selecting 1.2.2 instead, which incorrectly marks that mod as 1.2.2 compatible. No, there's not much you as a user can do about that; it might get straightened out once Curse adds a 1.3.0 option and modders start using it, or it might not. Ah, ok. Thanks for the info. For the time being I'll just manually hunt for the compatible versions and manually install. Not a big deal, just tedious. Thanks for the reply, and have a good weekend. Cheers. Link to comment Share on other sites More sharing options...
Recommended Posts