Ok - Those who know me tell me I can't afford to do this - pull out my hair.Which is what I am currently trying to do - I've found one solution but it kills another options.I want to be able to press the vs button on my cockpit and maintain the current rate of climb. So if I'm cluimbing at 2305ft/m I want to continue at that rate - not 1500 or whatever the preset is on the plane.Is this possible?Another problemWhen I press a button - it may light up the corresponding light - even though that mode is not active - for example the approach when you're in the middle of no where - the light goes on - but the corresponding fs button on the plane doesn't - which is correct. How can I get my led to turn on only when it's suppose to?

>Another problem>When I press a button - it may light up the corresponding>light - even though that mode is not active - for example the>approach when you're in the middle of no where - the light>goes on - but the corresponding fs button on the plane doesn't>- which is correct. How can I get my led to turn on only when>it's suppose to?You need to hook the led into the same *fsuipc offset* as the button, instead of the FSBUS button directly (you are using FSBUS?)//Tuomas

Yeah, that's what I was trying to do with the project magenta stuff.But if the fd was not on and you pressed a button, I still got the light on, and could end up with the light off when it was actually suppose to be on.As I can't get the nav working using the progect magenta - which is more bothersome than having an accurate rate of climb system, I've reverted back to the standard fs stuff, and now trying to work out the difference between vor/loc and the app - I can't get the vor/loc to turn on.I know this all sounds stupid, but well I'm learning, and i just hope that one day I can help others as well.

>Yeah, that's what I was trying to do with the project magenta>stuff.>>But if the fd was not on and you pressed a button, I still got>the light on, and could end up with the light off when it was>actually suppose to be on.So first off: "A" is "FS2004 panel gauges", "B" is "Project Magenta stuff".You need to use either, not both, since Magenta uses its completely separate and own autopilot and everything. I have never used it, but as far as I know, you cannot use both the FS autopilot and the Magenta one. So if you use Magenta, you must use the Magenta FSUIPC offsets, not the FS ones for anything related to autopilot etc.So you need to focus on "B" stuff here and forget about everything "A" if you want to use Project Magenta.//Tuomas

Yup - preoblem isSystem A - I can't do a realistic vs climb descent.System B - I can't use ap to navigate.I've decided system a is the lesser of two evils, and going to look at seeing if I can learn a way to do the vs some other way.Was hoping I could do a ccc type thing, where if I press this button it reads in the current vs, and then change the ap vs to that, but that hasn't worked :( Well not with my limited brain power - back to the drawing board.

A few clarifications on previous posts:PM software do indeed use default FS autopilot but to a limited extent.As long as i know, PM can't operate without FS own autopilot being active.Edit:PM, though using FS ap, is operated by own offsets, as Tuomas said, not the FS own ones.End edit.That said, i wonder: why can't you make PM work?Have you asked Enrico for help?It is a complex software surely, but Enrico (and the PM team) is always prompt to help if you ask, and so is the support forum.At least this is my experience as a non-PM user.Regarding your very problem (VS mode): are you able to program in any language? (C,c++ or VB)If so that's your solution, if not...Well if not, PM is your only solution :(

I have a little experience at vb, but don't have it any longer, but have access to delphi, which I'm not sure will work, but going to look into it.I can use the cdu of the pm stuff (I have the glass cockpit software) but at the moment, I'm not interested in doing that - as I don't have another computer available to run all the pm stuff - and my computer would grind to a standstill running it all on one computer.

So you are not really haveing problems with PM, it's just that it goes slow.That's another story.Anyway when i tried the demos, i was able do run almost everything from one pc.At least the MCP and the MFDs.So i think that you can surely run the MCP on the same computer, all the more if you use no panel on the plane.