February 23, 200422 yr Hey everyone,I was getting frustrated the other night trying to complete a route for my VA when I kept getting a crash-to-desktop (CTD) in the middle of the flight. Nothing quite so maddening as flying half of a 2-hour flight 6 times.Well, I think I finally found out what was happening. My CTD occured as I approached with 26-28 miles of the HVQ VOR. I was flying a plane with RealityXP gauges (the GNS530 uses its own nav database) and didn't notice that FS2004 is reporting a duplicate entry for HVQ.Well, I start thinking add-on problems, so I start to fly default planes with all my add-on scenery deactivated... same problem.I can force a CTD at will if I fly within 26NM or so of HVQ (an MS proximity range?). Also, If I start at any airport in the US, go to the default GPS (e.g. the 500), hit the "direct to" button and enter HVQ, I get a "Duplicate Waypoints" dialog to choose between two IDENTICAL waypoints.Can anyone else reproduce this glitch, confirming either a duplicate entry for HVQ or a CTD in proximity to HVQ?Many thanks,Eric Courtney
February 23, 200422 yr Hi Eric,No and Yes. No, I cannot reproduce a CTD nearing HVQ, and in fact overflying it.Yes, I also have 'duplacate waypoint' for HVQ in the FS2004 GPS.Looking at it with FSNavigator, it shows however only one waypoint HVQ. As you know, FSNavigator gets its info from reading the BGL files.Did you perhaps install any landclass for that area? Landclass seems to be one source for CTD's.Jozef http://pluizig.ath.cx/signature.jpg
February 23, 200422 yr This has nothing to do with the VOR. It is the "seasonal CTD" issue discussed elsewhere in the forum. Making the recommended changes to TERRAIN.CFG solves the crash.
Create an account or sign in to comment