Have been posting about this for 3 days but no response. NEED HELP topic title. Is PMDG going to look at this?

 

 

Is PMDG going to look at this?

 

Probably not.  This is a well known issue with FSUIPC.  Map anything else through FSUIPC, but not the throttle and you'll be fine.

Could you be more specific on "the issue" please, I use FSUIPC to map everything and I don't think I have any issues [throttle retard on flare  going to reverse potentially] but ottherwise fine

 

Alex

I had the issue after installing 777. With NGX everything worked fine.

After deleting fsuipc.ini file and remaping again, the problem gone.

Throttles works without any issues with FSUIPC.

For me deleting ini file didn't help. It also didn't work skipping FSUIPC and just run through fsx. Running through FSUIPC and set both engine to one axel was the only thing that worked for me.

For me deleting the ini file and remapping didn't work either. I am now using FSX controls. The NGX works fine with FSUIPC. 

Delete the file again.  Assign the throttles "Direct to FSX axis" not "send to calibration"...Throttle 1 and 2 AXIS set (if you have separate throttles), not Throttle set.  Don't assign any other axes yet.  This makes it easier to find which  axes in the ini file are for the throttles.  Find the axis assignments in the ini file if you have to reverse the throttle axis.  They should be at the very end.  If you do need to reverse the axis add the following to the end of the axis line in the ini file...  ,*-1. (Not the period).  Now you can assign the rest of the axes, buttons etc.  You must restart FSX for the reversal of the axes to take effect.

 

The problem seems to lie with any calibration info at all in the FSUIPC.ini file.  The above setup doesn't allow for any calibration info to muddle the works.

Probably not. This is a well known issue with FSUIPC. Map anything else through FSUIPC, but not the throttle and you'll be fine.

No issue anymore, I followed Robert McDonalds guide in post #18 in this thread:

 

http://forum.avsim.net/topic/419504-throttle-problems/?fromsearch=1

 

With this dead easy "fix" the throttles works just fine with FSUIPC / A/T / HOLD.

 

Personally I try to avoid the FSX control mapping system, as I have had alot of problems with spiking and jerky movements.

 

FSUIPC is butta'

FSUIPC throttles work, assigned to FSUIPC or as direct FSX axis:

 

You have to go to the calibration site of FSUIPC and RESET the calibration and leave it uncalibrated!

 

Make an Aircraft specific profile, so no other planes would be affected

Also make sure you haven't assigned a custom slope to the throttle either otherwise that will stop it working too.

Nope, throttles are wacked!  No PMDG 777 FSUIPC calibration anywhere in the fsuipc.ini file as other 'solution threads' have suggested, and it doesn't matter if I set 'Direct to FSUIPC Calibration' or 'Send to FSX as Normal Axis'.  With the Saitek Cessna Yoke, it simply doesn't work anywhere near as well as the NGX.  I'm about to put this bird in the hanger and let PMDG figure it out, if they ever care to do so.  The throttles continue to snap back to idle upon the slightest movement of any throttle lever.  This might be the last PMDG product I buy if they continue to ignore us high-end customers whom also use FSIUPC axis assignments, instead of the crappy built-in FSX axis API.  The same "FSUIPC statement" was made in the NGX Introduction document and hardly a word was ever mentioned with regard to any difficulties between the NGX and the use of FSUIPC in these forums.  Yet, look at the number of 'throttle' threads related to the 777 and the exact same FSUIPC caveat in the 777 Introduction doc - a world of difference, and not one shred of official support or 'we're continuing to investigate' statements.  Right now, as a very, very, long time PMDG dedicated customer, I am simply not pleased!.

Probably not. This is a well known issue with FSUIPC. Map anything else through FSUIPC, but not the throttle and you'll be fine.

I've gotten my HOTAS Warthog throttles to work just fine. Rather than deleting the ini, I reset the axes for throttle 1 and 2. I.e., I unassigned them in FSUIPC and then reassigned them. I did that with all of my axes (rudder, ailerons and elevator). All is good.

FSUIPC throttle mapping was one of those things that worked immediately from memory, everything else needed more work...  So if you be more specific with your question, maybe someone here can help?

 

RE PMDG's support.  I do expect a long time wait as there can only be single digit number of support staff answer everyone (including people that are not on public forums)'s questions.  So I always ask in public forums before submitting tickets to PMDG as otherwise I have to expect a long wait.

 

And in the PMDG document, it was quite explicit that PMDG had taken the effect to make the T7 fully compatible with FSUIPC, only that they recommend that we don't calibrate using it...

Well, damn!  It looks like I'm going to have to man-up here and recant my above rant/post regarding the use of the T7 and FSUIPC - with much humility, as I go stand over in the 'corner of shame' in the back of the class.  :fool:

 

To PMDG....   I'm sorry....   :sorry:

 

The T7 does work if you set axis as Pete suggests over in his forum - with one major caveat that I just discovered on my own, after a lot more trial and error testing again today.

 

NOTE - this was not the case with the NGX and hence some considerable frustration.

 

I will now post my finding over in the 777 sub-forum.  My T7 & FSUIPC Throttle Fix - Not what I expected... thread.

No issue anymore, I followed Robert McDonalds guide in post #18 in this thread:

 

http://forum.avsim.net/topic/419504-throttle-problems/?fromsearch=1

 

With this dead easy "fix" the throttles works just fine with FSUIPC / A/T / HOLD.

 

Personally I try to avoid the FSX control mapping system, as I have had alot of problems with spiking and jerky movements.

 

FSUIPC is butta'

 

Cool - I'll have to check that out.  I've always loved the amount that I can command with FSUIPC (particularly in combination with WideFS), but I don't like how certain things can get disagreeable.