Jump to content

Just a quick question


Recommended Posts

I don't have the pay version of FSUIPC :oops: (yet) but am now considering it. When you use the program FSUIPC to control your joysticks, what does FS "see" as a controller? Does it still "see" all the joysticks seperately or is there one controller listed with many buttons and axis'.

Thanks,

LouP

Link to comment
Share on other sites

When you use the program FSUIPC to control your joysticks, what does FS "see" as a controller? Does it still "see" all the joysticks seperately or is there one controller listed with many buttons and axis'.

Best to peruse the User guide -- you'll see from the text and pictures. Really the answer to your specific question isneither. It sees buttons and axes you move and it identifies them by the internal numbers the Windows joystick interface gives them -- 0 to 15 for joysticks, 0 to 31 for buttons on each joystick. For axes is converts the internal ids to one letter -- X Y Z R U V for the standard 6, for FSX another two, S and T, are recognised.

But you never really need to know the names or numbers as they are programed by detection.

FSUIPC treats Buttons separately from "axes" -- buttons include buttons and toggle switches, and also "hats" which are treated as 4 or 8 buttons (numbers 32 to 39). Axes are those inputs which provide a variable input value as they are moved - i.e. the traditional function of a joystick which had two axes, X and Y.

For buttons there are a variety of assignments and options associated with them. They are dected by opetaing them.

For Axes there are two distinct facilties in FSUIPC:

1. Calibrationwhich is simply taking an already-assigned axis, selected by FUNCTION, not by joystick or anything like that. The function might be Throttle, or Elevator, or Flap selection, but the assignment of what real axis does those functions is elsewhere -- either in FS's own assignments, or by using the other FSUIPC facility -- Axis Assignment.

2. Axis Assignment, which allows axes (detected by movement) to be assigned either to FS-defined functions, like FS does but with rather more choice, or directly to those functions specifically dealt with in the Calibration section. In the former case they may optionally still be FSUIPC-calibrated, in the latter case they must be, or they don't get through to FS.

Regards

Pete

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.