Heads up for nvidia users

[Pete Dowson 558]

Maybe I should just wait for a 300+ release which has a fix for this listed in its changes.

 

Okay, I saw there was a Beta 302.xx release so I tried that -- same result as with 301. But i took the opportunity to look at those clocks and you are right. They were at their minimum idle values. Even trying to select the "P0" level in the overclocking tab wouldn't change that.

 

I saw the 296.10 drivers too (my previous was 295.51) so I tried those, and they work fine -- frame rates up on the limits again and the clocks match my overclocking settings.

 

I hope nVidia are working on this as it does most certainly seem to be a serious bug for some of us!

 

Regards

Pete Dowson

[Jean-Paul 167]

I hope nVidia are working on this as it does most certainly seem to be a serious bug for some of us!

 

I don't have the issue with my GPU but yes I hope they do. It is really a shame that you of all people can't enjoy the 1/2 refresh rate goodness after all you have done for the community.

[Ben Cap 89]

 

Hi Pete,

 

Some have reported 3d clock problems with the 300 series : http://forums.nvidia...pic=226930&st=0

 

You could perhaps check your clock settings with Nvidia Inspector.

 

I have this issue. It is extremely irritating and I hope they resolve it asap.

[timers15 11]

Ok I tried the new drivers, fsx framelock, and nvidia inspector vsync divider. I really thinks it's alot smoother. I was too fast on approach today and marvelled at the smoothness as I was doing energy waste turns. Normally I have my scenery off for jets but I turned it all the way up and locked at 15 fps. It was a trip seeing the little houses get bigger in the 737.

Looks good so far, I'm going to test more.

[ti_dabbelju 6]

I thought, this was something for the high-end machines only.

 

But after trying this new approach I am speechless! It really works. My fps rose some 8-10fps AND no stuttering. Brilliant!

 

Intel Core 2

2.13GHz oc => 2.66GHz

4GB RAM

GTS 250 512MB

[1st fltsimguy 466]

Okay, I saw there was a Beta 302.xx release so I tried that -- same result as with 301. But i took the opportunity to look at those clocks and you are right. They were at their minimum idle values. Even trying to select the "P0" level in the overclocking tab wouldn't change that.

 

I saw the 296.10 drivers too (my previous was 295.51) so I tried those, and they work fine -- frame rates up on the limits again and the clocks match my overclocking settings.

 

I hope nVidia are working on this as it does most certainly seem to be a serious bug for some of us!

 

Regards

Pete Dowson

 

Pete I had the identical issue, so I did what you seem to have as well, reverted to my 296.1 and everything is fine now. The 300+ series are not working correctly for me. I have a GTX260 card.

[Pete Dowson 558]

Pete I had the identical issue, so I did what you seem to have as well, reverted to my 296.1 and everything is fine now. The 300+ series are not working correctly for me.

 

I'll check now and then for updates, just in case, but I can't grumble about the performance I'm getting with the 296 version.

 

Regards

Pete

[ZKOKQ 984]

Looks like I have the issue too, on my 580. So, I hope they address this issue. I am surprised they have not released a fix, as it is widespread.Will try the drivers you are using Pete.

[Kosta 122]

What is the issue guys? Either I'm not looking at the right place or I have no problem!?

[Pete Dowson 558]

What is the issue guys? Either I'm not looking at the right place or I have no problem!?

 

Seems only us unlucky few have the problem -- 3xx.xx series drivers locking the clock rates on the video card to their minimum, the power-saving idle rates. My 40 fps + in FSX with 29x.xx drivers drops to below 12 and mostly around 4-6! Unflyable!

 

Pete

[ZKOKQ 984]

Ok, looks like I was wrong, my clock on my 580 is working. Read it wrong. Senior moment.

[nateanderson 1]

I have been quite surprised with the great performance from the 3xx drivers and NI 1.9.6.5. I set the VSync to 1/2 and keep the NI limiter off. In FSX I have the limiter set to 24. Super smooth. The only discrepancy is a little blurriness on distant objects, which is a small price to pay. Even that could probably be fixed by increasing texture resolution. My graphics card is a 9800GT.

 

Ben

[N1G 88]

I am running the latest ones and GPUZ is showing the correct clocks on my 570. Did anyone go into the overclock area of the inspector? If you do, for some reason it drops one of the clocks back, but GPUZ still reports the correct speed. Not sure what is going on there.

 

Bob

[ti_dabbelju 6]

I have been quite surprised with the great performance from the 3xx drivers and NI 1.9.6.5. I set the VSync to 1/2 and keep the NI limiter off. In FSX I have the limiter set to 24. Super smooth. The only discrepancy is a little blurriness on distant objects, which is a small price to pay. Even that could probably be fixed by increasing texture resolution. My graphics card is a 9800GT.

 

Ben

 

You could possibly play with the FIBER_FRAME_TIME_FRACTION in the MAIN section of your fs9.cfg. This will assign more or less computing power to the texture loading. I changed it to 0.33 and get very good results.

[mabe54 17]

- 1.9.6. Nvidia Inspector with Vsync set to 1/2 of monitor refresh rate

 

Srdan Kostic,

 

How, as in where, do you accomplish your above quote?

 

http://img13.imagesh...nvinspector.jpg

 

I do not even see the Vsync anywhere.

 

Chears,

 

MAB