Guys,I'd like to build my own custom controls, and I'm wondering what's the best software interface to use for FS2002?Am I right in thinking FS2002 uses DirectX for input?Does anyone know how the commercially available panels handle the interface?Just simulating keyboard input seems a bit clunkyAnd what about output for dial's, display etc?Sorry if it's a lot in one go

Welcome, David.In answer to your questions, you might want to start by looking at FSUIPC by Peter Dowson. You can find a link to info about it on the Project Magnet web site www.projectmagenta.com . Take a look at the SDKs from Microsoft available the FS2002 support page. In particular look at the gauge module docs. This will give you an idea of what you have to work with if you code your own instrument output. If you're not into C, take a look at the EPIC card by R&R Electronics, and by all means visit the Blue Side Up site here on AVSIM. The EPIC driver handles a great deal for you but you still have to tell EPIC what's hooked to it and how to respond to changes on its input channels. You may also find some useful information on my web site.Mikewww.mikesflightdeck.com

DavidMike makes a lot of excellent points. For the output side, you have a plethora of choices (despite the fact that Mike hates "legacy" options!!!)But you will for sure need FSUIPC. Get used to that fact right from the get-go.For output, you'll need some way of interfacing what you build to your hardware. A good site for real basic interfacing is www.myke.com Lots of good info on building electronice interfaces to your PC. Personally, I think that serial/parallel interfaces are perfectly acceptable. Mikes point that they will be dropped at some point is certainly true, but its also true that as an intro to the topic, the learning curve is a lot more gentle, and what you learn from them will be invaluable regardless of whether you use serial, parallel or USB.One other point - dont dismiss PC keyboard emulation for input. There are a lot of utilities avilable that can help overcome the purported limitations of this approach. And if you can code in VB, you are well set to start building. And you can do a lot without going anywhere near DirectX (although the Dx object model is quiet nice and introduces a lot more flexibility)If you get stuck, ask in this forum, there are lots of folks who are extremely generous with their help.WelcomeDave

Thanks guys,This forum seems a much friendlier place than the software developer newsgroups I normally use.Maybe it's because it's a hobby, not 'the day job'