Confused, so how are you getting 16X then?  

 

Cheers, Rob.

 

I have to start a flight, enter settings and change it another option, go back into the flight, enter settings again and put it back to 16x, and go back to the flight.

 

A pain in the back-side and I must report it in the LM forum... it been like this since 2.0 despite different drivers etc, so assume it an issue with the sim and not just me..

Hmmm ... I don't have that problem ... just did a re-check 16X all good.

 

1.  Setup scenario on taxi way (LSZS)

2.  Set to 16X in P3D (nothing in NI, all application controlled)

3.  Exit P3D

4.  Enter P3D loading same flight

5.  I can see 16X working

 

Is this correctly duplicating?

 

Cheers, Rob.

the only issue I have with it are "jitters" (not stutters) in external view and it slews thru the P3D world in a very uneven manner.

 

Rob, with regards to the Q400 stuttering in the external view, try switching the view mode to 'locked spot' That should get rid of them. The Q400 disables the normal 'spot' view in FSX, but since it hasn't been programmed for P3Dv2, it doesn't alter the view modes.

Craig.

 

ps, I hope that makes sense.

 

 

I have to start a flight, enter settings and change it another option, go back into the flight, enter settings again and put it back to 16x, and go back to the flight.

 

I stand corrected, I wasn't testing correctly ... yes 16X does need to be set every time one enters P3D.

EDIT: just seen your reply - Thanks for testing again Rob... I'm glad I've got confirmation. Perhaps you could relay this to the LM team, as you are in direct contact with them... things get lost on the forum.

 

 

I stand corrected, I wasn't testing correctly ... yes 16X does need to be set every time one enters P3D.

Having found my 'sweet spot' it's difficult not to feel some concern when I read that the next update (2.3) may default to using all available cores. As can be seen from my Affinity Mask setting of 14, P3D is using physical cores 1,2 and 3 and core zero is 'reserved'.

 

After reading Beau's comments I decided to try 2.2 w/o the AffinityMask of 62 which is my preferred one for hexacore leaving the whole Core0 unused by P3D:   frames dropped by 50%.  What really puzzles me is if they can change something in the engine to spread the work over all cores--or perhaps what was said was include Core0, then why the heck can't they dedicate specific elements to specific cores instead of leaving them on the main thread (if that's what's happening now), for example as w/ XPlane, dedicate traffic to a non-main core for example.   We can all see the non-main thread cores never get fully utilized, bouncing between 0 and 70% utilization or so.  For simulator components that have less critical synchronization needs (like AI traffic, road traffic, etc) that seems like the obvious route to take.   Or...was he saying the entire simulation will be balanced over all cores?  I doubt that's possible again because of the need to keep most everything in sync w/ everything else, except components as I say like traffic.

Done, reported to Wes.

 

For those not sure what this is about, this picture should clarify issue:

 

 

 

Done, reported to Wes.

 

 

Thanks Rob :smile:

I have to respectfully disagree with this. There are no negative consequences using 16x in the sims settings, unless you dislike your distant terrain being sharp.. at 4x there is noticeable loss of quality, for little or no performance gain. My issue is getting 16x to stick, as it reverts to 4x every time I start the sim, despite what it says in the settings.

 

 

The only time you get odd things happen with filtering is forcing through NI or the GPU control panel, which makes the water look blurry.

Hi Novation,

 

Well, this is a puzzle. Of course, I should accept what you are saying and, indeed, have always used a setting of 16x, whenever possible, in any application that allows it. However, in P3D, on my system at least, the difference is astonishing. It's almost as if, despite the in-sim setting telling me AF=4x is active, I am in fact seeing 16x. Very odd, but, whatever the explanation, I am very pleased with what I'm seeing. So much so, in fact, a couple of nights ago I couldn't pull myself away from the sim until 4.00am!

 

Mike

 

 

Of course, I should accept what you are saying

 

No, not at all Mike.. you need to do what you feel is best for you. The irony is even with 16x set, it seems everyone has only been seeing 4x, unless they have changed it during a flight.

 

I wonder if this is why some have complained of poor LOD when in fact it was the filtering?

I wonder if this is why some have complained of poor LOD when in fact it was the filtering?

 

AF isn't related to loading of Higher resolution textures ... if that's what you mean by LOD?

 

Cheers, Rob.

I'm glad Howard started this topic as I was having some nasty blurries with my MSE V2 photoscenery.  Only way I solved it was via locking FPS to nothing higher than 30 (which is completely the opposite of what I was doing in FSX - FSX was unlimited or locked around 60).  That was good for looking out the VC or wingview but, when I went to spot view, total blurries again and totally unacceptable.  Then I saw the recommendation to get rid of the P3D profile I had before installing P3DV2.2 and leaving the NI and display driver settings at default.  That did it!  Now I have crisp clear textures with fps set to unlimited.  I go to spot view, clear textures.  It's clearly the difference between night and day.  I have settings that are pretty much the same as Rob, maybe a little higher in some cases.  So that is definitely one thing everyone needs to do once they upgrade to P3DV2.2.  Pictures?  Okay.  Have a couple....

 

This is during departure from Chicago O'Hare

 

This is during descent into St Louis

 

Best regards,

 

 

The irony is even with 16x set, it seems everyone has only been seeing 4x, unless they have changed it during a flight.

 

Uh oh, I must have missed something.  Are you saying if you change from 4x to 16x during a flight then and only then do you see 16x filtering?  I have kept on 16x since day 1.

Are you saying if you change from 4x to 16x during a flight then and only then do you see 16x filtering?

 

Yes that's exactly what he is saying.  AF 16X on entry will actually be AF4X ... you have to goto Display settings change it to 4X, accept, then go back and change it to 16X in order to get 16X for the duration of your P3D session.  See images I posted (look at images full size, it'll be more obvious).

 

 

Pictures?  Okay.  Have a couple....

 

Lovely Jim ... ya know, when I watch live racing events on TV, I've started to notice clouds and cloud shadows, especially when they use Helicopter cams.  And I must say, P3D even in this early stage has done a very good true to real world job with the cloud shadows.

Wow that's great to know and should be easy to fix for LM.

 

Rob, did you say Vector adds the same amount of processing overhead as an FTX region, or more intermediate between plain FTXG and an FTX region?