Custom checklists?

[AphelionHellion]

I was wondering if anyone here has customized the DGIII checklist file in order to show procedures for, say, aerobraking or
add-on MFDs such as TransX or iMFD?
If not, that's probably something I should do, then  
It'd be one of the very few things I could actually contribute to Orbiter, not being a programmer or modeler or anything

[MattNW]

I've made a couple changes but not any of those. Mostly what I've done is change some of the procedures for
shutdown and Safe Mode due to some accidents either I or the kids have had. Things like the breakers on the engine
panel are to be shut down immediately after docking to avoid accidently hitting an RCS control and a rule that at least
one airlock door must be closed whenever the ship is docked (the reason for this should be obvious ).

[AphelionHellion]

Ah, so I'm not the only one who wishes he'd been wearing a space-suit after undocking, sometimes?  

I was thinking of something new/different enough to justify posting it and having people download it. I'd hafta make it
worthwhile, of course


____

[DanSteph]

AAAAHHHH cool ! someone that took advantage of the edit check-list possibilities.
If you find yours is better than the base one (not hard I didn't reworked them too much)
please send me your file I'll incorporate it in the next release so everyone can have better
checks.

Credit due of course.

Dan



Post Edited ( 05-23-04 13:18 )

[freespace2dotcom]

*rips his hair out due to lack of thoughtfulness on his part*

[AphelionHellion]

*salutes*
I'll get right on it, sir!  

*begins test pilotage*


__________

[AphelionHellion]

Hmm this is old school. No word wrap!  
Are there any other handy formatting commands I should know about besides
@blue:
@white:
@red:
and @title: ?

I tried gray and yellow and no luck
Hehe
In the meantime, here's what I've got down before I go to bed:



@title: TransX Interface
------------------------------------------------------
@red:TransX MFD Keys (and colors)

--Shift-J starts TransX
@blue:(There are twelve buttons, and
@blue:each has a keyboard equivalent.
 
@white:--(Shift-F) Select between the
@white: three TransX function modes.
@blue:(they are: Eject, Cruise, and
@blue: Orbit Eject. Changing functions
@blue: effectively resets the MFD, so
@blue: TransX will sometimes ask
@blue: you to confirm a change)


@white:--VAR (Shift-V) Next Variable
@white:--VR  (Shift-B) Prev. Var.
@blue: (Each TransX function has
@blue: its own set of Variables -
@blue: up to 11 in one function!

@white:--VW  (Shift-W)Select View
@white:--MAJ (Shift-R)Set Major body
@white:--MIN (Shift-M)Set Minor body
@white:--TGT (Shift-T)Select Target
@white:--NT  (Shift-N) No Target
@white:--ADJ (Shift-J) Set Adjust-
@white: ment method
@white:-- ++ (Shift - +) Increment
@white: variable/adjust value
@white:-- -- (Shift - _) Decrement
@white: variable/adjust value
@white:--RST (Shift-X) Reset all


@red: Visual Key

*A thick green line: The path
 of your craft. This is the path
 TransX projects for your ship if
 you do nothing.
*A thin green line: The path
 of some other body - probably a
 planet.
*A yellow orbit: A hypothetical
 orbit.This is an orbit that you
 have specified using variables,
 and may perhaps choose to man-
 euver your craft into.
*A yellow line: A place where you
 either plan to carry out a
 manoevre, or the places where
 you and your current target are
 closest together.
*A grey line: The place where 2
 orbital planes cross one another.
 This intersection is often a
 useful place to carry out
 certain maneuvers.
*A grey circle: The surface of
 a planet. Don't run into it!




This is the first part of the transX series I want to do. Note the shameless theft of material from
www.orbitermars.co.uk  
Anyway, to use it, copy and paste this into Orbiter\sound\deltagliderIII\check_list.txt and enjoy!
Granted, everyone here is probably already an expert at using TransX, but sooner or later I'll come up with something
really
useful, I hope. One thing I DO do particularly well is staying up late at night writing odd things

[AphelionHellion]

Agh! My little list is infested with frownies!!

Well, you folks can figure it out, I'm sure.

[freespace2dotcom]

(Not to be outdone, freespace devises a clever yet truely serious strategy.)

Say Dan, Is there any documentation on making simple little DG3 flight computer programs? I've got a few ideas that I
would love to try out pending it isn't as scary as coding in C+.


Freespace, who DOESN'T use TransX 'cuz it's pure *EVIL* with difficulty.



Post Edited ( 05-23-04 14:13 )

[AphelionHellion]

Hehehe Freespace  
I've been curious about that as well... For instance I'd love a program that can orient you 90 degrees nose-up or down
relative to the path of your orbit (not the plane of the orbit, ie normal and antinormal). I've found burning "up and down"
this way to be an easy way to eyeball orbits that intersect with moons or space stations without using a transfer MFD and a
bunch of hard numbers...
 


One thing to check out until Dan gets back to ya: Go to the \sound\deltagliderIII\PROG directory.
If your installation is like mine, there should be a text file called PRO903SPEC.
You know what to do

[freespace2dotcom]

Well, I was thinking of a program like that, but instead of just 90 degrees, you could choose any variation. it would be
very handy for those who prefer the manual ascents seeing as the nose of the dg3 rises up over time due to one's
extreme speed over the earth. (hard to cancel out perfectly, and the effect increases the faster you go.) level horizon
is only good when you're almost done with your ascent, you know?

[DanSteph]

AphelionHellion wrote:
Are there any other handy formatting commands I should know about besides
@blue:
@white:
@red:
and @title: ?

You got them all, nice idea to include the transx help, if someone find his check is almost complete
(NOT to complicated it should be straight to follow, but you can add subject like the transx one)
Send it to me I'll make it available as a third party download.

About programs: you can only edit the ascent autopilot and the check-lists to make your custom
ascent autopilot matching one of your ascent, just start the ascent and record on a paper your pitch
and alt when it change (start high pitch at 1500 meter).

copy and edit the sound/deltagliderIII/pro/Pro903spec.txt and give it another number (ex: 602, 904 etc ?)
and change the number in it, cut or add lines...

The new pilot should replay your ascent (difference: it will try to null the ecc when it goes below
a certain value)

Dan

[AphelionHellion]

Dan, are there any other commands for the autopilot? I don't get it...
The pro903spec file says "Type: Ascent" - Does that mean there are other types?
Also, are there commands other than for pitch? Stuff like heading or burn time?
Thanks!

[DanSteph]

No others info available appart "pitch/altitude"
and "msg" lines

the engine/autopilot stop themself when the ECC reach a minimum
and start to increase again.

If your ascent is well done you must have an ecc less than 0.00009

the DGIII ascent start to null the vertical speed thus try to null the ecc
when the ecc is below 0.00030

Dan

[AphelionHellion]

Awww

I guess we have Redshift... But I do hope you add more features to the flight computer. It's already the most original
and useful feature of your DG - Or... Well... One of many. SO many cool things - I can't decide!  

And thanks for the clarification. I normally have pretty good luck with the eccentricity anyway, fortunately.

[DocHoliday]

Alright Aphelion dammit, since you're bragging

Gimme a launch curve solution for the ISS altitude (about 330km) right now, I'm at the edge of bursting with
frustration. 330 is probably a little lower than ISS but that is good because if you launch too late, you can catch up
with it in quarter of an orbit if need be.

Please?

[AphelionHellion]

I would except that I suck at that sort of thing

Ah I just saw your "Direct Ascent thread" - Looks like you've got it figured out yourself.
*heading off to try it*