Sign in to follow this  
gpbarth

Saitek Sensitivity and FSUIPC

Recommended Posts

I have abandoned the FSX controller settings and settings everything up in FSUIPC. But now I need to set the sensitivity on my Saitek rudder pedals, and I need some advice on doing this in FSUIPC. Can anyone recommend a good tutorial on setting this up? I've been playing with the calibration, but can't seem to desensitize the pedals, and my take-offs are all over the place.

 

Any FSUIPC experts out there?

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Gary, have you tried using curves?  Using a curve, you can basically set things up to have reduced sensitivity for small inputs near the neutral point and gradually increase with larger deflections of the pedals.  I don't use this with my Saitek rudder pedals as they seem fine, but I definitely do for pitch on most planes with my Saitek yoke.  Works great.

 

Scott

Share this post


Link to post
Share on other sites

Gary, have you tried using curves?  Using a curve, you can basically set things up to have reduced sensitivity for small inputs near the neutral point and gradually increase with larger deflections of the pedals.  I don't use this with my Saitek rudder pedals as they seem fine, but I definitely do for pitch on most planes with my Saitek yoke.  Works great.

 

Scott

That's what I'm talking about, but I still haven't figured out how to use them. I just got the Real Air Turbine Duke, and they recommend around 30% sensitivity on all flight controls. Since I can't set the sensitivity in FSX, I need to figure out how to do it in FSUIPC. I guess I'll go and mess with the curve settings and see what happens.

Share this post


Link to post
Share on other sites

I'd shoot you a screen capture, but not at home right now so can't fire up the sim.  Can do so later in the evening if you still need an example.

 

Scott

Share this post


Link to post
Share on other sites

Scott

I have the same problem. Would appreciate the screen shot thanks.

 

John

Share this post


Link to post
Share on other sites

ttocs, I doubt a screenshots necessary, but when you get the time just please state what value you use for the Duke curves that you feel is equivalent to a 30% axis sensitivity in the FSX cal screen. I think that's what he's asking. I am pretty sure that 50% in FSX, the default, represents pure linearity (no curves). If someone knows differently, please do tell.

Share this post


Link to post
Share on other sites

OK, assuming you've already assigned the axis in question, go to the "Joystick Calibration" tab and go to the first screen for the main flight control axes that you've assigned:

 

FSUIPC1.jpg

 

In this case, the control I've added a slope to is the Elevator.  Click on the Slope button under the axis you want to change and you'll see this:

 

FSUIPC.jpg

 

Here I've set a slope of 4 for the elevator which gives a mild reduction in sensitivity near the neutral point.

 

Hope that helps,

 

 


but when you get the time just please state what value you use for the Duke curves that you feel is equivalent to a 30% axis sensitivity in the FSX cal screen.

 

Unfortunately, I've no idea.  I moved to FSUIPC exclusively several years ago in order to solve some persistent issues I had with my Saitek yoke and rudder pedals and haven't used FSX assignments in so long that I have no idea how FSUIPC curves would correlate.  Sorry.

 

Scott

Share this post


Link to post
Share on other sites

Well, after doing some research and performing the requisite RTFM chores, I have learned more about FSUIPC, particularly the DELTA setting. Pete says in his docs that the DELTA is the minimum change before stuff starts happening, and the default is 256 (I think...I'm not there right now). The bigger this number is, the more a control can move before a change is seen in FSX. He suggests setting the number as high as possible before you start seeing negative effects.

 

So I decided to "hide" my fsuipc.ini file and start over.  I now have a setting on the rudder of somewhere around 1200, and I seem to have a bit more control over my take-offs now. I'm still working on the curve method, but I think my problem was the rudder was way too sensitive. When I looked at the initial setting, I seemed to have set the DELTA at 1, which meant if I breathed on the ruddres something would happen.

 

I'm going back and reading a lot more about FSUIPC, because I also have problems now with the Duke and the prop speed levers. I assgned them to an axis on my X55 throttle through FSUIPC, and the levers move beautifully...but the prop RPMs don't change at all. I had to hit Ctrl-F2 and Ctrl-F3 to make them work, and I think now that I have to assign them using the FSUIPC command to assign both props, not as one, but individually, to the same command, and then use the "Send to FS" instead of FSUIPC Calibration.

 

I'm a bit on the ADHD/OCD side, so I don't bother with the docs until I've totally screwed everything up, and then the light bulb comes on. Back to my FSUIPC docs now...got a lot more to learn.

Share this post


Link to post
Share on other sites

 

 


So I decided to "hide" my fsuipc.ini file and start over. I now have a setting on the rudder of somewhere around 1200, and I seem to have a bit more control over my take-offs now. I'm still working on the curve method, but I think my problem was the rudder was way too sensitive. When I looked at the initial setting, I seemed to have set the DELTA at 1, which meant if I breathed on the ruddres something would happen.

 

Yeah, a Delta of 1 would definitely make things pretty jumpy, especially if you've had your gear for a while and the pots are getting a bit grungy.  I've always used the default of 256 on all of my axes (elevator and aileron, rudders and dual throttle quads) and never had any problems.  Sorry - never considered you might have set that to 1.  :huh:  

 

 

 


I'm going back and reading a lot more about FSUIPC, because I also have problems now with the Duke and the prop speed levers. I assgned them to an axis on my X55 throttle through FSUIPC, and the levers move beautifully...but the prop RPMs don't change at all.

 

That's odd, but perhaps I don't understand how you're setting up the axes.  If you're using a single axis to control both - sorry, not sure what the best setting would be.  In my setup with dual quadrants, I have prop levers set up as 'PropPitch1' and 'PropPitch2' and all works as it should with the Dukes (I have both turbine and piston, V1 and V2).  This setup also accommodates single engine planes, as prop 1 (or mixture one, or throttle 1) seems to work fine for single engine planes as well.  The only exception I've found is A2A's GA aircraft, where the throttle needs to be "Throttle" rather than "Throttle1" and similarly for prop and mixture.

 

Best of luck getting things sorted.  FSUIPC can seem a bit arcane when first tackled, but once you get used to the logic of it, it's pretty sweet.

 

Scott

Share this post


Link to post
Share on other sites

I agree with ttocs. Set Delta to default of 256 and leave it. Now back to curves, even though you're going to assign your controls in FSUIPC, since that developer recommends "30% sensitivity" in FSX, I recommend you temporarily assign them in FSX with a calibration of 30% sensitivity. See how that feels, unassign in FSX, and then implement a similar feel in FSUIPC to the axis by using curves, as ttocs as shown above. Ttocs use of a curve with a value of 4 on the rudder is where I would start. Real controls are basically linear, so I don't particularly like it when a developer recommends that the user implement non-linear calibration methods in order to establish appropriate control feel; but that's how it is, and the above is how I would go about trying to recreate their calibration recommendations via FSUIPC.

Share this post


Link to post
Share on other sites

I have 2 wheels on my X55, the top I've assigned to the props, and the bottom to the condition levers. In FSUIPC, you can assign up to 4 actions to one axis. So I set both prop1 and prop2 to work on that one axis...did the same thing with the condition levers (mixture 1 and mixture 2). Funny thing was that the condition levers worked, but the props didn't - the levers moved, but no change in RPMs. If I used Ctrl-F2 and Ctrl-F3, it worked.

 

I don't think the RA Duke likes FSUIPC, though, so I'm going to try to send to FS through it, and hope that works. I don't want to reactivate the X55 in FSX when everything else is working fine with FSUIPC.

Share this post


Link to post
Share on other sites

 

 


I don't think the RA Duke likes FSUIPC, though, so I'm going to try to send to FS through it, and hope that works. I don't want to reactivate the X55 in FSX when everything else is working fine with FSUIPC.

 

Well, you have to do what works for you, but I've had all 4 of the Dukes (V1 and V2 of each) and I've used nothing but FSUIPC to control all of them without any issues.  Prop, throttle and mixture (or condition levers in the Turbine) are all bog standard FSX commands, so I can't imagine what's wrong there.  Sorry, I'm out of ideas on this one.

 

Scott

Share this post


Link to post
Share on other sites

Well, you have to do what works for you, but I've had all 4 of the Dukes (V1 and V2 of each) and I've used nothing but FSUIPC to control all of them without any issues.  Prop, throttle and mixture (or condition levers in the Turbine) are all bog standard FSX commands, so I can't imagine what's wrong there.  Sorry, I'm out of ideas on this one.

 

Scott

But do you "Send directly to FSUIPC Calibration" or "Send to FS as normal axis?" I had everything set up the first way (with the Duke), and now I'm thinking that I have to use the "Send to FS..." method instead. Anyway, I've reset my FSUIPC.ini file and started over...maybe I had some kind of glitch there. Like I said, I found that the DELTA on several of my settings was 1. I want all of the defaults to remain at 256. I won't have time to do it right away (why does work always get in the way?), but I'll let you know what happens.

Share this post


Link to post
Share on other sites

All of my axes are set up with "Send directly to FSUIPC Calibration".  This was actually the original issue which pushed me to move to FSUIPC, as I'd repeatedly lose calibration on various axes whenever I'd reboot my system.  Assigning to FSUIPC and using FSUIPC calibration was the ultimate solution to that annoying problem.

 

 

 


(why does work always get in the way?),

 

Why indeed!  Speaking of which, I'd best get on with the work day. :lol:

 

Scott

Share this post


Link to post
Share on other sites

All of my axes are set up with "Send directly to FSUIPC Calibration".  This was actually the original issue which pushed me to move to FSUIPC, as I'd repeatedly lose calibration on various axes whenever I'd reboot my system.  Assigning to FSUIPC and using FSUIPC calibration was the ultimate solution to that annoying problem.

 

 

 

 

Why indeed!  Speaking of which, I'd best get on with the work day. :lol:

 

Scott

Well, I "complained" to RA, and here's the answer I got:

 

Hi Gary,
 
Clearly there is something odd going on with an element in the chain of how you've set up the levers the Duke, whose prop levers work perfectly.
 
I have Saitek throttle levers which I can assign to any function using the standard FSX axis assignments and again they work flawlessly, as they did in hundreds of hours testing.
 
The Duke does not need FSUIPC to function. Perhaps adding another layer of complication is making things unnecessary? Surely your levers can be assigned using the standard axis assignments?
 
We do have a lot of customers for the Duke and so far no reports similar to this. Not knowing exactly what you are doing it is hard to make a useful comment, other than that we are quite certain there is nothing wrong with the prop levers, which, as you say, can be operated in three different ways: Mouse, Keys,or Levers.
 
Regards,
 
Rob
 
So I decided that he really doesn't agree with FSUIPC, and then I read from Pete's FSUIPC docs:
 
Turning to the other assignment method, the one labelled “Send direct to FSUIPC calibration”

actually bypasses FS altogether until the axis input has been through FSUIPC4’s own Joystick

Calibration section. In this case the drop-down shows only those controls which can be calibrated

in FSUIPC4, but this includes some which you would otherwise have to assign special numbers to

in FSUIPC4.INI as described in the Advanced User’s guide. For example these include Aileron

Trim, Rudder Trim, and the four Cowl Flaps controls.

 
So I figure that I probably used a control that was foreign to the Duke, and that I'd get better results by going the Send to FS route, which is what I am about to try as we speak. Maybe you could tell me the exact control in FSUIPC you have assigned to the props. As I said, when I did that, I could move my wheel and the levers moved back and forth, but there was no change in prop RPM. Could very well have been a glitch, too. Gonna keep playing with this until I get it fixed. I'll post again shortly after I run FSX and fly the Duke a little.

Share this post


Link to post
Share on other sites

Here's a screen capture of one of my two prop lever assignments (the left one):

 

FSUIPC2.jpg

 

BTW, while I understand where Rob's coming from - basically why complicate something that's fundamentally simple - in my case I control through FSUIPC for everything so that I  1) have all setup in one location and  2) because I had a specific problem with axes which only FSUIPC fully solved.  I very much needed what the manual describes, removing all calibration from FSX and default Windows.  And note the rest of the line after what you put in bold: until the axis input has been through FSUIPC4’s own Joystick Calibration section.  The difference here is simply in who handles the calibration, not what the control ultimately does, and that difference was critical to me.  To be clear, the problem I had was actually related to axes that center (rudder, aileron and elevator), but with my Saitek yoke the first three quadrant levers are actually part of the yoke controller, so I needed to handle that controller through FSUIPC anyway, and also see 1).

 

I should also note that for A2A GA singles, I use a profile specific assignment for throttle, mixture and prop (on the 182) with the only difference being that the assignment for this axis is PropPitch, rather than PropPitch1 and similarly for the other two axes.

 

One other possible issue occurs to me - one of the early problems I had when I first moved to FSUIPC was that for some reason or other, the controllers that I'd completely deactivated in FSX would somehow or other magically reactivate themselves and I'd get bizarre results due to the double control.  Double check to be sure your controller is still set to be inactive in FSX.

 

Hopefully using "Send to FSX as normal axis" will take care of things for you, but I just can't imagine why using FSUIPC to calibrate would mess things up.

 

Scott

Share this post


Link to post
Share on other sites

Well, I'm back in the saddle again - everything is working, and I can't tell you why. I deleted (saved) the old FSUIPC.ini file and started over, and assigned everything to FSUIPC calibration with one exception. The throttles (the X55 has 2) were working with the default "Send to FS" choice  - when they were at minimums, they sat at idle in the Duke. In order to get Beta, I had to use the F2 key. So I switched the assignment to Send direct to FSUIPC Calibration, moved the throttles full up and down, left the Delta at 256, went to FSUIPC calibration, and clicked SET. Did this on both throttles.

 

When I went back to the Duke, I now had full Beta with the throttles at minimums, and full throttle at max. Okay, not too bad. But now I had to set the throttles at idle (there is no detent on the X55) manually, and as I was warming up the turbines, all it took was a slight bump to go into Beta range. During taxi, if I wasn't verycareful, those nasty warning lights on the dash would illuminate, and I'd have to gently bump the throttles back to idle using the warning lights going out as an indication that I was out of Beta.

 

I'm sure that messing around with FSUIPC will let me set that a bit better, but for now, I went back to the "Send to FS as normal axis" choice, and have set another button on the throttle quad to do the F2 trick - while it's held down, I'm in Beta and when I release it, the throttles go back to idle. I wish there WAS a detent on the throttles, but I'm happy again. I even took the 2 small knob axes on the throttle and assigned them to the condition levers, so at least I can control each one separately. And the props are both working through a single axis - both are assigned as Prop Pitch 1 and Prop Pitch 2 to the same wheel.

 

So I think I had a problem initially with my FSUIPC.ini file, and now I'm ready to start flying the Duke again. I took it up for a test flight and took off at full flaps (very short runway at 69N), and thought I had brought them all the way up. Heading into cruise I heard and felt a load bump and realized that I still had Flaps 1, or used to. The flaps failed and I couldn't get them up or down. Lesson learned. I fly enough A2A aircraft to know better.

Share this post


Link to post
Share on other sites

all it took was a slight bump to go into Beta range

 

As you have realised, your Saitek hardware is not suitable for setting up the power levers with complete realism. You need to check the 'no beta range' checkbox on the FSUIPC calibration screen. Then you manage the beta range some other way. You can do it with buttons as you have done, but a better way would be to use two additional analog levers. FSUIPC implements full analog reversers that can be assigned to individual axes or to a single axis. In my Twin Otter I use this (these are the yellow levers if you have seen any of my cockpit videos).

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this