Jump to content

Rory Yammomoto

Members
  • Posts

    496
  • Joined

  • Last visited

Everything posted by Rory Yammomoto

  1. OK, it's not 1994 (it took me about 6 days) but I finally got Spacelab 3 to full operational capacity. I don't know what I'm going to do with it, but I thought of using the primary docking port to house a thruster unit and sending it off on a mission to Duna or Eve.
  2. Lenovo-IBM X201, with an i5-520M and an Ironlake Graphics card. I actually get about 30-40 F.P.S looking at the sky, depending what other planets are in the view. (I still get 5 when looking at the planet) This is why I'm using BDB as opposed to FASA, and HabTech instead of CXAerospace (except for the Docking ports) - they don't run like crap, and they look actually good, even if model- and texture-wise, they are very modest. Consider this: I was originally going to expand Spacelab 3 with CXA parts. but two modules in, and the frame-rate was unbearable, even for me. I had to switch to HabTech just to make a large, multi-module station.
  3. oh, so long as I don't look at the ocean, I'm fine. The ocean is really poorly coded - I heard it is an entirely different planet, which would explain my terrible frame-rates.
  4. The new Solar Cells just came in. Which is good, considering that Spacelab 3's main solar panels have been blocked by the truss segments. I'll have to send a pruning mission - too many RCS nozzles means I'm getting about 14 out of 21 frames per second. (I always get a constant FPS of 21 when looking up and 10 when looking at a planet. 5 if I'm looking at a planet with an ocean.) PS: can anyone put a KIS container in the AARDVark... container?
  5. If I had the skill... I would do a lot more than just make RPM configs. But I don't, so I'm mostly restricted to s h i t posting on this thread. Coming to my save in the far-off year of 1994... someday, there will come a time when Spacelab III will be as advanced as this. Until then, we have hope that it will survive that long.
  6. has anyone made RPM configs yet? Yes, for the Apollo internal. But what about the Leo, Botticelli, and other pods?
  7. Oh right, that other TL that E of pi did. should probably put the lower one upside down, to make the interstage fall off at both ends.
  8. they must have. That probably also explains the failure to dock between APAS and CADS - The Gendered-on-non-gendered conflict. My question is why you made it gendered in the first place - the CBM ports being mechanically different I understand, but the APAS system was specifically designed to be non-gendered - the name "Androgynous Peripheral Attachment System" derives from this.
  9. There seems to be a part of the patch that codes for a Block IV... My bad, only codes for the Mission Module, not the CSM and capsule as I thought. Misread the config. But I think the S1F DDS file got mis-uploaded to github, such that it is only 1 byte long. EDIT: The problem was the S1F DDS file being only 1 byte long. replacing the file with one from the drop-box paints the Saturn 1 parts white and creates the Blok IV MM.
  10. @Drakenex, There is a problem with the SaturnMB patch. It makes all the parts... Except the titular Multibody Tank, the Blok IV CSM, and the Blok IV capsule. I'm combing the config to see what could go wrong, but there seems to be no difference between the entries that go wrong and the entries that go right. There is another thing - the Sarnus S1 Tank is longer than the S1E when I don't remember it doing so before, and none of the parts that make up the Sarnus 1 have any textures. Perhaps this is connected, or perhaps it is due to the fact that the DDS file for the S1F is 1 Byte. Yes, you heard me right. 1 byte.
  11. Suddenly the Dnoces S and Regor A are gone after git pulling. what did I do? EDIT: they no longer exist, as of today.
×
×
  • Create New...