Damien_The_Unbeliever

Members
  • Content count

    176
  • Joined

  • Last visited

Community Reputation

102 Excellent

About Damien_The_Unbeliever

  • Rank
    Spacecraft Engineer
  1. Now updated for 1.3
  2. I'd be more interested in a Night-time Eclipse. I mean, what would that even mean?
  3. But as I've tried to point out before, because a **lot** of people don't seem to realise this, is that the more options you add to the system, the more you add to the testing work. Software isn't perfect and every *combination* could potentially throw up new and unexpected scenarios. So, you create a game that, say, takes 45 hours to test. You add a single option to vary the game and, in all thoroughness, you ought to now spend 90 hours to test. Of course, in reality you cut corners and say "of course" some features don't interact and so you only need to check on one of the settings. And then you end up generating all female scientists as your rescuees, or similar. --- Or, to put it another way - a lot of people seem to believe that adding options/checkboxes to software is "free" when in fact it's the opposite - it either adds to the testing costs or it produces more unique combinations that aren't tested.
  4. Isn't any reply to this, in some coded form "I don't like this feature and anyone who uses it is obviously wrong"? I don't think anything should be removed because I'm sure there are plenty of people who enjoy this game in different ways to how I do.
  5. I'd just like to resurrect my original comments from post 4 on this topic:
  6. Helium tank failure appears to be in second stage. None of these have been recovered or planned for reuse.
  7. 0.2.0 should have worked for 1.1.3, if you can still find it (i'm not sure how easy it is to find previous versions on spacedock, but it was there)
  8. Now updated for 1.2.
  9. So, you're already in a situation where you know that engines aren't restarting as you expected them to do. And your solution is to start more engines. Added to which, these are often fuel-starved situations. To be able to start more engines, I believe you'd have to have primed the turbopumps on all of them, despite the fact that you don't expect to use them ~95% of the time.
  10. So, assume one of the engines is contributing 0% of the thrust it's meant to, and it's not the centre engine. If you boost the other two engines to compensate, you have quite a lot of asymmetry to deal with. During normal (ascent) usage, you don't have to deal with this because it's always assumed that (given we're not talking about the centre engine, again) there's another engine opposite each engine and so we don't have to deal with any torque issues. Do you design your entire set of engines to have far more gimbal to cope with that situation, or accept the loss?
  11. Unlike KSP, where you can sum someone up as either an Engineer, Scientist or Pilot, and they're all of equal ability (given equal experience), unfortunately, the real world doesn't work like that. The "Developer" class is a very broad one, and the skills that can come be brought into a situation very much depend on the individual. Added to which, throwing more developers at a problem doesn't necessarily speed up bug fixing - you're adding more lines of communication that have to be maintained to ensure everyone is working on *different* issues rather than duplicating effort
  12. You should be very careful with the assumptions you make, when it comes to software. For example, there should be no reason why the Asteroid Day mod should cause all rescued astronauts to be females (or was it scientists? Or both?) And yet that's what happened. This is the magic of software at work - seemingly unrelated systems can interact in surprising ways. (And also why I get annoyed when people suggest that an easy thing to do is to add an extra setting/option for X or Y - without realizing that every additional setting added to the game potentially doubles the amount of testing that should be performed)
  13. Done. As I said, I've just been remiss in putting information out there.
  14. Launch Numbering is a very simple mod - with one job to do. Every time you launch a vehicle, the mod examines the name. If it's seen that name launch before, it appends a number on the end. So, if you launch the same vehicle 4 times, they should all be uniquely named. Downloadable from Spacedock Source on github MIT Licensed In game settings, you'll find options on whether we use Arabic or Roman numerals, and whether we show Bloc numbers (wherein we try to identify "variants" of the vessel, in terms of its structure, and show it as a different Bloc). Now that this is doing what I wanted, I'm open to suggestions for anything that others would like to be able to configure with it.
  15. Also, there's a general pattern to be observed here. We use it all the time. It's why we use caches within our computers. Recent history is generally a good predictor for near-term future. What people sometimes forget is that, at some point, this fails. Whether that's a cache miss or a shift in market forces, at *some* point, recent history will always fail to be a good predictor for the future. It's just bloomin' difficult to predict this before it happens