Ray,

I posted my findings over at the PMDG 747 forum (in short form, referring to this thread).

It's a pity Kryten didn't understand that this is not a RC problem but a PMDG one.

This gave one of the leading figures at the PMDG forum an easy opportunity to blame RC (being "rubbish") and declare PMDG planes to be "realistic planes behaving realistically".

Seeing that sort of attitude I doubt the support team is interested to investigate further so I hesitate to go on there.

Thanks Andreas.

 

I couldn't restrain myself and have posted my reaction to scandinavian13's comments about RC. Let's see if there's any formal response from PMDG. It does seem an astonishing oversight.

Ray,

I have seen it. Kyle Rogers' reaction is exactly why I didn't feel like going on with it.

 

 

The above was the last thing you posted 4 days ago. Since then, silence. I have spent a fair amount of time trying to resolve this problem for you so I hope you haven't given up. The problem clearly lies with the STD knob on the PMDG747 as Andreas has kindly confirmed.
 
I notice you're not even subscribed to this thread so won't be notified of new posts. A response would be appreciated.

 

I have previously acknowledged suggestions

 

 

 

Originally I thought that the solution would be simple but after many replies from people making suggestions, and which I appreciate for them spending their time,

 

Ray, I have seen on another post a claim that you are associated with RC. Is this true? If the problem lies entirely with PMDG and RC is at no fault it would seem that it would be best to curtail this thread and concentrate on the PMDG forum. i cannot expect RC to sort a PMDG problem out. They cannot be expected to be as savvy with how  PMDG works as PMDG support.

 

 

 

Now that I'm home I can better help with this problem. Please indulge me and load the default FSX 747-400.
 
Locate your aircraft at your preferred airport / runway and go into Weather / Advanced Weather and set pressure to 989. Obviously do not run any weather program.
 
Set up the logging in FSUIPC for offset 0330 and for it to output to the title bar.
 
Press B. You should see the value 15824 in the title bar. Dividing that by 16 gives us 989. Check the pressure shown in the altimeter bottom centre on the 2D panel. It should show 989 / 29.20.
 
With RC running take off and climb to cruise. When you pass the Transition Altitude manually adjust the altimeter to 1013 / 29.92. As you do this you will notice the altitude on the tape on the PFD increases. The FSUIPC readout in the title bar should be 16209 or 16214. The difference is 9ft which will not matter to RC.
 
Let me know how you get on. If that works on the default 747 then use that as a guide when you switch to the PMDG one.

 

I did what you suggested. I don't know how anyone can fly the default 747. It has no EFIS, no FMC, no LNAV, no VNAV and no FMA's (just to name a few things missing). When i set the altitude to 6000ft and A/P on the aircraft it just continued climbing past 6000ft instead of levelling off. I am going to have to read the RC manual again as it was different from the PMDG. I got weather and clearance but no pushback and ground options. All there was in the window was the next 2 waypoints. No response from RC after clearance obtained and no options in the window to ask for anything.

 

As I said earlier I appreciate the time and effort put in by those in this forum but if the problem is a PMDG one then they should sort it out. I have been in contact with PMDG support and await there answer. I cannot expect other people to spend any more time on this problem than they have already done.

 

 

 

Actually I never noticed that behaviour. Maybe it has to do with the initial low pressure, and hopefully it will be fixed in PMDG's version 2.

 

You seem to be implying that the problem is a bug with the PMDG and as such no amount of effort by Ray, Agutz, Ronzie or myself is going to help. It would just be a waste of time.

 

 

 

I have spent a fair amount of time trying to resolve this problem for you so I hope you haven't given up.

 

I appreciate it but the problem is not yours, it is PMDG's. It is not a question of giving up but being realistic and realistically I don't believe that a PMDG problem can be best investigated in an RC forum. You have spent a lot of time ( I have spent a lot more time following up suggestions) on a problem that I now know is not your problem and cannot expect you to spend even more time on it.

Ray, I have seen on another post a claim that you are associated with RC. Is this true? If the problem lies entirely with PMDG and RC is at no fault it would seem that it would be best to curtail this thread and concentrate on the PMDG forum. i cannot expect RC to sort a PMDG problem out. They cannot be expected to be as savvy with how PMDG works as PMDG support.

 

 

Perhaps you missed my signature block. I was heavily involved in beta testing RC back in 2006 and regularly provide forum support.

 

I agree that further discussion on this thread is probably pointless as the fault clearly lies with PMDG and the STD button. But, as a workaround you should dial 29.92 / 1013 on the altimeter when appropriate. That is in effect the same as pressing the STD button.

 

I did what you suggested. I don't know how anyone can fly the default 747. It has no EFIS, no FMC, no LNAV, no VNAV and no FMA's (just to name a few things missing). When i set the altitude to 6000ft and A/P on the aircraft it just continued climbing past 6000ft instead of levelling off. I am going to have to read the RC manual again as it was different from the PMDG. I got weather and clearance but no pushback and ground options. All there was in the window was the next 2 waypoints. No response from RC after clearance obtained and no options in the window to ask for anything.

 

 

It's easy to fly the default aircraft without LNAV and VNAV. Just use the top line in the RC window for the heading to your next waypoint and use the HDG control on the autopilot. I'm not suggesting you do that for all your flights. Merely a way to test the scenario I described a couple of days ago. I don't understand why you had problems with the aircraft climbing above the altitude set on the a/p. It worked fine for me. You need to engage Vertical Speed mode and dial up 1800fpm.

 

Using a default aircraft won't affect how RC operates. Perhaps you need more experience with the tutorial flights? Only you know that.

 

As I said earlier I appreciate the time and effort put in by those in this forum but if the problem is a PMDG one then they should sort it out. I have been in contact with PMDG support and await there answer. I cannot expect other people to spend any more time on this problem than they have already done.

 

 

The purpose of recent posts by me was to give you an alternative to using the STD button. I agree a post here won't draw PMDGs attention to an apparent defect in their product. Have you raised a formal support ticket or just a post on their 'unofficial' AvSim forum? They probably don't read AvSim's much.

 

I appreciate it but the problem is not yours, it is PMDG's. It is not a question of giving up but being realistic and realistically I don't believe that a PMDG problem can be best investigated in an RC forum. You have spent a lot of time ( I have spent a lot more time following up suggestions) on a problem that I now know is not your problem and cannot expect you to spend even more time on it.

 

 

Agreed. I have given you all the info required should you wish to continue flying the 747 and use the workaround suggested. Perhaps when you fly next you will try that and let us know if it was successful.

 

 

It's easy to fly the default aircraft without LNAV and VNAV. Just use the top line in the RC window for the heading to your next waypoint and use the HDG control on the autopilot. I'm not suggesting you do that for all your flights. Merely a way to test the scenario I described a couple of days ago. I don't understand why you had problems with the aircraft climbing above the altitude set on the a/p. It worked fine for me. You need to engage Vertical Speed mode and dial up 1800fpm.
 
Using a default aircraft won't affect how RC operates. Perhaps you need more experience with the tutorial flights? Only you know that.

 

I did as you suggested above and after clearance cleared me to 6000ft I took off, climbed at 1600fpm to 6000 Ft and above but did not hear a thing from RC. At 7000ft I descended back to 6000ft. After 15 minutes I climbed to 18000 and in all this time never a word from ATC. I will try again.

 

 

 

The purpose of recent posts by me was to give you an alternative to using the STD button. I agree a post here won't draw PMDGs attention to an apparent defect in their product. Have you raised a formal support ticket or just a post on their 'unofficial' AvSim forum? They probably don't read AvSim's much.

 

I have contacted PMDG support ticket. Their response was that the problem is not due to the PMDG 747 but is caused by RC.

 

As I said previously, continuing posts about a PMDG problem on a Radar Contact forum is inappropriate and I will be posting no more replies here. 

 

 

I did as you suggested above and after clearance cleared me to 6000ft I took off, climbed at 1600fpm to 6000 Ft and above but did not hear a thing from RC. At 7000ft I descended back to 6000ft. After 15 minutes I climbed to 18000 and in all this time never a word from ATC. I will try again.

 

Why are you having these problems with RC? You are starting well away from the runway aren't you? You must go through the process of Clearance, contact GND for taxi clearance to the appropriate runway and as you approach that runway you'll get clearance to line up and wait. Once take-off clearance is given you should then be fine.

 

I have contacted PMDG support ticket. Their response was that the problem is not due to the PMDG 747 but is caused by RC.

Really! Sounds like they're not taking you seriously. It's very easy to demonstrate the STD button isn't working. It doesn't need RC to be running to prove that. Ask them to set manual pressure of 989 and then press STD. The altitude tape should move significantly. We have already proved it doesn't.

 

As I said previously, continuing posts about a PMDG problem on a Radar Contact forum is inappropriate and I will be posting no more replies here.

 

But if they're blaming RC rather than what appears to be a problem with their own software then discussion is apprpriate. We do have independent confirmation from Andreas there is a problem with the STD button.

 

 

I did as you suggested above and after clearance cleared me to 6000ft I took off, climbed at 1600fpm to 6000 Ft and above but did not hear a thing from RC. At 7000ft I descended back to 6000ft. After 15 minutes I climbed to 18000 and in all this time never a word from ATC. I will try again.

 

RC will stall if a required ack is not completed. Be sure you have received credit for all crosspoints identified in the RC status window.

 

Be sure your RC altitude variance is no more than 500 in its options.

 

RC keeps its own comm database. Let RC autotune your radios. For now keep com control, be sure com1 is selected in the aircraft audio annunciator panel.

 

Todays full fsuipc version is 4.936 will an 4.936a interim available:

 

http://forum.simflight.com/topic/66139-updated-modules/

 

If you change com frequencies on RC's controller panel than those changes are for that session only.

 

As Ray stated, sequences must follow.

 

Did you level off at 6,000 for a while (or FL60 if above the transition altitude) until cleared higher or did you continue climbing.

 

And to rehash, you are using RC4.3 build 3845, correct?

 

I am just rehashing to insure all procedures are being followed.

 

Now, when RC stalls like this, it is best to start a log to submit from loading your plan until the stall occurs. In order to save the log, do not attempt to quit FS until RC is closed out by alt-tabbing until the RC main window shows up. The start button now states Stop. Clicking Stop will save the log and close RC. Aborting RC through the task manager will not save the log. Now  you can close FS.

 

Go into the RC folder and rename the log maybe rcv4-date.log to make it unique so it will not be overwritten the next time you make a log. Now if you wish you can zip it up and send it to [email protected] with a subject of RC4 stalls and a description of the problem.

 

The log will show where RC stalled and hopefully offer a clue why it is not continuing.

 

 

Locate your aircraft at your preferred airport / runway and go into Weather / Advanced Weather and set pressure to 989. Obviously do not run any weather program.
 
Set up the logging in FSUIPC for offset 0330 and for it to output to the title bar.
 
Press B. You should see the value 15824 in the title bar. Dividing that by 16 gives us 989. Check the pressure shown in the altimeter bottom centre on the 2D panel. It should show 989 / 29.20.
 
With RC running take off and climb to cruise. When you pass the Transition Altitude manually adjust the altimeter to 1013 / 29.92. As you do this you will notice the altitude on the tape on the PFD increases. The FSUIPC readout in the title bar should be 16209 or 16214. The difference is 9ft which will not matter to RC.
 
Let me know how you get on. If that works on the default 747 then use that as a guide when you switch to the PMDG one.

 

I did as above but used EDDF this time instead of EPRZ which I used last time. When passing T/A I had a problem manually adjusting the QHN to 1013 as there is no EFIS and I couldn't find any other obvious way to do it. Perhaps I am missing something. Incidentally, as there is no EFIS there is no knob to press when passing T/A to set the pressure to STD. Anyway, the only way I found to set the pressure to 1013 was to go back to weather/advanced weather and reset it there. Going back to the flight I had to press B again and the altimeter tape increased as you suspected. 

 

This post is just to tie up the loose ends of past suggestions. I have said recently that as the problem is a PMDG 747 problem it should not be discussed in this forum. As such, I will not be posting any more replies here. Please do not post any yourself.