I know there was a few threads about this but I'll be darned if I can find it.

 

I remember some talk about people getting blurries regardless of what settings.. Did anyone ever figure this out?  Running v2 on Windows 7 now I seem to be running into this very problem. 

 

I've killed NI settings

P3D settings range from default to turned way down below default.

Cleared shaders

Disabled SLI

Zero scenery addons

Tried AM=84 / 85 .. No change

deleting CFG

HDR off

 

I don't recall any of this during my time on Windows 8...  So.. Looking for some input

 

Some examples

 

Look at the water here (expand it)...  Strangest thing I've ever seen

 

 

So I decided to kill all reflections.. Same results

 

 

Blurrie

 

 

Two seconds later... It finally rendered parts of the terrain

 

Found what I was looking for (Google search resulted in the AVSIM thread I was looking for).. Conversation I had with Brian.. I set AM to 14... And like magic  cores 1-2-3 all came alive and Core 0 remained free. Where as before Core 2 was pegged at 100% and the rest were sleeping. Blurries drastically reduced back to what I remember in Windows 8... 

 

 

Look at the water here (expand it)...  Strangest thing I've ever seen

 

Yep, the water appearance is not the same as the FSX "blurries" issue. It just looks bad in P3d2. There's a whole thread here about the water in P3d2, if you want to ponder various people's opinions on how and why. The REX 4 Direct screen shots of their water textures look a whole lot better in P3d2.

 

The blurry scenery is from having your settings to high. This is nothing new with the ESP family of flight simulators. Maybe the AM suggestion will help. It's worth a shot.

Yep, the water appearance is not the same as the FSX "blurries" issue. It just looks bad in P3d2. There's a whole thread here about the water in P3d2, if you want to ponder various people's opinions on how and why. The REX 4 Direct screen shots of their water textures look a whole lot better in P3d2.

 

The blurry scenery is from having your settings to high. This is nothing new with the ESP family of flight simulators. Maybe the AM suggestion will help. It's worth a shot.

 

It did help a lot.. I heard others talking about it but didn't believe it till I saw it (I was wrong!)

 

Default P3D (No AM) or AM=84. (I have HT on). They both resulted in the same thing

 

 

After setting it to 14 and still keeping HT on.

 

 

It's not the FPS I'm comparing.. It's the CPU usage that is DRASTICALLY different. 

Hi Styckx

 

Please, what is this soft you are using to display the ressources use (pink) ?

 

I'm very interested for my tests

 

 

Luc

Just MSI Afterburner (and RivaTuner which is included)..  

Ok, thank you

styckx,

 

How does this entry look in the cfg, and are you sure that that LM programmed this entry to be looked at? I am almost positive that an LM Dev posted something concerning this and other entries and stated there were not even looking at them in the cfg. I guess if you are seeing the differences in the cores beyond a shadow of a doubt then I guess you are on to something. I would though post this in the p3d forum and get it validated.

 

Regards

Bob

Just your standard

 

[JOBSCHEDULER]

AffinityMask=14

And the P3D devs included it the tuning guide (in P3D's help center)

 

 

[JOBSCHEDULER]

AffinityMask=14 Non-Default entry. This entry will not exist in your Prepar3D.cfg file by default and must be added to the file.

Performance Tuning Tip:
Prepar3D runs best with one thread per physical processor core. By default, the application will create one thread per physical processor core. On quad core plus machines, the application will leave the first physical core open to allow the operating system, drivers, and other programs to run without interfering. Please note that many AMD processors that are marketed as 4 or 8 core processors really have 2 or 4 physical cores with something analogous to hyper-threading, so the default of one thread on every other core is still the intended behaviour. The easiest method for modifying the affinity mask is to open the windows calculator in programmer view, select the binary display mode, and flip the bits in the binary number displayed to select which cores the application should run on. Note that the cores are represented right to left. /dd> 

Yeah.. The strange this is though is that AM 84 / 14 should be close to the same as not touching the cfg at all but there are clear drastic differences

 

Here is about as equal test between all three as I could conduct..

 

Engine in the plane is off..

I load P3D

Wait 3 seconds

Un-skew

Count to 3

Screenshot...  

 

No clouds or traffic etc to skew results..  The scene needs to be in motion to see the differences.. HT is on 

 

Default CFG (click to read stats)

 

 

[JOBSCHEDULER]

AffinityMask=84

 

 

 

[JOBSCHEDULER]

AffinityMask=14

 

I'll be darned. I thought for sure I read that it was not looked at. So, which setting offered the best experience for you?

 

Bob

Definitely 14.. 

 

To give credit where it's due.. Flyce was the original one who stumbled upon this.. (I think?) Whatever the case.. Someone else stumbled upon it first

 

http://forum.avsim.net/topic/427301-affinity-mask-setting/?p=2868278

Thanks, Bill. I did explicitly raise the blurry texture question, but in that thread Jimmy is the one who posted affirmative statement that AM=14 solved his blurry texture issue. I merely confirmed his results...

 

By all means, we should all be happy that this is a solved issue. Now, if LM can one day finally break the autogen thread to two or more cores, I guess we'll be in heaven. I feel that in autogen heavy scenery autogen thread maxed at 100% core usage is the only thing that absolutely limits the performance of P3D2 ...

Thanks, Bill. I did explicitly raise the blurry texture question, but in that thread Jimmy is the one who posted affirmative statement that AM=14 solved his blurry texture issue. I merely confirmed his results...

 

By all means, we should all be happy that this is a solved issue. Now, if LM can one day finally break the autogen thread to two or more cores, I guess we'll be in heaven. I feel that in autogen heavy scenery autogen thread maxed at 100% core usage is the only thing that absolutely limits the performance of P3D2 ...

 

 

The weird thing is.. When I was on Windows 8.. I had to TRRRRRY very hard to get blurries.. On Windows 7.. It's very easy..  Even very moderate settings (like default) you can still get blurries around a big city.. Difference now is they clear up somewhat fast but they still exist especially around big cities and low altitude.. In Windows 8 I was mashing the switch view button and never got them.. Windows 7, sometimes a single change to the outside will cause them.. Very strange.