weekend_pilot

I retested the flight by resetting all of my settings in FSX. It turns out everything landed without any problems. The same procedures set me right on the runway, so I believe it was probably a configuration issue. * I reset all graphic settings to default * Restored original fsx.cfg To further test this and rule out it being my system, I fired up REX to add some load. The same result, the ILS landing was successful at KSNA. So in my case I do feel it had something to do with the FSX configuration causing the initial issue. Thanks again to everyone that responded.

What is your hardware configuration? I do not believe this is a PMDG specific issue rather a FSX issue. I have a relatively old set of hardware Intel Core 2 w/8GB of memory. My video card is a bit more modern GTX650 (which is low end), but unfortunately if you are running FSX (not prepar3d), the code is CPU bound meaning it does not effectively use the video card for driving the graphics. Therefore having the fanciest graphics card while playing FSX will not get you any results. There are a host of variables at play could be the reason why you are seeing low FPS numbers. Usually it centers around the graphics detail and what addons are running at the same time. In addition, what other guest processes are running on your system too that may be stealing CPU time. I do know this that when flying approaches and settings are somewhat high detail, it is normal for the FPS to drop significantly. I would say it is more pronounced in older hardware, newer hardware would obviously handle this better.

My traffic settings are minimal and I am not trailing anyone. Also I was unaware that FSX could even simulate wake turbulence. From a high level standpoint do the ILS procedures I am following look ok, or is KSNA ILS 19R a more complicated approach in FSX? Thanks again!

Thanks Kevin, I will give that a try. I will post back with results. I am not a real pilot so it is highly likely I am doing something wrong too. Thank you again for your response, very much appreciated.

I have flown the flightpath from KOAK to KSNA on the PMDG 737NGX prior without any issues using the autoland on ILS 19R. However recently I have been having problems with the autoland functionality. In my case just prior to reaching the runway, the aircraft will rapidly descend and my display goes from "Land 3" to "no autoland/apch warn". I found a similiar problem described here http://forum.avsim.net/topic/441447-autoland-disaster/. I am trying to ascertain if this is a FSX bug or am I doing something wrong that I must be forgetting from the past successful landings. Below is some information on my setup: [Procedures] * FSX * PMDG 737-700 NGX * AIRAC 1407 I am flying from KOAK to KSNA during my descent into the Los Angeles region, I perform the following: * Set both nav radios to KSNA ILS 19R frequency * Set the HGS runway elevation to 54 and runway length to 5701 I got these values from the IFR plate for 19R * I set both course headings for the Captain and FO to 194 * I have set a 30 degree approach in the FMC As I approach SNAKE (int) I am at an altitude of around 3600, when I am turning to align with the runway I press the VOR/LOC button once I am facing the airport I press the APP to lock on to the glidescope, shortly after this I press CMD B and both channels are active. I then set the MCP speed to the flaps 30 which is somwhere between 133-135. During this time I am extending my flaps at the correct interval when I get to flaps 15 I drop my gear, as I get close to the runway everything is great speed is good and I am at flaps 30. However just prior to reaching the runwayr, the plane will descend quickly and "no autoland" will be displayed. It should be noted that it is not stalling as it appears the autopilot is adjuting power and dropping the nose to get lower. If i continue on that course it will drop the plane a few 300-400 feet in front of the runway. To work around this I simply shutdown autopilot all together and take the aircraft in myself, but I have in the past used the autoland feature on ILS 19R without issue. [system Info] It should be noted that I do have a dated system, on average I may only get between 8-12 fps when in these approaches so while frustrating, that could be contributing to the issues. FSX is CPU bound too, so any interrupts will cause every so slight pauses which could be contributing to the issue too. However I was able to complete these approaches using the same system in the past. My installation though has been redone. Is there anything specific about 19R that I should know about, that maybe is a bug in FSX? Is it possible that the system itself could be contributing to the problems as well? Thanks again for any help and advice. Best Regards,

I have flown the flightpath from KOAK to KSNA on the PMDG 737NGX prior without any issues using the autoland on ILS 19R. However recently I have been having problems with the autoland functionality. In my case just prior to reaching the runway, the aircraft will rapidly descend and my display goes from "Land 3" to "no autoland/apch warn". I found a similiar problem described here http://forum.avsim.net/topic/441447-autoland-disaster/. I am trying to ascertain if this is a FSX bug or am I doing something wrong that I must be forgetting from the past successful landings. Below is some information on my setup: [Procedures] * FSX * PMDG 737-700 NGX * AIRAC 1407 I am flying from KOAK to KSNA during my descent into the Los Angeles region, I perform the following: * Set both nav radios to KSNA ILS 19R frequency * Set the HGS runway elevation to 54 and runway length to 5701 I got these values from the IFR plate for 19R * I set both course headings for the Captain and FO to 194 * I have set a 30 degree approach in the FMC As I approach SNAKE (int) I am at an altitude of around 3600, when I am turning to align with the runway I press the VOR/LOC button once I am facing the airport I press the APP to lock on to the glidescope, shortly after this I press CMD B and both channels are active. I then set the MCP speed to the flaps 30 which is somwhere between 133-135. During this time I am extending my flaps at the correct interval when I get to flaps 15 I drop my gear, as I get close to the runway everything is great speed is good and I am at flaps 30. However just prior to reaching the runwayr, the plane will descend quickly and "no autoland" will be displayed. It should be noted that it is not stalling as it appears the autopilot is adjuting power and dropping the nose to get lower. If i continue on that course it will drop the plane a few 300-400 feet in front of the runway. To work around this I simply shutdown autopilot all together and take the aircraft in myself, but I have in the past used the autoland feature on ILS 19R without issue. [system Info] It should be noted that I do have a dated system, on average I may only get between 8-12 fps when in these approaches so while frustrating, that could be contributing to the issues. FSX is CPU bound too, so any interrupts will cause every so slight pauses which could be contributing to the issue too. However I was able to complete these approaches using the same system in the past. My installation though has been redone. Is there anything specific about 19R that I should know about, that maybe is a bug in FSX? Is it possible that the system itself could be contributing to the problems as well? Thanks again for any help and advice. Best Regards,

I have flown the flightpath from KOAK to KSNA on the PMDG 737NGX prior without any issues using the autoland on ILS 19R. However recently I have been having problems with the autoland functionality. In my case just prior to reaching the runway, the aircraft will rapidly descend and my display goes from "Land 3" to "no autoland/apch warn". I found a similiar problem described here http://forum.avsim.net/topic/441447-autoland-disaster/. I am trying to ascertain if this is a FSX bug or am I doing something wrong that I must be forgetting from the past successful landings. Below is some information on my setup: [Procedures] * FSX * PMDG 737-700 NGX * AIRAC 1407 I am flying from KOAK to KSNA during my descent into the Los Angeles region, I perform the following: * Set both nav radios to KSNA ILS 19R frequency * Set the HGS runway elevation to 54 and runway length to 5701 I got these values from the IFR plate for 19R * I set both course headings for the Captain and FO to 194 * I have set a 30 degree approach in the FMC As I approach SNAKE (int) I am at an altitude of around 3600, when I am turning to align with the runway I press the VOR/LOC button once I am facing the airport I press the APP to lock on to the glidescope, shortly after this I press CMD B and both channels are active. I then set the MCP speed to the flaps 30 which is somwhere between 133-135. During this time I am extending my flaps at the correct interval when I get to flaps 15 I drop my gear, as I get close to the runway everything is great speed is good and I am at flaps 30. However just prior to reaching the runwayr, the plane will descend quickly and "no autoland" will be displayed. It should be noted that it is not stalling as it appears the autopilot is adjuting power and dropping the nose to get lower. If i continue on that course it will drop the plane a few 300-400 feet in front of the runway. To work around this I simply shutdown autopilot all together and take the aircraft in myself, but I have in the past used the autoland feature on ILS 19R without issue. [system Info] It should be noted that I do have a dated system, on average I may only get between 8-12 fps when in these approaches so while frustrating, that could be contributing to the issues. FSX is CPU bound too, so any interrupts will cause every so slight pauses which could be contributing to the issue too. However I was able to complete these approaches using the same system in the past. My installation though has been redone. Is there anything specific about 19R that I should know about, that maybe is a bug in FSX? Is it possible that the system itself could be contributing to the problems as well? Thanks again for any help and advice. Best Regards,

Thanks everyone, it seems that I was not notified about replies to this thread, so I assumed no one responded. Again thank you for the explanation. I talked with a few pilots, a STAR is not necessarily always assigned and most likely this flight was simply vectored to ILS19R, so I guess the answer is a STAR is not necessary in a route. Since I am in a simulation and I am not using Vatsim, or ATC for that matter, I have to kind of assume that I will be given vectors to airport for the final landing. Having flown this as a passenger I believe from SLI they are being vectored to SAGER. I am also assuming that ATC is vectoring them to line the aircraft up because SoCal air traffic is probably very heavy. In any event thank you again for all the replies.

Everything you have listed should work fine. In my opinion building the ultimate FSX PC is gated by the fact that the software itself is CPU bound. Therefore the GPU is not entirely factored into the equation. That being said the more CPU/Memory you can throw at it the better. The software itself is dated (~2006) much of the latest processor technologies, storage, memory, etc will greatly enhance the experience. The ultimate FSX PC will be when the code is updated such that it is no longer CPU bound and can really take advantage of the GPU.

I am unsure how to even go about asking this question. I fly a common Southwest route between KOAK to KSNA as a passenger. I wanted to duplicate this flight in FSX(pmdg737ng). So I went to flight aware and looked up the flight plan which according to Flightaware is KOAK COAST5 SXC KSNA. http://flightaware.com/live/flight/SWA915/history/20131008/0115Z/KOAK/KSNA Using simroutes.com or even the FMC selecting what I believe is correct has some waypoints overlapping. My question is the flight plan ends at SXC I would assume that a STAR is used for ILS19R and based on having been on this flight I believe it was Tandy3, but there is nothing in the flight plan. Therefore given that SXC was the last point in the plan, how did or what did they use in the FMc routes to get them on ILS19r? I can modify the route in the FMC. I pick COAST5 with SXC transition on arrival I have selected Tandy3 with ILS19r using SLI transition. Of course viewing the legs shows many waypoints overlapping. If anyone can clarify this route plan and how that setup may look on the FMC that would help. It may be that no matter what the legs must always be adjusted. Thanks

Noble, thanks going to page 9/9 of the FMC setup and changing "FUEL TOTAL DISPLAY from NO to YES worked. Thanks again

The failure is due to a memory access violation in the g3d.dll library file, what vdubbin points out is correct. Quick search yields this which may help you http://forum.avsim.net/topic/355100-g3ddll-workaroundfix-to-prevent-fsx-crashes/

In a majority of the screen shots I see a center display unit showing three engines in a side by side view. However in my 737NGX setup, I see a different display. Examining the FCOM manual these appear to be features, however in examining the FMC setup menus and reading the PMDG 737 Introduction manual I do not see where I can make this change. I have attached a screen shot from the FCOM manual and a screen shot of my center display in the cockpit. Does anyone know how to make this change?

Thank you for this explanation. It is quite possible a problem with FSX. I use REX to create my flight plans and it would not be a far fetch to assume that maybe FSX is not fully importing those in or something like that. Given a lot of people's responses, it appears that the best course of action may be to use ATC until it advises to resume your own navigation then use GPS. I will look into those applications. Thanks again for everyones feedback.

I can definitely do that. The actual GPS functionality is working, but I wanted to know if you should even use it if ATC is advising you what heading your aircraft should be in. For example in the flight plan I provided if using GPS, my aircraft will be taken up to JIPEM at which point ATC is advising me on their designated course. If I wanted to use GPS, I would have to ignore all of ATC's commands which is FSX is ok, but does not seem realistic. So should you use GPS up to a certain point, or should you just ignore ATC for the sake of the simulation. Thanks again for the reply.