Jump to content

blowfish

Members
 View Profile  See their activity

  • Posts

    4,559

  • Joined

  • Last visited

 Content Type 

Everything posted by blowfish

  1. blowfish
    You should probably check before saying things like this, because that is definitely not true. I think my assumption when setting that system up was that I’d be releasing more frequently, but given the slowish pace of releases it does seem unlikely that someone would be on a previous version of KSP and not have the latest B9PartSwitch for that KSP version. Honestly the way AVC works right now seems wrong to me. It should be able to check against more than just the “latest” version. But maybe using the wrong tool in the wrong way isn’t right either. I’ll think about my options here, using AVC the way everyone else does is one, but I might also consider submitting changes to AVC to add what I feel like is the missing functionality
  2. blowfish
    @linuxgurugamer each KSP version has a different file. So that’s presumably the one pointed to from v2.3.2? The idea is that it’ll tell you about updates that affect your KSP version. Unfortunately it doesn’t handle the case that you upgrade KSP while leaving the mod on the old version (it will still look for updates on the old KSP version). I’ve thought about ways to deal with this but haven’t come up with anything yet.
  3. blowfish
    I don't think the way the CKAN metadata is currently set up supports the LFO patch
  4. blowfish
    The metadata is only marked as compatible with 1.4.5. I don't think anything would break in 1.4.3, but I'm surprised that's happening. Maybe CKAN doesn't know about 1.4.5 yet?
  5. blowfish
    Simple Adjustable Fairings Plugin v1.2.0 for KSP 1.4.5 Recompile for KSP 1.4.5 Add Deploy action for action groups
  6. blowfish
    B9PartSwitch v2.3.3 for KSP 1.4.5 Recompile against KSP 1.4.5
  7. blowfish
    Yes, you need an account. If you're using a lot of mods I recommend creating one as many mods track issues through Github
  8. blowfish
    I recall that they might require inner nodes. Can you log an issue on Github so I remember to investigate?
  9. blowfish
    @Apaseall there is no MODULE involved, so there should not be anything called that in your patch. If you want to edit the model node, it's @MODEL { }
  10. blowfish
    @Gordon Dry not sure about the Infinity issue, can you by chance edit it to output all the intermediate values as well? That would help in figuring out where something is going wrong. You can truncate with regex replacement. I think you want something like @value ^= :(\.\d\d)\d+$:$1: How does this work? You're matching a period followed by two decimals, followed by one or more decimals, followed by the end of the string, and replacing it with the part you're capturing (the period and two decimals) Disclaimer: I haven't tried this
  11. blowfish
    @Gordon Dry that seems right to me, and bd_GeigerCounter should work too. I don't see anything wrong there, I'd look for other reasons why it might not be applying.
  12. blowfish
    @JoE Smash here are some useful practices I've found for avoiding these scenarios: Don't mod your Steam install. Steam auto-updates can leave you with incompatible mods and a broken install. Even if you disable automatic updates it's too easy to forget something end end up with a broken mod. Copy KSP outside of your Steam folder and mod it there. KSP will work fine. Start with a fresh install for each KSP version. This is a pain, yes, but you can ensure that all your mods are working before trying to port over a save. And if something proves to be broken you still have the old version to work with until it gets fixed. Back up your saves. If one gets corrupted just restore from the backups.
  13. blowfish
    Which version is it trying to install? I inspected the metadata, and v2.3.1 is marked as compatible with only KSP 1.4.3 and v2.3.2 is marked as only compatible with KSP 1.4.4. So unless you've marked KSP 1.4.4 as being compatible in CKAN's settings, it should be installing v2.3.1. That being said, there weren't really any breaking changes between 1.4.3 and 1.4.4 as far as this mod is concerned. I recompile on every KSP version just to be sure but I would be surprised if something broke.
  14. blowfish
    There is no -force-gl11 options. There's -force-d3d11 and -force-glcore But that doesn't sound like it's related to the issue you're having. No way to tell what the issue is without logs though. If you don't know what those are or how to get them, please read the "HOW TO GET SUPPORT" link in my signature.
  15. blowfish
    There's some efficiency that can be applied for variants of the same engine family - large parts of the model and texture can be reused which reduces the work required to add them by a lot. So maybe that's not the best example...
  16. blowfish
    TU provides an API for other mods to use, it doesn't do anything to any parts by default.
  17. blowfish
    I modified the deployment force such that it always seemed to deploy cleanly for me, even under acceleration ... have you run into scenarios where you still run into the fairings?
  18. blowfish
    I could add another action group for deploying the fairing pretty easily. Do you prefer not to use altitude-based autodeployment?
  19. blowfish
    @Gordon Dry you can't use indices in a HAS clause. I'm confused about your use case though ... :HAS[@PROPELLANT[ElectricCharge]] will be true for anything that has any PROPELLANT node with name = ElectricCharge, it does not have to be the first one. So why does the position matter at all? And why would you want to rely on things being in a particular order?
  20. blowfish
    There's not currently a way to do this. I have contemplated being able to add tech restrictions to subtypes in the past, but I generally don't build things until there is a solid request for it. And this could be that. Add an issue on Github and I'll look into what it would take. Although just for the sake of really figuring out the use case, what would be the gameplay consequence if players could select LH2 before that tech was unlocked. Would they be able to do something with it other than having it sit unused in a tank? Presumably engines that use LH2 would also require that tech or a following node.
  21. blowfish
    There is no HX crew module As far as patches for things like USI go, I will gladly accept pull requests and other submissions but will not be doing them myself.
  22. blowfish
    Sorry, exactly which piece isn't having the intended result. Also unused B9_TANK_TYPE entries won't really affect anything.
  23. blowfish
    Simple Adjustable Fairings Plugin v1.1.1 for KSP 1.4.4 Recompile against KSP 1.4.4 No changes are required to the KW Fairing pack at this time. It's already marked as compatible with any KSP 1.4.x version for AVC/CKAN
  24. blowfish
    You can’t. Physics.cfg has special handling to allow this. Modifying settings in a patch would be problematic anyway since it’s contents can be modified by the game. Is there a specific reason it needs to be applied right before FAR and not earlier?
  25. blowfish
    B9 Aerospace v6.5.1 for KSP 1.4.2+ Release for KSP 1.4.2+ Fix RCS effects being backward and too big Update CryoTanks patch to be consistent with current CryoTanks I've loosened the .version restrictions a bit so AVC/CKAN will accept this on any KSP version between 1.4.2 and 1.4.99 Note, bundled dependencies are for KSP 1.4.4
×
×
  • Create New...