Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Everything posted by borgfan

  1. Thanks, Creating the flight plan folder and put a checklist in my aircraft folder resolved the problem, so all is well. Just need to find a way of running the Garmin checklist creation program help file in Win7 as it is in the old unsupported format. Appreciate the speedy response. Gerard
  2. Sorry if this is a silly question, but I can't find the checklist menu within the utilities page. I'm using "GarminTrainerSetup_2000" for the trainer (version 6.41?) and GTN750 v 2.4.10 on Win7 and FSX. Running the trainer in demo mode doesn't show the checklist option. Appreciate any pointers to resolving this. Gerard
  3. Thanks Bill, I'll have a look at that. I guess its just a little disappointing that the upgraded gauge is not a straight drop-in replacement for the old, especially that RealAir made a 3d model for the gauge.. Nevertheless the RXP gauge is probably the best buy I've made for FSX, so I'll persevere for a solution.
  4. Having used the V1 GNS430 successfully in the RealAir Piston Duke, I've upgraded to the V2 gauge and am having a problem using the new 430 in the VC. I used the menu option to replace the existing V1 gauge with the new and at first appearance things seemed ok. The windowed gauge works fine, but with the VC gauge I cannot access the left lower knob clickspot to change the khz frequencies ( no mouse cursor appears). The upper knob clickspot to change mhz is ok as is the center click spot on the knob, I've not changed any other settings, but against my assumption, I wonder if the new gauge dimensions are slightly different from the old?I'd be grateful for some guidance on how to resolve this. Also the V1 gauges had the ability to popup the windowed gauge by clicking within the vc gauge window, is there a similar function in V2. Thanks Gerard
  5. Yes, I am seeing the exact same problem and also found the RAASPro addition to the xml.dll file which I think must be placed there in error.
  6. Yes, something is wrong about how this navaids are defined in FSX for this airport. You loose the DME reading as soon as the localiser is picked up, but if your aircraft happens to have something like a Bendix 62A fitted ( as per some A2A models) you can get DME by setting the frequency on the DME receiver itself. I settled for the compromise of creating a new AFCAD with DME just defined with the localiser.
  7. I believe the issue is that the default EGPO airport does not have DME on 110.9. Often FSX does not reflect reality as per current charts and airports need to be updated as required. EGPO can be easily corrected by modifying the stock airport to create a new AFCAD using ADEX.
  8. I've been in a very similar situation, out of memory errors and erratic behaviour under Winxp/32. After upgrading to Win7/64, and doing nothing else, I can now run the 737ngx without failures. As said earlier though, you may still encounter problems if running with lots of add-ons, complex airports etc. Every time I fly the NGX, I run the SceneryConfigEditor ( a brilliant freeware program) and ensure that only the scenery I need to run for the flight is loaded with FSX, thus helping ensure that memory usage is kept to a minimum. Keeping sliders to modest settings can only help as well.
  • Create New...