JHepburn Posted October 5, 2009 Report Posted October 5, 2009 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
Pete Dowson Posted October 5, 2009 Report Posted October 5, 2009 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). It is certainly possible, but generally undesirable. Those add-ons you are talking about cannot tell the difference between axes assigned in FS and axes assigned to the same FS controls in FSUIPC. The can only be detected as FS controls. At present you are probably using the FSUIPC facilities to assign "direct to FSUIPC calibration", which doesn't use FS controls at all until, possibly, after the calibration process -- and that depends on how it is implemented in FSUIPC. For FSX or ESP it aactually means those controls bypassing any applications wanting to hook into them before they reach FS. So, for those add-ons, just make a separate Profile or "aircraft-sepcific" arrangement where the axes affected are assigned to FS controls instead of direct. If you try to use FS assignments instead, you'll have to do so for all aircraft as FS doesn't have the capability of switching for different aircraft. 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. No, you misunderstand. Once you assign an axis in FSUIPC, no matter which method you select there, you do not need, and in fact certainly do not want, ANY assignment in FS for them. The assignment in FSUIPC is sufficient. Regards Pete
JHepburn Posted October 6, 2009 Author Report Posted October 6, 2009 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
Pete Dowson Posted October 6, 2009 Report Posted October 6, 2009 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 Yes, though you may wish to investigate the Profile facilities FSUIPC offers, instead of using the "aircraft specific" option. They are alternatives, but the profiles allows you to define classes of aircraft for which the controls etc will be the same. You can name the profiles then simply assign new aircraft to the correct profile in a drop-down selection list. Regards Pete
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now