Jump to content

blowfish

Members
 View Profile  See their activity

  • Posts

    4,559

  • Joined

  • Last visited

 Content Type 

Everything posted by blowfish

  1. blowfish
    Even if splitting up every part isn't possible, I'd still recommend trying to segment things as much as possible - for instance, the tanks don't depend on the engine textures, so the tanks can be put in their own folder Since the main use case is people wanting to remove certain parts, I think this makes sense anyway, since it prevents them from accidentally removing a texture that something else depends on.
  2. blowfish
    Indirectly, I think. Rotor thrust is proportional to density, with a reference density of 1.2 kg/m3.
  3. blowfish
    Your best bet is let us inspect your logs - instructions on how to find these logs are in the first link in my signature. Once you find the log file, upload it somewhere (Dropbox or Google Drive work, just remember to share the file), and show us.
  4. blowfish
    I noticed that many of the wheel modules now use an index to link back to the base wheel, e.g. baseModuleIndex = 0, i.e. they look for a ModuleWheelBase at position 0 in the part's modules. In my experience, this is extremely error prone when you involve mods, since modules are added, removed, duplicated, etc very frequently (this comes from actual experience with ModuleSurfaceFX which uses the same paradigm). Engine modules can be found easily and reliably because they have the engineID field which is used as a unique identifier. Would it be at all possible to change the wheel modules to use something like this? I know that it would save myself and many other modders a lot of headache (reposting here from the 1.1 prerelease board at @NathanKell's suggestion)
  5. blowfish
    You know, you could at least try to read the posts above yours
  6. blowfish
    It's a prerelease with a lot of breaking changes. If you're just trying to play, as opposed to find bugs or updating mods, the prerelease probably isn't for you anyway. FAR will be compatible when ferram4 says it is. Not before. And if I had to guess, I'd say that it will be after the real 1.1 release.
  7. blowfish
    The clusters might complicate things, yeah. It definitely relies on order, which is difficult to guarantee, although there's probably some pattern. The basic way it works is this: All the thrust transforms for a particular engine module have the same name. If you had 3, and you wanted 2 to have 25% of the thrust each and the other to have the remaining 50%, you would put a node something like this in the engine module (obviously I don't remember the exact names): NODE { something0 = 0.25 something1 = 0.25 something2 = 0.5 }
  8. blowfish
    Not something I've ever dealt with, but maybe look into how stock texture replacements in MODEL nodes work?
  9. blowfish
    I took a look at this and it looks relatively simple ... basically it loads a node which defines proportional thrust by index for all of the transforms. If you set up the node correctly and then tell the engine module to load it things should work. Let me know if you need any help with this. I don't think anything has broken compared to how it used to work. The main new things to think about are the axis and control input limits, both of which look pretty easy to set up. Again, let me know if you want help figuring out what the parameters are / what they do. Could I suggest leaving the default configuration as it is? Players can change it in-flight if they want, but I think having the defaults makes things easier.
  10. blowfish
    I think a lot of stuff has just moved to a different plugin. For instance, ConfigNode is now in KSPUtil.dll. I don't think much has been made outright inaccessible.
  11. blowfish
    It's mostly the plugins that need updating, but they will be broken. You're welcome to try, but don't bother complaining when it doesn't work.
  12. blowfish
    It won't work, don't try it. There are a lot of plugin changes that need to happen. Most likely, the game won't even load. On that note though, here are my current thoughts on the state of the 1.1 prerelease and B9: I will not release any official version of B9 for the prerelease, even if everything manages to get working before the final 1.1 version is out (doubtful). It's just too much headache to worry about who is on what version as KSP will change between now and the official 1.1 release. However, I will be pushing commits to Github, so if you're savvy you might be able to get something semi-working from there once some dependencies have updates. Since stock now allows different X and Y gimbaling, it's certainly possible to remove KM_Gimbal as a dependency now. This would loose a little bit of functionality (per-engine trim), but that's pretty minor (personally I have never used trim anyway). Not sure about whether FSWheel will work in 1.1, or whether Snjo will even update Firespitter. This might put the legacy landing gear in an odd place, I might investigate whether they can be ported if I have time.
  13. blowfish
    I've experienced issues with duplication as well - specifically with regards to rescaling the duplicated part. My best guess is that both this and the z-fighting have the same cause - somehow, a duplicate mesh is created.
  14. blowfish
    No up-to-date craft files currently, sorry. Just gives you more freedom to design your own
  15. blowfish
    Here's what I'd recommend: Remove any mods in GameData/GameData and delete that folder. Then reinstall those mods. I am 100% sure that none of those mods are actually supposed to be installed that way.
  16. blowfish
    You probably copied the GameData from some mod's download into yours, whereas you're supposed to merge them. Many mods are distributed with a GameData folder in the download so you know what to merge in. As usual, logs will probably reveal the issue immediately. Follow the first link in my signature for instructions on how to find and upload them.
  17. blowfish
    No, all mods should be installed to the root GameData directory. Some things are not path-dependent so they still work but many things are not. As it is you're actually missing a bunch of core B9 parts and you probably have a bunch of MM patches applying incorrectly.
  18. blowfish
    Umm ... you have another GameData folder inside your GameData folder. This isn't the way to install mods
  19. blowfish
    Please follow the first link in my signature for instructions on how to find and upload your output logs. If I can inspect these logs I can probably identify the problem immediately.
  20. blowfish
    You could try a binary search through your mods - remove half, see if it fixes it, if not try the other half, keep narrowing down by half until you figure out which one is doing it. These performance issues are not easy to isolate.
  21. blowfish
    I doubt Stock Revamp is the cause. Most likely something with a plugin, that affects many if not all parts, and is computation heavy.
  22. blowfish
    If you're on Windows, it's KSP_Data/output_log.txt. KSP writes to it continuously.
  23. blowfish
    I thought so at first, but maybe not? Could you open your log and give the full stack trace of the exception?
  24. blowfish
    https://github.com/shadowmage45/SSTULabs/issues/275
  25. blowfish
    You're asking in the wrong place, and with the wrong tone. The CKAN team isn't responsible for maintaining mods in a distributable form. If the original author hasn't updated it and no one has taken up maintaining it, you're out of luck.
×
×
  • Create New...