Hello all,I'm asking this here rather than in the official Orbx support forum because at this point I'm more interested in discussion with other users and seeing if this is unique to my situation than I am in asking for a support solution. Here's the situation:I have what seems to be a very stable and reliable FSX system running. I run UTX (US), GEX (NA), REX, all of the ORBX NA regions, plus Tongass X, and I use FSUIPC (registered) with the latest patches to catch the very occasional G3D.dll issues which would sometimes trip me up in and around Seattle. I can fly for hours in any of these areas, ORBX or elsewhere in NA, long flights, short flights and everything in between with absolutely no issues. None. Except - I will reliably CTD (NTDLL.DLL errors) EVERY SINGLE TIME in NRM in any of several areas. One near Kelowna, another near Nakusp and another south of Williams Lake. Weather, plane, time, altitude, season - makes no difference. Other areas in NRM, including everything south of the border, work fine.The easiest to pinpoint is the one outside of Williams Lake. If I fly out of CYWL to the YZA NDB, I will CTD a few minutes/miles south on that track. I wonder if anyone else has this kind of consistent crashing in one area, with everywhere else rock solid.Thoughts, suggestions...?Thanks,Scott

try disabaling UTX and GEX and see if that helps.

try disabaling UTX and GEX and see if that helps

Thanks for taking a crack at this Josh. UTX Cananda is not installed, so it doesn't seem too likely that something's going on there, and GEX NA shouldn't make any difference (or so "they" say), but it was worth a shot. Nope.Here's what did help - some time back someone (sorry, I don't recall who) had posted something about doing automated saves to help with these kinds of NTDLL CTDs. I had tried this manually back then (saving liberally on liftoff from Williams Lake) which resulted in the only succesful flight I'd ever made south of CYWL although not a terribly satisfying or immersive one. After installing FSUIPC some time back, I attempted automating this but it didn't seem to help. Last night I bumped the save frequency from every 30 seconds to 20 seconds and whaddya know. All the way from Williams Lake to Abbottsford with no CTDs.More tests flights are needed before I feel like I've found a solution, and even then this sure seems like a sledgehammer approach, but if it gets me there I'm at least happier.Scott

Scott, I just reinstalled my ORBX scenery and was doing a flight from Edmonton to Victoria. About 40 minutes out of Edmonton I had a CTD. The event viewer indicated that it was NTDLL.DLL. I have the latest version of FSUIPC installed whaich I thought had taken care of this. Please psot if you have a solution.

The event viewer indicated that it was NTDLL.DLL. I have the latest version of FSUIPC installed whaich I thought had taken care of this. Please psot if you have a solution.

Mike, as I understand things, FSUIPC now traps the formerly common G3D.DLL CTDs, but doesn't help with NTDLL.DLL issues. What has helped for me is using FSUIPC to autosave as I mentioned in my last followup. Moving to autosaving every 20 seconds has so far eliminated the problems I always had south of Williams Lake and outside Kelowna. I've been able to do multiple flights in these areas now without issues. Unfortunately, I think there's still a timing element involved, as I have had one (but only one) NRM NTDLL.DLL CTD (in the Princeton, BC area) since making this change.As previously mentioned, I have no issues in any other Orbx region outside of NRM, or even in the US areas of NRM.Scott

Just thought I'd update this following the big NRM patch/update/SP. Basically, the problem seems to be resolved as the release notes had indicated.

 

Turned off the autosave which mostly (but not completely) worked around the problem and did my "flight of sure NTDLL.DLL CTD" - CYWL to the YZA NDB - and on to Abbotsford. Had a marvelous flight with no problems in the new C90 King Air. In fact, this was one of those flights that makes you forget all about any issues you may have had over the last months and reminds you why you do this. Nice wx out of CYWL allowing some good sightseeing, then nasty over the mountains and on into Abbotsford where the C90 and I handled the ILS almost flawlessly. Greased it on in light rain. Orbx scenery, REX clouds at sunset, yadda, yadda, yadda. You know.

 

I'm happy. Looking forward to a nice VFR flight out of Missoula now to enjoy those (hopefully) fixed bridges along I 90 on the way to Coeur D'Alene.

 

Scott

Hello all,

 

I'm asking this here rather than in the official Orbx support forum because at this point I'm more interested in discussion with other users and seeing if this is unique to my situation than I am in asking for a support solution. Here's the situation:

 

I have what seems to be a very stable and reliable FSX system running. I run UTX (US), GEX (NA), REX, all of the ORBX NA regions, plus Tongass X, and I use FSUIPC (registered) with the latest patches to catch the very occasional G3D.dll issues which would sometimes trip me up in and around Seattle. I can fly for hours in any of these areas, ORBX or elsewhere in NA, long flights, short flights and everything in between with absolutely no issues. None.

 

Except - I will reliably CTD (NTDLL.DLL errors) EVERY SINGLE TIME in NRM in any of several areas. One near Kelowna, another near Nakusp and another south of Williams Lake. Weather, plane, time, altitude, season - makes no difference. Other areas in NRM, including everything south of the border, work fine.

 

The easiest to pinpoint is the one outside of Williams Lake. If I fly out of CYWL to the YZA NDB, I will CTD a few minutes/miles south on that track. I wonder if anyone else has this kind of consistent crashing in one area, with everywhere else rock solid.

 

Thoughts, suggestions...?

 

Thanks,

 

Scott

hi ihad the same problem as you but since the sp has come out i think it has since i havnt checked yet . but the solution that work for me and havnt had any ctd yet was to do the followin

 

 

cvx_300_FTX_NRM_LCpoly_1712_Edmonton_cutblocks.BGL

cvx_300_FTX_NRM_LCpoly_1613_Jasper_cutblocks.BGL

 

find thse files and remove them from your nrm folder make sure you back up your folder just in case it doesnt work. but it has for me and a few others that had ctd found this solution in the fscew2 voice adition for the ngx

cvx_300_FTX_NRM_LCpoly_1712_Edmonton_cutblocks.BGL

cvx_300_FTX_NRM_LCpoly_1613_Jasper_cutblocks.BGL

 

Hi Pete,

 

Thanks for the info. I'd found this workaround just before the service pack, but hadn't gotten around to removing them to try it.

 

However, these cutblock files are specifically addressed in the release notes for the SP. I'm happy to report that you no longer need to remove them. I've been flying extensively all over NRM since the patch, in areas that would previously guarantee an NTDLL CTD, and have had nothing but amazing flights over spectacular country. I can safely say that Orbx have put this problem to bed.

 

Scott

Hi Pete,

 

Thanks for the info. I'd found this workaround just before the service pack, but hadn't gotten around to removing them to try it.

 

However, these cutblock files are specifically addressed in the release notes for the SP. I'm happy to report that you no longer need to remove them. I've been flying extensively all over NRM since the patch, in areas that would previously guarantee an NTDLL CTD, and have had nothing but amazing flights over spectacular country. I can safely say that Orbx have put this problem to bed.

 

Scott

good to see that they finally fixed the ctd problem