HebaruSan

Members
  • Content count

    1522
  • Joined

  • Last visited

Community Reputation

1998 Excellent

4 Followers

About HebaruSan

  • Rank
    External Tank

Profile Information

  • Interests http://kerbalx.com/HebaruSan
    http://steamcommunity.com/profiles/76561197970804764/screenshots/
  1. There seems to be a bad caching server somewhere on the internet (one of those "akamai" things) truncating one of the files. It's still being looked into as far as I know, but thanks to @ManeTI for helping me set up this hosts file workaround: 23.67.252.234 forum.kerbalspaceprogram.com I believe that address is simply a different caching server that has been confirmed to work (it also has an "akamai" WHOIS entry), so it should be harmless to switch. (But it could cause problems later on if akamai shuffles their server addresses, so don't do it unless you're unable to use the forum otherwise.)
  2. CKAN is currently confused by the format of this mod's download. http://status.ksp-ckan.org/ NetKAN Last Checked Last Inflated Last Indexed Last Error Impact 4 hours ago 4 hours ago 6 months ago Could not find Impact entry in zipfile to install The Impact folder is no longer present in the zip; instead, the files are directly in the root folder of the archive, which could be inconvenient for manual installation as well. v1.6.2: v1.6.0 (last indexed version):
  3. [1.3.0] Kopernicus (Release 7) - Sep. 25

    This allows time warp to be exploited to circumvent "difficult" planets like @Galileo's Thalia: Presumably the stock code to dissipate heat is scaled properly, so time warp drastically increases the cooling/heating ratio.
  4. I'm actually seeing ".1.1.0", with an extra period at the beginning. It seems to think that's the newest release for 1.2.2. I don't know why it would sort them that way, but that's also how it was entered in Github: Hopefully renaming it to 1.1.0 will help: https://github.com/KSP-CKAN/CKAN-meta/pull/1292
  5. Kopernicus does the same thing, so those devs might have some useful insights. It can work, but there are quirks. Most notably, CKAN will only check the most recent release each time it crawls Github, so if you upload them too quickly (which apparently does not apply in your case), intermediate versions can be skipped. For what it's worth, your versioning scheme sounds reasonable in principle (though I'm not a CKAN dev). I see two problems. First, both downloads' kOS.version files say: "KSP_VERSION_MIN": { "MAJOR": 1, "MINOR": 0, "PATCH": 0 }, ... which is being imported into CKAN's registry. So technically, both versions are marked as compatible with 1.2.2 (and 1.1.X, and 1.0.X), which could confuse things. I would suggest updating these to reflect the actual minimum KSP versions supported by each release (presumably 1.2.0 and 1.3.0), or just remove the _MIN and _MAX clauses completely since you do have regular KSP_VERSION in there. Second, the version number for 1.1.3.1 was mis-entered in Github: ... which was also pulled into CKAN's database. So if you're looking for "1.1.3.1", that's going to show up as "1.3.3.1" instead. But I'm not sure whether that's what you're seeing from your description.
  6. problem with modmanager

    It's not clear what problem you're having. Can you describe it with words?
  7. Undocking Not Working---How to Hack?

    Sure thing! Load this quicksave and press space bar: https://gist.github.com/HebaruSan/e22372e8b299fedf37a0b1bdf0414134/archive/f1a019223fbc778da2a0825b05c9629b9dc91763.zip
  8. Undocking Not Working---How to Hack?

    OK, I just re-tried it to make sure I wasn't leading you down a dead end, and that procedure does still reproduce the issue. Save file where the only active vessel has this issue Relevant portion ("state = Acquire (dockee)" for both ports): PART { name = dockingPort2 cid = 4294190358 uid = 3676834291 mid = 3278824030 launchID = 10 parent = 67 position = -8.476409912109375,-8.5787544250488281,0.00057887949515134096 rotation = 0.416523188,-0.416349232,0.571527243,0.571418047 mirror = 1,1,1 symMethod = Radial istg = 3 resPri = 0 dstg = 12 sqor = -1 sepI = 6 sidx = -1 attm = 0 srfN = srfAttach, -1 attN = top, -1 attN = bottom, 67 mass = 0.0500000007 shielded = False temp = 303.13664498589304 tempExt = 303.98759600676408 tempExtUnexp = 307.45932935809236 expt = 0.5 state = 1 attached = True autostrutMode = Off rigidAttachment = False flag = Squad/Agencies/Kerlington rTrf = dockingPort2 modCost = 0 EVENTS { } ACTIONS { } PARTDATA { } MODULE { name = ModuleDockingNode isEnabled = True crossfeed = True stagingEnabled = False state = Acquire (dockee) dockUId = 1867064019 dockNodeIdx = 0 EVENTS { } ACTIONS { UndockAction { actionGroup = None } DecoupleAction { actionGroup = None } MakeReferenceToggle { actionGroup = None } EnableXFeedAction { actionGroup = None } DisableXFeedAction { actionGroup = None } ToggleXFeedAction { actionGroup = None } } DOCKEDVESSEL { vesselName = Hot Fudge 1.0 Ship Debris vesselType = Debris rootUId = 632182998 } UPGRADESAPPLIED { } } } PART { name = dockingPort2 cid = 4294686114 uid = 1867064019 mid = 3278824030 launchID = 10 parent = 68 position = -9.0381135940551758,-8.5789861679077148,0.00053119583753868937 rotation = 0.379148751,0.379192799,-0.596632421,0.597066939 mirror = 1,1,1 symMethod = Radial istg = 4 resPri = 0 dstg = 0 sqor = 4 sepI = 7 sidx = 1 attm = 0 srfN = srfAttach, -1 attN = top, -1 attN = bottom, 70 mass = 0.0500000007 shielded = False temp = 311.5449700377394 tempExt = 309.81687072730409 tempExtUnexp = 4 expt = 0.5 state = 1 attached = True autostrutMode = Off rigidAttachment = False flag = Squad/Agencies/Kerlington rTrf = dockingPort2 modCost = 0 EVENTS { } ACTIONS { } PARTDATA { } MODULE { name = ModuleDockingNode isEnabled = True crossfeed = True stagingEnabled = True state = Acquire (dockee) dockUId = 3676834291 dockNodeIdx = 0 EVENTS { } ACTIONS { UndockAction { actionGroup = None } DecoupleAction { actionGroup = None } MakeReferenceToggle { actionGroup = None } EnableXFeedAction { actionGroup = None } DisableXFeedAction { actionGroup = None } ToggleXFeedAction { actionGroup = None } } DOCKEDVESSEL { vesselName = Hot Fudge 1.0 vesselType = Ship rootUId = 1208503703 } UPGRADESAPPLIED { } } } Screenshot with missing right click options to prove I'm not crazy:
  9. Undocking Not Working---How to Hack?

    Precision timing sounds painful. I made (unintentionally) a craft where complete docking without decoupling is impossible, since there isn't room for the free-moving port to fit with proper alignment; and if you decouple everything up-front, it's prohibitively difficult to dock because one of the pieces is free-floating with no control system and lots of initial rotation. But you can wedge them together so they're held in place by the magnetic attraction, and then dock by activating a decoupler to free up the constrained port. After that, the right click options to undock are either missing or ineffective (I don't remember which), and the status fields in the save file are "Acquire" instead of "Docked". It should be pretty easy to construct a simplified version of this for testing, or you can download my craft: Un-undockable docked ports on the right ---^
  10. Undocking Not Working---How to Hack?

    Is there an existing bug tracker entry where we should submit such? I found a way to reproduce it* consistently a while back. * I say "it," but I think there's actually a family of related bugs here. Mine has to do with injecting a stage/decouple event in between the point when the ports activate their magnets and when they attach.
  11. KSP Making History

    They announced the expansion at the beginning of development rather than close to the end, as with most projects, so we're getting a real-time lesson in how long it takes to develop software. Kind of unavoidable given their established practice of public weekly updates about what the developers are doing. Imagine a year of, "More unspecified work this week on the secret project that we won't announce until it's almost done." Presumably there will be a hype train reboot once it's in a pre-release testing state.
  12. Alright, so either it's not finding the ITS2 part modules, or the part modules aren't working the way you expect. Do you know which it is? If not, you could use Debug.Log() calls to add messages to KSP.log, like this, continuing from my previous post: foreach (InterstellarTextureSwitch2 intPart in intParts) { Debug.Log("Updating ITS2 module..."); // <-- Add stuff like this as needed intPart.updateSymmetry = false; if (next) intPart.nextTextureEvent(); else intPart.previousTextureEvent(); Debug.Log("ITS2 module updated."); // <-- Add stuff like this as needed } If it's finding the part modules, those messages will show up in KSP.log, otherwise they'll be absent.
  13. This is probably a case where the long story would be better, since it may be possible to solve whatever the problem was.
  14. So something like this? List<DCKtextureswitch2> dckParts = new List<DCKtextureswitch2>(200); List<DCKtextureswitch2> intParts = new List<InterstellarTextureSwitch2>(200); foreach (Part p in EditorLogic.fetch.ship.Parts) { dckParts.AddRange(p.FindModulesImplementing<DCKtextureswitch2>()); intParts.AddRange(p.FindModulesImplementing<InterstellarTextureSwitch2>()); } foreach (DCKtextureswitch2 dckPart in dckParts) { dckPart.updateSymmetry = false; //FIX symmetry problems because DCK also applies its own logic here // send previous or next command if (next) dckPart.nextTextureEvent(); else dckPart.previousTextureEvent(); } foreach (InterstellarTextureSwitch2 intPart in intParts) { intPart.updateSymmetry = false; if (next) intPart.nextTextureEvent(); else intPart.previousTextureEvent(); }
  15. What problems are you encountering with the current code?