The A2A Simulations Community

It sounds like Linda is your thing then, but yeah, if you dual map controls then obviously you are going to run into problems, but nobody suggested doing that. A lot of people map their primary controls surfaces straight through FSX, since those are common for all planes, map their brakes through FSUIPC, map common button controls through FSX, buttons that must be individualized through FSUIPC, and then use something like the A2A Configurator when you need something like a plane-specific turbo lever. No conflicts or fluttering at all. But I guess that is the beauty of the system, lots of flexibility there, and each can do it their own way.

_________________
1)i7 980x 4.35 ghz, gtx 470s SLI, Matrox th2go, Creative x-fi
2)i7 2600k, Gigabyte z68x, gtx 285s sli

Initially that is the route I took in having FSX controls totally disabled but to be honest I didn't like FSUIPC's handling of the pan function using a joystick hat. So that went back into FSX. Now I use trackIR and EZDOK so its probably not an issue anymore, but the point being as long as you have cleared out the axis and button controls in FSX that you want to use elsewhere there isnt an issue. I have no control surface flutters or anything like that simply because my FSX doesn't know anything about my joystick axis as I have cleared them.

Sure if you have them mapped to two places at once then expect trouble !

_________________
Asus P6X58D-E Intel X58 MB with onboard Realtek HD audio
Intel i7 970 3.2GHz 6 Core
Samsung 256Gb SSD for Win 7 64 bit
Corsair Vengeance 12Gb Triple Channel DDR3
nVidia 680 GTX
TrackIR 5,Track clip pro, EZDOK and a host of CH/Saitek controls and panels

No, you won't run into problems as LINDA works exactly like FSUIPC (as it IS FSUIPC).

I have all axis disabled for FSX (best and fastest way to delete all entries in the standard.xml), except panning for the hat switch.
(Anyway I use EZDOC now for a few days)


And with LINDA, you assign all your standard buttons for any standard airplanes.
And then the special needs for every addon separate as you like, which is of course automatically selected (same way like FSUIPC)

Yeah, understood. I think the OP was under the impression that it was somehow mandatory to totally disable his controllers in FSX in order to be able to individualize his controls per plane using FSU, and as a result of that practice was running into problems with the P40 Configurator. I don't use Linda personally, since I tend to be pretty conservative in what I map to buttons/keys, but it sure sounds like a top notch effort on your part and very useful.

I don't know how you would map something like the Turbo Lever of the B377 to an actual axis unless you used the A2A configurator for that plane, so if those configurators have some kind of problem when the controllers themselves are totally disabled in FSX, that might argue against the way jmig is doing things. (I don't know if this is true or not that when the controllers are disabled in FSX that the A2A Configurators don't work right, but that is what some guy in another thread reported)

_________________
1)i7 980x 4.35 ghz, gtx 470s SLI, Matrox th2go, Creative x-fi
2)i7 2600k, Gigabyte z68x, gtx 285s sli

As far as I am aware, FSX joysticks need to be enabled (even if no controls are assigned) for the A2A configurators to work.

The A2A configurator will OVERRIDE any FSX controls but only for the aircraft the configurator is used for. So if you map an axis in FSX for prop pitch, then decide to use for example the same axis in the Spitfire configurator for elevator trim, every time you load up the Spitfire in FSX you will get that axis controlling the elevator trim, as soon as you return any other aircraft that same axis will be prop pitch again.

This is based on my own observations.

Personally I no longer use any axis mapped in FSX but still use the occasional joystick button directly FSX mapped. I use LINDA and a registered FSUIPC as well as using the A2A configurators as I'm a bit lazy to map some controls in either LINDA or FSUIPC as the configurators do the job. I don't have any issues with things not working or conflicts.

_________________
Asus P6X58D-E Intel X58 MB with onboard Realtek HD audio
Intel i7 970 3.2GHz 6 Core
Samsung 256Gb SSD for Win 7 64 bit
Corsair Vengeance 12Gb Triple Channel DDR3
nVidia 680 GTX
TrackIR 5,Track clip pro, EZDOK and a host of CH/Saitek controls and panels