Thanks lg and Pete,
My question betrayed my lack of real understanding of the purpose of FSUIPC in its present incarnation. I'm not sure who's fault that really is. I believe it is shared. Forget the fact that I am an RAF-trained pilot and honours graduate, like most things 'technical' the supporting documentation seems to start from the engineer's perspective rather from that of the layman, who wants to see: 'this little programme will let you do this, this and this, and this is how you will benefit'. Look at almost any user manual. I subscribed to FSUIPC out of appreciation and loyalty for what it had enabled me, as a casual simmer to do for free, for so long, in earlier versions of FS. But then I asked myself 'hey, what more might this little gem be able to do?' No expectations however.
When setting up the PMDG 744 in conjunction with FS2Crew the mouse is used intensively. Its intuitive. I have a SAITEK Av8R joystick and it can be programmed that for the purpose but due to its limitations its actually easier to use keyboard presses in the end. So the L/R clicks of the mouse wheel (you must admit its a clever idea) is an elegant solution - or at least it would be. And sure, the Logitech mouse in question has its own programmable software. I assigned the L and R click to key presses. I assigned those same key presses to the MAIN and SECONDARY buttons in FSUIPC. But to no avail. The FS2CREW interface employs a gauge that recognises only the joystick and keyboard inputs you have entered and that's that. Its not a big deal to me, and certainly no implied criticism of FSUIPC at all.
Regards
Gareth
