Ruahrc

Yeah I figured out I can remove the "detent" zone by calibrating the two center values to be the same: I calculated the center of my travel (min: -10,000, max:16384 = center at ~3000, etc) and put the dead zone there. Then I realized that I had to adjust the "response curve" to -15 (center-flat, exponential) in order to get what most appears like a linear travel on the mixture control, judging by the OUT value. If I have it up at 0, even with a "zero" dead zone and the center set at approximately half-travel, I will still get mixture OUT values "jumping" from say 4,000 to 11,000 as soon as I pass the center. Only by changing the response sensitivity can I get it to work. Ruahrc

I have run into a problem while trying to assign my various joystick/throttle levers to various axes via FSUIPC. A brief search of the forum did not reveal any immediate results on this topic either. I'm trying to assign the 6 levers in my CH TQ to the 6 levers in the Default DC-3. Throttle and Propeller I can get no problem. When trying to do the mixture, however, I have trouble. Since I am trying to assign two levers to two mixture controls, I am using the "Mixture1" and "Mixture2" controls rather than the generic "mixture" control. Here's what I run into: Since the separate mixtures have both a min/max and a center zone (Min, Idle, and Max) the throttles, once calibrated, do not progress smoothly from 0 to 16384 as reported in the "OUT" box. It appears as if the "Idle" zone actually corresponds to a mixture of 8192 (50% rich) whereas the "Min" corresponds to 0% (Cut-off). Therefore when I calibrate the "Idle" detent to the physical detent in the CH TQ, the output jumps quickly from 0 to 8192 in the space where the physical mixture lever is moved from full down to the detent. Then if I push the lever forward past the detent the OUT value increases gradually to 16384. The problem with this is that since the Idle detent corresponds with 8192, the lowest usable mixture value I can assign to the engine is 50%. If I try to go lower, I will enter the cut off zone and cut fuel to the engine. What I'm looking for is to calibrate it such that movement from the absolute bottom fo the throttle into the detent is cut-off, then any advancement forward past the detent should proceed linearly from 0 to 16384, giving me full mixture range. Note that when I previously applied calibrations to my other aircraft (i.e. default Cessna) I did not have this problem, since I could assign the solitary mixture axis to the generic "Mixture" command. Also, there is no trouble with turboprops either using "Mixture1" and "Mixture2" because 50% corresponds well to "Low Idle" (Also you don't adjust the mixture of a turboprop). I have only reached this issue now that I am trying to calibrate for a twin-engine, reciprocal aircraft. PS I did a quick test and also encounter this trouble on the default Baron 58, which again requires a 0-100% mixture working range. What's the solution for this? Any way to disable the idle detent in the separate mixture controls? Ruahrc

Thanks for explaining that- I was getting caught up I suppose because the words "minimum" and "maximum" do not make much sense when paired with "elevator" and "ailerons". Therefore I was reading the menus like "minimum aileron"... and didn't know if that was left aileron or right aileron or what... The UI is in fact inconsistent regarding this because on some dialogs (for example the throttle ones) the labels are clear, i.e. "feather", "idle", etc. and refer to the in-game position of that particular control. Other dialogs, however (example, aileron and elevator) are merely labeled "min" and "max" and apparently refer to the value of the controller input as read in the "IN" box. This tripped me up, and personally I think it woudl be a bit clearer if you modified the aileron and elevator labels to read something like "left", "right", "forward", "back". Anyways that clears up that issue. Next issue- I am having a bear of a time working out these "aircraft specific" controls. It seems like I set up a set of controls for a particular aircraft class and it works great. Then I load up a different aircraft and go back to the FSUIPC dialog to configure the controls for that new aircraft. Once I have that finished, I switch back to the first aircraft only to find that the assignments I have made are either missing or have been overwritten to match that of the second airplane I configured. More specifically, the "button assignments" work fine. It is only when I get to the axis assignments that things get screwy. The way I planned it was to assign the most basic axes to be common to all aircraft (pitch/yaw/roll/brakes). Then, all of my levers and buttons will be specific to each aircraft. I followed the documentation and am able to navigate the axis assignments page in order to create a new axis assignment, but I am unsure as to the proper order of operations regarding the "aircraft specific" checkbox. It seems like sometimes I will check the box first, then make the assignment, and it looks okay. But then I move on to the next axis, (the box is already checked now) and when I select a new assignment for that axis, the box unchecks itself! And I have no idea of telling when a particular assignment gets saved, and whether or not it was saved as a global or specific assignment. Furthermore I am unsure as to how to review the current assignments for a particular aircraft, in order to make sure I have done it properly. When exactly do changes in assignments get written to FSUIPC.ini? As soon as they are made? Or when you press "OK"? etc. What if I make manual changes to FSUIPC.ini, how do I see those updated changes in the FSUIPC options dialog, do I need to reboot FS or something? If you could shed some light on what I might be doing wrong I'd appreciate it. I am happy though that I got my basic axes working... now just need to figure out the levers and "aircraft specific" configuration! Ruahrc

Edit: the thing with the aileron calibration must have been a fluke too: since I tried to re-calibrate it and it behaves just like the elevator calibration does. BTW I have dis-assigned all axes in the FS assignments menus, FSUIPC should have complete control over all of the control axes. Lastly: I noticed that I was getting some jerky movement with the ailerons, whether or not the "filter" checkbos was checked or not. I cannot observe any effects of using the filter checkbox on any of my axes (this was also the case in the previous version of FSUIPC 3.5.3 where I had things semi-sorted out control-wise, but the pitch/roll axis were still being a bit fiddly). Ruahrc

I just got a CH yoke, pedals, and throttle (whopee!) and am trying to get them all calibrated up in FS. I am using the latest FSUIPC 3.558. What is happening is that I can't seem to be able to set the elevator axis using the "Joystick Calibration" dialog. Here's what I'm doing; Go to the "axis assignments" tab. Move the Yoke forward/back, until it is detected. Select "send direct to FSUIPC calibration" Check the first box, and select "Elevator" from there I go to the Joystick Calibration tab: Press "Set" under the Elevator heading Here is where I run into trouble. Instead of setting it up straightforward like I was able to do with the Ailerons, Rudder, Brakes, etc.- I run into problems. I try to set a center null zone first using the centre "set" buttons. That works okay. Then I pull the stick all the way back, and press the "min" set button. The "IN" box reads 254 or 255, like it should. I press the min "set" button and instead of assigning the value of 254 to the min box, it puts the value 254 into each the Min, and both Centre boxes. I then push the stick all the way forward and the "IN" box reads 5 (or whatever), and if I try to press the max "set" button, there is no effect. I can press the reset button and try this again using different ordering (set the min first, or set the max first, etc) but eventually I press one of the "set" buttons and it overwrites my center values, throwing the calibration off. The "out" box is recording correct (but unusable, if that makes any sense) values according to the listed min/centre/max values, but since those are messed up it pegs at either 0 or 16384 or -16384. I was having the exact same type of problem using my old version of FSUIPC (3.5.3) but it was happening with both the elevator and aileron axis. I was able to do the aileron axis okay this time with 3.558 but the elevator is messed up. Do you have any ideas what is going on? I'm using the USB versions of the control devices btw. I am just using the buillt-in WinXP drivers for these devices (plug'n'play, autodetect) and have not installed CH's control software (I would prefer to do it all in FS and FSUIPC) Ruahrc PS, I plan on making some custom button/lever assignments for different aircraft that I own. Naturally I would take advantage of the "aircraft specific" feature for this. My question is, is this tied to the "title=" entry in the aircraft.cfg? And would I be able to manually manipulate the fsuipc.ini file to be able to copy/paste these assignments for multiple aircraft titles? I ask because for example if I have a particular aircraft that has 5 liveries, each would have a unique title and would thus require me to set FSUIPC up with each livery, unless I could manually copy/paste previously defined assignments and just change around the "title=" part or something in fsuipc.ini. But this may be the subject of a new topic just to keep things orderly (and once I get past this current problem)