Jump to content

Zorg

Members
  • Posts

    2,145
  • Joined

  • Last visited

Everything posted by Zorg

  1. Atlas works quite well with PVG guidance in my experience. In fact I believe the original implementation of PVG in mechjeb was based on Atlas Centaur algorithms.
  2. I think that biconic fairing had a standard length. looks similar to the one used for many classified missions including the 33B/34B missions. It always looks the same length to me unlike the Titan III standard fairing which was height adjustable. Not that I've done pixel measurements or anything. https://www.ulalaunch.com/docs/default-source/rockets/delta-iv-user's-guide.pdf https://www.sciencedirect.com/science/article/abs/pii/S0094576505001050
  3. I think the strongest probable connection between Hubble and KH11 is that the NRO donated two surplus 2.4m mirror assemblies to NASA; exact same size as Hubble although of course the NRO wont say which program its from. One of them is of course being adapted on the Nancy Grace Roman telescope. However this does not imply the optical tube assembly and the bus are the exact same shape as Hubble though. Personally I think the most likely explanation is that for the Titan III launches it was similar to the Kh9 like Pappystein suggested. Supposed KH-11 launch from https://space.skyrocket.de/doc_lau_det/titan-3d.htm
  4. Completed science for Voyager Mars orbiter. Baseline '73 mission used only the planetary scan platform from the lower right with vidicon cameras & various other instruments. Future missions would upgrade PSP with lunar orbiter derived film camera & scanner + extra instruments The upgraded science package includes some OGO derived booms as well. You can see the breakdown of the instrumentation on both versions of the PSP too. We will not be able to match them 1:1 in KSP of course but it will have several BDB experiment definitions We also have an all new Star 24 which will be used as the deorbit motor for the lander. It seems to be in the right size ball park and is contemporaneous having been flight qualified IRL in 1973.
  5. Im hopeful most of our models will be good (maybe re UV and a little bit of work here and there). Since KSP2 is clearly using PBR textures fully (physically based rendering) almost none of the textures will make it through. While you can in theory mess with current textures made for legacy shaders and get it to at least function, they wouldnt look great. KSP2 means a full PBR re-texture of all BDB assets. Here is a little practice I did for example on the NERVA FF in Substance Painter (a PBR texturing software) Current Remade (some of the height map used to create the normal/bump details survived but everything else was redone from scratch)
  6. It’s sized specifically for this and it’s 3.6m i guess I could do a variant at3.75m if people are interested
  7. Between the orbiter and the lander the texturing is not even a quarter done. Plus getting things functional, playtesting (I definitely want it to spend some time in dev) balancing etc. there’s no reason to delay the next release.
  8. Not so much available for sale as an option for a future upgrade based on the customers willingness to pay, development time (maybe 4-5 years) and whatever financial agreements could be worked out between ULA and the customer. Presumably it would only be worth it for some block buy but i dunno. Its mentioned briefly in the payload planners guide which isnt too hard to find online.
  9. The baseline design for the TRW orbiter does not have a magnetometer... But the growth option does (they are OGO derived booms)
  10. No the backshell will be retained by the orbiter. Most of the documents for Voyager Mars (and there are various designs) do indicate a separate sterilisation lid but I am making the lid and heat-shield 1 part for simplicity.
  11. Getting close to finishing modelling this. Keen to get this unwrapped and start actually texturing. (all procedural placeholders for now)
  12. As mentioned by Rodger you need to enable the depth buffer mode in scaterrer for now. We will look deeper into the cause but for now this should fix it
  13. Gonna need to see a full modlist and logs, also whether its the current BDB release or the dev branch.
  14. Perhaps whats being referred to here by "transparency" is that the boost protective cover has no collider over most it (just the tower only). Allows users to click through the BPC onto the capsule. There is no actual transparency on mousover functionality on the Apollo LES.
  15. Nothing new from me today, just taking a look at the extension Cobalt added to the S4B interstage. Allows for a clean NERVA XE on S4B build.
  16. Easiest way is to install Distant Object Enhancement. That will reduce the brightness when you look at a planet close by if Dynamic Sky Brightness is turned on (should be by default). However to turn it off completely you can go to the Distant Object Enhancement settings and turn the maximum sky brightness setting under dynamic brightness all the way down. Now your skybox will always be black regardless of what you're looking at.
  17. Chaotic as our development may seem sometimes we do have a plan. You can keep track of current dev things loosely here. https://github.com/CobaltWolf/Bluedog-Design-Bureau/issues Most of the main part lists have been ticked off but we're not too far off from the next release as we're wrapping up various miscellaneous items. That said how long it takes can still vary based on devs free time.
×
×
  • Create New...