Jump to content

allista

Members
 View Profile  See their activity

  • Posts

    2,208

  • Joined

  • Last visited

 Content Type 

Everything posted by allista

  1. allista
    Are you trying to use GC with KSP-1.4? It's not yet compatible.
  2. allista
    Probably some bug or mod incompatibility. output_log.txt, some screenshots/video, save file -- all would help in determining the problem.
  3. allista
    You need to use the HangarGateway module like it is done in AsteroidGateway part. This module defines the size limit for a ship, but not the storage; while the asteroid mined through the AsteroidHatch defines the storage. You can make a gateway part and attach it to a hangar extension and it will work the way you want.
  4. allista
    @francescopela, @drhay53 AVP may be the culprit. We had trouble with it and TCA recently: TCA was unable to calculate altitude. So AVP definitely changes something deep. No, there's currently no way to simplify this. But the feature request is noted. It's not an easy one, though: dynamic part resources are a pain.
  5. allista
    Indeed it seems so. I'll check what's going on there, thanks. Unfortunately not. It's a matter of part.stagingIcon value which is set OnStart to "DECOUPLER_HOR". I'll consider this as a feature request, though.
  6. allista
    Unfortunately, I don't think that you're doing something wrong; rather, it's probably a miscalculation of some sort in TCA itself. *to answer the later posts: stage activation in TCA is separated by at least 0.5s For both VAB and SPH you can save in-editor current configuration as default for new vessels -- at the top of the TCA Editor Window there's the "Save As Default" button. The second question is trickier: find the active ModuleTCA of your vessel (resides in one of the command parts) and inside it a VSLCONFIG.EnabledTCAParts node. There are saved all the TCA modules that are installed on that TCA instance. To enable others you need to add corresponding subnodes there. But you have to copy them from some other vessel which has them enabled.
  7. allista
    I've experienced this bug myself, but I could never reproduce it on the same save after reloading. Can you reproduce it? It does not, and right now I've no capacity to learn how to integrate it, sorry. You can try to learn their API and write corresponding MM patches, though.
  8. allista
    Looks like a bug, but I can't pinpoint it looking at the code. Could you share your save so that I could look inside the DIYKit's config?
  9. allista
    @Onigato, @Teslamax, @Basto this is a hard issue, for as you can see, the error occurs inside KSP's main code that fails (for reasons unknown) to recalculate the orbit of the launched vessel. The workaround with landing legs points to problem with colliders and Unity's physics engine that, apparently, generates infinite forces or something. I thank you for the saves you provided, this will allow me to try to invent some fix for GC. Meanwhile, I can only recommend to move the kit a little using HyperEdit or direct save editing.
  10. allista
    For that we need to see the output_log.txt. Share it using gdrive or the likes, please.
  11. allista
    I only know where it's in Monodevelop: at the top left, on the toolbar, there's a drop-down selector that lets you choose the build configuration.
  12. allista
    Correct. In Release configuration all this will be gone.
  13. allista
    Oh boy, how long have I been absent! It pains me to see all the activity around 1.4 and be unable to even read the forums properly. But tomorrow is the deadline of our project at work, and after that I will finally have some time of my own. I miss KSP development and won't abandon my mods no matter what. Thank you all for patience and support!
  14. allista
    Version 2.4.1.2 for Kerbal Space Program 1.3.1 Released on 2017-12-20 Compatibility patch for MM-3.+ Download
  15. allista
    Alas:
  16. allista
    And FSengineBladed inherits FSengine, which is not related to ModuleEngines at all, but uses IThrustProvider which is a stock(?) interface new to me. Though I doubt TCA can use IThrustProvider instead of ModuleEngines, because it has to tap into velocity and atmosphere curves, thrust limiters and so on.
  17. allista
    Thanks, will fix that. FYI, TCA balances RCS the same way it balances engines; this helps a lot when the CoM shifts, or if it's impossible to balance RCS in the first place. But there's no user configuration, so most people don't even know TCA does this
  18. allista
    This may be caused by the new MM that has changed its syntax all of a sudden. This, for example, has broken Configurable Containers. TCA patches are simpler, but if they're not applied for some reason, TCA won't work at all. Another common reason for TCA to not recognize an engine is if it uses a thruster-module that does not inherit from the stock ModuleEngines.
  19. allista
    Thanks everyone for the help here! I have my hands full right now, so I really appreciate it Willrelease a version with this patch tonight.
  20. allista
    That's an interesting idea, but modules are only a part of the configuration; other parts should not, in general, be merged. Take engine profiles for example. Also, if you can upgrade modules by docking, why not OTA? The "story" behind immutable modules is that a module may require not only the software, but also some hardware. And that upgrading the mainframe may brick the thing; and you wouldn't want that in deep space. Or in an LKO, for that matter
  21. allista
    Hm... Modules cannot be changed in flight purely to increase game difficulty; technically this would require some work, yes, but not that much. More importantly, there's a general problem of docking two TCA-capable vessels (KIS or not). Each has its own config, but only one could be used. Current architecture doesn't quite support this use case; so that's what I'll be working on: one should be able to switch between control modules with TCA, and the ships have to remember their configs when undocked.
  22. allista
    @Rivvik, also, when you deem your part config finished, you can share it with me so that I could include it into Hangar as MM patch that is active when KIS is installed. I imagine others may find it useful as well
  23. allista
    That's simple: your active vessel is too far from the kit. By default, KSP unpacks vessels at 200m from active vessel and packs them at 2.3km. So you need to switch to the kit, than back, then try to launch it. EDIT: vessels are also packed for time warp.
  24. allista
    You may also want to decrease the mass/cost of the part and the base CoM offset and jettison force of the fairings.
  25. allista
    That's the problem then. But you can make a smaller new part by simply copying its .cfg and changing the MODEL.scale (and removing the AnisotropicPartResizer MODULE). Oh yes, it is, especially on Linux
×
×
  • Create New...