Response to Throttle Axis- FSUIPC

[brucekn]

Since using FSUIPC for FSX (ver 4.40, registered ), I have come across a repeatable issue that I'm wondering if anyone has seen before (couldn't see a post here). I have my CH yoke throttle using FSUIPC Z axis (send direct to FSUIPC calibration), and have disabled the default control is FSX. The USB connection from the yoke is plugged directly into the PC (not via a hub).

On initial start of FSX, I find I need to move the throttle up to around mid-range before FSX recognizes that I have moved it. After this initial movement and after the throttle movement is recognized, the throttle tracks OK throughout all of it's range, until I restart FSX.

I can see the numbers for the IN and OUT windows moving with the CH throttle on the yoke, but there is no throttle movement in FSX.

I am also using TrackIR and a simple GoFlight module, although I had seen this occur prior to connecting these 2 peripherals.

Thanks, Bruce.

[Pete Dowson]

On initial start of FSX, I find I need to move the throttle up to around mid-range before FSX recognizes that I have moved it. After this initial movement and after the throttle movement is recognized, the throttle tracks OK throughout all of it's range, until I restart FSX.

Something is bottlenecking at the start. How long after FSX appears "ready to fly" are you waiting? On FSX, with both FSUIPC4 and TrackIR running, there is a lot of initialisation taking place right at the beginning.

FSUIPC4 does discard the first 10 or so reading it gets, because there are a number of USB joystick drivers which appear to send spurious values initially, before they themselves are properly initialised. But at its default scan rate of 20 readings per second, that should only take half a second -- though, again, if FS is very busy just then, it could take longer.

And then FSUIPC needs to see a movement on the axis before it will use it. Mid-range seems rather far, unless you are using an overlarge Delta value in your assignment?

I can see the numbers for the IN and OUT windows moving with the CH throttle on the yoke, but there is no throttle movement in FSX.

The IN and OUT numbers are shown on the yoke? It has its own display? Or do you mean in the Axis assignments option in FSUIPC, or in Calibration?

Once FSUIPC is seeing and showing changing values, it is most certainly passing them on to FS. Enable Axis logging in FSUIPC's logging page and check it for yourself.

Incidentally, version 4.40 was superseded by 4.50 a couple of weeks ago and is no longer supported.

Regards

Pete

[brucekn]

Hi Pete,

Thanks for your reply. A few comments to your's:

1. This issue doesn't akways coincide with FSX starting up, when I agree there is a lot happening. But I can start up FSX and leave it running for an indefinite time, and as long as I don't touch the CH yoke throttle, when I first touch it (later) the movement needs to be halfway thorugh the axis before the FSX sees any movement (when it will jump to half-way through it's axis to catch up with the CH yoke throttle). After that one incident is over, the throttle works perfectly and has full responsiveness to the CH yoke throttle, until I re-start FSX and it starts all over again.

2. The above is independent of TrackIR, that is, I can not start TrackIR and it still occurs, and did prior to installing TrackIR. However, it only started to occur when I used FSUIPC as a throttle axis. Although- all other axes (including aeleron, elevator, rudder) to not appear to exhibit this behavior.

3. "The IN and OUT numbers are shown on the yoke? It has its own display? Or do you mean in the Axis assignments option in FSUIPC, or in Calibration?"

The numbers are on the FSUIPC Axis Assignment tab.

More specifically (writing as I test this):

a. I start FSX, C172 (stock) a/c. Throttles (CH and a/c) are fully out (off). The FSUIPC Axis Assignment tab shows -16384 for the throttle (I had to "Ignore Axis" several times to see the throttle, and move the throttle very slightly to have the axis captured on the FSUIPC display).

b. I have to push the CH throttle in until the FSUIPC Axis Assignment tab In/Out windows show 0, before the FSX throttle jumps to about half-way in (full in is +16984).

I'm sure that this is something in my system and not FSUIPC, otherwise you would have seen this before.

Also, the Delta assignment is 256 (I think that was a default value ??).

Another, possibly related, effect, is the Pan switch in the CH yoke. It is the only axis or switch that I am still using the FSX assignments (to control the pan view), as when trying it with FSUIPC I get very animated motion (pans have large steps rather than smooth continuous motion), although this continues to occur throughout a FSX session. I only mention it in case it provides you with some useful info.

Thanks again. I am about to try some conditional button assignments in FSUIPC.ini, that should be fun :)

Bruce.

[Pete Dowson]

1. This issue doesn't akways coincide with FSX starting up, when I agree there is a lot happening. But I can start up FSX and leave it running for an indefinite time, and as long as I don't touch the CH yoke throttle, when I first touch it (later) the movement needs to be halfway thorugh the axis before the FSX sees any movement (when it will jump to half-way through it's axis to catch up with the CH yoke throttle). After that one incident is over, the throttle works perfectly and has full responsiveness to the CH yoke throttle, until I re-start FSX and it starts all over again.

StrangeI'm thinking, then, that it is the power-saving setting on your USB ports. Go into the Windows device manager, find the USB stuff, and turn power management off.

There's no other possible explanation I can think of. The power management in Windows turns off most of the power to USB devices when they are inactive for a time. Best switching it off.

Another, possibly related, effect, is the Pan switch in the CH yoke. It is the only axis or switch that I am still using the FSX assignments (to control the pan view), as when trying it with FSUIPC I get very animated motion (pans have large steps rather than smooth continuous motion)

Sounds like you weren't assigning it to the correct control in FSUIPC then. The hat is a POV control and can either be assigned, in FSUIPC, as a set of 8 buttons, or as an axis. For smooth movement (in 3D cockpit mode) assign in the Axis assignments to "Pan view". Then it is almost the same as assigning in FSX -- not quite as smooth because of timing through SimConnect, but pretty good.

If that's all you assign in FSX, best assign in FSUIPC instead, and disable joysticks in FSX altogether.

Regards

Pete