jimmy64

I'd like to pose a follow up question since I know that FTX Central has had some work done to it. I love the regions, both Cali's and PNW. Right now I don't have them installed, just FTX Global. Flying around FSDT LAX in SC is a slideshow, but out in the sticks it's great! I'd like to install the regions, but be able to turn them off if I'm flying IFR to add on airports in the 777. My understanding is that I could enable "Global" and not North America and visit Los Angeles without having the full region loaded.

So far the fix has worked.

Okay, couldn't resist. I installed MT6 and P3D crashed the first time I loaded a scenario. Ntdll.dll to blame. I can't supply better proof that MT6 causes crashes of P3D 3.3.5 than that. Nothing else had changed. Additionally, this was a full clean install of Windows 7. After changing the miltraffic.bgl to .old I was able to load a scenario. I'm going to load the exact same flight that I had trouble with last week (no trouble yesterday w/o MT6) and I'll come back with the results.

Been there! I should stay off the forums while I'm going through a complete re-installation of Windows the sim and add-ons. Reminds me of a line in the movie Sideways, "Did you drink and dial?!"

I just completed a flight that I could not complete last week without getting the error. Was it a fresh install of everything that solved the problem, or the fact that I didn't have MT6 installed? The only way to know for sure is to now load MT6 and fly the route again. I'm on the fence about doing it though. This is the cleanest and leanest, and best running install I've ever had. That includes FSX, SP1, SP2, DX Fixer, P3D V1, V2, 3.1,3.2 and now 3.3.5. Yes I could live w/o MT6 and just use Vatsim or Pilotedge, but then there's that part of me...

Unless some development begins anew now that will take full advantage of the CPU and GPU power that is 5-10 years out, this hobby will surely die off. Sub 60 frames or micro stuttering will send people packing. Take Skylake plus 4-5 generations, same for Nvidia, fire up your sim with what you want installed and settings you like. Will you stick around if the same problems persist. Not me. I'm saying that we need a completely new simulator by that point. No more legacy code. I think that the only entity that can pull it off at this stage is LM.

Ntdll is code for "not sure what the hell happened!"

Wow. In an effort to fix the NTDLL.dll error, I rolled back to Windows 7 from 10. That didn't work. Reinstalled everything, nope. Did a clean install of 7 again. Redid my overclock and have now once again installed V3.3.5. Now I learn, all I had to do was type three freakin' letters!

Sorry to tag an older thread but I can confirm the ntdll.dll crash which started happening for me when I installed MT6 in V3. I'm reticent to even install it again. Can anyone else confirm these workarounds? I have a new Windows 7/V3.3.5 clean install running perfectly and would rather leave it out than have it cause problems.

Good idea. Now that I'm totally happy again I feel a point upgrade coming!

After giving Windows 10 a go, I decided to do a clean install of 7. Redid my overclock and installed 3.3.5. So far, I've only added REX 4, FTX Global, Toposim and UTX2. Currently have 30 frames locked with Vsync on and the smoothness is stunning. Not even a hint of a micro stutter. I have a 3820k @4.6 and a 4GB GTX 760. I'm considering leaving the ORBX regions, MyTraffic, high detail airports, non GA aircraft and add-on ATC out of this install as it's just too perfect to mess up! So I'll fire up the A2A 182 or the Duke with the GTN 750 and fly between all those small FTX global airports on Pilotedge or Vatsim and go through all the ratings. Anyone wonder how long I can hold out before I throw in an FSDT airport in an ORBX region, load up a PMDG and fire up Pilot2ATC?

Made a few adjustments and used Vibrance custom shader. It looks amazing! Great tool, kudos to the developer.

Referring to PTA.

Looks like a great utility, however, I've read section 1 of the instructions over and over, it's still clear as mud. The menu items are poorly defined and what to click on, and when, is very vague. I assume that "core" shaders are the "original" shaders. The tweaks themselves are self explanatory. What I don't find clear is what to select, before making adjustments, and then which after they are made. There are many buttons that sound too similar in function. I'm not interested in custom shaders. I just want to properly get backed up before I start, make a few lighting adjustments, and apply them. Could somebody please do a step by step, using the exact language of the selections in the utility.

Yep, that took care of it!

Yes I do have MyTraffic 6.0. In fact I didn't notice the issue until I installed it, but then I was reinstalling a lot of programs as I did a full install of 3.3.5. Any fix?

Most of my jetways at payware airports are either 10-30 feet from the terminal or they are inside the terminal. V3.3.5 Possible culprits: FTX Central 2 (the migration thing) FSX/P3D Navaids Update Hopefully this is a common problem with an easy fix!

I hope that the folks at Dovetail can dismiss the ever present inconsiderate, intolerant blowhard who who manages to ruin a fair number of threads (not naming anyone but if the shoe fits). I'll do the survey later today.

I have flashing static aircraft (FTX Global and FSDT) and cranes (ORBX SC). Windows 10, P3D 3.2 and then 3.35. Using latest Nvidia driver.

+1 for the 1070. I'm using a 760 4GB now, minor compromises, with great results! Even with all the add-ons we all seem to like.

Keep tinkering with it. With your rig you could get 30 fps fixed even with settings at high-med high. I'd recommend cloud shadows low quality and dynamic reflections at low and autogen (houses) off. I have vegetation maxed, scenery complexity maxed and don't miss the terribly modeled little boxes. With ORBX, FTX Global and UTX, once above 1000' AGL it actually looks better without them.

I need the affinity mask for cores 1-999! Leaving core 0 for the OS.

MyTraffic maybe, or VoxATC? Neither of which I use in P3D V3.

Being hands on only semi-regularly, sometimes I've forgotten more than I know about this hobby. What I don't remember today is why I was downloading Level D navdata, when I don't have the aircraft. I did use it for something.

When taking off from 16R @ KVNY using the freeware pack airport scenery, I get a 2-3 second freeze mid-field, every time. It happened in P3D 2.5, 3.1 and now 3.2. Settings all to the left make no difference. 34L and R have no problem. I don't have this issue at any other locations that I've been to, several hundred airports at least in the U.S. Anyone else notice this?