Slayer

2 is 2x 4 is 4x etc Pro tip: use Notepad++ for editing and keep the .cfg open, when you change a setting and flip back to notepad++ it will say file changed would you like to reload it. Pick yes and you can see the changes.

You can edit: [DISPLAY] ChangeTime=4.000000 TransitionTime=4.000000 TEXTURE_FILTERING=16 MSAA=0 SSAA=4 VSYNC=0 FXAA=0 section in Prepar3D.cfg and change the numbers by hand, they will probably revert back should you change any settings in the interface later or you could override in Nvidia inspector.

It really depends on your video card - MSAA doesn't require as much video memory as SSAA does. With the shift to 64 bit you need not worry about a program OOM but need to be mindful of VRAM usage because when it is exhausted you will come to a crawl. Use something like GPU - Z or EVGA precision to monitor your usage. There are several discussions around here that tell what settings will impact VRAM and GPU usage. Bottom line is it's a balancing act like all the other settings. Also even though it is presented that way in the program interface , both kinds of AA are not mutually exclusive you can combine them. Some other wrinkle to think about too :P Edit: On my system SSAA eliminates the white glitter/sparkles that you find in ORBX scenery, MSAA doesn't do as good of a job.

Probably an indicator that something is wrong with your sim. Even the weakest GPU can do mipmaps with no issues. Have you downloaded the new installers for your aircraft or are you trying to use older versions?

Uncap FPS just means you are prioritizing FPS over scenery loading. If your system cant keep up with running unlimited, blurries is the result. The slider at anything but unlimited will give more of the time slice to loading so you get that huge drop. That being said, stutters comes into the mix too when you start using Vsync and tripple buffering.

Have actually you tried it without any affinity masks and just let the sim and processor run? Theses days there is less and less need to tinker... at least establish some kind of baseline before you start tweaking anything. This isn't the FSX days where you immediately have to start throwing tweaks at it because it's an 11 year old platform.

When moving large directories like that Id recommend a tool like FastCopy. It's just too darn slow in windows it could take hours.

He doesn't post on here but hes still active on his company's forums.

Either that or you are GPU limited. Reset display settings etc back to default and start adjusting stuff one slider at a time til you start loosing FPS

I beleve the IHS is soldered on in Skylake X. Not sure about it on the Kabylake for X299 though. I imagine it will be paste because it's cheaper.

You may be relegated to an older processor because Intel and Microsoft have conspired to push us forward so there will be no chipset drivers or processor support backwards compatible for Windows 7. Edit : Chips and boards beyond 6700K I should say.

I believe I read the higher end chips can OC 2 cores now too, it will be interesting to see the impact on sims.

You're comparing an older extreme chip to a newer mainstream chip with less cores and gimped memory bandwidth, hard to see how it all pans out but I've studied it hard and don't see that much more benefit unless you put that 7700k on water and get it to 5Ghz. P3D and FSX - clock speed is king. There is now the new X299 platform coming from Intel too that looks like a better replacement for an X79 system than a mainstream Z270 chipset

FOV Calculator

I see that you are using Chase Plane , it is more than likely it has to do with the external camera or P3D's lighting system.

DirectX 12 is built into your OS , there is no possible downgrade. Shouldn't need to even run that DirectX installer on Windows 10 as everything should already be in place. If you suspect corrupted DirectX, run system file checker and scan for corrupted files on your windows install.

Still lots of other uses for FSUIPC besides a tiller. Reverse thrusters for instance or grouping 4 engines to work with 2 physical throttles etc.

FS9 models are no good and Lockheed doesn't want addons dumped into the main program folder. Waiting for a traffic package that complies with V4 SDK.

Have you tried a saved flight yet?

As Mickeyj pointed out you can mix AA modes, MSAA gets applied first then SSAA gets applied to the whole screen after the MSAA is processed. While this discussion is interesting don't base your setup on AA settings alone , if you hit 100% GPU usage with just AA alone you've left yourself nothing for other settings that require GPU processing and will get degraded performance. AA should really be one of the last things visually you set otherwise you will end up chasing settings in an endless loop.

You need ASCA , full dynamic shifting textures colors etc

It was the newer PA46 500TP MERIDIAN G1000 HD SERIES not this version that was updated unfortunately. I doubt the older Malibu Mirage will get an update.

It seems that there are two different things being said here. 1) Setting a default "scenario" where a payware aircraft is used 2) Loading the sim with said default aircraft at the default airport before then switching aircraft to the payware aircraft and choosing an airport. I was referring to number 2. It is not required as harvester pointed out and says as much in your documentation or am I reading it wrong?

There seems to be a tipping point, where scenery loading; split up amongst too many threads has no benefit or could actually slow things down. There is no hard fast number as it is also highly dependant on clock speed of the cpu, IPC of your CPU and subsystems etc etc. You'd really have to ask someone who has say gone from for instance a 4 C , 8 T or straight 4 core to a HEDT CPU with 8+ cores. I expect it drops off at or after 6 core 12 thread but it's just supposition until the community tests it further. Edit; If you have 10 people trying to screw in a lightbulb does it actually get done faster? Same thing applies here.

"Seems to work" about sums it up. Seems to work (until it doesn't) is a saying in my business. It's a saying of customers too cheap to do needed repairs and or maintenance because it "seems to work" A lot of times seems to work will add niggling little problems and annoyances. Many manufacturers won't even deal with you if their stuff isn't installed by their prescribed methods and they don't care if it "used to work like that" or any other deflection type statements that people bandy about. Bottom line is the chaos theory kicks in and there are just too many variables in not doing something the right way and it only compounds the problem tenfold when you start mixing in several more products that aren't following the OEM's guidelines either. Edit : I suggest actually trying a PMDG with default scenery before just shuffling down the list and loading your sim down with every addon, runs surprisingly good. I'm about ready to wipe V4 again and just write off my previous scenery purchases for this reason. Everyone STILL dumpers their addons into the main sim folder even though they were warned not to 2 years ago...now thats just lazy.sorry.