October 15, 201114 yr Commercial Member Gents- Not for nothing, but: One of the team was in the sim today checking data on a few things for the SP, and was able to verify that we may be pushing the approach idle slightly higher than it should be... We are investigating... Stay tuned... Chase: Did you let the door hit him a few times on the way out? (thanks for handling that one... I still owe you that email I promised, but check my update at the top of the forum...) Robert S. Randazzo PLEASE NOTE THAT PMDG HAS DEPARTED AVSIM You can find us at: http://forum.pmdg.com
October 15, 201114 yr Not for nothing, but: One of the team was in the sim today checking data on a few things for the SP, and was able to verify that we may be pushing the approach idle slightly higher than it should be... We are investigating... Stay tuned...Robert - in case you ever read this topic again - it's not just "too high" everywhere. In fact, your N2 numbers are a tad too LOW in many conditions. Probably the N1 (and associated thrust) is too high, correct, then there's obviously some discrepancy going on (e. g. N1 and probably thrust should be lower, while N2 should be higher).N2 should not go below 72% anytime while inflight (even in flight idle), at least this is how I understand the documentation. Approach idle could be anywhere between 72-79%. I don't want to repeat everything here as I just posted about it a day ago or so, but the NGX will easily show mid sixties on the N2 inflight. I sent Ryan a PM many weeks ago, that also contained related issues. For example ground idle should not go below 58% N2, apparently for correct IDG operation. But on very cold days it's easy to get numbers below 58. I would think the EEC should chime in in this case and do something about it. I'm sure you know better about this though. BTW This is the "other" idle thrust-and-related-issues thread, if you or anyone is interested.
October 18, 201114 yr Chase: Did you let the door hit him a few times on the way out? (thanks for handling that one... I still owe you that email I promised, but check my update at the top of the forum...) The door sure did hit him at least once on the way out Take your time please with those questions, there's no rush at all. I like your motto about family and hope you focus on your father before anything else. I was going to release the "thing" and just amend it with those questions whenever you get them done. The "thing" should hopefully be up on the server in the next few days. Sincerely, Chase My 2017 Build: Liquid Cooled i7 7700K CPU idle @ 4.2GHz | MSI GTX 1080 Gaming X 8G | 16GB's DDR4 4000 RAM | ASUS 27" 144hz Gaming Monitor | MSI Z270 M7 Motherboard | Windows 10 | Samsung 960 EVO M.2 500GB SSD
October 18, 201114 yr I don’t have Hotfix 4, or any fixes installed, and I have experienced some strange behavior at times when attempting to control the airspeed in descent. A number of years ago I cut my teeth on the LevelD 767 in FS9, which I flew for several years. Later, I migrated to the PMDG 747-400 and flew for about 18 months. So I consider myself pretty familiar with these high end airliners. Several months ago, I picked up the 737NGX, and I’m loving it. However, I have noticed some unusual behavior with the 737NGX, depending on the flight plan entered and followed. 1) For example, once the TOD is reached, in some cases, the airspeed is decreased to just prior to descending. In other cases, it just starts to descend at cruise speed, and when this happens, I have to employ that special technique that was “pinned” a while back at the top of this forum on how to handle this…it does work. 2) There is one flight I made where I seemed to come down thru the approach STAR with no effort other than adjusting the speed manually via “speed intervene.” I use this all the time rather than setting up the speeds in the FMC. 3) Another flight I experienced that was tracking the descent path properly until the FMC directed a 90 degree left turn, then all of a sudden the descent path marker jumped to over 1000 feet above the flight path from where I was prior to executing the turn (no change in altitude). 4) On one approach I was about twelve miles out on final, probably doing 180 to 190 knots and I was having a really hard time slowing down. In fact, I disregarded the structural integrity of the 737 and popped up the speed brakes to full up, dropped the gear, and went to full flaps (well above the flap speeds), and I barely got it on the runway at a reasonable speed (sorry I don’t have more data, but I don’t remember). Now, I could be doing something wrong, and I can go back and try to reproduce these conditions, but it seems to me that when you crank the speed down using “speed intervene,” I would expect that the thrust would reduce sufficiently so the bird slows down (especially at descent rates of 900 to 1000 ft/min). The behavior also seems to vary from flight to flight. But I do find this bird is really a challenge to control speed on descent, and I have to reduce my speed well before I had to when flying the LDS 767 or the PMDG 747. If you like, I can go back to see If I can reproduce? I’m looking forward to SP1 when it gets released.Bill Clark Windows 10 Pro, Ver 21H2 CPU I5-8600K 5.0GHz, GPU Nvidia RTX 3090 VRAM 24GB Gigabyte Z370 Gaming 7, 2TB M2.NVMe, RAM 32GB
October 19, 201114 yr I realy like the 737nx i've flown this aircraft 6 times on fsx not got a problem since i got more memory. Cockpit is relistic not had fast approaches though.
October 19, 201114 yr Author I do know from experience in the forum that the real life NGX is very hard to slow down while descending (with the 800 series particularly), and that PMDG has tried to model this accordingly. The question is, how realistically have they modeled this "slipperiness"? I'm in no position to opine, but after HF4 I have found the NGX is very susceptible to overspeeding the flaps upon glideslope capture, so much so that I have to drop the gear early and/or add speedbrakes while flaps are extended in a futile attempt to stay within the speed limitations of the flaps settings used during the final approach (i.e. flaps 15 or greater). It's possible there is a glitch with the EEC and the engine thrust idle behavior, i don't know. At least Robert has acknowledged here that approach idle may be incorrect, and as such that could explain why the NGX feels like a falling boulder at the glideslope capture, so there is hope that SP1 will correct this. A.J. Domingo
October 23, 201114 yr Have to agree, I've to found circumstances where even flying into a 20kt headwind, I cannot loose any speed and in fact increase speed on approach, even with flaps and gear down, most common with a heavier aircraft. Taking into account the slipperiness of the aircraft in real life, I feel there may be some issues which are hopefully being addressed in the sp. Regards James Carr
Create an account or sign in to comment