cfelix Posted November 24, 2013 Report Posted November 24, 2013 I've working with PMDG support on a strange problem I was having with throttle control on the 777. I would taxi to the active, enter the runway when cleared, run the engines up to 55%, and then hit TOGA. The engines would spool up to full power and I then advanced my Saitek throttles full forward. Within a second or two FSX would permanently freeze. The cursor would move but FSX had stopped responding to any clicks or keyboard inputs. At first PMDG thought it was a VAS problem put I was able to rule that out by watching monitoring VMS with Process explorer. PMDG then said that they had seen a similar problem in early testing that was related to FSUIPC processing the throttle axis. I moved my throttle control to FSX and the problem went away. I would really prefer to use FSUIPC so is there anyway to tweak it to avoid this problem? BTW - This is the final response from PMDG: "It's a hard and fast compatibility problem unfortunately - our code and FSUIPC both basically use the same method whereby the joystick is intercepted outside of FSX via Windows functions. It's really one of the other, not both." Charlie Felix
Pete Dowson Posted November 28, 2013 Report Posted November 28, 2013 BTW - This is the final response from PMDG: "It's a hard and fast compatibility problem unfortunately - our code and FSUIPC both basically use the same method whereby the joystick is intercepted outside of FSX via Windows functions. It's really one of the other, not both." I suspect they are right. They should know their code. Maybe other 777 users can help? There are lots of configuration things you can do with FSUIPC for the axes, one might work fine as it did I'm sure for the many 747 and 737NGX users. 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