Jump to content

blowfish

Members
 View Profile  See their activity

  • Posts

    4,559

  • Joined

  • Last visited

 Content Type 

Everything posted by blowfish

  1. blowfish
    I've seen this before and it's definitely caused by a mod, but I haven't been able to figure out which one yet. It's probably just some debug output that the author wanted but forgot to remove. If you do figure it out though, it's probably worth letting the author know.
  2. blowfish
    Have you installed the community fixes? If not, try installing them. If that doesn't fix the problem, try re-installing both KW rocketry and the community fixes from scratch. If that doesn't fix it, post your output logs for us to inspect - instructions on how are in the first link in my signature.
  3. blowfish
    Try removing and re-installing SSTU. If that doesn't work, post your logs for us to inspect - instructions on how to do that are in the first link in my signature.
  4. blowfish
    I'll investigate when I get a chance. In the mean time, could you make sure you can replicate the problem when building a craft from scratch, and then post the craft file?
  5. blowfish
    Please don't necro old threads without good reason. This thread is more than a year old.
  6. blowfish
    I'm curious ... what are the main engines depicted there? They don't look like RS-68s or RS-25s.
  7. blowfish
    Find me some hard data to "do something" with and I'll consider it . Otherwise I'm just replacing made-up numbers with other made-up numbers.
  8. blowfish
    That sounds like a bug, and I think I know the cause and fix. Submit a ticket on Github and I'll try to fix it when I've got time.
  9. blowfish
    I guess it's more difficult with Steam but generally you shouldn't be modding your steam install - best to copy it somewhere else and then mod there. In your case though, you should probably be ok to just delete everything in GameData EXCEPT the Squad folder (this contains all the stock stuff and should never be deleted).
  10. blowfish
    Actually now that I look I can't find it on CKAN repository ... @The Destroyer are you certain you got it from CKAN? I'm generally supportive of finished mods getting on CKAN, but WIP stuff tends to be a headache. Past experience has suggested that it's very hard to get something off CKAN once it's on ... you might want to add an exception to the license if you want to prevent this from happening (basically the policy has been "if the license allows us to distribute, we're not taking it down" ... ask ferram4 if you want gritty details). Maybe something like "you must get permission from the author to distribute" or "you must get permission to distribute provided the author can be contacted in a timely manner" (no one plans to go AWOL but it does happen occasionally ).
  11. blowfish
    Yeah, given that this is a pre-release mod that could still encounter breaking changes, it worries me that this is on CKAN.
  12. blowfish
    I meant re-install KSP and start re-installing mods from scratch.
  13. blowfish
    Well, now that it's closer to 1.1, it's looking like the models won't actually need any changes, but I'll definitely keep it in mind that you have those Hard to tell for sure until we actually get to that point.
  14. blowfish
    The R-7 core is actually smaller at the bottom than at the top - you can see this in pictures if you look closely - and there is an adapter specifically designed for that launch vehicle. As for the textures, what ComatoseJedi said.
  15. blowfish
    I'd recommend starting with a clean install and adding mods one by one. If something breaks and you can't figure it out, just post logs again - it's a lot easier than trying to guess at the problem.
  16. blowfish
    Yes, that's how B9, and most mods for that matter, are installed. Possibly, though I don't know what that problem was or what the structure of BD Armory's download is.
  17. blowfish
    You have installed B9 incorrectly. You put the B9_Aerospace_6-0-1 folder in your GameData folder, whereas you should have put the contents of the B9 package's GameData folder into your existing GameData folder (B9_Aerospace, B9PartSwitch, etc, etc). The same goes for legacy and HX. E: Looks like you've made this mistake for a few other mods as well (KW for instance). Might want to check that you've installed all of these correctly.
  18. blowfish
    Google docs is fine. Just make sure to actually share the document so that it's not private
  19. blowfish
    That was my intention - the logs can be a little difficult to read without experience. Upload the file somewhere, share it, and post the link so I can take a look.
  20. blowfish
    @V8jester I do see how that I could be a problem. However, I'm not sure how I could serve that use case without breaking a bunch of others. In 1.0.5, the old medium jet pod became more or less completely redundant with the stock Wheezley, hence why I up-scaled it (and increased the thrust). What I could do for you is create a set of custom configs that recreates the parts as they were. But I'm away from home this week so I probably couldn't do it until next Sunday.
  21. blowfish
    Uhh you shouldn't have B9PartSwitch on 5.4.0 - it was added in 6.0. Try uninstalling B9 and all of its dependencies and re-installing them. If that doesn't work then let me see your logs - instructions on how to find them are in the first link in my signature.
  22. blowfish
    If you're on Windows, it will be in KSP_Data (which is inside your root KSP folder). The filename is output_log.txt Oh, and the self-deprecation is completely unnecessary. Just follow the debugging instructions to the best of your abilities and ask for help when you need it.
  23. blowfish
    That's fine, but does it make sense now? The post I linked guides you through how to find the logs, and about 90% of the time the problem can be identified immediately just by looking at them.
  24. blowfish
    As explained in this post (which I already linked in my first reply to you), please find your output_log.txt (or player.log on Linux/OSX) and upload it to somewhere like Dropbox or Google Drive, share it, and post the link so that I can see it.
  25. blowfish
    Well something is probably installed incorrectly, but I don't know what based on what you've told me, so that leaves step 3: provide logs.
×
×
  • Create New...