David123

John, Removing the calibration on the number 1 and 2 throttles worked. Thank you. I did not realize that some aircraft didn't like post calibration. For your information, the plane I am using is the PMDG DC-6B. One final question: When I was removing the calibration on the throttles, I made sure that the FSUIPC Log tab had Axes Controls checked just in case I would have to send you another .log file. My question is, should I keep things like Buttons and Keys, Events, and Axes Controls checked or should I uncheck them for normal FSUIPC use? David McCormick

I have assigned two throttle levers. One is assigned to throttles 1 and 3, and the other is assigned to throttles 2 and 4. I can advance the throttles to the forward stop (maximum power) but when I retard them only throttles 3 and 4 return to idle. The others (1 and 2) retard but they stay advanced to the engine start position. I tried setting all throttles to separate levers and calibrating them separately with the same result so I reassigned the throttle levers to my original configuration. When I calibrated the throttle levers, I calibrated the first lever (assigned to throttles 1 and 3) to throttle 1 and throttle 3 and the second lever (assigned to throttles 2 and 4) to throttle 2 and throttle 4. This caused the problem of not being able to advance throttles 2 and 3. So, I deleted the throttle 3 and throttle 4 calibrations (by pressing the reset button on throttles 3 and 4 and then not calibrating any throttle movement to throttle 3 and 4) and I am now able to advance all 4 throttles as assigned but, still, throttles 1 and 2 refuse to retard to idle. I have attached the FSUIPC .ini and .log files David McCormick FSUIPC7.ini FSUIPC7.log

The rudder position value of 0.000000 was when the rudder was in neutral. When I moved the rudder full left and full right the rudder position value did not change {it was still 0.000000) and no other Lvar was logged to show any position change at all. I made sure that I went to Log>WAPI>and checked Debug then I moved the rudder left and right again and went to the logging console, which was blank (it said "console started"). So I moved the rudder left and right again and a whole list of FS Rudder Controls showed up with all sorts of different numbers. I'm not sure which numbers I should use for values since every line has a different number and there are 139 lines (yes, I counted them. I'm good at that) for a single left and right throw of the rudder.

John, I went to Add-ons>WASM>List Lvars and the only thing I saw there was "RudderPos=0.000000 I went to Add-ons>WASM>Set Lvar. The only thing I found listed was RudderPos 1193. I tried to set this value but the Set button didn't work (it was a light gray color, unlike the Done button which was colored in such a way that it looked as if it could be pressed) I went to Log >List Input Events and there was nothing listed for rudder. Alphabetically, it didn't even get up to "R". I also tried deleting and reinstalling the aircraft but that didn't work either. Maybe I should just forget about it and chalk it up to a bad aircraft.

John. "Send direct to FSUIPC calibration" did not work, nor did assigning the rudder directly to MSFS. I really don't know what I'm supposed to do when looking for Ivars or Input events or, actually, where to look for them.

OK, i installed FSUIPC version 7.4.16. I assigned the joystick, throttle and rudder pedals to their correct axes. I assigned them when I had the DC-6 loaded to make sure that everything was working correctly (which it does). I then made sure that the Log tab had Buttons and Keys, Events. and Axes Control were checked. I loaded the JRF Goose and moved the rudder both left and right then allowed it to center. I still have the same problem. I made sure that there were no assignments to flight controls in MSFS. Here are the .ini and .log files you requested. as of now I have not assigned any buttons or switches to FSUIPC, only the rudder, aileron and elevator axes and the throttles, mixture and props axes. FSUIPC7.ini FSUIPC7.log

John, Nevermind, I found it. It launches with the simulator now.

OK, Here is the file. InstallFSUIPC7.log

Hello, OK, I'm very frustrated right now. Because of a previous problem, I was advised to download and install version 7.4.16. I downloaded it, I unzipped it and installed it to the drive in which MSFS lives. I did not uncheck any boxes for the components. After the installation I saw that my registration information was correct so I clicked on "Skip". When everything was done, I saw that I now have an icon on my desktop for FSUIPC 7 so I double clicked that and it launched MSFS. However, when I pressed the windows key to bring up the tray on the bottom of the screen there was no FSUIPC icon there. So, Where did it go? I need to reassign some axis and I can't do that because I cant find the assignments tab (or, for that matter, FSUIPC) anywhere. What happened and what do I do now?

John, I think I screwed up. Here are the files. Sorry for any inconvenience. I downloaded the FSUIPC version you suggested. I think I have to delete the version I have installed and then install the new one, Correct? FSUIPC7.ini FSUIPC7.log

I can't send the .log file because I am told it exceeds 4.81 MB. I also tried copy/past but it's still too big

John, Thank you so much for your help. I did what you asked. I started MSFS, started FSUIPC 7 (automatically started with MSFS) made certain that buttons and keys, events, and axis control were checked in the Log tab, Loaded the Goose and moved the rudder left then right then allowed it to center. I am attaching the results of the .log, .ini and events results that I copied just before I shut down MSFS and FSUIPC 7. Seems that it is, possibly, an aircraft specific problem because the only other aircraft I am currently flying is the PMDG DC-6 and all the control surfaces work fine with it. Al, I will check, but I think I turned all of the assistance settings off. David McCormick FSUIPC7.ini

Hello, I had to reload MSFS into my computer and I have been working on it since yesterday, trying to straighten everything out. Anyway, I'm trying to fly the Grumman Goose and when I did my flight control check I saw that the rudder moved but then snapped back to center. It did it for both left and right rudder. Knowing that I have to delete any control surface assignments in order for FSUIPC to work, I checked all my control peripherals (keyboard, rudder pedals, throttle quadrant, joystick) and I made sure that no control surface assignments were present in MSFS. Still, the rudder pedals did not hold the rudder in position, it moved slightly and then snapped back to center. So, I'm writing to figure out what happened. All the other inputs to FSUIPC work, including the brakes which are also mapped to the rudder pedals, and all inputs from all other control peripherals. My setup is as follows: Pedals are assigned to "Axis Rudder Set" Left Rudder has an "in" and "out" value of +16383 (for both "in" and "out") Right Rudder has an "in" and "out" value of -16383 (for both "in and "out") David McCormick

Thank you. I do have at least one unassigned axis that I could use for the throttles. The plane actually has no cockpit throttle levers as there was a crew of 10 and the captain would order an engineer to advance the throttles. As far as I understand it, the captain gave orders while the crew flew the airplane (kind of like a ship).

Forum Members, I am thinking of purchasing the Dornier DO X from the Marketplace. The plane has twelve (yes, 12) engines. According to what I have read thus far, I can set up one lever (axis) to control all twelve throttles in MSFS by going to "Control Options"-- "Power Management"--"Control Levers"--"Throttle"-- "Throttle Axis" and assigning one lever to "throttle axis". My question is: If I do that will it mess up my throttle assignments in FSUIPC and, if it does mess them up, is there a way that I could set up throttles in FSUIPC to attain the same results? I am using a CH Throttle Quadrant. It has six levers that I could possibly assign to throttles. The aircraft has no variable pitch (RPM) control, it's just throttle up and go (for lack of a better analogy). Thanks David McCormick