Archived

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

THRUSTER57

NGX AND ORBX

Recommended Posts

Hello, my ngx runs perfect on my i7 64bit 8gb ram 1tb nvida card until i use an airport with orbx installed sceenery then its performance is juddery,poor, slow and not good, anybody else get this, is it because they are both so power hungry.... thanksjames

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

No offense to ORBX but I can reproduce CTD all the time on some routes while others go off without a hitch. I will admit the stuff looks good but I never get CTD until I fly ORBX. As I said it only happens on some route or within some areas. But it's not worth the money and time finding these troubled spots as a CTD is never fun and without ORBX I'm 100% stable and enjoy my sim. I can get CTD near KORS on legs south to KLAS, or within 15 mins of takeoff @ YBBN witch many have and ORBX still has no explanation and if you check their forums you will see many others have crazy CTD issues in areas. To me ORBX is for if you want to GA fly a Cessna around or just play FSX for fun or eye candy and not into procedures witch is how I treat is a procedural sim so I don't need to see what HVAC unit the build on the hill has or my leaves to fall as I taxi to runway. I'm busy trying to replicate a pilots duties and task, not a take a virtual trip outside. If I wanted to see the leaves fall I'll go outside in Fall. As said all that stuff overkill and only for eye candy or only VFR flying IMO.

Share this post


Link to post
Share on other sites
No offense to ORBX but I can reproduce CTD all the time on some routes while others go off without a hitch. I will admit the stuff looks good but I never get CTD until I fly ORBX. As I said it only happens on some route or within some areas. But it's not worth the money and time finding these troubled spots as a CTD is never fun and without ORBX I'm 100% stable and enjoy my sim. I can get CTD near KORS on legs south to KLAS, or within 15 mins of takeoff @ YBBN witch many have and ORBX still has no explanation and if you check their forums you will see many others have crazy CTD issues in areas. To me ORBX is for if you want to GA fly a Cessna around or just play FSX for fun or eye candy and not into procedures witch is how I treat is a procedural sim so I don't need to see what HVAC unit the build on the hill has or my leaves to fall as I taxi to runway. I'm busy trying to replicate a pilots duties and task, not a take a virtual trip outside. If I wanted to see the leaves fall I'll go outside in Fall. As said all that stuff overkill and only for eye candy or only VFR flying IMO.
There has to be an answer to this some time. I am not willing to give up on such a great addon anymore than i am the NGX.

Share this post


Link to post
Share on other sites

Well I can find my topics in ORBX forums that are near a year old now and still no answers that are related to fixing the issue as well I'm not the topic starter so others with incidental problems in identical areas like within 15 mins leaving YBBN is popular one. Remove the ORBX and every flight before that I would get CTD was gone. It's not the aircraft as it happens with either my PMDG aircraft or my one Flight1 aircraft. As for giving up, it's not my job to trouble shoot anymore then I already have in the test they asked us to do with included removing YRED from the areas, removing the region it's in. So they know about the problem so whose given up? I have no clue if it's auto-gen or navaid within the area but me as a non developer I can only do so much and after all efforts have been exhausted what I'm I to do keep banging head on the wall or just go on with flying as prior to ORBX. I been simming since 1995; I don't need ORBX to keep me in the game! As said I use FSX as more a procedural sim. And to not sound like a total brasher, I can do 95%+ the ORBX flights no problems but I hate simming to get and in ORBX place find CTD's (witch I have only found 3 or 4 routes/areas that do it outta the 100's ORBX flight I've flown in the past) areas as without ORBX I can do as I want without worry. But I don't want to keep using it a find that 5th CTD! I've bought every scenery up until a few months ago when I decided that I was not longer running ORBX and speaking for myself I happy with my option to do so as I have not CTD since.

Share this post


Link to post
Share on other sites

ORBX says it's not their fault. The NTDLL.dll crashes happen in the same place for me whether I'm flying the iFly 737 or the PMDG NGX. I love their scenery, but I can't handle the CTD's when I'm flying in the PNW scenery.

Share this post


Link to post
Share on other sites

That's strange. I honestly can't speak for NGX yet, but i've not had a single issue flying in Orbx PNW with iether my PMDG 747X or my PMDG MD-11. Go figure???

Share this post


Link to post
Share on other sites

yea i got orbx and havnt had any ctds as of yet i make sure my settings are not maxed out

Share this post


Link to post
Share on other sites
yea i got orbx and havnt had any ctds as of yet i make sure my settings are not maxed out
Same here. I've got less than an idea rig by todays standards but never get CTD's or any other type of crashes when flying in either PNW or the AU areas. I think part of the reason for me being ok is that I don't run the huge 4096 REX clouds, dont extend my radius past the stock max setting, and dont select every option in the control panels for the large airports like YMML and YBBN. I think that people who even have the latest and greatest rigs and are getting the crashes are trying to ask too much from their rigs and get the crashes. Otherwise I can't see how I can run it fine with pretty reasonable visual settings with the NGX and be fine, while others with 2600K's and 8GB of RAM are CTD'ing, unless of course they have bad setups to begin with. I'm just glad I dont have any problems with their products. However their airports, especially their larger hubs are pretty demanding, namely the ones with the huge ground poly textures for the runways, taxiways, aprons, etc. can really drag performance down bad when using a complex a/c. I wish they could engineer their products to be a little more RAM and FPS friendly like FSDT and FlyTampa do, I know I would enjoy their stuff a lot more if they did. Sean Campbell

Share this post


Link to post
Share on other sites

Never had a problem so far with NGX at Orbx. I think you need to use the conrol panel to drop your scenery detail down. Your PC is clearly being overloaded. And as Sean says, drop your cloud res down, make some compromises. Not everything looks garbage when you lower the detail.

Share this post


Link to post
Share on other sites

yea i got all the fsdt airports and they alot better on fps than the orbx airports i find the ymml is the most hungry of the lot lol

Share this post


Link to post
Share on other sites
And as Sean says, drop your cloud res down
this helped me with REX and ORBX and NGX. had mine high and went back to 1024 bit. still nicely looking though, couldn't tell the difference. anyway, since then (knock on wood) no more OOMs in Orbx.

Share this post


Link to post
Share on other sites

+1 ORBX NT.DLL error and CTD with the NGX but somehow not with the Ifly. (australian SP4,brisbane,Melbourne,Cairns) Using 2048 HD clouds and normal Autogen. LOVE the ORBX work but as many say it has to be a comprimise between eyecandy outside OR inside :-) /Michael

Share this post


Link to post
Share on other sites

Like I mentioned on the other PNW thread on here I tried EVERYTHING to stop crashes in this region. I was flying GA aircraft either from Caranado or Flight1, using default or ASE weather and REX2 clouds (1024 texture size), tried various fsx configs including default, lowered display resolution, reduced autogen etc right down, had a default or nvinspector tweaked nvidea profile, ran my system at default clock speeds, tried Windows 7 Pro 64 bit and also XP 64 bit OS with up to date drivers and windows updates and it STILL crashed, mainly with the g3d.dll CTD. I love this scenery too but it's impossible to use it on my hardware. Oh for the record I also installed old spare components in my system, I went back from my i7 980x to my trusty old 920, I changed my Zotac 480GTX AMP to a BFG 295 and also an older 8800 Ultra, I changed my C6 DDR3 Mushkin 1600 ram to older C8 Patriot memory still crashed with G3D.DLL. I got so fed up and depressed trying to fix the unfixable Chris Ibbotson

Share this post


Link to post
Share on other sites
I got so fed up and depressed trying to fix the unfixable
chris, (y)our fellow simmer TexXxan91 had these issues and even the REX cloud texture reduction to 1024 did not help. but he actually sent me a PM that his frame rate limiter seemed to have caused crashes. no idea which one he is using but if you use one too and have not eliminated that cause yet then it may be worth a try...

Share this post


Link to post
Share on other sites
chris, (y)our fellow simmer TexXxan91 had these issues and even the REX cloud texture reduction to 1024 did not help. but he actually sent me a PM that his frame rate limiter seemed to have caused crashes. no idea which one he is using but if you use one too and have not eliminated that cause yet then it may be worth a try...
Believe me I have tried ALL viable options, reduced cloud textures, monitoring gpu demand as some think its related to load if scenery etc too demanding, I've tried with and without a fps limiter, tried it with fsx internal limiter, there isn't a single thing I have tried, different OS's, different hardware, different settings and config, different drivers....the scenery is fooked, it somehow causes issues FSX was never designed to work with. FSX would appear not to be as open sourced to allow addons as intended. Chris Ibbotson

Share this post


Link to post
Share on other sites

Guys,don't have any of ORBX sceneries but reading many of you have problems with them and PMDG 737NGX. Have you ever tried to perform a flight with other heavy aircraft addons, such as PMDG MD-11 or 747X?

Share this post


Link to post
Share on other sites

I have all of the above addons and NGX. I used to get ntdll.dll crashes all the time no matter what I enabled and disabled. It was a bad overclock. My memory O/C settings were borked. I looked at forums, spoke to ASUS, fiddled and fiddled (I'm an IT engineer which helps) and finally achieved a fast, cool and, most importantly, stable overclock. My ntdll errors went away. I *never* have them anymore. Now all I get is g3d.dll errors. g3d.dll seems to be the main renderer in FSX. From what I can gather, most of the ORBX ones come from corruption in bgl files causing GPF's in memory allocation.. ORBX are very coy about this subject, as has been pointed out above. I think the installer of one or more of their SP's perhaps? Not overwriting a critical bgl file when installing? Having two conflicting bgl files seems to be an answer. That means a complete rebuild. Although i do this at least twice a year anyway and it sucks. However, I can stop these errors, most of the time, by reducing my FSX autogen slider when flying out of, or over heavy sceneries, then kicking it back up again when I'm outback. Also, Don't change view constantly. If you want a true "real" experience then stop looking outside of your plane and then looking at the wheel well while the wheels retract, and looking at all of the cool little internal and external touches that this awesome plane has. Stick to your pilot's eyes and overhead panels. That's all you got in RL and it will stop your video card having to switch large chunks of video ram about. It works. I've tested long flights (which at some point will also always trigger a g3d error) with and without view-switching and I can get about a 5:1 ratio in favour of not switching views. Don't blame PMDG ORBX and REX for that, that's MS's sloppy programming at work. REX definitely causes g3d.dll crashes too. Don't use 4096 clouds, as pointed out above, and be careful with the runway textures on some of their preset themes. They are very heavy. FSX crashes when you ask it to do too much because it doesn't talk to your hardware very well. If they'd carried on making it and subsequently patching the code properly, it might be better..perhaps Flight will work..perhaps not Whistle.gif

Share this post


Link to post
Share on other sites
Guys,don't have any of ORBX sceneries but reading many of you have problems with them and PMDG 737NGX. Have you ever tried to perform a flight with other heavy aircraft addons, such as PMDG MD-11 or 747X?
With me anyhow the error occured within these regions using ORBX enabled scenery with heavy payware aircraft or basic GA payware aircraft. It doesn't appear to be triggered by system overload as I would even get it 'out in the sticks' as we call it in Ireland i.e. out in the middle of nowhere. It doesnt always occur within a demanding airport. Also tried with zero Ai traffic Chris Ibbotson

Share this post


Link to post
Share on other sites
Guys,don't have any of ORBX sceneries but reading many of you have problems with them and PMDG 737NGX. Have you ever tried to perform a flight with other heavy aircraft addons, such as PMDG MD-11 or 747X?
This is really making me nervous about NGX. Take a look at my post #7 and i mean "Not One Issue".

Share this post


Link to post
Share on other sites
This is really making me nervous about NGX. Take a look at my post #7 and i mean "Not One Issue".
Rick In my experience if you dont get the G3D.dll error in ORBX scenery then you probably wont as I got it in the simplist of aircraft in the outback so there wasnt much load on the system. I get very good performance with FSX and get 30fps with the NGX even using Ultimate Traffic so the crashes aren't really related to the aircraft you fly. Chris Ibbotson

Share this post


Link to post
Share on other sites
Rick In my experience if you dont get the G3D.dll error in ORBX scenery then you probably wont as I got it in the simplist of aircraft in the outback so there wasnt much load on the system. I get very good performance with FSX and get 30fps with the NGX even using Ultimate Traffic so the crashes aren't really related to the aircraft you fly. Chris Ibbotson
Thanks Chris. Please excuse my paranoia biggrin.png

Share this post


Link to post
Share on other sites

ORBX recommends turning traffic down to 16% and scenery detail to normal. Thats what I do, I was having the blue ring of death when running on high settings especially taking off out of Brisbane or approaching Melbourne. Amazing how I can run FSDT KDFW or KLAS with Megascenery and have great FPS's and no freezes( Fatal Errors). And that is with UT2 at 50% or more and dense or very dense set. When flying the GA airports in AustraliaSP4 or PNW along with Carenado type AC I can crank things up with the sliders to the right. Seattle though still requires UT2 at 16% and scenery turned down to normal.

Share this post


Link to post
Share on other sites

I just feel it would be much more enjoyable (to me) if you just find the "happy medium" so that you don,t have to keep reconfiguring this, that and the other before flying each time. Just my thoughts.

Share this post


Link to post
Share on other sites
I have all of the above addons and NGX. I used to get ntdll.dll crashes all the time no matter what I enabled and disabled. It was a bad overclock. My memory O/C settings were borked. I looked at forums, spoke to ASUS, fiddled and fiddled (I'm an IT engineer which helps) and finally achieved a fast, cool and, most importantly, stable overclock. My ntdll errors went away. I *never* have them anymore. Now all I get is g3d.dll errors. g3d.dll seems to be the main renderer in FSX. From what I can gather, most of the ORBX ones come from corruption in bgl files causing GPF's in memory allocation.. ORBX are very coy about this subject, as has been pointed out above. I think the installer of one or more of their SP's perhaps? Not overwriting a critical bgl file when installing? Having two conflicting bgl files seems to be an answer. That means a complete rebuild. Although i do this at least twice a year anyway and it sucks. However, I can stop these errors, most of the time, by reducing my FSX autogen slider when flying out of, or over heavy sceneries, then kicking it back up again when I'm outback. Also, Don't change view constantly. If you want a true "real" experience then stop looking outside of your plane and then looking at the wheel well while the wheels retract, and looking at all of the cool little internal and external touches that this awesome plane has. Stick to your pilot's eyes and overhead panels. That's all you got in RL and it will stop your video card having to switch large chunks of video ram about. It works. I've tested long flights (which at some point will also always trigger a g3d error) with and without view-switching and I can get about a 5:1 ratio in favour of not switching views. Don't blame PMDG ORBX and REX for that, that's MS's sloppy programming at work. REX definitely causes g3d.dll crashes too. Don't use 4096 clouds, as pointed out above, and be careful with the runway textures on some of their preset themes. They are very heavy. FSX crashes when you ask it to do too much because it doesn't talk to your hardware very well. If they'd carried on making it and subsequently patching the code properly, it might be better..perhaps Flight will work..perhaps not Whistle.gif
Excellent report, nothing to add, but I eliminated my g3d.dll errors over OrbX Sceneries (especially over/at YBBN) by deleting the freeware OzX Libs from the FSX library. Regards

Share this post


Link to post
Share on other sites