Controls setting.

[speedbird144]

Hello everyone.

I am new guy here and of course people like me has lots of questions right away. I purchased FSUIPC and I already have issues. After spending few days reading manuals (including simsamuray ) I was unable to assign any controls other than spoiler lever. I spend whole day today but still no luck. I followed exactly same procedures as shown in all manuals but still no luck. FSX does not see my saitek controls. I was trying to find a right topic for me but there are 300+ pages and if I read all of them I will turn 60. If anyone had same issues at the beginning please point me out to the right place where I can find more information how to assign Axis in FSUIPC. Like I said I was following all steps in manuals carefully but no luck. FSUIPC is not doing anything for me at the moment.

Thank you.

[Pete Dowson]

I am new guy here and of course people like me has lots of questions right away. I purchased FSUIPC and I already have issues. After spending few days reading manuals (including simsamuray ) I was unable to assign any controls other than spoiler lever. I spend whole day today but still no luck. I followed exactly same procedures as shown in all manuals but still no luck. FSX does not see my saitek controls.

If FSX doesn't see your controls then neither will FSUIPC as both use the same Windows' DirectInput facilities. You'll need to ask Saitek support to help. It sounds as if either they are broken or need some proper driver installing.

... how to assign Axis in FSUIPC.

First off, why do you want to assign axes in FSUIPC? That's a facility mainly airmed at those either wishing to have different controls automatically assigned for different aircraft types, or for those wishing to do unusual things with their axes or to assign axes which aren't supported by FS directly.

You can calibrate controls in FSUIPC even when they are assigned in FS, and that is the more usual way to proceed. FSUIPC has offered those facilities for a very long time. The axis assignments were added for cockpit builders and those more ambitious users.

However, that said, there is nothing to assigning. You simply select the Axes tab in FSUIPC options, move the lever around till FSUIPC sees it, then select and action for it in the drop down list on the left hand side after selecting one of the 4 entries. There are 4 to allow 4 distinct simultaneous assignments to the same axis.

I don't see it takes scouring manuals or 300 pages of Forum messages to do something which is so simple, obvious and natural to most users, and expressed in a few short paragraphis in the supplied User Guide. It is certainly no more complex than FS assignment despite being more powerful in several ways.

Regards

Pete

[speedbird144]

If FSX doesn't see your controls then neither will FSUIPC as both use the same Windows' DirectInput facilities. You'll need to ask Saitek support to help. It sounds as if either they are broken or need some proper driver installing.

First off, why do you want to assign axes in FSUIPC? That's a facility mainly airmed at those either wishing to have different controls automatically assigned for different aircraft types, or for those wishing to do unusual things with their axes or to assign axes which aren't supported by FS directly.

You can calibrate controls in FSUIPC even when they are assigned in FS, and that is the more usual way to proceed. FSUIPC has offered those facilities for a very long time. The axis assignments were added for cockpit builders and those more ambitious users.

However, that said, there is nothing to assigning. You simply select the Axes tab in FSUIPC options, move the lever around till FSUIPC sees it, then select and action for it in the drop down list on the left hand side after selecting one of the 4 entries. There are 4 to allow 4 distinct simultaneous assignments to the same axis.

I don't see it takes scouring manuals or 300 pages of Forum messages to do something which is so simple, obvious and natural to most users, and expressed in a few short paragraphis in the supplied User Guide. It is certainly no more complex than FS assignment despite being more powerful in several ways.

Regards

Pete

Thank you for the response.

"First off, why do you want to assign axes in FSUIPC? That's a facility mainly airmed at those either wishing to have different controls automatically assigned for different aircraft types, or for those wishing to do unusual things with their axes or to assign axes which aren't supported by FS directly.

You can calibrate controls in FSUIPC even when they are assigned in FS, and that is the more usual way to proceed. FSUIPC has offered those facilities for a very long time. The axis assignments were added for cockpit builders and those more ambitious users."

Sorry. I might be misspelled something, I was trying to assign controls using those tabs you were saying about.

I was able to assign one of the lever for speedbrake via FSUIPC. That one seems to work fine. I know my saitek pro yoke and pedals work. Problems began when I re-installed FSX and after assigning controls via FSX they worked till I calibrated it within FSX. I was trying to assign each lever for each engine and problems began. Everything worked fine except thrust lever. It spikes power very fast. When I disabled and deleted everything in FSX and went to FSUIPC I was able to assign spoiler lever only. Throttles still messed up. Rudder pedals and yoke don't work as well (like I said it worked in FSX fine). So I am more than sure controls are operable. Either I am doing something wrong withing FSUIPC or there is something else I do not understand.

Thank you.

Edited May 2, 2012 by speedbird144

[Pete Dowson]

I was trying to assign controls using those tabs you were saying about.

Yes, but as I asked, what is it you want to achieve by assigning in FSUIPC instead of FSX? The main use of FS to improve controls is calibration. Assignment in FSUIPC is not necessary for proper and accurate calibration.

I was able to assign one of the lever for speedbrake via FSUIPC. That one seems to work fine. I know my saitek pro yoke and pedals work. Problems began when I re-installed FSX and after assigning controls via FSX they worked till I calibrated it within FSX.

So not when you assigned in FSUIPC, only calibrated? Is this with default FSX aircraft? How did you calibrate -- following the numbered steps in the User Guide?

I was trying to assign each lever for each engine and problems began. Everything worked fine except thrust lever. It spikes power very fast.

Assigning or calibrating? You are confusing me now. If you assign in FSUIPC to the FS controls it is exactly the same as assigning in FS. If you assign in FSUIPC "direct to FSUIPC calibration" then you MUST then calibrate -- that's what it means "direct to calibration".

Some aircraft need different ways of assigning. You must always state the aircraft if not default. Some, like the Wilco Airbuses and the PMDG series do not respond correctly to all the possible ways of assigning -- throttles especially.

Also you must not have the same axes also assigned in FS -- they will conflict! Your description of your problems sounds a bit like such a conflict -- either that or completely bad calibration.

BTW the current FSX version of FSUIPC is 4.827, so make sure you are up to date. Then, if you still have problems, show me your FSUIPC4.INI file (from the FS Modules folder) so I can see exactly what you've done. You can paste it here in a message, it is only a text file.

Pete

[speedbird144]

Sir.

I am sorry I made you confused. Looks to me it’s interpretation issue here. I will try to explain it once again to make it clearer. I am confused even more than you. I am still trying to understand why I purchased FSUIPC. Sounds silly but it is what it is. I went on Saitek and PMDG NGX forum and posted issues I was having. I received many responses and all of them were saying the same- Buy registered version of FSUIPC and all my problems with controls would go away. I’ve heard a lot about of FSUIPC and I know it is good software; I just need to understand how to use it right. One of the suggestion was: “Important: Delete all the axis settings within FSX (ie aileron, elevator, rudder, throttles, brakes)It is a bit wierd that the elevator, throttles, aileron and rudder are set up then calibrated in 2 separate tabs within FSUIPC.Ihave yet to do FSUIPC mouse macros and buttons, I still use saitek smart-tech for buttons, but will use FSUIPC when I get around to it.” Manual states: “REASSIGNMENT OF THROTTLE QUADRANT AXES WITH FSUIPC” and steps how to that. So that’s why I said I was trying to assign throttles via FSUIPC. So I don’t know the right wording when I’m dealing with FSUIPC, if I should say Assign or Set up controls, axes…whatever. So my goal is to make my controls working. I was advised by many users to delete all the axis settings within FSX (ie aileron, elevator, rudder, throttles, brakes) and do that within FSUIPC and disable controls in FSX settings and I did that.

Q. I asked, what is it you want to achieve by assigning in FSUIPC instead of FSX? The main use of FS to improve controls is calibration. Assignment in FSUIPC is not necessary for proper and accurate calibration.

When I used FS calibration it messed up all throttle quadrant completely and folks on forums suggested me stop doing this within FSX and go with FSUIPC.

Q. So not when you assigned in FSUIPC, only calibrated?

I had assigned and calibrated within FSUIPC.

Is this with default FSX aircraft?

Yes.

Q. How did you calibrate -- following the numbered steps in the User Guide?

Sorry, but for me it was lack of information on original FSUIPC user guide came with download and I had to use additional one from SimSamurai. The person who wrote it explained it in very details how to assign and calibrate controls. I used those steps carefully. I am not saying original manual worse but for me it was a bit difficult to understand. I believe when I get more experience using FSUIPC I will be using original manual more often. It’s just me, nothing personal. Sorry.

Q. Assigning or calibrating? You are confusing me now. If you assign in FSUIPC to the FS controls it is exactly the same as assigning in FS. If you assign in FSUIPC "direct to FSUIPC calibration" then you MUST then calibrate -- that's what it means "direct to calibration".

Like I said most of users advised me not to deal with FSX anymore, delete all axes and disable controls in FS settings and go to FSUIPC. And I did. I was trying to assign (I hope the wordings is right, huh..) controls in FSUIPC and calibrate them as well inside of FSUIPC. I left FS alone.

I hope at this time I explained my problem better. If not, please be patient to me, I am still learning. Thank you.

[Pete Dowson]

... and all my problems with controls would go away.

So you had problems before? Oh, that's different! You seemed to be saying that FSUIPC was the cause of all your problems!

One of the suggestion was: “Important: Delete all the axis settings within FSX (ie aileron, elevator, rudder, throttles, brakes)

if you are assigning axes and buttons in FSUIPC you mst not also have them assigned in FS. They will conflict, as i said. that is all that means. In fact because of FS's habit of automatically assigning things if it thinks they are newly attached, it is better to disable the controllers in FS rather than simply unassign everything. Quicker too!

However, this is only if you ARE assignbing in FSUIPC. First you need a reason to do that. Most of the benefits of FSUIPC control handling come not from the assignment facilities but from the more precise calibrations you can achieve and the control over axis effectiveness over its range. That can be done with all the standard aircraft controls without any reassignments.

It is a bit wierd that the elevator, throttles, aileron and rudder are set up then calibrated in 2 separate tabs within FSUIPC

Huh? if you think that you are completely misunderstanding things. maybe English is not your main language?

Assignments, if needed, are on one tab. They are independent of calibrations, exacty as they are in FS -- FS doesn't even provide calibrations, but leaves that to Windows' Game Controlllers in the Windows Control Panel.

Assignment is the process of relating a hardware axis or button to a desired action in FS. FSUIPC offers three distinct ways of accomplishing that for joystick axes

-- assignment to standard FS controls, which is just like in FS except FSUIPC uses FS's actual interbal names for those controls, and lists ALL of them, not just those which microsoft exposed in its interface.

-- assignment direct to FSUIPC's own calibration interface, bypassing the FS controls and relating them directly to FSUIPC's calibrations only

-- assignment to FSUIPC offset changes. This last is very techncal and needs knowledge of the FSUIPC SDK details.

The assignment to normal FS controls will operate just like assignment in FS. Whether you then also calibrate is optional.

Calibration can be done for axis controls no matter how they are assigned. It is mandatory for the "direct" method of assignment for obvious reasons), but optional otherwise. And because it operates on standard FS controls it is irrelevant whether you assign in FSUIPC or in FSX.

This is why they are "separate tabs". They are completely separate functions and separately applicable! How is that "weird"?

Ihave yet to do FSUIPC mouse macros and buttons, I still use saitek smart-tech for buttons, but will use FSUIPC when I get around to it.” Manual states: “REASSIGNMENT OF THROTTLE QUADRANT AXES WITH FSUIPC” and steps how to that. So that’s why I said I was trying to assign throttles via FSUIPC. So I don’t know the right wording when I’m dealing with FSUIPC, if I should say Assign or Set up controls, axes…whatever. So my goal is to make my controls working. I was advised by many users to delete all the axis settings within FSX (ie aileron, elevator, rudder, throttles, brakes) and do that within FSUIPC and disable controls in FSX settings and I did that.

All this sounds as if you are following some third party advice and not bothering to use the FSUIPC User Manual which I provide for this purpose. Why not use the correct documentation? You seem to have just thoroughly confused yourself.

When I used FS calibration it messed up all throttle quadrant completely and folks on forums suggested me stop doing this within FSX and go with FSUIPC.

FS doesn't provide any calibration. Calibration for FS is done with the joysdtick makers own drivers, in Windows. I think you must have started out completely wrongly in the first place. Doesn't Saitek supply drivers? Doesn't it provide any documentation? If you start out with a mess then go on to compound it by making a further mess with software you never used before and by reading all sorts of evidently conflicting and misleading advice from third parties, what do you expect to result?

My advice is to go back to square one. Find the driver disk that came with your joysticks and things, read its documentation, get it working in FS with the default aircraft. Then and only then maybe improve everything by applying FSUIPC, and use the FSUIPC User Guide.

Sorry, but for me it was lack of information on original FSUIPC user guide came with download and I had to use additional one from SimSamurai.

Where on Earth do you find a lack of information? Are you sure you ever looked at the User Guide? It doesn't sound like you did. It isn't in the ZIP you downloaded, it is in the FSUIPC Documents folder inside your FSX modules folder -- in fact in exactly the place the Installation guide (which is in the Zip) tells you it is!

If you still want me to look at your settings so I can see what you've done wrong, don't forget to paste that INI file here. But I think you should also explain what the problems were that you were trying to solve in the first place. It sounds to me like that's the key!

Regards

Pete

[speedbird144]

OK Mr. Pete.

It’s been said a lot here. I really don’t want to post lengthy topics here but I still need help. I don’t want to make this place as a battlefield. I will try to do that again tomorrow and see what It does. I will reinstall all drivers again and re-check FS controls setting. Maybe I missed something (but I did it twice already). If still no progress I will probably show every step I did in details. When/if you have a time please share your thoughts with me.

I know where documentation is and I want you to help me. Will also try to paste INI file.

PS. “It is a bit wierd that the elevator, throttles, aileron and rudder are set up then calibrated in 2 separate tabs within FSUIPC…”

Q. Huh? if you think that you are completely misunderstanding things. maybe English is not your main language?

That was not my statement. One of the simmer is trying to help. I will ask him, if English is his first or fifth language. His is trying to help me and appreciate it. I cannot ignore a person who is trying to help. As for me, true, English is not my first one. I speak 4 languages, English is the second one. :)

Regards.

[Pete Dowson]

It’s been said a lot here. I really don’t want to post lengthy topics here but I still need help. I don’t want to make this place as a battlefield.

Battlefield? Sorry, I don't understand where you are coming from.

I AM trying to help. It seems you had problems with your controls and were seeking to fix them with FSUIPC. It seems you rather rushed into it, followed all sorts of potentially conflicting, or at least rather advanced, advice, got into deep waters, and the consequences are that you are confused, and are unable to explain enough to me to unconfuse anything.

This is why I think the only way forward is for you to explain what the ORIGINAL problems were. Maybe they are not fixable by FSUIPC after all. Once I know what the problems were I can advise on the best way to proceed. Starting from an extra complicated muddle, with me effectively having no real information at all, we are just wasting spce here. That's why the INI file contents would have been so useful -- I could have seen what you have done and at least sorted that out, if not your original problems whatever they were.

Unfortunately we are running out of time before my upcoming holiday. I am away from tomorrow evening (Friday 4th May) until Tuesday 15th May. Others may be able to step in and help, but if you want me to examine your INI file you'll need really to do it today, or at latest by early afternoon Friday, UK time.

Regards

Pete

[speedbird144]

[General]

UpdatedByVersion=4827

History=6JHR8D7OFFSFK905D70LE

AxesWrongRange=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

MouseWheelMove=No

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

DeleteVehiclesForAES=Yes

AutoScanDevices=Yes

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=3

MinIce=-1

UpperWindGusts=No

SuppressWindTurbulence=No

SuppressWindVariance=No

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=Yes

WhiteMessages=No

ShowPMcontrols=No

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=Yes

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=No

UseProfiles=Yes

EnableMouseLook=No

FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0

SimConnectUsed=10.0.61259.0

[JoyNames]

AutoAssignLetters=No

1=Saitek Pro Flight Rudder Pedals

1.GUID={CFEBAD70-87F2-11E1-8001-444553540000}

0=Saitek Pro Flight Yoke

0.GUID={B0246CE0-87F5-11E1-8002-444553540000}

[WideServer]

WideFSenabled=Yes

[sounds]

Path=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Sound\

Device1=Primary Sound Driver

Device2=Speakers / Headphones (IDT High Definition Audio CODEC)

Device3=Digital Output (S/PDIF) (IDT High Definition Audio CODEC)

Device4=Communications Headphones (IDT High Definition Audio CODEC)

[buttons]

ButtonRepeat=20,10

[AutoSave]

Next=1

Interval=60

Files=10

SaveOnGround=No

AutoSaveEnabled=No

[GPSout]

GPSoutEnabled=No

Port=COM0

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[GPSout2]

GPSoutEnabled=No

Port=<none set>

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[Axes]

0=0X,256,D,0,1,0,0

1=0Y,256,D,2,0,0,0

2=0Z,256,D,22,0,0,0

3=0U,256,D,0,9,0,0

4=0V,256,D,0,0,10,0

5=1X,256,D,7,0,0,0

6=1Y,256,D,8,0,0,0

7=1R,256,D,3,0,0,0

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

Aileron=-16380,-898,2853,16380

Elevator=16255,16255,16255,16380

Rudder=-16319,0,0,16128

LeftBrake=-16384,16383/16

RightBrake=-16384,16383/16

Throttle1=-16384,16383,16383,16383

Throttle2=0,16383,16383,16383

Spoilers=-16380,16380/16

Thank you

[Pete Dowson]

Okay. The relevant parts are just these:

1=Saitek Pro Flight Rudder Pedals

0=Saitek Pro Flight Yoke

[Axes]

0=0X,256,D,0,1,0,0

1=0Y,256,D,2,0,0,0

2=0Z,256,D,22,0,0,0

3=0U,256,D,0,9,0,0

4=0V,256,D,0,0,10,0

5=1X,256,D,7,0,0,0

6=1Y,256,D,8,0,0,0

7=1R,256,D,3,0,0,0

[JoystickCalibration]

Aileron=-16380,-898,2853,16380

Elevator=16255,16255,16255,16380

Rudder=-16319,0,0,16128

LeftBrake=-16384,16383/16

RightBrake=-16384,16383/16

Throttle1=-16384,16383,16383,16383

Throttle2=0,16383,16383,16383

Spoilers=-16380,16380/16

Your rudder pedals are joystick #0, but you have device 0 axes assigned to

0=0X,256,D,0,1,0,0 ailerons

1=0Y,256,D,2,0,0,0 elevator

2=0Z,256,D,22,0,0,0 spoilers

3=0U,256,D,0,9,0,0 throttle1

4=0V,256,D,0,0,10,0 throttle2

and your joystick #1, the yoke has:

5=1X,256,D,7,0,0,0 left brake

6=1Y,256,D,8,0,0,0 right brake

7=1R,256,D,3,0,0,0 rudder

So, it seems you swapped sockets for the two devices, or at least done something which made Wndows identify them differently.

To prevent this happening again you would be best using letters for the joystick IDs. FSUIPC then uses those strange "GUID" values, which are unique to each device, to track such changes. There is a chapter in the User Guide about this -- managing multiple devices. But for now I can fix it manually for you. I'll select "P" for pedals and "Y" for Yoke. Okay?

Replace these sections:

[JoyNames]

AutoAssignLetters=No

1=Saitek Pro Flight Rudder Pedals

1.GUID={CFEBAD70-87F2-11E1-8001-444553540000}

0=Saitek Pro Flight Yoke

0.GUID={B0246CE0-87F5-11E1-8002-444553540000}

P=Saitek Pro Flight Rudder Pedals

P.GUID={CFEBAD70-87F2-11E1-8001-444553540000}

Y=Saitek Pro Flight Yoke

Y.GUID={B0246CE0-87F5-11E1-8002-444553540000}

[Axes]

0=YX,256,D,0,1,0,0

1=YY,256,D,2,0,0,0

2=YZ,256,D,22,0,0,0

3=YU,256,D,0,9,0,0

4=YV,256,D,0,0,10,0

5=PX,256,D,7,0,0,0

6=PY,256,D,8,0,0,0

7=PR,256,D,3,0,0,0

That's the main part sorted. Looking at your Calibrations:

Aileron=-16380,-898,2853,16380

That looks reasonable, except that the 16380 values for min and max are the defaults, so you've not really followed the steps and allowed a little leeway..

Elevator=16255,16255,16255,16380

That's totally up the creek. You need to calibrate the elevator properly. The values for minimum, and centre are all the same and so close to the maximum that you have no range or control at all.

Rudder=-16319,0,0,16128

That's okay, but i'd recommend a proper null zone around the centre to prevent unwanted rudder movement just because you rest your feet on them or the spring doesn't centre them correctly.

LeftBrake=-16384,16383/16

RightBrake=-16384,16383/16

They're okay except you need to allow some leeway -- i.e. you want the brakes to be definitely off with your feet off or only resting, so you need an null zone. The calibration steps in the User Guide advise you exactly how to do all this.

Throttle1=-16384,16383,16383,16383

Throttle2=0,16383,16383,16383

Those are very odd. You haven't selected the "No reverse zone" option (NRZ) for throttles, so I assume you want a reverse zone? But Throttle 1 seems to only have a reverse zone and no forward space because the idle area is set to be the same as the maximum.

Throttle2 has been calibrated incorrectly too, even more odd. It is only using half of the levers range and again only for reverse for the same reason.

Spoilers=-16380,16380/16

Okay, but no leeway for any variation in the lever input values. Those numbers are the defaults, in fact, so you've not actually followed the steps.

Please, after correcting the assignments as I suggested above, go through each axis and follow the numbered steps in the Calibration chapter of the User Guide. Proper calibration is essential to happy flying. If oyu don't calibrate correctly there really is no point in using FSUIPC for your controls.

I don't know what your original problems were, but the main problems you presumably came here about were all because of the swapping of the two devices. Using letters will prevent that happening again If you add any more controls, assign them a letter too.

Once you've calibrated correctly you'll be okay. but note that some add-on aircraft won't like the way you've assigned ad calibrated your controls. You'll then probably need to start using Profiles so you can have specific differences for those aircraft.

Regards

Pete

[speedbird144]

Thank you. My Windows crashed few weeks ago and I had to start over. Maybe the was part of problem. Throttles were major issues. I will try to apply these adjustments for default aircraft. The final goal is to make it work in PMDG NGX. Thank you.

[Pete Dowson]

Thank you. My Windows crashed few weeks ago and I had to start over. Maybe the was part of problem. Throttles were major issues. I will try to apply these adjustments for default aircraft. The final goal is to make it work in PMDG NGX. Thank you.

Ah. The PMDG 737NGX is one of those which doesn't like the sort of throttle assignment you are making. For the NGX it appears you need to:

1. Assign to FS controls, not direct to FSUIPC calibration.

2. Either do not calibrate throttles in FSUIPC , or set "UseAxscontrolsForNRZ=Yes" in the INI (i.e. change the "no" to a "Yes").

3. If calibrating, calibrate with the NRZ (no reverse zone) option set.

You'll need to use some other method for reverse as the NGX does not support reverse on any axis at all. I think most Saitek users program the button on the levers (when you pull right back) to operate the "throttle1_decr" or "throttle2_decr" controls repeatedly when 'pressed', and the "thtottle1_Set" (or '2') with a parameter of zero when released. There are some better solutions, but since I am neither a Saitek nor PMDG user I can't really advise further. There have been plenty of threads here with working solutions. Do a search on "NGX", maybe?

Pete

[speedbird144]

Will it be easier for all of us if we forget about revers or I have to assign revers in anyway? I mean I can use button for revers thrust. If we can make full thrust and idle only will it be easier? I'll do research on PMDG as well.

Thank you.

[Pete Dowson]

Will it be easier for all of us if we forget about revers or I have to assign revers in anyway? I mean I can use button for revers thrust. If we can make full thrust and idle only will it be easier? I'll do research on PMDG as well.

The points I made in my last reply apply. As far as I know, the first two points (1 and 2) are needed for the NGX in any case. The last, for using the button for reverse, can of course apply to all aircraft -- but then so can the other two. by all means, program it now, for all aircraft, as if you were doing it for the NGX. See if that meets your needs.

I can't really make these choices for you, espcially since i don't have the same equipment or add-on aircraft. FSUIPC is a box of tools, a "Swiss Army Knife" application. You use the parts you want in the way you want to use them.

Regards

Pete

[speedbird144]

I though attaching file will be better.

Thank you.

FSUIPC.pdf

[Pete Dowson]

I though attaching file will be better.

Better for what?

What does "most reward position" mean?

By sending me a PDF I cannot quote parts of your text, but if there are no intermediate values between minimum and maximum then that usually means the levers are set, in Windows, to behave as on/off switches not smooth analogue axes. I seem to remember that this is a bug in the Saitek installers or similar and is fixed by a Registry patch. If this is the problem you had originally, before trying FSUIPC, then I can understand your frustration -- which should actually be vented at Saitek. Check their forum anyway. I'm sure this is a subject which crops up regularly.

Incidentally, also in your "pdf" you say you are now "dealing with PMDG". If you mean the NGX, then I notice you've not set the "No reverse zone" option, and you are still assigning "direct", which won't work correctly with the NGX. I told you the three things you'd need to change for that.

You say "reverser seems to be working"! On an axis? Different axes?

Pete

[speedbird144]

Better for what?

What does "most reward position" mean?

By sending me a PDF I cannot quote parts of your text, but if there are no intermediate values between minimum and maximum then that usually means the levers are set, in Windows, to behave as on/off switches not smooth analogue axes. I seem to remember that this is a bug in the Saitek installers or similar and is fixed by a Registry patch. If this is the problem you had originally, before trying FSUIPC, then I can understand your frustration -- which should actually be vented at Saitek. Check their forum anyway. I'm sure this is a subject which crops up regularly.

Incidentally, also in your "pdf" you say you are now "dealing with PMDG". If you mean the NGX, then I notice you've not set the "No reverse zone" option, and you are still assigning "direct", which won't work correctly with the NGX. I told you the three things you'd need to change for that.

You say "reverser seems to be working"! On an axis? Different axes?

Pete

I was trying to save space here...

Yes, it is NGX.

Saitek forum is locked, currently they do not accept new registration due to spam issues. I'll try to email tech support.

When I adjusted INI file as you suggested thrust reverses started working. When I place throttler into full reward (aft) position below friction notch, reverses levers pull to On position and I can see engine thrust drops as supposed to. It means to me reverse is working.

Q.I seem to remember that this is a bug in the Saitek installers or similar and is fixed by a Registry patch. If this is the problem you had originally, before trying FSUIPC, then I can understand your frustration -- which should actually be vented at Saitek.

It could be bug but everything worked perfect until the day when I had to re-install FSX and was trying to set up controls from the beginning. It is really frustrating.

Q. You say "reverser seems to be working"! On an axis? Different axes?

Different axes.

I have checked throttle lever movements via saitke profile editor and they are moving smooth, no spikes. Saitek says if all controls movement has normal indications in Profile editor, it means controls working fine.

[Pete Dowson]

When I adjusted INI file as you suggested thrust reverses started working. When I place throttler into full reward (aft) position below friction notch, reverses levers pull to On position and I can see engine thrust drops as supposed to. It means to me reverse is working.

As far as I know there is no axis change before that 'notch'. I thought all pulling back further did was press the button. So if that is the case it sounds like either you've programmed at button for throttle decrements, or it has automatically been assigned that way -- maybe via Saitek's own software?

Sorry, but I think from now you are dealing with Saitek-specific matters with which I cannot help.

It could be bug but everything worked perfect until the day when I had to re-install FSX and was trying to set up controls from the beginning. It is really frustrating.

Yes, but the reinstalling of something -- Windows? Saitek? Has certainly intriduced it. I'm sure there's a registry change you can make to fix it. There may be a thread somewhere in this Forum which mentins it, but otherwise you certainly need Saitek support or Forum.

I have checked throttle lever movements via saitke profile editor and they are moving smooth, no spikes. Saitek says if all controls movement has normal indications in Profile editor, it means controls working fine.

Aha, so you are trying to use Saitek software for assigning and controlling things AND FSUIPC too? There may be some conflict from using both.

I'm afraid I've run out of ideas now. Everything I've told you is correct as far as FSUIPC is concerned. I wouldn't touch Saitek hardware at all, I have a very low opinion of Saitek I'm afraid. But I think you need to get things sorted out first. If the throttles don't work in FSX without FSUIPC there's no chance of them working with it either. It isn't a fix for bad hardware or drivers.

[LATER]

I searched this Forum on the word "registry" and soon came up with this from one "jase439":

Thank you for the tip! I just needed to add "registry fix" to my search and I dropped right in on the solution. I applied the registry "tweak" and it worked like a champ. Also got rid of alot of spurious noise I was getting in the neutral positions on the yoke!

Should anyone else experience this issue, you can find the answer here:

http://www.saitekfor...ead.php?p=89502

In case you aren't allowed in that part of the Saitek forum either, I reproduce the critical part:

Try this recalibration fix

To recalibrate, first unplug the quadrant.

Go to start/run and type regedit.

The registry editor will have a list of folders on the left hand side. Go down into the following folders in order.

HKEY_LOCAL_MACHINE (CURRENT_USER if on VISTA)

System

CurrentControlSet

Control

Media Properties

Private Properties

Direct Input

Inside the Direct Input folder, delete any folder that begins VID_06A3.

Once done, close the editor. Plug the quadrnat back in and move all the axes through their full range of movement 4 times.

I think that'll be HKEY_CURRENT_USER on Win7 too, but check both.

Regards

Pete

[speedbird144]

Q. Aha, so you are trying to use Saitek software for assigning and controlling things AND FSUIPC too? There may be some conflict from using both.

Saitek said it was not really calibrating until you hit OK, that editior may be used for controls checking before actually applying calibration. Well. Thanks for all your help. I will go ahead and spend some time with Saitek to see, may be there is something wrong with registry (like you said) or something else. May be I'll buy another throttle quadrant (other than Saitek). Wil see.

Thank you.

[Pete Dowson]

Q. Aha, so you are trying to use Saitek software for assigning and controlling things AND FSUIPC too? There may be some conflict from using both.

Saitek said it was not really calibrating until you hit OK, that editior may be used for controls checking before actually applying calibration. Well. Thanks for all your help. I will go ahead and spend some time with Saitek to see, may be there is something wrong with registry (like you said) or something else. May be I'll buy another throttle quadrant (other than Saitek). Wil see.

Thank you.

Try that registry trick I gave above. That was from a Saitek support guy.

Pete

[speedbird144]

OK. I did registry trick and not sure if it helped.

I'll try to use plain language. What I have found is when I assign the left lever of TQ to Throttle 1, Throttle 2, for both Engines at the same time (Throttle mode in the tab) or spoiler it works fine and smooth with no spikes. When I assign the middle lever to Throttle 1/2 or right lever to Throttle 1/2 (was trying to swap each other to see if it works) so they do not work. If assign middle or right lever for just Throttle (not separate) or for speedbrake they both works but with spikes, no smooth movements.

I used options Send to FSUIPC, because with Send to FS do not work.

As for No reverse zone" option, I enable it, no difference with middle and right lever. Work with the left lever.

I ran myself in a deep forest and I am trying to understand what the heck I've done. :shock:

[Pete Dowson]

I'll try to use plain language. What I have found is when I assign the left lever of TQ to Throttle 1, Throttle 2, for both Engines at the same time (Throttle mode in the tab) or spoiler it works fine and smooth with no spikes. When I assign the middle lever to Throttle 1/2 or right lever to Throttle 1/2 (was trying to swap each other to see if it works) so they do not work. If assign middle or right lever for just Throttle (not separate) or for speedbrake they both works but with spikes, no smooth movements.

You most certainly either have double assignments to some levers (i.e. assigned in FSUIPC and also in FS), or your hardware is broken. To deal with the former, go to FS's control assignments and disable all controllers. To deal with bad hardware (and there seems to be a lot about) you need to go to Saitek.

I used options Send to FSUIPC, because with Send to FS do not work.

Send to FS is FAR more likely to work than Send Direct. If Send to FS, assigning to the controls called "Axis throttle ..." etc (axis as first word) does not work then you most certainly have a corrupted FS installation, because that is the same as assigning in FS. No difference at all.

I recommend you delete the FSUIPC4.INI file from the FSX Modules folder so that all your messing about is removed, then assign things in FSX first and get things working there. You still have not yet explained why you are assigning in FSUIPC in any case. Maybe you don't need to. When you explain that maybe we can proceed further. But get things working normally first, else there is no point in continuing.

Regards

Pete