Sign in to follow this  
Bert Pieke

Problem with 53.16 drivers - scrolling on the kneeboard

Recommended Posts

Hi everyone,I am having a problme with the new 53.16 drivers from nvidia. I'm using a Ti4200 and I had a problem with AA like everyone else, before 52.13. Those drivers solved the problem for me, but gave me another one. While I can already check out the kneeboard while flying with 2x AA, I cannot scroll down. The only part of the kneeboard that scrolls down is a small portion on the lower part of it. This also happens with FS Nav, on the flight plan window. Only the lower part scrolls down, while almost everything else stays on the top. Looks like only the lower part is redrawn.Is anyone else having this problem? DId you solve it? How?Help appreciatted.

Share this post


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

Assuming you mean 52.16 drivers and not some beta, use 4x AA OR if you must have 2x AA, turn the AA setting in the Nvidia Control Panel to Application Controlled and turn it on in the sim.Allcott

Share this post


Link to post
Share on other sites

As best I can tell, turning AA on in the sim causes 4xAA to be set.Yes it works, but better to set it outside FS9..Another workaround is to revert to windowed mode when you want to access the kneeboard and return to full screen mode when done.. not pretty maybe, but it gets the job done and 4XAA on a Ti4200 is costly in framerate impact..

Share this post


Link to post
Share on other sites

Turning AA on in the sim causes 2x AA to be set. However, using FSNavigator and `outside` 2x FSAA causes FS to load FSNavigator very slowly.4x FSAA programmed OUTSIDE the sim offers better results and I've not noticed any difference in frame rates.Allcott

Share this post


Link to post
Share on other sites

Well, whatever gets set by checking AA in the sim causes awful framerates on my system.. much better to set AA "outside the sim"!Sample on my P4-2.8 with Ti4200:2XAA fps=28 :-)4XAA fps=21AA set inside sim fps=17 :-(

Share this post


Link to post
Share on other sites

Ok, it's a typo, I meant 52.16. I don't like to be forced to go to 4x AA, if anyone could come up with a solution....

Share this post


Link to post
Share on other sites

I think you have a workaround.. live with it and use windowed mode for your kneepad access until nvidia fixes it.

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