Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

714 Excellent

1 Follower

About micha

  • Rank
    Sr. Spacecraft Engineer

Contact Methods

Profile Information

  • Location
    Tokyo, JP
  • Interests
    Computer (games); Motorbiking; Scuba-diving; reading; travelling; ...

Recent Profile Visitors

3,917 profile views
  1. 1.8 moved to a new version of Unity (2019.2.2.f1) and thus DotNet (4.x up from 3.5) which may have helped.
  2. You're talking IRL. I believe most other people here are talking KSP (where a Pod is a single item, not a collection of (redundant) subsystems). Of course, I reserve the right to be utterly wrong on this The OP was (I believe) saying that it doesn't make sense that a fully assembled Pod consisting of chassis plus all integrated subsystems and components costs the same as a parachute system. And I'd go out on a limb here and say the same is true IRL; that is, that a fully assembled command capsule (eg, Dragon) costs WAY more than the parachute subsystem integrated into it (IRL, the parachut
  3. Methinks there might be miscommunication. "Pod" != hull. "Pod" == hull + avionics + lights + life support + ....... Just like "parachute" != "canopy" but "parachute" == canopy + rigging + deployment mechanism + ....
  4. Umm... hardly. What primarily chews up memory is that the way KSP was written, ALL assets are loaded at the start and held in memory at all times. That's sounds, textures, models, etc etc. Most other games load levels or assets "on demand" which does slow them down a bit at times, but reduces their memory footprint significantly. Code itself is generally small. Maths functions in particular don't allocate memory so they barely impact RAM. There are lots of management and informational functions which DO use up lots of RAM though because they are constantly allocating memory. Poorly writt
  5. Well, they've only got a couple of body retextures left to do which will complete the promised stock texture revamp. Who knows what other feature additions they have planned though (there's a couple I can think of which the community has been somewhat loud about..). So maybe after that things will calm down a bit for a pure stability release?
  6. v2.0.0.6 is released for KSP1.11. Fixes a few issues and adds more part configurations. Please see the Changelog. Notably the StockFreedomAddon configuration is now enabled by default to have less restrictions. Also the "Enable Optional Passable Parts" option now takes effect immediately making it easier to tweak a parts' passability on the fly.
  7. I've not been able to repro. Can you please send me a save-game and detailed instructions to repro? I enabled "Enable Optional Passable Parts" then made a part surface-attachable passable and added a couple of Radial Attachment Points and some more pods to those. Single CLS. I then removed one from symmetry, the craft remained as a single CLS. I then re-rooted the craft and again, the craft remained as a single CLS.
  8. Release 1.3.6 is out. I've added some inventory to the pod and made most parts able to be cargo in-line with similar stock parts. I'm open to any balancing suggestions though.
  9. Is there a reason that parts have a stack limit? Seems that volume/mass restrictions of the container would have covered it along with a "canStack" flag if a part should not be stackable for some reason. Alternatively could we add a "0" or "-1" value to indicate that a part can be stacked infinitely (assuming volume/mass limits are maintained)? Also it would have been great if the game could calculate a parts' volume (if not explicitly provided) based on its dragcube thus automatically making all parts up to a certain size storable in inventories. It's a lot of work for modders to e
  10. Thanks, especially for showing that the hatch EVA button still works. I'll take a look. https://github.com/mwerle/ShipManifest/issues/7 EDIT: Figured out a fix; will come Soon (tm).
  11. Nothing at all? If the part which the crew member is in has a hatch then the Kerbal should go on EVA. If it has no hatch, then an error message should show up. It works for me so if the error persists, can you please share the log file and/or your save file so I can check?
  12. Release 2.0.0 is out! This release breaks compatibility with KSP versions prior to v1.3 due to the addition of localisation. More languages welcome! It also adds support for KSP1.11's inventory and EVA construction modes - you can now bring a KDex on a maintenance mission and have an Engineer attach it to an existing craft. Enjoy and please let me know if there are any issues.
  13. Donations to allow me to quit my full time job and work on this instead? FIrst of all (I haven't had a chance to test yet) it is highly likely that this mod continues to work just fine in 1.11 - have you tried it? If so, it would be valuable for me and the rest of the community to post your test results here along with any issues. Secondly when I do get around to verifying/updating it, I will post here. Sorry, but modding KSP is a volunteer project for most, if not all, modders, with at best the occasional beer token. Asking for updates shortly after a KSP update drops is consi
  14. Working as intended. If you don't like it, uninstall KSP-AVC. Awesome update! Looking forward to getting some time to playing around with it. Might even be able to finally remove KIS-dependency from NEOS now! (Love KIS, just dislike dependencies..)
  • Create New...