Howdy,Just wondering if anybody else has experienced a seasonal CTD whilst flying in NZ in the past couple of days (especially on the Eastern coast of the South Island)?Last night, set up FS2004 for a flight using the C172SP (with RealAir Simulation .air file and panel) between NZCH and NZOM. For weather, downloaded a METAR from the IFALDA site (which links to the NOAA site) for the time of the flight (0845hrs.) and ran it through the freeware weather programme, FSMETAR.About 25 minutes into the flight (just south of NZHR), computer CTD's! Refering to the MS "crash" report, discovered the culprit was: weather.dll.Oookay.Stopped FSMETAR, loaded FS again (but duplicated the local weather in the Customize Weather screen) and picked up the flight (courtesy of AutoSave) several minutes prior to the previous CTD. Two-three minutes down the track, Bang! over she falls, again. This time the MS report lists ntdll.dll as the problem.Okkkkay.Rebooted, used EndItAll to close down various programmes, CTR-ALT-DEL all other non-essential programmes, and did a West Coast test flight from NZMF-NZQN (followed the coastline to John O'Groates river, up the valley to Park Pass, crossed the Hollyford and Rees rivers, over the Richardson's, and keeping Coronet Peak on my left, down to Frankton and on to NZQN. Total flight time: .8 hr. ... and no sign of a CTD. Weather was set as per the second flight.Okaaay.Rebooted again (and all the usual close-down palava) and set off from NZHR to NZKI. Get as far as the coast, and am just lining up to land at Kaikoura, when ... you guessed it, CTD! This time, no bug report to MS, just a straight, unceromonious dump back to desktop.Okayyy.The problem seems to be confined to the area Rangiora-Kaikoura. Now I am using one of Robin Corn's photoreal Godzone sceneries (Cheviot), and I have yet to deactivate this particular file to see if it makes a difference. I have three custom made AFCADs (NZHR, NZKI, and NZOM) installed in the area (made by myself from AIP data). And it ain't dodgy AFCAD's, as I've run an AFCAD check on them, and they return the all clear.I suspect it may be the dreaded MS seasonal CTD bug, as NZ is now approaching the Winter solstice (June 22). Similar CTD's were reported here back in late December last year (and about 5-7 days before the Northern Hemisphere Winter Solstice (December 22).So, has anyone else experienced a similar CTD? Especially in the area immediately north of NZRT? Or anywhere else, for that matter?System specs: Compaq Presario S4040AN; Intel P4 2.66 GHz, 512 MB PC2700 DDR RAM; Albatron 128Mb GeForce4 Ti-4800SE video card running nVidia 4523 drivers; DirectX 9b; Win XP (Home); NZ150 Mesh; default LandClass; and all of Robin Corn's photoreal scenery; yada, yada, yada.

Hi Captain."I have three custom made AFCADs (NZHR, NZKI, and NZOM) installed in the area (made by myself from AIP data)."I would suspect these, first.Dick

HiI had this very same problem but around the Nelson area when using add-on scenery for NZNS. I can't remember whose scenery it was but it certainly conflicted with one of my settings - could have been the Render To Texture switch. The problem only ever appeared when I was near Nelson. So NZWN to YSSY would cause a CTD as I crossed over NZNS (climbing to FL370) and the NZWN - NZHK track at FL150. When I uninstalled the NZNS scenery add-on everything came right. I am fairly certain it was not AFCAD related. But it could well have been one of the common scenery library components that developers use.I fly into NZNS now darn nearly every evening and its never been a problem since uninstalling the scenery. Pity really - it was great scenery.

Howdy Mike,>I had this very same problem but around the Nelson area when>using add-on scenery for NZNS. I am fairly certain it>was not AFCAD related. It probably is, however. While attempting to track the problem down, I ran each and every NZ AFCAD through the AFCAD Fault checker. NZNS was one of the airports which returned a number of faults.Regards,Dorian

Howdy Dick,Yep; must admit, I did too, at first. However, they do not return any fault when running them through the AFCAD Fault checker. (And secondly, they are simply start locations at the end of the default MS rwys).Just about to do the same flight again, this time having edited the MSFS terrain.cfg so that the MaskClassMap=1 (and =3) now read MaskClassMap=0. Here's hoping :)Regards,Dorian

Hi DorianWell you could try removing the offending AFCAD and see what happens. I did that for Nelson and it did not make any difference, so I concluded that the AFCAD was not contributing. Of course, your problem is very likely caused by something else anyway.I still have a feeling though that one of the VOD/APT scenery library files could be at the core of it. PS Are you using the NZCH scenery by Ian Warren? NZCH_04 I think its called. Its excellent scenery but the 02/20 runway ends up misaligned with the ILS. I wondered if you have found that problem and if you had an AFCAD that fixes it?

Howdy Mike,>Well you could try removing the offending AFCAD and see what>happens. I did that for Nelson and it did not make any>difference, so I concluded that the AFCAD was not>contributing. Okay. Have to admit that I have had no problems with Ian's NZNS. But, it's not a regular "port o call" for my 1 man VA (thus I don't fly there very often) , so I may yet get to experience a problem afterall. :)>PS Are you using the NZCH scenery by Ian Warren? NZCH_04 I>think its called. Its excellent scenery but the 02/20 runway>ends up misaligned with the ILS. I wondered if you have found>that problem and if you had an AFCAD that fixes it?Yep, (it's my hometown airport). As I only ever fly out of the grass runway (only fly GA, I'm not into metal, meself) I know it's misaligned, but it ain't an issue for me. :) Have you tried the one by Clive Ryan. Having said that, I'm also kinda partial to John Haine's Christchurch and use his rendition of NZCH to fly out of. Just depends how the mood takes me :)Regards,Dorian

Hi Dorian.AFCAD2's fault checker is not very complete. Also, AFCAD was written before the SDKs, and AFCAD writes ML code directly... not with XML and the BGLComp program.The start locations were exactly the problem with a carribean scenery a few months ago. Removing the AFCAD files ( or altering the start points ) was the solution. It was an Antilles scenery:http://forums.avsim.net/dcboard.php?az=sho...90626&mode=fullWhen I saw you simply have start locations, it confirmed my guess that the problem is the AFCAD files.Dick

Try this:http://forums.avsim.net/user_files/80636.zipAlso works great with PAI/MRAI traffic. Great to do circuits while watching the airlines go about their business.

I could be proven wrong - BUT I think the "usual" CTD problem is the Equanox NOT the Solstice

Howdy Dick,Okay; thanks for that. Hmmmm; yes, I do remember the Antilles GPS crash bug (out of Martinique). Will run the flight again with the CTD bug terrain.cfg fix, and if that don't work will try yet again, but without the AFCAD's, and see what happens. Thanks.Regards,Dorian

Howdy Andrew,Thanks. Just outa idle curiosity, who did the AFCAD? (there's no ReadMe).Regards,Dorian