FSUIPC Sends Double Commands

[jdriskell]

I'm running Win 8, FSX Gold and PMDG 737 NGX. I've set up FSUIPC 4.88 (licensed) to control my CH Yoke, Throttle Quad and Peddles. Recently I've been getting strange results when I press various buttons. Pressing the button for flaps down incrementally causes the flaps to jump two notches. Flaps up incrementally either doesn't work or produces forty degrees of flaps. I've reset the buttons but no joy. I also have a button that should cycle thru various views (the same as pressing "S") but the button causes the view to jump thru one view and settle on the next view. I want to use the buttons but until I figure out the problem, I'll use key strokes and hot spots.

Any ideas?

Jim Driskell

[Pete Dowson]

I'm running Win 8, FSX Gold and PMDG 737 NGX. I've set up FSUIPC 4.88 (licensed) to control my CH Yoke, Throttle Quad and Peddles. Recently I've been getting strange results when I press various buttons. Pressing the button for flaps down incrementally causes the flaps to jump two notches. Flaps up incrementally either doesn't work or produces forty degrees of flaps. I've reset the buttons but no joy. I also have a button that should cycle thru various views (the same as pressing "S") but the button causes the view to jump thru one view and settle on the next view.

It sounds exactly like you have multiple assignments to the same buttons, probably in FS and in FSUIPC. You must use one or the other for buttons.

Pete

[jdriskell]

You are absolutely right. For some reason, I fat fingered the check box in FSX and reactivated its controls. Maybe too much Glenfiddich 0:)

Thanks,

Jim Driskell

[DEN19]

Jim

Try a decent whisky, like Laphroag!

0:)

[jdriskell]

Too smokey. I prefer Lagavulin but it costs $$$$ :o)

Jim Driskell

[Pete Dowson]

Too smokey. I prefer Lagavulin but it costs $$$$ :o)

The Macallan was always my favourite, but I don't touch spirits these days! ;-)

Pete

[qqwertz]

I definitely did not drink too much Bruichladdich, but I have the same problem: under Win 8 I assigned some buttons on my Saitek yoke via FSUIPC (registered) for trim. However, these buttons also raise/lower the gear and flaps, even though I was careful to delete all button assignments (both in normal and slew mode) for the yoke in FSX itself.

If that may have something to do with it: my default flight is for the Majestic Dash 8.

Thanks,

Peter

[Pete Dowson]

I assigned some buttons on my Saitek yoke via FSUIPC (registered) for trim. However, these buttons also raise/lower the gear and flaps, even though I was careful to delete all button assignments (both in normal and slew mode) for the yoke in FSX itself.

Did you disable controllers in FSX? If not try that and re-test. FSX has a habit of automatically re-assigning things if it thinks the connection is new for any reason. If you still have double assignments with controllers disabled in FSX, and you aren't running Saitek's own software (which I believe can also make assignments?), then you'll need to show me your FSUIPC4 ini file -- at least all of the [buttons] sections, and also tell me which buttons have the problem (joystick and button numbers).

You could also check things for yourself by using the FSUIPC4 logging facilities -- try both the Button and the Event (non-axis) logging options.

Regards

Pete

[qqwertz]

Did you disable controllers in FSX?

Hi Pete,

yes, I made sure that under FSX settings all button (and axis) assignments for the Saitek yoke are deleted, both in normal and in slew mode. I verified that there were no assignments even after several restarts of FSX. I never installed the Saitek software.

I have a double assignment for Aileron trim right / gear toggle and elevator trim / flaps. All other assignments work perfectly. In the log file these events look as follows:

158157 Button changed: bRef=0, Joy=0, Btn=7, Pressed

158157 [buttons] 22=R0,7,C66277,0

158157 Repeating flag set: bRef=0, Joy=0, Btn=7 (RepeatDelayCtr=1)

158157 FS Control Sent: Ctrl=66277, Param=0

158157 *** EVENT: Cntrl= 66277 (0x000102e5), Param= 0 (0x00000000) AILERON_TRIM_RIGHT

158157 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE

152610 Button changed: bRef=0, Joy=0, Btn=4, Pressed

152610 [buttons] 6=R0,4,C65607,0

152610 Repeating flag set: bRef=0, Joy=0, Btn=4 (RepeatDelayCtr=1)

152610 FS Control Sent: Ctrl=65607, Param=0

152610 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN

152610 *** EVENT: Cntrl= 65758 (0x000100de), Param= 0 (0x00000000) FLAPS_INCR

The corresponding settings in FSUIPC.ini are

6=R0,4,C65607,0

22=R0,7,C66277,0

Thanks for looking into this,

Peter

[Pete Dowson]

yes, I made sure that under FSX settings all button (and axis) assignments for the Saitek yoke are deleted, both in normal and in slew mode. I verified that there were no assignments even after several restarts of FSX. I never installed the Saitek software.

I still suggest you test with FSX controllers actually disabled. It's easy enough to do and loses nothing. After the test, if you wish, you can re-enable them.

I have a double assignment for Aileron trim right / gear toggle and elevator trim / flaps. All other assignments work perfectly. In the log file these events look as follows:

158157 Button changed: bRef=0, Joy=0, Btn=7, Pressed

158157 [buttons] 22=R0,7,C66277,0

158157 Repeating flag set: bRef=0, Joy=0, Btn=7 (RepeatDelayCtr=1)

158157 FS Control Sent: Ctrl=66277, Param=0

158157 *** EVENT: Cntrl= 66277 (0x000102e5), Param= 0 (0x00000000) AILERON_TRIM_RIGHT

158157 *** EVENT: Cntrl= 65570 (0x00010022), Param= 0 (0x00000000) GEAR_TOGGLE

152610 Button changed: bRef=0, Joy=0, Btn=4, Pressed

152610 [buttons] 6=R0,4,C65607,0

152610 Repeating flag set: bRef=0, Joy=0, Btn=4 (RepeatDelayCtr=1)

152610 FS Control Sent: Ctrl=65607, Param=0

152610 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN

152610 *** EVENT: Cntrl= 65758 (0x000100de), Param= 0 (0x00000000) FLAPS_INCR

Okay, so this shows conclusively that FSUIPC is sending just the one control, but two events are being seen. The others are NOT from FSUIPC, so must be either from FSX or some other software.

There is no way I can determine what other software they are from, but I still think the most likely source is FSX. I think this is made even more likely by the fact that the default FSX assignments ("Standard.XML") include these two:

	  <Entry>
		    <Index>7</Index>
		    <Down>GEAR_TOGGLE</Down>
	    </Entry>
 [/CODE]

i.e. button 7 = GEAR_TOGGLE, and

[CODE] <Entry>
<Index>4</Index>
<Down>FLAPS_INCR</Down>
</Entry>[/CODE]

i.e. button 4 = FLAPS_INCR.

So, your "I verified that there were no assignments" was not very complete, I think!

Anyway, always try disabling controllers in FSX. It's the only way to prove it one way or the other.

Regards

Pete

[qqwertz]

Hi Pete,

wow, you're fast. Thanks for replying so quickly.

I still suggest you test with FSX controllers actually disabled.

Ooops. I thought you meant removing all button assignments, I never realized that you actually could disable the controllers completely in FSX :oops:

I just did that and the double assignment is indeed fixed. However, it appears I can only disable all controllers together. I therefore also lost the mouse controls, which I use very often to change the view (with the space bar held down). Is there a way to disable individual controllers or to use FSUIPC to get this back (I tried to assign "mouse look" and "mouselook" but it didn't work)?

Thanks,

Peter

[Pete Dowson]

I just did that and the double assignment is indeed fixed. However, it appears I can only disable all controllers together. I therefore also lost the mouse controls, which I use very often to change the view (with the space bar held down). Is there a way to disable individual controllers or to use FSUIPC to get this back (I tried to assign "mouse look" and "mouselook" but it didn't work)?

Mouse trim, mouse move and mouse look options are described in the User Guide and shown on the Miscellaneous options tab.

Pete

[qqwertz]

Thanks Pete,

that solved my problems.

Cheers,

Peter