Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

1 Neutral

About JerryH

  • Rank

Profile Information

  • Gender
  • Location
    Bellevue, WA

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. Hi Ryan, I may not fully understand your problem, but I recently had something go wrong with airport grassy areas. For some reason, it all looked like a puddle of watery split pea soup. After checking everything I could think of, I took a look at the FS9 scenery settings under the Display tab. There I discovered "Terrain Detail" and "Water Effects" had both been set to "None". The problem was solved when I set them back to my preference of "Land Only" and "Low". I had not touched any of the settings for a long time. Why or how did they change? I have no idea, but maybe it will give you something else to check. Regards, JerryH
  2. I believe NAM also includes the effect of winds.In flight planning, the ground distance plus the effect of winds will determine the NAM. Regards,JerryH
  3. Have you checked to see if your KSNA runway has a glideslope?My info on KSNA shows an ILS approach only for 19R.Regards,JerryH
  4. Checkout this website:http://www.cat-tamer.com/flightsim/faq001.htmlI think you will find the gauges on Disk #2.Regards,JerryH
  5. Two more ideas:Have you checked your Hardware Acceleration? If not, then (for XP) right-click the desktop, click the Settings tab, the Advanced button then the Troubleshoot tab. The Hardware Acceleration slider should be set to Full.Have you run DXDIAG lately? It may help you diagnose your problem.Regards,JerryH
  6. Hi Adam,In the 2D, it's a circular gauge on the far left, just below the brake light. Has a nice white dial.Regards,JerryH
  7. Thanks, Tom.I think I've got it sorted out now, but I've made a note of your AFCAD fix and will check it out.JerryH
  8. pschlute,That did it! Just a simple procedural change that had eluded me. Now if this old dog can just remember the new trick.I was so hung up on the way it worked for me in FS2002 that I never considered doing it any differently. Capturing the localizer with NAV (or with LOC) makes perfectly good sense. Others had hinted at doing it that way, but your demo proved it.So my friend, I owe you one. My wife has plans to drag me over your way sometime next year. If I happen to see you, I'll buy you a pint or two.Best regards,JerryH
  9. pschlute,A very interesting response. As I said earlier, most of my experience is with FS2002 where my procedure worked without a hitch.I will try your procedure with the default B734, first capturing the ILS localizer with NAV, then pressing APP when closer to the GS.Incidently, I had noticed on some KSEA approaches that after pressing APP, the instrument had the localizer to my right, then it jumped over to my left. Maybe that was a clue that I missed.If I can duplicate your KSEA approach doing it the "usual" way, then the FS2002 and FS2004 autopilots must have some differences.I'll report back when time permits.Many thanks for your effort.JerryH
  10. Thanks to all who have responded.Ian: 1) I understand that disabling ALT could be normal, but in my case the aircraft does not maintain altitude. 2) In my testing, I tried to be as "plain vanilla" as possible, so I'm flying the default Boeing 737-400 with the default panel. This panel is lacking a LOC button.pschlute and Andy:As above - if normal means ALT is disabled and the APP mode maintains the current altitude, that would be great. But (for me) when ALT goes off, the aircraft begins a shallow dive that will not have a happy ending.Douglas:Thanks for all the testing and screen shots! I'm pleased that you feel something is amiss, though I'd prefer a solution. As mentioned earlier, my recent testing was with the default B737-400 and panel. I don't normally fly the default B734, but was just trying to be as close as possible to an out-of-the-box aircraft with no tweaks or modifications.I didn't mention in my original post that a few test flights have behaved normally. Tried the default C172 on an approach to KSEA and it was okay. Earlier, when I was "playing" with an add-on 737-200, the failure was inconsisent. Switching panels sometimes seemed to help, but success was erratic.Thanks again,JerryH
  11. Hi,You make a good point about early ILS engagement, but I'm very familiar with the KSEA approach and have never had a problem with the signal. However, I will try ~15 nm and see what happens.I didn't mention it, but I always tune the ILS frequency into NAV2 so I'll know when I'm in range.Regards,JerryH
  12. I've finally given up trying to solve an FS2004 problem and am in need of an autopilot wizard. The problem was first noticed with an add-on B732 when I was approaching KSEA and selected APP. Since then I've tried the same flight many times with the default B734, but the same thing happens. Let me explain the sequence of events.1. Everything normal during the descent to KSEA; NAV1 radio at 116.80; autopilot set to NAV and tracking the 340 radial; ALT is set to level out at 3400 feet.2. Levels out at 3400 feet; DME about 30; the ILS comes alive a short time later; set NAV1 to 110.30; click on APP and it lights up; at the same time, ALT is disabled (Problem #1).3. Next, click ALT back on (pretending everything is okay); continuing to track the ILS localizer; nearing the glideslope; when the glideslope centers, nothing happens - the B734 maintains level flight (Problem #2).4. After several failures, I've learned that if I quickly click APP OFF and ON, I can salvage the approach, because ALT then turns off and the aircraft makes a nearly normal descent to the runway.I've deleted (renamed) FS9.cfg, let FS create a new one, then tried the above approach with the same aircraft and got identical results. Searched the forums and Googled the subject with nothing useful so far. With FS2002, I've performed that autopilot approach several hundred times. Only purchased FS2004 a few months ago and can't believe the AP operation should be any different. Many thanks for any suggestions.JerryH
  13. Hi Xander,I'm not the expert you were hoping for, but let me offer two suggestions.If you are one who leaves the PC running continuously, shut it down and reboot. That works for me with many problems.Next, locate the FS9.cfg fle and temporarily drag it to your desktop. When you next run FS2004, it will create a new FS9.cfg file, possible fixing your error. If this works, you may have to edit the new file to add any tweaks that you made to the original. If it made no difference, just delete the new file and drag the original from your desktop back to it's normal location.None of the above takes much time or costs any money, so you can't lose. If you are unsure about where to find the FS9.cfg file (or which one it is), come on back and someone will help.Regard,JerryH
  14. Check out this website:http://www.cat-tamer.com/flightsim/faq001.htmlLet us know if this helps.Regards,JerryH
  15. You're welcome, GIP. Glad it worked for you. Thanks for the feedback.JerryH
  • Create New...