MichaelMcE

Okaytry PFC 1.994 and FSUIPC 3.537, both now available above. Be aware that if you assign PFC axes in FSUIPC you need to disable those same ones in the PFC options (uncheck the enabling checkbox for each). The FSUIPC assignments do not override thse in PFC, unlike the Button assignments. Regards, Pete Wow! I was did not think you were going to tend to this so soon. I will give it a try either tonight or tomorrow night and will report back. Thanks. -michael

Yes, I agree that having such user facilities centralized is the best way to go. Thanks. -michael

Pete, That is the change I am requesting. If one can assign a throttle quadrant config to a specific aircraft, why not also save the flight control response curve that has been set for that aircraft? -michael

Pete, Ok, I see that under the pfc.ini section [FlightControls], a single response curve is saved and therefore applies regardless of the aircraft selected. I would like to configure different response curves specific to "Jet 2-engined" and "User Config 2" that I have assigned to LDS 767 and PMDG 747 respectively. Its a nuisance to have to reset the curve each time a/c are changed. If you could put it in at some point it would be appreciated. :) Thanks. -michael

Hello Pete, Expo := exponential. I'm not sure what term you use to describe the non-linear response for flight control axis, but they look to me like the application of an exponential mathematical function that translates linear h/w axis movement into non-linear actual control response. The use of the abbreviated term 'expo' is a habit from my Radio Control flying days - we would apply an exponential function to "soften" control response around neutral for more precise control of the aircraft in hi-speed flight. I am using 1.993. Let me double-check tonight, perhaps I made additional changes to the response curves *after* assigning the TQ configuration to specific aircraft. I'll get back to you. Thanks. -michael

Pete, Now that I am enjoying using my 2-engine jet throttle quad to fly different aircraft, I noticed that the flight control response is not being saved individiually for each config. I am using the 2-engine config to fly the LDS 767. I have the flight controls tailored with some expo in both aileron and elevator. For the PMDG 747, I use Config 2 and no expo on aileron and 1 click on elevator. Each time I fly, pfc.dll properly selects the correct config, but I have to manually reset the expo each time I change a/c. Please consider saving the flight control response settings when a config is saved for a specific aircraft. Thanks. -michael

Pete, Glad to report that I can not reproduce the error with 1.993. Thanks for the quick turnaround. -michael

Good man! Thank you. I know how these strange issues can eat at you and it's impossible to rest until you solve them! ;-) I will test it tonight and get back to you tomorrow. -michael

Pete, We can eliminate hardware as an issue. I checked the raw input value as I deflected the yoke. As the raw input value progressed from 85 to 97, the 'scaled output' went full negative. At one point I was able to hold the yoke steady with a raw input value of 87, and the scaled output remained locked on full negative. But, then the really interesting part ... The above test was made with a response curve. When I set the response to linear, I could not reproduce the problem. I then made a single click on the response curve and was able to reproduce the problem. I then made a second click on the response curve and was not able to reproduce the problem. After a series of tests on the response curve, I can only reproduce the problem if I make a single click to the response curve from the linear setting. The tests were run with pfc.dll v1.992. -michael

And no filtering, just in case, please. Regards, Pete Will do. -michael

1. I tried it with several user configs: 1, 2, 3, 15. 2. Just forward thrust 12 and 34. 3. Filtering is on. 4. Slope is selected - about 2 clicks. Ah yes. Good point. I will check the actual values to see what is happening with the raw input. I will also try it with zero slope. BTW: I initially suspected h/w (and have not ruled it out :-) ). I had to return the yoke to PFC 3 months after I purchased it to have them address an intermittent problem with the left/left rocker randomly triggering input on the other rocker switches. Since I use that rocker for trim, I was getting all kinds of random actions occurring during a flight when manually flying - very frustrating to say the least. I used the "test" page to document what was happening (thanks Pete!). Since then, the h/w has performed flawlessly. I will make a visual check of the board in the TQ Console and also pull the board at the base of the yoke - PFC had me do that when I first reported the left/left rocker issue. Very good. It will be a long day for me, I wont get to test this until about 11PM tonight. Look for it tomorrow. Thanks. -michael

Will do so when I get home tonight. -michael

Pete, I verified that the behavior exists independent of aircraft. I just ran a series of tests with pfc.dll v1.989 and v1.92, using the default 777, default 747, and the LDS 767. The behavior existed in all tests. And yes, prior to acquiring the 747 I never tried mapping throttles in this manner. I figured I would give it a try to see how I like it before investing in the 4-engine throttle quad. Thanks for the help. Let me know if I can help further at this time. -michael

Pete, I hope you can help me troubleshoot this strange behavior ... I have the PFC Jet Yoke, Rudder Pedals and use the 2 engine jet throttle quad. The PFC h/w is connected to my FS host via a USB-to-serial interface. I'm using PFC.dll v1.989. I've been flying this setup for 2+ years with 767PIC and LDS 767 and have experienced no issues. I recently purchased the PMDG 747. After the install I configured the pfc driver to use the 2 engine throttle quad to control the 4 engines. I enabled a user config, assigned the left throttle as throttle 1+2 and the right throttle as throttle 3+4. I also enabled the spoiler and thrust reverse levers. I closed down the pfc configuration utility and double checked my assignments by observing throttle, reverser and spoiler movement. All looks good. I then get the aircraft airborne and initiate an easy right turn. The a/c violently rolled left, and then began to roll right. This behavior repeated everytime I would initiate a right roll. So, I ended the flight, restarted, and double-checked all my settings. When observing the aileron movement on the Flight Controls page, I noticed that as I slowly and continously input right aileron, the "dot" on the response curve would drop full negative and then return to the plotted curve. When inputing left aileron, all is fine. All is fine for up/down elevator, left/right rudder, brakes, etc. ONLY with right aileron to I get this sudden full down (negative) deflection. And it occurs at the same point in the deflection. I decided to start over from scratch. First, I loaded the LDS 767 using the 2 engine throttle quadrant config. I repeated the test of control movements that I described above. Everything worked as it should. I ended that flight and started the PMDG 747, still using the 2 engine throttle quadrant config. Repeated the test again, everything worked just fine. I then selected a user config, but did not make any assignments. I checked control throws and everything was fine. I then assigned throttle 1 to engine 1+2 and throttle 2 to engine 3+4. When I checked control throws, the full negative deflection behavior reappeared. I'm not sure where to go from here. I have started from a clean FS9 start, using clean (archived) versions of pfc.ini, and regardless of user config I use to assign the controls, I get the same behavior. Do you have any ideas on what might be going on; is there some data that I can log to help explain what might be going on???? I'm stumped????!!!!! Thanks. -michael

Once again, I never thought to look! Ok - will take a look. Basically, via the dll provided by LVLD, you provide a pointer to a STRUCT that is populated with all internal state information. Perhaps I should just request permission from LDS to allow me to provide you with the SDK??? (I'm aware of the past issues ...) Honestly, in my experience to-date with the LDS767 I have no problems with minor throttle movements/control jitter and the a/t. The significant problem occurs on takeoff after manually positioning the throttles at ~70%N1 and then engaging THR/N1 on the MCP. There is a short period during which the two seem to fit each other, and then it settles out. I actually complicate this because I routinely practice manually advancing the throttles to the full open position while the a/t takes over (which I believe is also the case for real world ops: although the throttles are motorized the pilot does keep his hands on them while they are automatically positioned!) I would say this boils down to having a solution that is more eloquent than the current work-around. Perhaps others do have jitter issues. -michael