FSUIPC causing Throttle jitters when sidestick is moved.

[ampharoah]

Hi,

I have the Thrustmaster Airbus Sidestick and the Extended TA Throttle Quadrant.

I use FSUIPC v5.151 but only for macros to assign switches in the sim to buttons on the Trhrustmaster sidestick.

Since creating these Macros, I'm seeing starnge behavior as I move the Sidestick.

If I move the sidestick, left right, forward or back, it makes the simulated throttle levers move in a jittery way. The Axis of the Sidestick are assigned correctly in P3D v4.5 to Ailerons, Flaps and Rudder, nothing else.

There is no assignment anywhere linking movement of the sidestick to throttle movement. The Throttle Quadrant levers operate the sim correctly having been assigned, calibrated etc.

But as soon as i touch the sidestick the throttles start to thrash forwards and backwards wildly!

It has been suggested that FSUIPC might be mistaking my sidestick for a throttle quadrant somehow.

How could I test / fix this please?

Any advice would be much appreciated.

Andrew

[Pete Dowson]

33 minutes ago, ampharoah said:

But as soon as i touch the sidestick the throttles start to thrash forwards and backwards wildly!

If this is really the case you must have some hardware or USB driver interaction. And "thrashing" isn't really like "jittering", surely?  And just "touching" the sidestick, not moving it as previously stated.

Having two completely different descriptions of the problem isn't much of a help really.

Saying it only started happening after you created these 'macros' implies that all was well with the sidestick before then. Is that so?

Anyway, we can't possibly advise without seeing your settings. Please show or attach the FSUIPC5.INI file, a Log file (FSUIPC5.LOG) and the macro files (.mcro).

Pete

 

 

[ampharoah]

Hello Pete,

Very grateful for your prompt response, it's much appreciated.

The joystic has been operating just fine until recently and I have only just recently introduced FSUIPC programming of some buttons and switches through the Macros function at which point the problem started. That may be a co-incidence, but I'm now exploring every possibility trying to track down the problem.

If I move the physical joystick, the in-sim throttles step rapidly up and down the detents. Not sure the specific definition of thrashing v jittering, but they flick forward and back in a wild way through TOGA and back to REV Max and all points in between, randomly. I hear a click,click, click as they rush up and down the detents.

Even the slightest deflection of the joystick left/right/forward/back starts the problem. twisting the sidestick also has the same effect.

I will read the manual and learn how to find the FSUIPC5.INI file, a Log file (FSUIPC5.LOG) and the macro files (.mcro) and send them to you immediatly.

Andrew

[ampharoah]

I hope these are the ones you need?

Andrew

FSUIPC5.1.log FSUIPC5.ini A Packs L.MCRO A LLR.MCRO A LLL.MCRO A Strobes.MCRO A Packs 2.MCRO A Taxi.MCRO

[ampharoah]

I have tested all aircraft in my collection, not just the FSLabs A320, A2A, Default P3D aircraft, etc etc same result with all of them.

On the default F22 right bank advances Left throttle smoothly, pull up advances the right throttle smoothly. It backs off as soon as i release the stick pressure.

In the Maul Right bank advances the throttle, likewise it backs off as soon as I release the stick pressure.

In the FSLabs Airbus Left and Right bank advance and retard respectively Englie 1 throttle lever, climb and desent advance and retard respectively the Engine 2 lever.     Twist advances and retracts Engine 2 lever, though this is not consistent and may be due to a very small climb and descend reading registering due to the torque.                            

Andrew

[Pete Dowson]

38 minutes ago, ampharoah said:

I hope these are the ones you need?

Thanks. You said this:

1 hour ago, ampharoah said:

I use FSUIPC v5.151 but only for macros to assign switches in the sim to buttons on the Trhrustmaster sidestick.

but that plainly is not the case.

You have throttles assigned AND calibrated in FSUIPC.  Not only that, but you have actions assigned to the throttle movements on the right-hand side of the assignments facility:

[Axes]
PollInterval=10
RangeRepeatRate=10
0=0X,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
1=0X,BR,0,0,65966,0,65967,0    -{ DIRECT: Throttle1Entering=THROTTLE1_DECR, Leaving=THROTTLE1_CUT }-
2=0Y,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
3=0Y,BR,0,0,65971,0,65972,0    -{ DIRECT: Throttle2Entering=THROTTLE2_DECR, Leaving=THROTTLE2_CUT }-
 

The axes are not only trying to control the throttles normally, but you've also assigned "throttleN decr" and "throttleN cut" controls to then as well, both at the idel position.

Also, you evidently have axes enabled in P3D. So your throttles will be acting there independently of what you set FSUIPC to do.

For axes you MUST either assign all in FSUIPC or all in P3D. If you assign in FSUIPC you must disable controllers completely in P3D.

It is your choice.

The macro files are merely normal mouse macros and cannot interfere unless P3D operating those switches has such side effects.

Pete

 

 

[ampharoah]

Hi again Peter,

I haven't made thiese assignments.

FSLabs provide a routine that runs on install, that facilitates the Thrustmaster Sidestick and Throttles with their Airbus when you first start the sim and it detects that you have the Thrustmaster hardware attached. I guess its possible that this may be something that they have created in FSUIPC for distribution.? i certainly wouldn't even know how to assign throttles and sidesticks in FSUIPC having never attempted to do so. The throttle assignments you mention in P3D are for my other aircraft and other throttle hardware when I'm not simulating the Airbus.

These two Thrustmaster controllers are further complicated by the fact that the sidestick also has a throttle facility built in, though I don't use this as i also have their throttle quadrant addon and so its not needed.

I'm sorry Peter but my technical ability (or lack of) means that i don't understand your advice when you say:

"Not only that, but you have actions assigned to the throttle movements on the right-hand side of the assignments facility:

[Axes]
PollInterval=10
RangeRepeatRate=10
0=0X,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
1=0X,BR,0,0,65966,0,65967,0    -{ DIRECT: Throttle1Entering=THROTTLE1_DECR, Leaving=THROTTLE1_CUT }-
2=0Y,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
3=0Y,BR,0,0,65971,0,65972,0    -{ DIRECT: Throttle2Entering=THROTTLE2_DECR, Leaving=THROTTLE2_CUT }-"

Since i didn't assign anything knowingly, this doesent mean much to me I'm afraid.

I truly appreciate you assitance.

Other than delete any sidestick or throttle assignments in P3D (which FSLabs dont ask you to do at any stage?) i don't know how to resolve this problem.

Are you able to offer any further helpful advice please?

Andrew

 

[Pete Dowson]

3 hours ago, ampharoah said:

Are you able to offer any further helpful advice please?

Delete the complete [Axes] and [JoystickCalibration] sections from your FSUIPC5.INI file.

3 hours ago, ampharoah said:

Since i didn't assign anything knowingly, this doesn't mean much to me I'm afraid.

Well, someone else did it for you then? they appear to be very deliberately made settings. They couldn't possibly have been made by accident or even fooling around!

I strongly suggest you at least peruse the FSUIPC user guide and even check the pictures there before messing with things "unitentionally"!

Incidentally, there's absolutely no way whatsoever for the use of the mouse macros you created could interfere with any controls other that whatever those mouse macros were attached to. The axes interaction would have all been due to both P3D and FSUIPC controlling the axes.

Pete

 

[ampharoah]

Hi Peter,

There appears to have been a miss-understanding, for which I apologise - please read below:

I tried to explain in my last post above that I think it's the FSLabs developers who have created the FSUIPC axis assignments and installed them. 

FSLabs provide an auto-run routine that that links the Thrustmaster Sidestick and Throttles with their Airbus software when you first start the sim and it detects that you have the Thrustmaster hardware attached. I guess that's where the assignment originated. Honestly no one has been fooling around "unintentionally".

You get a dialogue box that asks if you want the controlers to be auto-setup.

I can only suggest that they used FSUIPC for this and that's where it came from.

I have uninstalled v5 and re-installed, uninstalled the FSLabs Airbus and re-installed, and now I get no throttle deflection when I move the sidestick. I have not yet disabled any controller settings in P3D but it seems to work.

I have enabled one .mcro and it still seems ok so I will press on and report back.

Once again, thanks for your generouse support on a Sunday - much appreciated.

 

Andrew 

[Pete Dowson]

3 hours ago, ampharoah said:

I tried to explain in my last post above that I think it's the FSLabs developers who have created the FSUIPC axis assignments and installed them. 

Okay. I didn't understand that. Did they also create the A320X profile, which only has and [Auto ... ] section to load a Lua program called "PMCO"?

If they need those two throttle assignments (with the action for reverse engagement at idle), they you'd have thought that they would have also added assignments for the other flight controls. Also, really, if the assignments they have added are supposed to be specific to the A320 then they ought to be in a specific assignments section for the A320 profile.

I find it rather odd that FSLabs depend on FSUIPC. I thought it would be the opposite.

Anyway, reading back a little I see you said

Quote

It has been suggested that FSUIPC might be mistaking my sidestick for a throttle quadrant somehow.

7 hours ago, ampharoah said:

These two Thrustmaster controllers are further complicated by the fact that the sidestick also has a throttle facility built in, though I don't use this as i also have their throttle quadrant addon and so its not needed.

So, whilst FSUIPC may not have such assignments, the fact that controllers are enabled in P3D will mean that it is probably active there. Check what P3D is assuming with these connections.

At least, I assume "T.A320 Pilot" is not the "sidestick"?

Anyway, I do hope that your endeavours since then prove fruitful!

Pete

 

 

 

[ampharoah]

Hi Peter

I'm afraid i can't answer for FSLabs, but I'm confident that it's their handiwork you are seeing, from their Forum you will see that they have been under a lot of user pressure regarding the interfacing of these new Thrustmaster products and I suspect that a quick fix using FSUIPC was their short term answer. I believe that further work will be included in their next update release.

The T.A320 Pilot is indeed the name of the Thrustmaster sidestick.

Everthing is working now and i have been able to re-enabe my Macros without incident so I'm a happy man.

I'll report back to you if I discover anything else of interest.

Once again, a big thanks for such selfless Sunday support and for your product. I only wish I was technically more compitent to enable me to make more of it .

Best wishes

Andrew