Sign in to follow this  
Joakim

Annoying squares in displays.

Recommended Posts

Well first of all! I did search, just not as widely as I prob. should. So when you hit, don't hit me hard..

 

I recently upgraded my complete computer and screens, with resolution set to 1900*1080.

As I had not yet installed FSX, and P3Dv3 got released, and since i bought both the NGX and 777 for P3D when these were discounted i figured, why not just jump over to P3D.

And this works like a charm!

Now I'm going to let the picture speak for itself.

 

Currently only used settings in p3d, and no Nvidia Inspector yet(Not sure if needed?)

 

 

squares.png

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Robert.

 

I think he is mentioning the large squares in the ND .if you look closely you see the gray and black patches..if fhe terrain is switched on then this becomes very visible..they dont look lke dots but big squares.

I initially saw this a few days back but it was with 2.5. Since i had got a new 4k screen and used 1024 textures i thought the textures are getting stretched and dismissed it..but it looks like the same problem the poster is having

Joakin..by any chance are you having a 4k display??

Share this post


Link to post
Share on other sites

Pankaj,

 

Thanks- that helps.

 

Those artifacts are a result of the method we use for overlay rendering.  They have been there since day 1.

Share this post


Link to post
Share on other sites

Dear Mr. Randazzo and Pankaj,

 

First of all sorry for not specifying a bit better what the problem was.

 

Yes I'm indeed speaking about the squares in the ND,PFD and the rest of the displays.

I'm indeed running my GTX980 via DP on aa 4kscreen, although the resolution both on the computer and p3d is set to 1900*1080.

 

Noticed that when I zoomed in to *1.0 they kinda disappeared, but running the sim in these scales is not in my interest, I do indeed want to keep it realistic with POV but that is just way to zoomed in for me.

 

Kind regards

Share this post


Link to post
Share on other sites

I have the same problem with 737NGX. What is the solution to eliminate this anoing thing???

Share this post


Link to post
Share on other sites

I have the same problem with 737NGX. What is the solution to eliminate this anoing thing???

 

Check your display settings and zoom level. It's called a moire pattern, and the farther away from 1.0 that you get, the more pronounced it will be.

Share this post


Link to post
Share on other sites

I call it the "shimmering effect." Assuming we're talking about the same thing, as Kyle says, it's all about display settings and zoom. The best solution is Inspector. There's a pushpinned post by Ryan on his settings. It's a bit dated, but still highly reliable and the endless pages of posts in the thread help serve as "updates" / guidance from those that have had similar problems. Also google "shimmer" "fsx" "pmdg" and you will find a bunch of pages elsewhere that may help.

 

It's a pain, but you just have to keep tweaking it (namely, antialiasing and transparency supersampling). Most important - once you find the best configuration, be sure to save your settings, take a picture of them, etc. Every time I update my driver, I lose the settings. 

 

So, is it accurate that this limitation is attributable to the state of GPUs in general? I always thought it was another example of FSX's age, but he's in P3D.

Share this post


Link to post
Share on other sites

I call it the "shimmering effect." Assuming we're talking about the same thing, as Kyle says, it's all about display settings and zoom. The best solution is Inspector. There's a pushpinned post by Ryan on his settings. It's a bit dated, but still highly reliable and the endless pages of posts in the thread help serve as "updates" / guidance from those that have had similar problems. Also google "shimmer" "fsx" "pmdg" and you will find a bunch of pages elsewhere that may help.

 

It's a pain, but you just have to keep tweaking it (namely, antialiasing and transparency supersampling). Most important - once you find the best configuration, be sure to save your settings, take a picture of them, etc. Every time I update my driver, I lose the settings.

 

So, is it accurate that this limitation is attributable to the state of GPUs in general? I always thought it was another example of FSX's age, but he's in P3D.

Yes Kyle is right, as about that post of Nvidia Inspector is very "out of date", also is refering to Dx9, I use Dx10 with fix and Nvidia inspector, so that post is no use for me.

Share this post


Link to post
Share on other sites

So, is it accurate that this limitation is attributable to the state of GPUs in general? I always thought it was another example of FSX's age, but he's in P3D.

 

GPUs can affect how it's presented, but you can see it without a graphics machine in front of you:

 

Sit on a train with a wire fence and watch the wheels of cars as they drive by, through that fence. It's a physical effect that also has ramifications in a digital world, as well. Basically, there's a collision between the rendering of the screens "inside" the screen on your physical screen. Zooming adjusts the number of those "inside" screen pixels that need to be displayed on the physical pixels, causing the weird effect. It's probably a bit easier to see in a video:

 

EDIT - This video shows it better:

https://www.youtube.com/watch?t=92&v=jMpZ_vpWyWo

Share this post


Link to post
Share on other sites

Need my eyes checked after watching that. 

 

-Jim

Share this post


Link to post
Share on other sites

Just out of curiosity, is this also what happens to the wing whilst using a wing view? I noticed that soon after purchasing the 777... that the wing indeed has a moire pattern to it at night.

 

 

______________

Garrett Frank

Share this post


Link to post
Share on other sites

Just out of curiosity, is this also what happens to the wing whilst using a wing view? I noticed that soon after purchasing the 777... that the wing indeed has a moire pattern to it at night.

 

This is more of something Jason should answer, but there's definitely a reason behind it. I could've sworn he made a post about it (or Ryan did, explaining what he said), but I can't find it after a quick search. It was a method to sidestep some constraint we had, though, I believe.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this