Jump to content

linuxgurugamer

Bug Hunter
  • Posts

    24,989
  • Joined

  • Last visited

Everything posted by linuxgurugamer

  1. New release, 0.8.0.1: Updated for 1.3 (0.8.0) Replaced depreciated call to GameEvents.onLevelWas Loaded with Unity SceneManagment calls (0.8.0) Rebuild due to bad packaging Please tes and let me know if this is still happening, if it is, please ping me and raise a github issue
  2. @-MM- Most likely a simple recompile will fix this.
  3. And the answer is: The part.name contains the kerbal name, inside parentheses, so using the Split method, it's easy to get.
  4. I'm capturing the onCrewOnEva event, and while it works, when the event is called, the kerbal name is not yet set in the part.partInfo.title. This is bad, since I need to do something based on which kerbal it is. The title is set properly when the onCrewBoardVessel is called. Is this a bug, or a quirk, and, if a quirk, is there anyway around it? And, before anyone suggests it, the name is either kerbalEVA or kerbalEVAfemale
  5. I have this patch for Fusebox which works for everything EXCEPT the parts in Squad/Parts/Prebuilt: @PART[*]:HAS[#module[Part]]:Final { @module = PartTapIn } Is there any way to make it work for those? Right now I'm hard-coding in the exceptions for the three parts there: kerbalEVA kerbalEVAfemale flag
  6. No formal rules per se, but, you can fork it and release your own version. I assume you have tried to contact them? The license allows forks, and, if you make a good-faith effort to contact them, I don't think anyone will be offended. If you do fork, let me know when you have a release, I can get CKAN updated for you
  7. Thanks. I'll add this as a patch for now, and incorporate it into the individual parts for the next major release in a few weeks. I've deleted those files from the mod, they didn't belong there ========== New release, 3.1.4: Added interstage fix by Starwaster Deleted unnecessary files
  8. So, this is probably what you want instead of adding the CLS to all the picoports: @PART[dockingPort2M|dockingPort2F|dockingPort2Basic|dockingPortLargeM|dockingPortLargeF|dockingPortLargeBasic]:NEEDS[ConnectedLivingSpace] { MODULE { name = ModuleConnectedLivingSpace passable = true passableWhenSurfaceAttached = true } } I assume you are using this with the PicoPort4AllSizes patch. Save this as a file: zzz_CLS.cfg in the same directory as the patch : GameData\SHED\Patches and let me know how it works. Assuming it work properly, I'll add it to the patch file release
  9. it's fixed in the newest release. No need to edit anything in the file now
  10. I installed the last version of SSTU for 1.2.2 into a clean install along with Fusebox, it worked perfectly. I looked at your log file. The first errors happened with SSTUTools during loading, but I did not see those errors when I tested. I see lots of SSTU errors, ConnectedLivingSpace errors, etc. The fact that the toolbar itself isn't showing is another big issue The function doesn't reference any objects, other than the GameDatabase.Instance, and, if that is invalid, you have more problems than this
  11. New release, 0.1.0: Updated for 1.3 Disabled data window for ShipSections since it's not being used
  12. First, what version of the game are you playing? This is caused by a bug in 1.2.2 which there is some code to work around, I'm working on fixing it New release, 1.1.1.1: Fixed bug where the Base vacation rate being off by a factor of 100
  13. Thanks, I'll take a look. Just an FYI, it actually not a duplicate variable. The case is different. My guess is that someone messed up on typing in some info. I'll get this sorted out, thanks
  14. No, it's there. Try refreshing. I just tested by installing, worked without a problem. If it still isnt there, restart CKAN
  15. Oh, I see it now. This is a part made by a MM patch, the file with .new is a leftover from some work I was doing. It duplicates the KW2mengineSPS part, but changes the fuel from mono to rocket fuel. You can find the correct file here: KWRocketry/KWCommunityFixes/KWPatch-Community-Parts.cfg
  16. NO idea, but it wasn't done with this release. I'd have to look at the history to see when it was done
×
×
  • Create New...