FSUIPC4 Build 4062 and Controller Assignments

[RichardL]

Hi Pete,

I'm seeing a minor issue with build 4062 and joystick assignments. This is happening since installing 4062.

No axis is assigned or enabled in FSX. I do all the axis assignments and calibration with FSUIPC.

Every time I start FSX, no axis controllers (yoke, rudder, throttles) work. I have to go into FSUIPC controller assignments and rescan one axis. After that they all work again. Odd but that's how it happens. I read in the notes that you may have to assign them again, but isn't that only if you select Direct mode?

Regards,

Richard

[Pete Dowson]

Ah. The very first feedback after changing over to DirectInput! Thanks. I need some -- all my axes are PFC via the PFC driver so I don't get to use these facilities myself.

Every time I start FSX, no axis controllers (yoke, rudder, throttles) work. I have to go into FSUIPC controller assignments and rescan one axis. After that they all work again. Odd but that's how it happens.

Hmmm. Sounds like the call the create the DirectInput device isn't being made. Strange.

I should be able to trace that through. Could you show me the [Axes] section or sections from your FSUIPC4.INI file please?

I read in the notes that you may have to assign them again

Well, calibrate again, possibly, as I'm not sure whether DirectInput reads them the same way -- probably depends on the "HID" drivers for the joysticks, so it would vary. The only ones which might need re-assignment are those which were classified as "Z U or V" axes which may, in DirectInput terms, be "Sliders" (S and T in my notation). The most likely candidate is a slider throttle, Z before, S now.

But even if you needed to do that the values should "stick" not need doing each time you load FSX. I need to fix that -- it will be something to do with the initialisation.

... but isn't that only if you select Direct mode?

4.062 Axis Assignment IS using DirectInput. There's no old code not using DirectInput. I can't have both sets of code in there.

If you mean "direct assignment to FSUIPC's calibrated axes" as opposed to assignment to FS controls, then, no -- that determines where the results get sent, not how they are obtained.

I'll check it, find it and fix it as soon as I can, but give me your settings please in case it is specific for some reason.

Thanks,

Pete

[RichardL]

Pete,

Here you are:

[Axes]

0=0X,256,D,9,0,0,0

1=0Y,256,D,10,0,0,0

2=0Z,256,D,17,0,0,0

3=0R,256,D,14,0,0,0

4=0U,256,D,18,0,0,0

5=0V,256,D,13,0,0,0

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

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

8=1Z,256,D,3,0,0,0

9=2X,256,D,1,0,0,0

10=2Y,256,D,2,0,0,0

And just incase you need it:

[JoystickCalibration]

ExclThrottleSet=No

SepRevsJetsOnly=No

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

MaxSteerSpeed=60

Aileron=-15309,-1880,1412,15819

Elevator=-13607,-3055,3223,15041

Rudder=-15335,-1180,1180,15990/16

PropPitch=-16380,16380

LeftBrake=-15351,-258/16

RightBrake=-15609,-258/16

Throttle1=-15671,-10507,-7301,15679

Throttle2=-15831,-11045,-7916,15831

Mixture1=-15291,-10194,-7828,14927

Mixture2=-15303,-10082,-6841,15123

PropPitch1=-14543,-11597,-8836,14381

PropPitch2=-14247,-12288,-8726,14798

SlopeLeftBrake=12

SlopeRightBrake=12

Richard

[Pete Dowson]

Here you are:

Thanks, but didn't you receive the 4.063 version I emailed you soon after my message? I think I found out why the initialisation wasn't occurring correctly, and asked you to check it with that version.

Pete

[RichardL]

No, never received it. I'll send you one in case the address is wrong.

Richard

[Pete Dowson]

No, never received it. I'll send you one in case the address is wrong.

I sent it to the email address you use here (us moderators can see them). I've received nothing from you yet. Did you send something already?

Regards

Pete

[RichardL]

Consider that issue fixed with 4063.

I launched FSX a few times and each controller axis is staying assigned and functioning.

Thanks Pete,

Richard

[Pete Dowson]

Consider that issue fixed with 4063.

Good.

I'll wrap the Installer around it and put it up here insttead of 4.062.

Regards,

Pete