FSUIPC 4.6x, Windows7_64 and Flap Detents

[UTF]

My FUSIPC 4.60 runs under Vista 64 smoothly without any problem, not so in my recently built system with Windows7 64.

First I couldn’t properly install 4.60, the installation couldn’t find FSX.cfg, the installation of 4.638 solved this problem. But I am still unable to calibrate my detents.

I am using CH controls (eclipse yoke, quad throttle, rudder pedals). The axis assignment poses no problem; I am getting the numeric display of the lever positions and can put in the data for the up and down values.

If I try to calibrate the detents according to pages 54/55 of the manual I get no input whatsoever if I move the lever. As a result the flaps move either entirely up or entirely down or don’t move at all in the cockpit situation.

I tried to input the data for FlapStarts, FlapEnds and FlapDetents directly into the .INI without any success.

I also checked the DLL.xml for any problems, but there were none.

No I am pretty much lost!

Can Pete or anybody help?

BTW installation of 4.656 didn’t help either.

[Pete Dowson]

My FUSIPC 4.60 runs under Vista 64 smoothly without any problem, not so in my recently built system with Windows7 64.

First I couldn’t properly install 4.60, the installation couldn’t find FSX.cfg, the installation of 4.638 solved this problem.

There's little difference in how FSUIPC4 finds FSX.CFG in the two installers. It is always via the AppData\Roaming\Microsoft\FSX folder in the "Users" section. The only addition in the later installer was to search the "all users" section as well.

If I try to calibrate the detents according to pages 54/55 of the manual I get no input whatsoever if I move the lever.

you are doing it incorrectly then. You must calibrate the lever normally first, with the correct minimum and maximum values. Then you use the detente's facility to define a zone around each of your flap positions. Do NOT try to limit the values too much around those positions.

As a result the flaps move either entirely up or entirely down or don’t move at all in the cockpit situation.

Show me the results of your attempts in the INI file and I'll tell you what is wrong with them.

How are you assigning the axis itself?

I also checked the DLL.xml for any problems, but there were none.

since FSUIPC is obviously running that isn't surprising!

BTW installation of 4.656 didn’t help either.

Since it is something you are doing wrong, changing FSUIPC versions isn't going to help.

Please supply some actual information and I'll check.

Regards

Pete.

[UTF]

Hi Pete,

Thank you very much for your quick response!

I meanwhile realized that I am barking up the wrong tree.

I found a lot of references that the game controllers from CH-Products are not very well cooperating with Windows 7.

Now I have to find a solution in this arena.

Thanks again and regards,

Uwe

[UTF]

Hi Pete,

Here I am again and I am moving in circles!

Meanwhile I could convince myself that I don’t have a problem with my CH Products controllers and I am back to square one.

After four subsequent installations of FUSIPC 4.60 and FUSIPC 4.638 I can exactly reproduce the results, which I mentioned in my first blog. But let me elaborate a bit.

The difference between installations with the two versions is, that 4.60 tries to find FSX.cfg and can’t, whereas 4.638 claims to have found it. I am trying to attach the two installation logs. Surprisingly there is no difference in the behavior of the installed program itself.

In both cases I can easily assign buttons and I also can assign axes and calibrate them.

The problem starts when it comes to axes with up and down values, in my case for landing gear and flaps.

I didn’t do anything wrong because I couldn’t: The windows for data entries are frozen and don’t let me do anything.

It’s 4:00 am and I am tired. I will put together some documentation tomorrow. Please continue to watch this threat.

Regards,

Uwe

[Pete Dowson]

The difference between installations with the two versions is, that 4.60 tries to find FSX.cfg and can’t, whereas 4.638 claims to have found it.

Yes, because the newer installer looks in "All Users" too, and other users than the current one. The earlier one only fails if you don't install FSX for the current user.

The problem starts when it comes to axes with up and down values, in my case for landing gear and flaps.

Why are you using the up and down section for flaps? There's a perfectly good detente setting section in the calibration tabs, for use after you calibrate.

I didn’t do anything wrong because I couldn’t: The windows for data entries are frozen and don’t let me do anything.

Sorry, which windows where?

I still have no information from you, so I still cannot help.

Regards

Pete

[UTF]

Paul,

I never had any problems with all the versions of FSUIPC over many, many years. The program always performed perfectly in combination with my CH-Products controllers in Windows XP as well as with Vista 64 until I migrated to Windows7_64.

After having had a good nights rest I found out that FSUIPC seemingly just works fine but the data transfer to my CH Throttle Quadrant doesn’t work properly. I have to seek for a solution in the CH Forum.

I apologize for pestering you and I am checking out for the time being. If and when I am able to resolve my problems I let you know.

Best regards,

Uwe.

[Pete Dowson]

I found out that FSUIPC seemingly just works fine but the data transfer to my CH Throttle Quadrant doesn’t work properly. I have to seek for a solution in the CH Forum.

I'm not sure what data you are expecting to be transferred to a throttle quadrant. Normally it is the other way around, that the quadrant sends data to FS.

Regards

Pete

[UTF]

Pete,

I am still trying to get my problem resolved and I am waiting for advice from the CH people.

Here are a short update and a clarification:

As I mentioned, I have FSX Acceleration and FSUIPC 4.60 installed in a Vista 64 based system. No problem there. This is my hardware:

CPU: Intel Core2 Quad Q9550 2.83 GHz no OC

MB: Asus P5Q-E

RAM: 8 GB DDR2 (4x2 GB)

My new computer looks like this:

CPU: Intel Core i7 extreme 3.33 GHz no OC

MB: Asus P6X58D Premium

RAM: 16 GB DDR3 (4x4 GB Corsair Dominator)

To narrow down the possibilities I disconnected my OS with Windows 7_64 HDD completely and installed an OS with Vista 64 on a new HDD. But to my surprise I ended up with exactly the same problem, which I had before!

I conclude, that the CH Control Manager for an unknown reason seems not to be fully compatible with my new system.

Now some clarification when I was writing ”I didn’t do anything wrong because I couldn’t: The windows for data entry are frozen and don’t let me do anything”.

To illustrate my point I try to attach a screenshot of the joystick calibration screen, where I marked the “frozen window for data entry” with a red circle.

I can toggle toggle through the detents from #1 to #7. But I never get any reaction when I move the supposed flap lever, the zeroes always remain zeroes.

Now a short remark to the axis assignment for my gear lever: I can program the lever as usual, but the results are pretty erratic. Sometimes the lever works, sometimes it works for a while, sometimes not at all. This behavior seems to indicate again, that the CH Control Manager probably is not fully compatible with my new system.

Ok, that’s where matters stand right now. I wait and see.

Regards,

Uwe

[Pete Dowson]

I conclude, that the CH Control Manager for an unknown reason seems not to be fully compatible with my new system.

Have you tried without this "CH Control Manager"? Certainly FSUIPC doesn't need it, and there may be conflicts for all I know.

Have you tried the CH Hangar at all? http://www.ch-hangar.com/ .

Now some clarification when I was writing ”I didn’t do anything wrong because I couldn’t: The windows for data entry are frozen and don’t let me do anything”.

To illustrate my point I try to attach a screenshot of the joystick calibration screen, where I marked the “frozen window for data entry” with a red circle.

Well, please start again -- clear the detentes, because your current detente #1 (the centre pair of values) runs from 1 to 16380 as far as I can read on that graphic. That removes any possible scope for calibration. Press the Reset button and start again.

I can toggle toggle through the detents from #1 to #7. But I never get any reaction when I move the supposed flap lever, the zeroes always remain zeroes.

And this happens on all axes, all axis assignments?

Where are you assigning the flaps lever, and to what control? In an earlier message you stated:

In both cases I can easily assign buttons and I also can assign axes and calibrate them.

The problem starts when it comes to axes with up and down values, in my case for landing gear and flaps.

which still makes no sense to me, because an axis is an axis which is an axis! Your odd reference to "landing gear and flaps" in the same sentence as "up and down values" is of concern, because there is NO landing gear axis, but there IS a flaps axis, which is what you should be using. You cannot calibrate landing gear up and down controls, nor any "inc" and "dec" controls. You can only calibrate genuine axis controls, as it is only they which provide any parameter (other than 0) to be calibrated!

Therefore I think you are misunderstanding "flaps".and are not even assigning to a flaps axis at all!

Why not show me your FSUIPC4.INI file (paste it into a message) so I can see what sort of mess you have made. I'm sure it is all something you are completely confused about.

Regards

Pete

[UTF]

Pete,

Thank you for your patience with a total idiot!

The whole thing is still beyond me.

I am using FSX/FSX Acceleration with the combination of CH Yoke/Yoke Eclipse, Quad Throttle and Rudder Pedals together with FSUIPCs 3/4 and the CH Control Manager for ten years. I was carrying this setup through multiple upgrades of my Motherboard, CPUs and OS without any problem.

Before I make any of your recommended changes, here are my answers to your last reply together with my FSUIPC4.INI as it exists right now.

Posted Today, 04:28 AM

UTF, on Yesterday, 09:58 PM, said:

I conclude, that the CH Control Manager for an unknown reason seems not to be fully compatible with my new system.

Have you tried without this "CH Control Manager"? Certainly FSUIPC doesn't need it, and there may be conflicts for all I know.

Have you tried the CH Hangar at all? http://www.ch-hangar.com/ .

Yes, I did but no response so far.

Now some clarification when I was writing ”I didn’t do anything wrong because I couldn’t: The windows for data entry are frozen and don’t let me do anything”.

To illustrate my point I try to attach a screenshot of the joystick calibration screen, where I marked the “frozen window for data entry” with a red circle.

Well, please start again -- clear the detentes, because your current detente #1 (the centre pair of values) runs from 1 to 16380 as far as I can read on that graphic. That removes any possible scope for calibration. Press the Reset button and start again.

I can toggle toggle through the detents from #1 to #7. But I never get any reaction when I move the supposed flap lever, the zeroes always remain zeroes.

And this happens on all axes, all axis assignments?

No, only with the flap lever.

Where are you assigning the flaps lever, and to what control? In an earlier message you stated:

In both cases I can easily assign buttons and I also can assign axes and calibrate them.

The problem starts when it comes to axes with up and down values, in my case for landing gear and flaps.

which still makes no sense to me, because an axis is an axis which is an axis! Your odd reference to "landing gear and flaps" in the same sentence as "up and down values" is of concern, because there is NO landing gear axis, but there IS a flaps axis, which is what you should be using. You cannot calibrate landing gear up and down controls, nor any "inc" and "dec" controls. You can only calibrate genuine axis controls, as it is only they which provide any parameter (other than 0) to be calibrated!

I am going straight to the axis calibration and try to emulate the flaps settings for the B 737.

Therefore I think you are misunderstanding "flaps".and are not even assigning to a flaps axis at all!

Why not show me your FSUIPC4.INI file (paste it into a message) so I can see what sort of mess you have made. I'm sure it is all something you are completely confused about.

Regards

Pete

Here is my messed up FSUIPC4.INI with nothing else than gear and flaps entered:

[General]

UpdatedByVersion=4637

History=96Y9Z0JRXRU4XFQOESK5X

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

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=No

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=No

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=No

UseProfiles=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

GetNearestAirports=No

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

[JoyNames]

AutoAssignLetters=No

0=CH ECLIPSE YOKE

0.GUID={D493EFC0-2765-11E0-8001-444553540000}

1=CH PRO PEDALS USB

1.GUID={546F9AC0-27E1-11E0-8001-444553540000}

2=CH THROTTLE QUADRANT

2.GUID={D493EFC0-2765-11E0-8002-444553540000}

[buttons]

ButtonRepeat=20,10

[AutoSave]

AutoSaveEnabled=No

[GPSout]

GPSoutEnabled=No

[GPSout2]

GPSoutEnabled=No

[WideServer]

WideFSenabled=Yes

[sounds]

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

Device1=Primary Sound Driver

Device2=Speakers (Realtek High Definition Audio)

Device3=Realtek Digital Output(Optical) (Realtek High Definition Audio)

Device4=Realtek Digital Output (Realtek High Definition Audio)

[Axes]

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

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

2=0U,256,D,5,0,0,0

3=0V,256,D,6,0,0,0

4=2R,256

5=2R,B,-10922,14720,65595,0,65603,0

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=Yes

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

Flaps=0,16380

FlapStarts=-16384,1,16381,16379,16379,16379,16379,16379,16379

FlapEnds=0,16380,16378,16378,16378,16378,16378,16378,16384

Now I try to make my changes and I will report back thereafter.

Regards,

Uwe

[UTF]

Pete,

That was fast and unsuccessful!

Step 1: I need the control manager to calibrate all six axes of my quad throttle; FSX sees only four of them. I uninstalled the CM anyhow, cleared all detents in the flap calibration, reset and tried to calibrate again. No reaction whatsoever, total snafu.

Step 2: Reinstallation of the CM, then same procedure as above with identical results i.e. none.

Step 3: Shut down the computer mildly steaming.

BTW my explanations are sometimes pretty clumsy. For the assignment of a lever for “gear up” and “gear down” I use the right field of the axis calibration window, which is assigning buttons and no axes. Ok I stand corrected.

So, that’s it for now.

Regards,

Uwe.

[UTF]

Pete,

Just a few more sentences.

The result of step 1 seems to indicate that the CM isn’t the culprit!?

During one of my test runs I disabled the joystick control in FSX to run on a clean CM control. Result: No success.

Question: Where do I go from there?

Regards,

Uwe.

[Pete Dowson]

I can toggle toggle through the detents from #1 to #7. But I never get any reaction when I move the supposed flap lever, the zeroes always remain zeroes.

Have you assigned a flaps axis in FS at all, because, as this shows, you most certainly haven't assigned one in FSUIPC:

[Axes]

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

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

2=0U,256,D,5,0,0,0 =Prop pitch

3=0V,256,D,6,0,0,0 =Mixture

4=2R,256

5=2R,B,-10922,14720,65595,0,65603,0 =These two are assigned by range to the FLAPS UP and FLAPS DOWN buttons.

You also appear to have no Throttle assigned.

If you assign to the Flaps up and Flaps down buttons (same as keypresses), they are not calibratable because they are not axis inputs, as I keep telling you.

if you don't assign an axis to an axis control is doesn't operate like an axis control and you cannot calibrate it. Why didn't you read my last reply?

Here is my messed up FSUIPC4.INI with nothing else than gear and flaps entered:

There's no gear axis either, but an entry like your Flaps entry would actually make more sense for the gear because there is actually no gear axis control -- only gear up and gear down.

On your other message I'm afraid I cannot support the CH Control Manager, you need to talk to CH about that.

On the flaps, I don't want to hear any more from you whatsoever until you assign the flaps lever to the flaps -- on the LEFT hand side of the assignments, just as you obviously have done already for Aileron, Elevator, Proppitch and Mixture! [Why on Earth are you going daft with the flaps instead of treating it like the other axes? It makes no sense and I don't want to have ot repeat all this again].

:roll:: :roll:: :roll:

Pete

[UTF]

Pete,

I don’t know what bit me, I am deeply embarrassed but everything runs smoothly now!

Thanks,

Uwe.

[Pete Dowson]

... everything runs smoothly now!

Good. I am pleased you got it all sorted!

Pete