FSUIPC V3.75 not Recognizing "Dial" Axis Saitek X45

[ak49er]

Greetings all. First off thank-you very much to Peter Dowson for this powerful tool he has created. Tonight, I decided to use Peter Dowsons FS Module to it's fuller potential, assigning joystick functions, axis, buttons, etc. After reading through the manual, and attempting what I am about to describe with V3.7, I went to his support forum, performed a search and updated to V3.75. I was successful with assigning all buttons, switches, and axis save for the "dial" axis, (thumbwheel designated dial by the Windows calibration screen). I wanted to use it for elevator trim. I am using a Saitek X45. The functions have all worked before, while using the FS Controls, and while simply using the FSUIPC Joystick Calibration. The joystick is disabled, it has been calibrated through the control panel and I have read the updated manual. the one anomlay is this, after the initial observance of the axis not registering in the Axis Assignments page, I went around the different menus to disable any "conflict" I noticed that some values were "stuck" in the values window of the Joystick Calibration screen, "Elevator Trim". After pressing the "Reset" button, the values remained, and after pressing the same button, now showing "Set", the values did not change. I have shut down the program several times. Any suggestions Captains? :?:

[Pete Dowson]

I was successful with assigning all buttons, switches, and axis save for the "dial" axis, (thumbwheel designated dial by the Windows calibration screen). I wanted to use it for elevator trim. I am using a Saitek X45.

It is probably not one of the 6 axes (X Y Z R U V) supported by the Windows Joystick API which FSUIPC3 uses. I have changed over to using DirectInput for the axes in FSUIPC4 (for FSX), but this is not something I can really undertake for FSUIPC3. With DirectInput you get two more axes, so possibly this dial might be one of those. I'm sorry, but it might be the only way is to assign them in FS. You can still calibrate in FSUIPC if you want.

Was there any particular reason you were doing assignments in FSUIPC itself? It was really added as a facility for those who needed different axis assignments for different aircraft, such as helicopter controls for helicopters, yoke control for Boeings and GA, joystick control for Airbus and military. That's the main benefit, as FSUIPC's assignments can be aircraft-specific.

Regards

Pete

[ak49er]

Thank-you for responding Peter. I chose to change my configuration for two reasons, First, the never ending quest for optimized performance while utilizing this powerful tool to it's more full potential. Second, I could not get the feel of the elevator trim just right using the dial with just the FS sliders, so I thought I might get more "control" ability. In my previous config. it seems that no matter what I tried, the elev. trim seems too sensitive. Now using a different axis as the trim (with FSUIPC "direct" and using v axis), it has a more correct feel. By feel I mean that before, I could not use the full range of the dial, I would turn it just a degree either way and get full stroke from the elevator trim. I tried so many configs. in FS before attempting to just assign axis direct. Any suggestions?

Also could you elaborate on the special use for helicopters?I do not understand what you mention in the manuals. I rarely sim with them but have begun to use them more along with V-22 Osprey, and my current sim sits inside a discarded UH-1 Cockpit Section. Soon the FO side will have the helo controls active.

[ak49er]

Another thing I thought of at lunch. I have my axis assigned as follows, X=Elevator, Y= Ailerons, Z= Rudder, R= Nothing (but shows up), U=N/A (this one does not recognize), V=Throttle. So "U" does not show-up. I have another sim set up at home, with a Saitek X45 as well. When I get home I will see if the problem replicates on the other system. Thanks for your help.

[Pete Dowson]

First, the never ending quest for optimized performance while utilizing this powerful tool to it's more full potential.

Yes, but whilst assigning axes directly in FSUIPC and calibrating them their may, theoretically, be a little more efficient than having FS reading them and FSUIPC still calibrating them, I doubt if the difference is at all measurable. The problem with FSUIPC3 not using DirectX at all does restrict the axes it can read, so it isn't always the best choice.

Second, I could not get the feel of the elevator trim just right using the dial with just the FS sliders, so I thought I might get more "control" ability.

I've always thought that, for trim, an INC/DEC control arrangement is often more sensitive and controllable than having an axis in any case. But an axis is very usable providing it has enough range (so it can be sensitive enough) and adjustability with a good linear readout.

One of the problems of having FS read the axes, even with FSUIPC calibrating them, is that by default it does some sort of rate-of-change over time interpretation of the incoming values. FS started doing that back in FS2002 times I think. It can be stopped, and returned to a straight linear reading, by a parameter in the FS CFG file. I document this in the FSUIPC User Guide:

For more predictable responses from your joystick, consider editing the FS CFG file and adding:

STICK_SENSITIVITY_MODE=0

To the [CONTROLS] section. This makes FS treat the raw joystick readings in a linear fashion. By default, since FS2000, FS has applied a time-change formula to the axes that, in my opinion at least, which can give rise to some unwanted behaviour. You will need to edit the CFG file before running FS, as any changes you make whilst FS is running will be overwritten.

In my previous config. it seems that no matter what I tried, the elev. trim seems too sensitive.

Sensitivity is a funny word. When I said the axis needs to be sensitive, I meant that you need to be able to make teensy-weensy adjustments to trim, with just a nudge on the control. The "sensitivity" is in the number of sensible values the trim can actually be set to.

You probably mean if was making big changes with a little nudge. That's the opposite of course.

Also could you elaborate on the special use for helicopters?I do not understand what you mention in the manuals.

Special use?

No, all I was saying is that there are folks with yokes for aircraft, and G-sticks and Collectives for helicopters, and maybe even joysticks for fighters or Airbuses. Using FSUIPC's aircraft-specific assignments you can have them all connected and assigned separately for separate aircraft, as appropriate. FSUIPC will disable one set and enable the other set when you load a different aircraft.

That was the original and main reason axis assignments were added.

Regards

Pete

[Pete Dowson]

Another thing I thought of at lunch. I have my axis assigned as follows, X=Elevator, Y= Ailerons, Z= Rudder, R= Nothing (but shows up), U=N/A (this one does not recognize), V=Throttle. So "U" does not show-up.

So, your control doesn't provide a U axis. There isn't one to "show up".

You can check what the Windows Joystick API can see and read using the Joyview utility I attach below.

Pete

joyview.zip

[ak49er]

Thanks for your immense help to a tiny problem, I understand and will heed your advice for one system, and maybe try the fix for the other sim.