I have FSX installed with the Porflight yoke and pedals and an extra throttle quad. Also have saitek trim wheel.

All was working well with basic control setup in fsx..

I usually fly pmdg, majestic dash8 and recently insalled milviz 737.

I then decided to attempt disabling controllers in fsx and use fsuipc.

Well that was a mistake. Too many problems for me setting up that software.

I setup everything back to fsx control but now my throttles dont work properly.

When I start to move them from idle a little, the engines rpm  jump up about half way.

I deleted the fsuipc.dll and reinstalled fsuipc and recalibrated all controllers in fsx/ options/ settings/ controls.

Anyone know how to fix this?

thanks

 

Paul 

Hello Paul :

 

Here is my suggestion : Reset all controls in FSX to default .  Shut the PC down, disconnect the Saitek- USB plugs. After that restart the PC, connect the USB-plugs and check if everything works normal.

 

Good luck,

 

Ben.

hi Ben

 

Did exactly as you said but it did not help at all.

Anything else I can try, short of uninstalling everything and starting again...LORD not that again.

 

Paul

Hello Paul,

 

Not an easy one this time. As problems accure with fsuipc I suggest in addition the following : after starting pc, uninstall fsuipc and take the USB plug out of the socket; shut down PC and restart. Then install fsuipc (look in the manual) clean the registry (for instance with CCleaner = free) connect the USB in another socket ad start FSX.

 

Hopefully this works. Some problems you have to solve with try and error.

 

Ben

One of the primary reasons I moved to FSUIPC (several years ago now) was an issue with needing to recalibrate the Saitek axes after every system restart.  The routine went like this - reboot, unplug and replug and then recalibrate from the MS controllers panel.  If I didn't recalibrate, what you're seeing seemed to occur.

 

My Saitek axes can still get "confused" after system restarts, but with FSUIPC a simple unplug and replug is all that's needed.  No need to recalibrate.

 

My first suggestion would be to give FSUIPC another try.  It can be intimidating at first, but once you get past the initial learning curve it works great.  But if you've already decided not to go down that route, try going back through the calibration routine after replugging.

 

Scott

As a suggestion before doing any thing drastic here. For the Q400, in FSuipc, for the throttles, you can either, check the No Rev zone box  and calibrate. If that doesn't work, try setting the idle zone closer to/equal to the min. values.  Try both methods to find out which you prefer. I'm not near my flying box, so I'm unable to copy in my settings as a guide.

  regards, C.

Thanks for the replies.

 

I had my controllers partly setup with fsuipc but got frustrated with hatswitch views, could not get them working properly.

I did not understand the profile stuff.

Is there anwhere I can find a step by step guide to setting everything so it works.

Do all the pmdg and mcdash8 work in fsuipc?

 

Paul

hi scott

 

ok, if I get this throttle problem fixed I will try fsuipc again.

 

But I have some questions:

When setting up fsuipc do you uncheck the enable controller box in fsx.

How do you setup your hat switch button if you use it for panning.

Do you everything: axis, calibration, joystick buttons and keyboard keys assigned through fsuipc.

 

I am reading the simsamurai fsuipc tutorial and going to look at the fsuipc manual.

Any other tips you can give me on setting this up properly.

I mostly fly PMDG jets, mcdash8 and recently bought milviz 737.

I also use EZDOK and would like to still program some yoke buttons for ezca view changing.

 

Thanks

Paul

Paul,

 

You can do some controls in FSUIPC and others in FSX, but I found it simplest to disable the controller entirely in FSX and do everything in FSUIPC.  For some reason, in the first months after I'd converted to FSUIPC FSX would sometimes re-enable one of my controllers (the yoke and attached quadrant) which can cause all kinds of issues, so if something's going wrong one of the first places to look is to see if FSX has suddenly take control back.  This stopped happening over a year ago, however.  Not sure why it was originally doing it and what changed to stop it.  It was only an occasional problem.  If you do decide to leave the controller enabled in FSX you need to be meticulous about being sure there are no duplicate buttons or axes enabled.

 

As for the hat switch, I need to go back and look at how I did it, but what I recall is that there are two ways to set it up, and one of the ways is terrible, while the other works great.  Not at my FSX machine now so I can't look, but I'll try to get this information to you when I get back to my system later today or tomorrow - unless someone else chimes in first.

 

All of my controls and buttons are done through FSUIPC (I use a Saitek yoke and quadrant, second quadrant and rudder pedals), but I don't do anything with keyboard keys in FSUIPC.

 

As noted, however, while I think FSUIPC is great and solves one very specific problem I had with Saitek controls, you can probably solve the issue you're having with a replug and recalibration of the controller axes from within Windows.  The problem for me was that I had to do this every time following a reboot and I got really tired of re-calibrating.

 

More to follow as soon as I get a  chance...

 

Scott

I can fix all your problems............I will get back to you............much to late to do this evening.........give me time............Brian.

Took me a minute to remember how this (hat switch in FSUIPC) worked after looking at it.  What you want to do is assign POV as an axis.  To do this:

 

- Go to the "Axis Assignment" tab

- Click on the "Rescan" button and be careful not to move any of your axis controls.  If you accidentally hit another control, just hit the "Rescan" button again.

- Carefully move the hat switch - be careful not to move the yoke, but see previous step if you do

- Once the switch has been recognized, under "Type of action" select the "Send to FS as normal action" radio button

- Under this heading put a check mark in the first box and to the right of that in the drop down find "Pan View" and select it.

 

This method works way, way, WAAAY better than assigning each hat switch direction as an individual button with pan up, down, etc with repeats.  This, I think, was the single biggest "ah, hah!" I had in moving to FSUIPC for everything, rather than leaving the controller enabled.

 

Hope that helps,

 

Scott

I think I can do it now Scott.

In a week when I get home I will start setting up with FSUIPC.

 

Thanks

Paul

Question re. Saitek quadrant USB vs PS2 version (yoke system) and theirs levers and “0 button detent”.

I have both and realize that USB version has very soft “0 button detent” .

I can hardly feel when the thrust lever is in the lowest position or in reverse thrust

Whereas in the PS2 version “0 button detent” is firm very easy to distinguish two lever positions i.e. zero thrust and reverse thrust.

 

My doubts are whether I have bought faulty USB quadrant or it is normal in compare to PS2 quadrant.

If someone who has both quadrants could compare it on its own quadrants and let me

Thank you

 

 

My doubts are whether I have bought faulty USB quadrant or it is normal in compare to PS2 quadrant.

If someone who has both quadrants could compare it on its own quadrants and let me

 

Mine are the same, purchased about 2.5 years ago.  The USB quadrant has a smoother feel with less noise and less resistance and with a bit of a mushy detent.  The PS2 quadrant has a firmer feel, makes a raspy noise as it's moved and has a firmer detent.

 

Neither are problematic, but I do prefer the firmer feel of the PS2 version.

 

Scott

thanks Scott. I will keep then usb quadrant.