Landed the NGX at KEUG in the dark, 22FPS locked with all sliders to the right. What a fantastic plane, didn't flare too much as this plane is quite floaty...hit the runway fairly hard, engaged reverse thrust but I guess when you bounce 10 ft back into the air, reverse won't engage! I never managed to complete that many flights before so I guess I can now polish up on my flaring technique. I also never seen the blinking strobes on the grass verges. What a delight to be able to relax while flying, makes the experience 200% better. Now just to finish work and do a flight from KEUG up to Skagit..

I can now do a COMPLETE LOWI approach AND landing with settings and LOD cranked up!I do so hope you're genuinely proud of your work Pete?I for one am proud to have you amoung us.Sorry, that sounds a 'tad' patronising - it's not meant to. Words are not and, have never been, my thing.EDIT: Surely, parts of this should be 'stickied' somewhere?

EDDF - EGLL without CTD. I've just 3 words: Thank you Pete!

EDIT: Surely, parts of this should be 'stickied' somewhere?

There is a post that has been pinned at the top of the FSX Forum.Best regards,Jim

I have updated my fsuipc to the latest beta to cure the gd3.dll error and instead of getting that error I got another one. Not sure if it has anything to do with fsuipc.here it is:------Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58Exception code: 0xc0000005Fault offset: 0x0005b84bFaulting process id: 0xe38Faulting application start time: 0x01ccb02072303146Faulting application path: D:FSXfsx.exeFaulting module path: C:WindowsSysWOW64ntdll.dllReport Id: f17b8367-1c39-11e1-846d-90e6ba9716da

There is a post that has been pinned at the top of the FSX Forum.Best regards,Jim

ha ha.... New glasses Jim???

ntdll.dll errors point to the graphics drivers crashing.

Let me add my congratulations to Pete for his outstanding reserch and solution to this very troublesome error.Everyone's experience with FSX will be greatly enhanced through his work. ramsa329www.fs-gs.comwww.simaddx.com

Well, I could have made it a Registered User facility only. But sales are generally good inany case, so I'm not complaining. Maybe more folks will install it as a result of this and may then decide it is worth purchasing.RegardsPete

-----------------------------------------------------------------------------Exactly what I did, Pete. I would have 'rewarded' you regardless if this (crash fix) was open to the public in a free version or not. I mean c'mon....you have ramped up my value-added to FSX in leaps and bounds! Everybody knows the sheer frustration of getting through pre-check, taking to the runway...lifting off and settling in for a (you hope...) satisfying flight...and only find (usual...) that FSX dumps you to the desktop ANYWHERE....along the flight path.... My thank you's extend to having purchased two keys in the last two days. One for FSX, yesterday, and today, one for FS9. Never mind the other features of the full version that is offered. Thanks for all your work for, and to this community. Go and buy yourself a few brews with my compensation....LOL! Mitch

Will check it out some more

OK I did run with procmon and the g3d crash is after opening some AI aircraft files. I did see a bad airfile name on one of them which I fixed, but that didn't stop the g3d error unfortunately. I'm going to have to sort through all the traffic files I think and see if I can narrow it down.scott s..

Sorry about the duplicate post, but IMHO, the kudos for Pete Dowson extend to his also apparently fixing a problem not directly involving a G3D.DLL CTD or AI Traffic on my system... so this FSUIPC update merits being tested for other issues that affect FSX performance as well ! Happy Flying ! GaryGB

Petes fix sure fixed my G3D issues in PNW but I'm still being plaqued with blurries which eventually crop up despite a very high end system, my config modified by ******* online tool. also tweaked it manually from default or run default cfg. Changing the LOD doesnt help and playing around with MipBias and nVidea inspector not helping either. Got it before Petes fix and still after. My sig says Im running RAID0, as I got the blurries recently using that I wiped the system and went for FSX on a single Velociraptor. Whole system is faully defragged using O&O 15, both Space and Name/Folder systems :(

Petes fix sure fixed my G3D issues in PNW but I'm still being plaqued with blurries which eventually crop up despite a very high end system, my config modified by ******* online tool. also tweaked it manually from default or run default cfg. Changing the LOD doesnt help and playing around with MipBias and nVidea inspector not helping either. Got it before Petes fix and still after. My sig says Im running RAID0, as I got the blurries recently using that I wiped the system and went for FSX on a single Velociraptor. Whole system is faully defragged using O&O 15, both Space and Name/Folder systems

Hi Chris,Lets make sure we do not hijack this thread, but quickly: Are you still using *******' tweaks (good thing) and if so, an outside FPS limiter? If you have been using the limiter, stop, and set your FPS between 30-40 manually (start with 30) from inside FSX. Change your TextureMaxLoad= from 12 to 9, and remove the line: SWAP_WAIT_TIMEOUT=2. Also do not exceed 4.5 LOD until after this clears up. Do a system restart. That should help stop the blurries for you.If there is not an immediate improvement, copy your fsx.cfg file elsewhere and then delete the one it reads from. FSX will build you a new one, then add back your changes and the rest of his tweaks one by one, testing each time for improvements or problems. A few minutes work and it should be working well. Good luck.Kind regards,

Hi Chris,Lets make sure we do not hijack this thread, but quickly: Are you still using *******' tweaks (good thing) and if so, an outside FPS limiter? If you have been using the limiter, stop, and set your FPS between 30-40 manually (start with 30) from inside FSX. Change your TextureMaxLoad= from 12 to 9, and remove the line: SWAP_WAIT_TIMEOUT=2. Also do not exceed 4.5 LOD until after this clears up. Do a system restart. That should help stop the blurries for you.If there is not an immediate improvement, copy your fsx.cfg file elsewhere and then delete the one it reads from. FSX will build you a new one, then add back your changes and the rest of his tweaks one by one, testing each time for improvements or problems. A few minutes work and it should be working well. Good luck.Kind regards,

Thanks Stephen, I appreciate not to hijack the thread, unfornately not all my original pasted quote from Gary came through as he had said his blurries had disappeared. There's been so much good info from a lot of knowledgable people on this thread alone it seems a shame to take it elsewhere where it may be missed. The blurries aren't as bad as before, there was something on ******* tweaks causing it and whilst the default config is better (though performance diminished) I've been working from that, better than it was but still not sharp textures, I have a text file containing various tweaks which I can manually copy into the default. I have SWAP_WAIT_TIMEOUT=2 and did remove it for testing but had same issue...TextureMaxLoad= was set at 30 by ******* but I had tried removing that also and tried reducing down to 15. My cpu is verclocked and my gpu is overclocked beyond that of a 580 so shouldnt have issues keeping up. Also testing the gpu are stock speeds incase the overclock was struggling. Worst blurries were around Portland, flying over them at approx 150knots after a few tiles the blurriness would get worse until you cannot even make out roads, pausing wouldnt even allow them to reload. Will eventually get it sorted. Seems fine using GEX regions outside ORBX. Oh also tried reducing texture settings down to 30cm or even 1m and also tested changing the config to 4096 size textures. I'll try your setting of 9 later tonight. ThanksSorry also meant to say I'm using FPS Limiter 0.2 locked at 30, also tried without it. I appreciate locking fps internally reduces blurries, which it did during tests, but in many cases the fps drops so dramatically compared if unlimited which wasn't good or a choice in my opinion. Will continue testing

Hi Chris, last post for me on this subject so as not to sidetrack thread any more. The external FPS limiter will be the reason for your blurries. You must look for and find performance enhancements elsewhere, as that program is doing it to you, 100 to 1. Make sure you try the new ORBX day/night switch utility. It can make a huge difference over Portland, Seattle, New York and London when flying heavy iron.Kind regards,

Hi Chris, last post for me on this subject so as not to sidetrack thread any more. The external FPS limiter will be the reason for your blurries. You must look for and find performance enhancements elsewhere, as that program is doing it to you, 100 to 1. Make sure you try the new ORBX day/night switch utility. It can make a huge difference over Portland, Seattle, New York and London when flying heavy iron.Kind regards,

Have the switcher already and agree will discuss on another thread if need be. Tried without limiter too. Only true cure is internally limiting the fps but that often comes with a severe performance hit. Busy this weekend so will test next week.