Can't get keystroke mapped

[PDXMike]

I have the registed version of FSUIPC (4.81), and have been trying out mapping my G940 joysticks via FSUIPC. Everything seems to have gone pretty well up until I tried to get the same results with FSUIPC as I was getting with the Logitech drivers.

I'm trying to map the throttle POV to zoom my view in and out. I can get the zoom out working by assigning Joy #1 Axis Q as range 1 from 0 to 270, and "control sent when range entered as a "Key Press/hold" with a parameter of 187+8 . But setting the range 2 to from 0 to 90 and then using the parameter of 189+8 nothing happens!.

I have a Logitech G11 keyboard, and I did note the note in the advanced manual that lists the keystroke codes, that these may be different from keyboard to keyboard, but I can't figure out how to tell what code to use for the "=/+" key. Apparently it is NOT 189. the "-/_" key IS mapped to 187 though.

How do I tell what code to use based on my keyboard?

Thanks,

Mike

[Pete Dowson]

I'm trying to map the throttle POV to zoom my view in and out. I can get the zoom out working by assigning Joy #1 Axis Q as range 1 from 0 to 270, and "control sent when range entered as a "Key Press/hold" with a parameter of 187+8 . But setting the range 2 to from 0 to 90 and then using the parameter of 189+8 nothing happens!.

Sorry, but i'm completely bemused by what you are wanting to do here. You are using the POV as an Axis but mapping it to keystrokes? Why such a complex round-about method?

First, the FS keystrokes are merely mapped to FS controls -- Zoom in and Zoom out. Just assign to the controls directly.

Second, FSUIPC can treat the POV as a lmited tyoe of axis, or as a set of buttons. If you want to use the Zoom In and Zoom Out controls it would be far far easier to assign the POV in the Buttons tab, directly to the correct controls.

If you did want to use an axis for Zoom, then consider using the View Zoom Set control instead, as a direct axis assignment. That's a little more complicated as you'd need to scale the axis input values suitably to get a decent zoom range. There's another recent thread about that here inn the Forum somewhere below.

BTW you can always find out what controls to use by using the Event logging facilities (FSUIPC's Logging tab), operating the facilities on screen or with the keyboard, and seeing what gets logged. You can even do that in real time by enabling the console log window, and running FSX (temporarily) in a smaller Wndowed mode.

Pete

[PDXMike]

Sorry, but i'm completely bemused by what you are wanting to do here. You are using the POV as an Axis but mapping it to keystrokes? Why such a complex round-about method?

First, the FS keystrokes are merely mapped to FS controls -- Zoom in and Zoom out. Just assign to the controls directly.

Second, FSUIPC can treat the POV as a lmited tyoe of axis, or as a set of buttons. If you want to use the Zoom In and Zoom Out controls it would be far far easier to assign the POV in the Buttons tab, directly to the correct controls.

If you did want to use an axis for Zoom, then consider using the View Zoom Set control instead, as a direct axis assignment. That's a little more complicated as you'd need to scale the axis input values suitably to get a decent zoom range. There's another recent thread about that here inn the Forum somewhere below.

BTW you can always find out what controls to use by using the Event logging facilities (FSUIPC's Logging tab), operating the facilities on screen or with the keyboard, and seeing what gets logged. You can even do that in real time by enabling the console log window, and running FSX (temporarily) in a smaller Wndowed mode.

Pete

Thanks for your quick reply!!

I guess I need to polish up my glasses! I could have sworn I looked all over the list of commands, and did not see the zoom.

I have it in place now. I tried using the button tab, but it does not recognize the POV on my throttle for some reason.

Thanks again,

Mike

[Pete Dowson]

I have it in place now. I tried using the button tab, but it does not recognize the POV on my throttle for some reason.

Ah, yes, because it ia axis "Q", the second POV not "P", the first. Sorry. The recognition of POVs as as set of 8 buttons, 32-39, derives from original FS98/2000 practice, and in those days only one POV was recognised by the system in any case.

Glad you sorted it out with the correct controls in any case.

Regards

Pete