JHepburn

Thanks Pete for the clear, concise, and prompt answer. More importantly, thanks for your contribution to the community. In summary, the correct setup for aircraft hooking into the FS joystick information is this: 1. No axes assigned directly in FS Assignments menus 2. Aircraft specific checked in FSUIPC Axis assignments 3. For each axis being sent as an FS axis--bullet in Send as FS Axis, Check next to the drop down control, and Axes Set selected from the drop down list I think this is correct. Thanks again for the help! Jeff

Hi Pete, I have a quick question regarding joystick assignment/calibration. Is it possibleto have a controller axis assigned in both FSUIPC and FS at the same time? Typically, I use FSUIPC to assign/calibrate all of my JS axes and buttons and disable all axis in FS, but certain addons seem to like (read require) axis assignments directly through FS to work correctly (typically fly-by-wire type of input intercepts -- e.g. VS F/A18, MD-11 LSAS). For these instances, I will typically check the Aicraft Specific box, send the input directly to FS, and add the axis in FS menu. Unfortunately, I then have to go do FS map/unmap the appriopriate axes each time I switch to/from this aircraft. If it is possible to assign via both without issue, is there some order of priority between the two (i.e. does FSUIPC or FS get priority)? How would a different mapping between the two be handled (e.g. Throttle 1 mapped to X-axis in FS and Y-axis in FSUIPC). If not, are there any better workarounds for these types of examples? Your help here would be much appreciated! Thanks! Jeff Hepburn