Glynn

The microswitches at the end of these Axis are sending the G and Z keypresses, you will need to track these down in the P3D controls if you insist on using P3D control assignments.
You will forever have a world of pain if you continue to use a mix of P3D controls and Fsuipc controls.
Choose one method and stick to it, my advice is to do everything within Fsuipc  as this gives you much more flexibility and access to many more internal P3d controls. The P3D controls section is absolutely of no help if you fly a range of addons, unless you particularly enjoy reconfiguring hardware between different aircraft types.

Matthew, your area 125 in your working scenery.cfg located in C:\ProgramData\Microsoft\FSX\ should read
 
[Area.125]
Title=MyTraffic
Local= D:\MyTraffic Professional\MyTraffic
Layer=125
Active=TRUE
Required=FALSE
 
And your FSX.cfg should contain the line
 
SimObjectPaths.0=SimObjects\Airplanes
SimObjectPaths.1=SimObjects\Rotorcraft
SimObjectPaths.2=SimObjects\GroundVehicles
SimObjectPaths.3=SimObjects\Boats
SimObjectPaths.4=SimObjects\Animals
SimObjectPaths.5=SimObjects\Misc
SimObjectPaths.6="D:\MyTraffic Professional\MyTraffic\Aircraft"
 
Note the quotation marks in the SimObjectPaths.6="D:\MyTraffic Professional\MyTraffic\Aircraft" line, this is a windows convention but the scenery library entry does not seem to need them.
 
These are the only two entries that MyTraffic needs to work, so as long as you are editing the correct scenery.cfg (C:\ProgramData\Microsoft\FSX\scenery.cfg) it should work

Rename \FSX\Scenery\World\Scenery\trafficAircraft.bgl to trafficAircraft.passive
That will get rid of the default traffic, for statics at your third party airports you will have to find the relevant bgl and rename it.
Obyx freeware airports seem to have a lot of static stuff dotted around.

Turn off FXAA

To have Vsync in windowed mode requires Aero to be on, see this post:
 
http://forum.avsim.net/topic/375526-addendum-to-vsync-fix-windowed-mode/

You need to install a PDF reader, I use SumatraPDF but Google will find you many more.
http://www.sumatrapdfreader.org/free-pdf-reader.html

FSUIPC4 User Guide.pdf
Page  26    Keeping track of multiple control devices ("Joy Letters")
 
In your Fsuipc.ini put AutoAssignLetters=Yes in the [JoyNames] section and then Fsuipc will look after them for you.
You can unplug your controllers and not worry about which ports they were originally on, Fsuipc will sort it all out and your assignments will still work
 
[JoyNames]
AutoAssignLetters=Yes

No,  I got it from the link above, then renamed it so that I can have both in my Ezca directory.
My exe.xml files on P3D and FSX are edited to call the correct exe.
 
Make sure when you put it into your ezca directory that you have renamed it first otherwise it will ovewrite the FSX version.
Then set its properties to run as administrator

The Readme.txt that comes with the lua files clearly states that "it will be listed as "Lua Q400VSpeeds"
Despite not owning the Q400 I have just copied this lua into my modules folder along with speeds.dat and just as the readme states there it is listed in Fsuipc
 

The fsuipc button programming page is fairly self explanatory but the excellent documentation is really worth reading through.
But  at its most basic it consists of pressing a joystick button and either assigning a keystroke combination (left hand side) or assigning a Fsuipc Control  (right hand side)
 
Read from page 26 of the FSUIPC4 User Guide.pdf where button programming is explained in detail and from page 16 of the FSUIPC4 for Advanced Users.pdf for a more in depth look at the facilities
 
Once you have an understanding of how the button programming page works you should fiind it easy to program one of your buttons to send a Fsuipc Control.
 
The special Fsuipc  controls for Squawkbox are:
1001  PTT on
1002  PTT off
1068  PVT voice transmit on
1069  PVT voice transmit off
 
A read through the List of FSX and P3D controls.pdf will reveal many other useful controls you can send with a button press