FSUPIC with A2A aircraft

[matt_smith]

Just a small query when using FSUPIC with A2A's aircraft. Previous to the most recent version of FSUIPC released in May I had all my axis assigned in FSUIPC and working fine (TPM). Since the update I noticed that only T responds to axis movement in cockpit yet in FSUIPC all axis' show movement. The same is also true in default aircraft and and the RealAir Duke. Since noticing this issue I have done a complete clean reinstall of win7 hp x64 and and P3D yet still have the same issues so I'm totally stumped on this. Other than windows updates the only thing that changed on my rig is that I replaced my 2 original Saitek throttle quadrants (PS2 and USB) with 2 new USB throttle quadrants. They both appear to work as one would imagine with all other aircraft other than the A2A aircarft. Is there just a setting in FSUPIC that I've missed that I must have had set in the old version?

Thanks Matt

[Pete Dowson]

Just a small query when using FSUPIC with A2A's aircraft. Previous to the most recent version of FSUIPC released in May I had all my axis assigned in FSUIPC and working fine (TPM). Since the update I noticed that only T responds to axis movement in cockpit yet in FSUIPC all axis' show movement.

Version numbers -- before and after -- would actually help identify changes in FSUIPC.

Is there just a setting in FSUPIC that I've missed that I must have had set in the old version?

Surely you didn't delete your settings (the INI file)? The installer most certainly doesn't change them.

I'm afraid I really don't know what is different specifically about A2A aircraft. Maybe if you do a search you might find clues from others. But first if I were you I'd try to find a back up for the settings file you must have deleted.

Regards

Pete

[matt_smith]

Hi Pete, wrote the last post when half asleep (not the best time lol). The ini file has gone as I have formatted and reinstalled windows and Prepar3d. The current version of FSUIPC Im using is the May 5th release 4.90, the previous version unforumately I can't remember. It would have been the current version as of the 6th April 2013 (when I purchased a registered copy). Thinking with a fresh head this morning it would appear to be an issue with A2A rather than FSUIPC.

Thanks Matt

[Pete Dowson]

Hi Pete, wrote the last post when half asleep (not the best time lol). The ini file has gone as I have formatted and reinstalled windows and Prepar3d. The current version of FSUIPC Im using is the May 5th release 4.90, the previous version unforumately I can't remember. It would have been the current version as of the 6th April 2013 (when I purchased a registered copy).

In that case it would have been identical except for the removal of the signature check.

If you have no backup of your earlier INI file then you wil need to find the method of assignment which works for the A2A aircraft. Either try them, or ask around, mabe in an A2A support forum? The different methods are:

Direct to FSUIPC calibration

To the FS controls AXIS_<type>_SET, which is what FS itself would do

To the FS controls <type_set>

Then, in calibrations, you have the option for No Reverse Zone or not, and in the INI file the option to use axis controls for No Reverse Zone.

All in all 3 assignment methods x 3 calibration options = 9 to try.

Regards

Pete

[matt_smith]

Hi Pete,

Apologies for the late reply, it turned out the be a busy end to the week. I had a chance to fiddle around with FSUPIC disabled and I think I'm on the right path now. WIll post back my outcome for others later this weekend.

[matt_smith]

Resolved the issue which was caused by a duplicate configuration for the 2 of the axis.

[Pete Dowson]

Resolved the issue which was caused by a duplicate configuration for the 2 of the axis.

One of the first things to check for when there are conflicts.

Pete