Hi all…
New to Nav Charts. Glad i upgraded.
However, i have searched the forums and seen this seems to be an ongoing issue.
I have latest version installed on both my pc and Samsung tablet.
The pc has the blurries which seem to clear as you move the mouse over the screen.
My tablet has no blurries whatsoever
!
I have tried the fix for nvidia graphics and that failed to cure the issue.
Latest drivers are installed.
Running Fsx on a Win10 machine and fully up to date.
To me it seems the refresh rate in the Nav Charts programme is slow to reload, didnt have the issue when using Charts via the Cloud…!!
Hi Skysail…
As stated, tried the "fix’ someone suggested.
That didnt work.
Changed various settings in Nvidia control panel…still no joy…
Double checked drivers…all up to date
All Windows updates installed…
Im running 3 monitors and dragging charts to any other monitor makes no difference at all…
Also reset Nvidia to defaults and re-booted pc…
Still same, charts goes fuzzy…until mouse is moved over it…
I dont gwt same issue with charts on my Samsung tablet…
What does “at times” mean exactly? Does it go blurry at specific moments? For how long? Can you describe the behavior in more detail? Could it be related to the load put on your GPU for example?
have created and flown 2 routes since this error started.
Both trips carried out successfully.
No sign of the blurred header line and nor on the side pane ie the menus…
I had changed the settings for FXAA etc but that yielded no solution. Set them back as per original settings.
Only thing done differently after setting change was to go to default settings.
Whether or not someting in the settings was slightly amiss i don’t know as now the blurries have gone.
I will monitor this closely for a month and see how it goes.
Thank you so much for the update! I am happy to hear that the issue is gone, and you are up and running.
It’d be nice to find the exact solution at some point. Please do not hesitate to reach out should it happen again! I will keep this topic open, since we have not been able to pin down the exact cause yet.