Okay, this is the state:
Why the Odyssey is on the surface of the Sun? :facepalm:
Is that something with my computer, or what?
---------- Post added at 02:44 PM ---------- Previous post was at 02:24 PM ----------
Problem solved!
Okay, this is the state:
We've completed a very nerve-racking crew and cargo transfer
Well done to the crews of both ships
Next stop, Mercury
---------- Post added at 01:22 PM ---------- Previous post was at 11:50 AM ----------
Discovery is on her way to Mercury
That was a very rough month or so We faced a lot more challenges than the Odyssey crew did, and still everyone did a terrific job:thumbup:
We wish a safe journey to the crew of Discovery!:hello:
Any idea what happened?Problem solved!
No problemI apologize for not being present, matters outside of my control interfered.
You know, the interesting thing is, something like that could very well have happened in real life.After a smooth cargo transfer, the airlock between Chronus and Discovery couldn't be opened. Therfore an emergency EVA was schedulded, to transfer the Crew of the Discovery to their ship. The failure was later discovered as a faulty pressurization valve.
For future reference, everyone please remember to replace the MJD decimal point with a "_" in the file name. Two dots in a file name can cause problems.
---------- Post added at 09:21 PM ---------- Previous post was at 03:08 PM ----------
You know, the interesting thing is, something like that could very well have happened in real life.
So far, we have faced down some of the challenges of conducting a real-life interplanetary mission: the logistics, the timing, the coordination of a lot of people in different places operating on different schedules. Even some of the glitches in Orbiter have some similarity to the mechanical failures that happen in real spacecraft--certainly they can have the same consequences! And most of all, we've had to rely on some deadly serious team-work.
I remember being in the pilot's seat of Chronus's first mission back in March, in the earliest days of the project. Everybody was in chat and ready (we didn't have Twitch yet:lol, so I hit the switches to fire up the APU and started taxiing to the runway. I got maybe ten feet before hearing a loud bang, and the ship was all the sudden spinning like mad through space, with a warning on the screen that my crew had all suffocated. It turned out that I had forgotten to raise the crew elevator before taxiing. I wrote it off as an Orbiter glitch and started the mission over. After all, if that had happened for real, the ship would probably have been severely damaged and the mission scrubbed, but certainly there wouldn't have been any deaths. But by all rights, we could have accepted it, and said that all of the A-Crew except Lydia died in a mysterious explosion. Mysterious explosions happen in space programs--think of Apollo 1, and Challenger! But I felt that after all that build-up and anticipation, I'd be a real to simply say "Sorry, guys, we all died" and end the project there. So I let that one go and restarted, figuring it was Orbiter's problem and not ours.
It haunts me to this day
There are also many problems in real spaceflight that we have not had to deal with. The psychological pressure of spending a few weeks--let alone a year!--crammed with a few other guys in a small metal tube where an uncountable number of things could go wrong, and anyone or everyone could bear some level of blame, could easily drive astronauts bonkers. Even the very successful Mars 500 experiment could not fully simulate the extent of that problem.
And of course, there are the nasty health issues of long periods in zero-g, radiation (especially on Mercury!), micrometeorites, and all the other things that make good Hollywood drama
I'd say that everyone involved in the Iron Hill Project has proven that they have at least some of the Right Stuff (though not all of it by any stretch)
Very true. I would suggest that you and the rest of the Deep 6 project team try to document some of the experiences you have in doing it.
Unfortunately, I couldn't post more this year, but I'm thinking about posting everything that happened during the mission in one single post.I'll look for a way to do that. We did it to a limited extent with Felipi's Iron Hill Project blog at ironhillupdates.blogspot.com. Good stuff:thumbup:
Not really about fix this, but about what to do after fixing: we can use Real Time Update. The advantage is we won't need ScnEditor to update time anymore AND turns the simulation more accurate.
Good idea, but for a more accurate simulation update, you need to change "ACCEL" value to TRUE, it will speed up the time instead of starting directly in the right MJD.