Whats this ?Let me explain.Where the idea came from is a long story so I won't start :(What it will be is simple:It's a program that will run in background. This way FS doesn't come out of 3D mode. Then all aircraft control related key commands must be removed from FS. My program will be able to capture key commands eventhough in background. The user will then use FS, send key commands to his pc. Unlike normal it won't be FS reacting, but my program. Then when certain conditions are cleared in my porgram, my program will trigger things in FS.To give an example that makes things clear:You'll first have to start up APU, bateries, etc etc before the engines will start in FS.The idea is to create a cockpit system that is FULLY accessible via key commands and NOT with visuals or mouse clicks. So just what HC builders need. Nothing more, nothing less.Then I have 2 options. 1 way to go is to look up gauges and use those in FS itself. (just the things you would show on a glass cockpit)An other way is to make own visual gauges and show these PM style in my program though I think this would be harder to do.I've already overcome 2 hard parts: 1 was the key to bgrnd program and 2 was the fsuipc thing so that i can read/write FS token vars.Now the last tricky part that i would like to achieve is to make my program comm. with fsbus directly. This way my program could turn on the APU AVAIL led after a few seconds after you pressed a key command.Now I want to know how all this sounds to you guys. I'm quite sure that I understand right that PM only does the "glass-cockpit-visuals" and no cockpit systems ... well they should I think. So if it's not PM that does this, then I'm the first one to come up with this idea .. right ?Anyway, if this is new or not .. let me know who might be interested in using this and who 's not.Then I got 1 last problem. I'm going to do this multy-type-compatible. Meaning that if I combo my prog with the air and mdl file of an MD11 or with a BAe146 or an ERJ145 ... should all work.However, this means that the systems & startup procedure will NOT be exact as ANY type of airplane but rather an own creation.Could anyone help me on setting up a startup sequell ? I want something that has the general things that you find comonly in all Jets. If you know what I mean. Not anything type specific.Anyone care to help on this ?

You may want to go to http://www.projectmagenta.com/comingsoon.html and scroll down to PM Systems ... It sounds like you've described it pretty well...Simpit:-rotor

Philipp,Excellent idea. To resume if I understood so far:1. No needs of an Epic card and writing its boring lines of codes.(you did it for us)2. No needs of complex programmed airplanes ( PIC-PMDG-PSS..in order to get the complex electrical - hydraulical - pneumatical systems.What means any simple Air file and Aircraft config file of your choice is needed and any card using keystrokes like Plasma - Gammaray - FS Bus - Opencockpit - Hagstrom would make the deal.It's what you mean or am I wrong ???Roger

Oops .. didn't know 'bout the PM plans ..either way PM is payware .. i don't do payware unless i'd find something realy unpleasent to make.Roger >> you are absolutely correct, that's the basic idea indeed.

Oh dear, that's exactly what I always wanted and never dared asking for.ETA ??? Now I am very keen about it.CheersRoger

Hi PhilippeIt also sounds almost the same as Robert Fisher is doing. Its called FS Communicator. I has just gone payware, but it is incredebly cool. For example one of the features (only for Airbus folks, sorry!) is the 99% true flybywire function. But this is by far the only cool thing.You can check it out at http://www.flightsimulator.at/frm_fscom.htmNow, I might be wrong, but its sounds similar. But I'll be intersted in what you come up with.My 2 cents.RegardsPeter

no ETA yet ;)i'm still experimenting to see if I got what it takes and can manage to do all the things i plan to do.other than that I still got no real sequences.