This is more of a public service announcement for anyone who may have encountered a similar problem as myself. There may be no one else though, as after spending SEVERAL hours searching online for help on this matter I found absolutely NOTHING--except one moderator response on Saitek's forums to take the unit back to the store.
I've noticed with at least FSX (especially since I've tried linking the throttle axis to the spoiler axis to make flying the sailplane more realistic); that I don't get full range of motion... In other words; max throttle is is 99% and minimum is 1%. In fact, it was one of the reasons why I decided to abandon my 7 year old Saitek X-36, and buy an over-priced Saitek X-52 Pro. After hooking it up today, I noticed that I was still having the same problem... (Yes, taking off at 99% throttle isn't that big a deal... but I hate soaring with spoilers sticking up 1%).
[A positive side-note: the X-52 ROCKS!!! compared to the X-36... so much more precise! I bet I could probably shoot someone down in IL-2 now!]
Anyway, I ran IL-2, and noticed I could get full throttle deflection there (0% to 110%)... but never-the-less, I uninstalled my drivers, deleted all references I could find... deleted half my registry as I madly scrubbed my computer of all traces of Saitek drivers... But that still did me no good. I tried adjusting deadzones both on the drivers as well as the FSX control settings. I also tried deleting the FSX.CFG, and deleting the standard.xml files too... but that made no difference.
Finally, I got up the nerve to try messing with "standard.xml" under c:\documents and settings\
\Application Data\Microsoft\FSX\Controls, using notepad...
Under "SimControls.Map
Name Saitek X52 Pro Flight Controller....
Axis
AxName ZAxis /AxName
Index 2 /Index>
AxEvent AXIS_THROTTLE_SET /AxEvent>
AxScale 127 /AxScale
AxNull 1 /AxNull
I decided to set AxNull thing to Zero, to read AxNull 0 /AxNull
Amazingly that worked! Now, I get full deflection on the throttle axis from 0% to 100%
I've noticed now since setting that line to zero, FSX has apparently simply removed the "AxNull" line altogether...
Anyway, none of you guys probably have ever had this problem... but just thought I'd post a solution here, in case I forget what I did, and need to get my own advise again.
TX-ScubaSteve
White 4