Jump to content

Archived

This topic is now archived and is closed to further replies.

JHepburn

CTD - On descent to ORBX PNW

Recommended Posts

I've had two CTD flying the same route in the NGX. LAS-SEA Both times crash happened just past TOD. Here is the routing - SHEAD7 OAL YERIN LKV BTG OLM7 I'm not able to test if this happens in other aircraft, because this is the only FSX jet I've got installed. Here is the crash log: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58Exception code: 0xc0000005Fault offset: 0x000ba79fFaulting process id: 0xd10Faulting application start time: 0x01cc6020cf64374fFaulting application path: K:\FSX\fsx.exeFaulting module path: K:\FSX\g3d.dllReport Id: 13591867-cc29-11e0-983c-001fbc083d55

Share this post


Link to post
Share on other sites

LOL, that doesn't make any sense. i7-920 at 3.8Ghz. I've been running this system without issue for the last couple of years.

Share this post


Link to post
Share on other sites

Search this forum and the ORBX forums...there are many reports of crashes associated with the NGX and ORBX scenery. The GPU may not be the issue but rather heavy loads on FSX's ability (or lack thereof) to manage memory loads. There appear to be many variables that might affect this issue, including a user's FSX graphics and ingame settings, particularly scenery autogen, AI traffic density, etc.

Share this post


Link to post
Share on other sites

My bad - GTX 460. I will check over on the Orbx forums. Interestingly it happened at the same time on the same route and not at other add-on airports. Thanks Wayne

Share this post


Link to post
Share on other sites

The Seattle area is the Bermuda Triangle of FSX. Adding ORBX and a resource-hungry NGX to the mix doesn't make matters better. Try taking autogen and AI traffic way down, that worked for me in that area.

Share this post


Link to post
Share on other sites
Its your GPU. What kind of GPU do u have?
It's nothing to do with the gpu. As already stated many people are experiencing g3d.dll errors with various hardware configurations, from old computers to bleeding edge in PNW regions and all flying different aircraft. I for one have given up even attempting to use this region and have gotten this error 100s of times and running it on Windows 7 Pro 64bit and also XP 64 Bit. ORBX wont fully accept there is something within this region which is triggering this error, perhaps not their scenery itself but certainly causing FSX and its subsystem to throw up this frustrating fatal error. The last time I looked their forum page had 21 pages of info with various tests being carried out and no one can find a cure. I for one couldnt cure it with my i7 980x and 480GTX, did all the drivers, vanilla cfgs, fresh OS installs, default clock speeds, basic addons etc etc...spent about a month solid trying to cure it before almost binning the sim then came across the forum showing so many have this issue in this area. Chris Ibbotson

Share this post


Link to post
Share on other sites

It doesn't just happen with the NGX. I have had CTD's with the iFly NG also. You can fly the same route 10 times in a row and it will crash in the exact same place. Mine are usually NTDLL.dll related. ORBX says it's not their scenery causing it. Who knows?

Share this post


Link to post
Share on other sites

I have PNW and have flown both my PMDG 747X and MD-11 without issue. Have not done so with my NGX yet.

Share this post


Link to post
Share on other sites

i have similar issues with ORBX its not the GPU or CPU and i run and I7-970 and GTX480 somebody help US!!!

Share this post


Link to post
Share on other sites

I used to get them flying into Seattle. Then I deleted the FPS Limiter, haven't had a single one since.

Share this post


Link to post
Share on other sites

I exp the same thing when I fly from PAFA TO KDCA when getting closer to AML way point it freeze I have to close it manually.

Share this post


Link to post
Share on other sites

I just flew the NGX into JFK down the Canarsie shoot to minimums using the HUD. It was amazing...and thankfully no crash. The Bermuda Triangle reference was hilarious! So, is this localized just to Seattle in people's experience? I was thinking of getting central rockies, but I'm nervous to drop the cash now.

Share this post


Link to post
Share on other sites
Guest simmer9304
It doesn't just happen with the NGX. I have had CTD's with the iFly NG also. You can fly the same route 10 times in a row and it will crash in the exact same place. Mine are usually NTDLL.dll related. ORBX says it's not their scenery causing it. Who knows?
There's some interesting testing going on behind the scenes at ORBX on CTD's. Some fixes have been found but Seattle was pretty terrible to begin with. Some of it is rather amazing how much of FSX ACES 'forgot' to put in. Missing textures, missing models, all sorts of missing things. Yes, there is also a bit of developer error in there too I found it in my own work and in other work. Regards, Alex

Share this post


Link to post
Share on other sites
I used to get them flying into Seattle. Then I deleted the FPS Limiter, haven't had a single one since.
I tried it with or without fps limiter installed to no avail, still got the error. Can invoke it by flying a flightplan as mentioned on ORBX forum and just passing Olympia VOR to head south towards Portland will cause it to crash no matter what my scenery settings are :( Chris Ibbotson

Share this post


Link to post
Share on other sites

So this thead is only about ORBX scenery in the USA? I don't have Pacific Northwest or any ORBX USA scenery but I do have 4 Airports from ORBX in Austrailia that are awesome, and a joy to fly into everytime. YBCS - Cairns / YBBN - Brisbane / YSCB - Canberra / YMML - Melborne Only issues I ever had with these was Melbourne when it first came out was FPS heavy but when Melbourne 2.0 came out that was all fixed. The other issue was with Cairns when pulling up to gate would collide with some invisible object. This has also been fixed. All four run flawlessly for me now. So if your using an older version go to their website and Get the patches. YMML - No Patch but current version is 2.0YSCB - Patch version is 1.10YBBN - Patch version is 1.21YBCS - Patch version is 1.10

Share this post


Link to post
Share on other sites
I have tried the uiautomationcore.dll file as well which didnt work, its only linked to Black Screen of Deaths (from accessing menus) or a CTD with your Event Viewer stating that module was at fault. In PNW, and even up into Rockies scenery from ORBX I was still getting the G3D.dll crash and no amount of tinkering would cure it or changes to my settings or even hardware as tried various cpu, memory and gpus Chris Ibbotson
So this thead is only about ORBX scenery in the USA? I don't have Pacific Northwest or any ORBX USA scenery but I do have 4 Airports from ORBX in Austrailia that are awesome, and a joy to fly into everytime. YBCS - Cairns / YBBN - Brisbane / YSCB - Canberra / YMML - Melborne Only issues I ever had with these was Melbourne when it first came out was FPS heavy but when Melbourne 2.0 came out that was all fixed. The other issue was with Cairns when pulling up to gate would collide with some invisible object. This has also been fixed. All four run flawlessly for me now. So if your using an older version go to their website and Get the patches. YMML - No Patch but current version is 2.0YSCB - Patch version is 1.10YBBN - Patch version is 1.21YBCS - Patch version is 1.10
Many users also get the CTD around FTX's Brisbane Airport, perhaps when running it alongside their texture replacement packages for Gold Coast etc Chris Ibbotson

Share this post


Link to post
Share on other sites

Well I been using Uiautomationcore.dll fix for over a year and never had any problems with it. Actually by installing it i have rarely had a crash to desktop since. I can't even remember the last time it happened other than the X52 Pro - NGX issue but I solved that one. If UIAUTOMATIONCORE.dll is crashing you then something else in your setup is conflicting with it. I do notice a lot of you are using Windows 7. I am still on 64-bit Vista cause after years of customizing and getting FSX to run so smooth, it just doesn't make sense to switch. If it aint broke don't mess with it. I won't have any problems with Brisbane cause I only using the ORBX airports and that is all. Another thing to think about is FSX Acceleration. If you have it, get rid of it! Nothing but a headache with a lot of sceneries. I used to have it until one of the Pros told me FSX will run better and more glitch free with SP1 and SP2 and NO Acceleration. He was right because I been running glitch free every since. With SP1 and SP2 installed it the same thing as acceleration without the extra planes and headaches. Other than that the only tweaks I did to my FSX.cfg were Highmemfix=1BufferPools=0Shader 3.0 ModENB Series Mod With the above configuration I can run Rex at 4096 resolution and still get pretty good frame rates on my low end system using a mix of high to ultra high settings. I am on a Q6600 Quad Core overclocked to 3.0 ghz, 8 gig of ram and an 8800 GTX card. FSX on all addons on a Dedicated Drive Do plan on upgrading soon to a next-gen Sandy Bridge or IVY Bridge. A little worried about the upgrade though cause even the guys with 4.4 ghz overclocks seem to have a lot of issues.

Share this post


Link to post
Share on other sites

×
×
  • Create New...