- Joined
- Mar 30, 2008
- Messages
- 178
- Reaction score
- 2
- Points
- 18
Hi Kuddel, no problem, you are welcome !!!
To all Orbinaut's now ! As we say in French "Always put back your work on the loom !!!" I announce now, that I am working already on a patch P2. The main reason is that I found a new bad problem (appeared probably since Orbiter 2010), in the particular Apollo 13 configuration. It is bad because it block the user and he cannot finish the adventure.
Seeking around this case, I discovered also that some "dirty trick code" I had to implement for Orbiter 2006, in order to overturn some bad CTD's where not anymore necessary. Obviously, Martin passed there !!! That's good !!! So, now, I decided to further check all that kind of stuff's and cleanup the code, when it is possible.
I had also the idea to add to the mini-panel the indication "FLIGHT ABORTED" when you enter in such a situation.
I am thinking also to forbid the LM extraction, if you have this "FLIGHT ABORTED" status. This is possible to do with the new abort mode introduced in 1.20 "premature 2nd stage separation". I mean, there is no reasons to be able build "the train for the Moon", if you aborted the flight during 2nd stage burn ? What do-you think ?
I would also love if some of you, would be interested to receive a beta version of this future patch and to make some tests of it. Better that not only me test if everything is still working well, after I have done this general code cleanup. Just tell me to my private Email (see at the end of AMSO-User-manual.doc) you want to participate and I will send you a private link to the beta-patch so you can test.
Thanks in forward !
ACS
To all Orbinaut's now ! As we say in French "Always put back your work on the loom !!!" I announce now, that I am working already on a patch P2. The main reason is that I found a new bad problem (appeared probably since Orbiter 2010), in the particular Apollo 13 configuration. It is bad because it block the user and he cannot finish the adventure.
Seeking around this case, I discovered also that some "dirty trick code" I had to implement for Orbiter 2006, in order to overturn some bad CTD's where not anymore necessary. Obviously, Martin passed there !!! That's good !!! So, now, I decided to further check all that kind of stuff's and cleanup the code, when it is possible.
I had also the idea to add to the mini-panel the indication "FLIGHT ABORTED" when you enter in such a situation.
I am thinking also to forbid the LM extraction, if you have this "FLIGHT ABORTED" status. This is possible to do with the new abort mode introduced in 1.20 "premature 2nd stage separation". I mean, there is no reasons to be able build "the train for the Moon", if you aborted the flight during 2nd stage burn ? What do-you think ?
I would also love if some of you, would be interested to receive a beta version of this future patch and to make some tests of it. Better that not only me test if everything is still working well, after I have done this general code cleanup. Just tell me to my private Email (see at the end of AMSO-User-manual.doc) you want to participate and I will send you a private link to the beta-patch so you can test.
Thanks in forward !
ACS