Elemental question

[soldano]

I read about it but my doubts continue about the differences in ax assigment between the 2 options: "Send direct to FSUIPC calibration"or "send to FS normal axis", which are the advantages or disadvantages and in which case should be chose each one ?

Thanks

[Pete Dowson]

I read about it but my doubts continue about the differences in ax assigment between the 2 options: "Send direct to FSUIPC calibration"or "send to FS normal axis", which are the advantages or disadvantages and in which case should be chose each one ?

As it says in the User Guide, the "direct" method bypasses FS altogether until the value has been calibrated. In FSX it also bypasses SimConnect altogether. It is more efficient, smoother, better in every wayEXCEPT that, as also stated in the User Guide, there are some add-ons which intercept the FS control and do things with it, and this method bypasses that possibility. That's why it says (with an emboldened NOTE) to try it first, make sure it doesn't mess your add-on up.

The only other reason for using FS controls, not direct to FS calibration, is that there are a lot of assignable controls for FS which are not subject to FSUIPC calibration and which therefore cannot be sent direct in this way.

Regards

Pete

[soldano]

Thanks for your quick reply, and 2 more questions:

Those addons which interfere with FS controls, are only panel related, or maybe also some aircraft with advanced panel management.- ?

When controls are disabled in FS, is it necesary also to delete posible redundant axes assigned in it , or in that situation they dont interfere with FSUIPC ?.-

Regards

[Pete Dowson]

Those addons which interfere with FS controls, are only panel related, or maybe also some aircraft with advanced panel management.- ?

Probably. Fly-by-wire for Airbus, perhpas.

When controls are disabled in FS, is it necesary also to delete posible redundant axes assigned in it , or in that situation they dont interfere with FSUIPC ?.-

Never unintentionally have multiple assignments to the same FS axes -- they will certainly conflict as each will send different values according to their different processing. Assigning them in one place cannot stop them also being read elsewhere, it is the nature of the joystick interface in Windows.

However, if you mean axes and FS controls you aren't using with a specific aircraft, then they don't matter.

Regards

Pete

[soldano]

Even when controls are disabled within FS ?

[Pete Dowson]

Even when controls are disabled within FS ?

Sorry, even 'what' when controls are disabled in FS? Not to assign in FS and in FSUIPC the same axis / control? I don't understand what you are now asking: If you don't assign in FS (ie. they are disabled) how can there be a conflict with assignments in FS? "It does not compute" as Spock would say!

Pete

[soldano]

My question is: I want FSUIPC get total control, so I disabled joysticks in FS.-

In FS there is ie. a throtle ax assigned as well as in FSUIPC, should I delete it ?.-

I think that being joysticks disabled in FS there should be no conflicts, but I want to be sure.-

[Pete Dowson]

My question is: I want FSUIPC get total control, so I disabled joysticks in FS.-

In FS there is ie. a throtle ax assigned as well as in FSUIPC, should I delete it ?

If it is disabled it doesn't matter, though for tidiness, or to avoid later confusion, I suppose you could delete everything in FS assignments. There's a slight worry though that it might reassign them automatically, as if it is detecting them afresh -- though obviously it shouldn't do this if they are disabled ...

I think that being joysticks disabled in FS there should be no conflicts, but I want to be sure.-

I think you can be sure. I've only ever disabled the joysticks, I've never bothered going through deleting anything.

Regards

Pete