I also would like to mention that I change speed settings in P3D menu to "instrument' as Dan suggested. Now I clearly believe that it's neither my hardware, nor my set-up are to blame. I really wish to get some sort of support for more than $250 I paid for NGX\T7,

 

So far the situation looks like something either inside P3D or PMDG software blocks the controls of an aircraft during the descend phase regardless of the FMA mode (IDLE, THR, HOLD or SPD). Again, it happens ONLY during the descend. My AV was turned OFF during PMDG installation and always turn it OFF during P3D sessions.

 

 

It does not have issues like this with Airbus Extended,  

 

Best Regards

Dmitriy.

...just wanted to compete the flight I described above from saved situation and AGAIN ran into the same problem, this time at FL054, approaching VHHH 7R. See the screen attached with all these crazy artifacts. And it again - throttles and rudder are both unresponsive (and throttles are pushing to max) and ailerons and elevator are partially working

 

https://www.dropbox.com/s/k1gjalce1swo5pi/2015-8-26_23-7-2-515.jpg?dl=0

 

PS. Is someone from PMDG reading this topic or it's only me and my diary of miseries? 

...just wanted to compete the flight I described above from saved situation and AGAIN ran into the same problem, this time at FL054, approaching VHHH 7R. See the screen attached with all these crazy artifacts. And it again - throttles and rudder are both unresponsive (and throttles are pushing to max) and ailerons and elevator are partially working

 

Hi, Dmitriy,

 

I did try one thing.  I forced the TAT up to over 40oC and it didn't cause the problem.  In some of your pictures the TAT is not very high, in others it is.  But I am using FSX:SE; I don't own P3D.

 

**One other thing occurred to me:  are you saving a flight at the end of your trip and then starting up your next flight with the same saved flight?  This often causes issues.  Also, if you are using your own saved panel state at each startup try using one supplied by PMDG.  Sometimes a bug gets into a panel state, especially one saved as part of a saved flight.  Once that happens it won't go away -- you need to start with a different panel state.

 

If that suggestion doesn't work, I suggest you file a support ticket with PMDG.  That would be your best bet, seems to me.

 

Also, they are unlikely to help you in this forum if you don't always sign your full name, per their forum rules.

 

Mike

Mike, thanks for the response and your continuous help. Greatly appreciate that.

 

Here is my routine for each flight as far as saved panel situation concerned.

 

1. Load the T7 at the airport.

 

2. Load C&D panel state provided by PMDG

 

3. Make the plane alive, going through routine FS2Crew checklists, request RC4 clearance/taxi/take-off

 

4. 50-nm before T/D saving the flight via normal P3D menu as well as via RC4 menu that also automatically saves last panel state of P3D including MCP and FMC data.

 

5. Reload the flight via standard P3D Menu "load flight", then reload RC4 situation and continue the flight. Used to do the same with PRO ATC, but I didn't like the interface and switch back to RC.

 

Thus, I don't have my own customized panel state files. Each new flight I start with C&D panel state provided by PMDG.

To PMDG: My name is Dmitriy Toropov as it's been stated in the beginning of the thread.

I'm trying to submit a ticket and as I obviously forgot the password, I asked to send me a new one and the system is telling me that such e-mail address does not exist in the database. Okey...then I decided to re-register and apparently I was told that this e-mail address cannot be registered as it's already existing in the system (!!!)

 

Have no idea what to do next. Hello, PMDG!

 

Dmitriy T.

 

 

Dmitriy T.

 

Can't really look into this to find your account if I don't have your full name, as is required by the forum rules  :wink:

Can't really look into this to find your account if I don't have your full name, as is required by the forum rules  :wink:

 

Holy Christ, people....are your serious? My full name is in the post #49, the last line

 

Best Regard,

Dmitriy Toropov.

Holy Christ, people....are your serious? My full name is in the post #49, the last line

 

Best Regard,

Dmitriy Toropov.

 

Deadly serious. Follow the rules: http://www.avsim.com/topic/245586-you-must-sign-your-full-real-name-to-posts-to-use-this-forum-posts-without-names-will-be-deleted/

 

Every post.

 

We don't have the time to go hunting through everyone's post to play the "which one of this person's several posts has their actual name in it" - particularly if it's a thread with multiple pages. There's a signature function that can add this information automatically for you: Click on your user name at the top right > My Settings > Signature on the left.

 

 

 

Have there been any flights where RC4 was not running and this happened?

The first screenie shows a white arc outside the N1 gauges indicating that your throttles were moved to full... and since you are in HOLD mode this would be logical if your throttle override setting allowed override in HOLD... it's not doing it earlier because your thrust mode in probably in SPD. As soon as it changes to HOLD your throttle overrides the PMDG descent idle.

 

This can only be your game controller. Disconnect the throttle axis completely and use the F1 keys.  I bet the problem disappears.

 

Also, full names please.

The first screenie shows a white arc outside the N1 gauges indicating that your throttles were moved to full... and since you are in HOLD mode this would be logical if your throttle override setting allowed override in HOLD... it's not doing it earlier because your thrust mode in probably in SPD. As soon as it changes to HOLD your throttle overrides the PMDG descent idle.

 

This can only be your game controller. Disconnect the throttle axis completely and use the F1 keys.  I bet the problem disappears.

 

Also, full names please.

 

Dan,

 

As I mentioned earlier, in the situations like these I disconnected the joystick and tried F1. When I press F1, the throttle move back to idle, but once I release F1, they move forward again to Full position. 

 

It's neither hardware, nor FSUIPS - something internally either inside PMDG or P3D, have no idea what exactly. I double checked all of Simconnects installations - they're all fine as well.

 

Dmitriy Toropov

Deadly serious. Follow the rules: http://www.avsim.com/topic/245586-you-must-sign-your-full-real-name-to-posts-to-use-this-forum-posts-without-names-will-be-deleted/

 

Every post.

 

We don't have the time to go hunting through everyone's post to play the "which one of this person's several posts has their actual name in it" - particularly if it's a thread with multiple pages. There's a signature function that can add this information automatically for you: Click on your user name at the top right > My Settings > Signature on the left.

 

 

 

Have there been any flights where RC4 was not running and this happened?

 

 

That's my plan for this weekend. I have other "crazy" ideas as well, but I don't want to share them here until I get a proof.

 

As far as RC4 concerned, my troubles have happened not only with RC4, but with PRO ATC as well. Actually, a bunch of people are flying with both RC and PROATC and have no complaints. Maybe it's because save panel state does not work with RC4 I don't know. If it's the case, then it's sad, as the threat of OOM is the only thing that is pushing me to save flights before T/D, hence I have no choice but to 'save" before TD

 

Dmitriy Toropov

It's neither hardware, nor FSUIPS - something internally either inside PMDG or P3D

 

That's your supposition.  Not sure I'm in agreement but I'm not there to observe; it's hard to imagine how P3D would cause an uncommanded throttle axis signal and PMDG doesn't have anything to do with it other than it has logic used to determine when to ignore the axis and when to accept the axis value.  FSUIPC could definitely be the culprit, this is a very long thread and I'm not going to go back through it to read what you've already tried, my apologies for that; however, move the FSUIPC.ini file onto your desktop and make sure there is no other FSUIPC.ini file and try that.  FSUIPC will create a new ini file, that's okay.

 

What are your "Simconnects installations" and how do you determine they are all fine?

 

EDIT:  I looked back over some earlier posts and I noticed last time you removed FSUIPC.ini the problem went away for a few days and then came back.. good time to remove the FSUIPC.ini and see if the problem disappears again. If so then you have been able to isolate where the problem is coming from.

 

Why are you using FSUIPC?

That's your supposition.  Not sure I'm in agreement but I'm not there to observe; it's hard to imagine how P3D would cause an uncommanded throttle axis signal and PMDG doesn't have anything to do with it other than it has logic used to determine when to ignore the axis and when to accept the axis value.  FSUIPC could definitely be the culprit, this is a very long thread and I'm not going to go back through it to read what you've already tried, my apologies for that; however, move the FSUIPC.ini file onto your desktop and make sure there is no other FSUIPC.ini file and try that.  FSUIPC will create a new ini file, that's okay.

 

What are your "Simconnects installations" and how do you determine they are all fine?

 

 

1. By meaning "all fine", I mean that all the installation are present and other programs that heavily rely on SC, such as EZDok and GSX work flawlessly.

 

2. FSUIPSC. In the meantime, per your earlier suggestion, I'm deleting *ini file before EACH and EVERY new flight. Actually, I'm using it mostly for RC and PRO ATC. Would be happy to throw it away, but I can't. Thus, FSUIPC issue is eliminated from the puzzle as well.

 

 

I'd like to share what I noticed yesterday. First of all, a bit of trivia. Since my FS2002 days, I have been always flying with AI Traffic as it's my second FS obsession after complex planes and complex airports. For all these years I have developed some sort of technique to manually delete specific AI via Traffic Explorer, mostly those AI that are expected to depart next day or later than in 5 hours from my arrival to release gates for other incoming AI traffic.

 

Yesterday, I was descending via BETTY 2B arrival to VHHH ILS 7R approach with ASN and RC4 (saved situation was loaded) and then I decided to free up some VHHH gates from non-needed AI. I have opened Traffic Explorer, selected the AI I wanted to delete, right-clicked on "Delete" and BOOM...this throttle issue came into action immediately upon deletion of this AI as you may see on my screen at the post #47. Actually, the practice of manual AI deletion has become so natural to me and it has been always so painless, that I had not until yesterday linked it with my throttle issue with T7 at P3D. I know that perhaps it sounds crazy to you, but I literally ran out of ideas what else can be suspected, so I'm going to test this theory also.

 

Dmitriy Toropov   

Hi, everyone,

 

In several of the screen shots, the TAT usually looks quite high to me when the problem happens:

 

#31 (make sure you follow link to "FL090...") 9,000, 29o #44 FL270 +8o (no problem), 10,500 32o; #47, 5400, 41o.

 

Would someone who has P3D please try forcing a high TAT during descent in HOLD mode?  I tried this using ASN to force a high TAT during descent and nothing bad happened, but I was using FSX:SE.

 

Mike

Yes, I'm just wondering if PMDG is affected by changes made in weather engine, especially by ASN that I use.

 

 

Dmitriy Toropov

In a previous post you said P3D was in TAS mode in setttings? It should always be in IAS, you should try again with the sim in IAS mode.