Jump to content

blowfish

Members
  • Posts

    4,559
  • Joined

  • Last visited

Everything posted by blowfish

  1. Ah - very good to know. In that case, I'd say yes, your fix should do the trick nicely.
  2. ATM is sort of in an odd place now as most textures are compressed to begin with. Always good to make an actual comparison to see if it's doing what it's supposed to.
  3. I was mostly waiting for someone to request it. It doesn't really have to be bac9 - they have to be separate mods but bac9 gave me access to the main Kerbalstuff page too. I'll work on getting that set up this weekend.
  4. Correct. But AFAIK (and someone should correct me on this if i'm wrong), it will no longer work in KSP 1.1 as Unity 5 only allows convex mesh colliders.
  5. There's probably an exception in the output log somewhere. If you can provide it, we can analyze. If you don't know how, follow the first link in my signature.
  6. Try deleting the Firespitter folder in GameData and reinstall from the 5.4.0 download. That usually clears things up And welcome to the forums You're limited to trapezoidal shapes, but fixed shape wings usually have the same limitation. You can join as many wing segments together as you like though (might need struts).
  7. That means that if you are using FAR you must use that version (or later). That probably needs to be clarified...
  8. The B9 procedurals have never required FAR. Where did you read this?
  9. @VenomousRequiem I'm willing to investigate this. I doubt it's KJR, a lot of people use that (including me) with no issues. Could you try to reproduce the issue with the smallest ship possible, then give me your output log? It sounds like something might be triggering an exception that is preventing certain things from working.
  10. Could you be more specific? Bugs can't be fixed if they're never reported.
  11. The B9 airbrake used the same module, so yes, that's not surprising. I say used, past tense, because I attempted to get the B9 airbrakes on the same system as the stock airbrakes, but they had integration issues, by which I mean half of them would refuse to trigger for no apparent reason.
  12. @kcs123 The airbrakes aren't included in legacy. If I ever figure out how to fix them they will be added back into the main pack.
  13. They are more powerful, but the way they function is identical to the stock RAPIER.
  14. Nice. But I thought that was tried before end ended up causing a significant performance hit...
  15. AJE 2.5.4 is now available on Github Changes: 2.5.3 Update Baha inlets with new cockpit Update for SolverEngines engine fitting changes Updates for Ven's Stock Revamp Updates for B9 5.4.0 Update SolverEngines to 1.14 2.5.4 Fix issue where ramjet would have no model
  16. I think that Readable: False just means that it's loaded directly into VRAM and not accessible by KSP plugins. It shouldn't affect this. But try removing ATM anyway, it could still be causing the issue.
  17. You can scale it, just replace @scale with %scale in your original code. @ means edit if it already exists, % means create or edit.
  18. One of two things could be wrong: (1) Most likely the original MODEL node doesn't include a scale value, in which case @scale will do nothing. You want %scale (2) The part uses mesh=whatever.mu rather than a MODEL {} node.
  19. The old ones still work and are the release version for now. But yeah, it looks like you installed the Firespitter plugin incorrectly or not at all.
  20. Two words: Infernal Robotics And welcome to the forums
  21. Parts of the configs rely on things being in specific locations in GameData. This includes the texture sets. Of course, this means we could still do it ourselves, but it would be a lot of work on each release that would probably negate the benefits of that setup in the first place.
  22. Minor request: Would it be possible to put the texture packs in a separate folder in GameData (e.g. SSTU-TexturePacks)? It would make installing updates a lot easier.
  23. Okay ... I didn't know they were included in the releases. My mistake. The next step would be to post your output log and see if it has any clues as to what's going on.
  24. Yes. I agreed with bac9 that now that B9 pwings are available, (1) The fixed wings are going to be unnecessary for many people (taking up loading time, RAM, and space in the editor), and (2) They are no longer going to be developed anymore. If they are too inaccessible as it is, I can add the legacy and HX packs to Kerbalstuff and CKAN without too much trouble, but I was really waiting to see if there was any demand for it first.
×
×
  • Create New...