A2A Aircraft and FSUIPC?

[RogCamp]

 

I have always used FSUIPC with FSX, it has always been great would not want to be without it.  I am running version 4.968.

I have a problem now but its not caused by FSUIPC its because of A2A and the way they handle their axes and buttons using L:vars.

I assigned an A2A  C182 to my single engine profile,some things work but many do not.

I would like to know if I could delete the A2A C182 from my profle then,   

When and only when I load the A2A aircraft (temporary enable controllers in fsx and use A2A's Input Configurator or FSX itself to control the axes and buttons)

If I did this only when using the A2A aircraft then (disabled controllers in FSX again) before using any of my other aircraft that all use FUSPIC would this cause any problems with Fuspic itself?

 

I would like to know how other people are getting around this problem?

Any help would be great.

Thanks

[Pete Dowson]

21 minutes ago, RogCamp said:

I assigned an A2A  C182 to my single engine profile,some things work but many do not.

I would like to know if I could delete the A2A C182 from my profle then,  

Yes. In the INI file there will be a section with a heading like

[Profile.Single Engine]

(or whatever the profile is called). In there will be a list of the aircraft assigned to that profile. Just delete that line. If you do this whilst Fs is running just be sure not to have the aircraft loaded at the time. Safer probably to do the editing before starting the sim.

24 minutes ago, RogCamp said:

When and only when I load the A2A aircraft (temporary enable controllers in fsx and use A2A's Input Configurator or FSX itself to control the axes and buttons)

If I did this only when using the A2A aircraft then (disabled controllers in FSX again) before using any of my other aircraft that all use FUSPIC would this cause any problems with Fuspic itself?

Not for FSUIPC, but you will get all osrts of strange tihngs happening. And there's absolutely no need.

25 minutes ago, RogCamp said:

I would like to know how other people are getting around this problem?

Assigning in FSUIPC to the FS controls (Axis ... Set) and not calibrating is exactly the same as assigning in FS and not calibrating. You can calibrate either way. Without knowing what upsets the A2A aircraft I couldn't say.

Pete

 

[shortspecialbus]

RogCamp, if you want I can send you some macro files that have binding for all the A2A controls for some of their planes, and then you can bind them in FSUIPC like any other button.  The macros make the custom LVars that A2A uses bindable like normal FS actions.  Send me a PM if you want it.  Then just create a specific profile for each A2A plane (they all use a slightly different combination of LVars) and you should be set.

-stefan