Hi all.

 

I've read most of the posts/topics. I see quite interesting things. Just installed my whole windows and fsx again, all fresh.

 

FSX is running almost perfectly, and what a stunning IQ gives DX10 :=)

 

But like most of the dx10 users overhere im also getting tears and stutters, I know for sure it is because of the function in Nvidia inspector which isnt working like it worked in DX9

 

Standard

1/2 screen refresh rate.

 

Ive an 120hz monitor so I got already minimal tears but I have stutters because the vsync options doenst lock it what it should need to do. (I use the 1/4 screen refresh rate options which worked just like the 1/2 for 60 hz screens)

 

If I unlock my fps in fsx it is jumping above 30fps so that's my conclusion that the new nvidia vsync function isnt working.

 

The only fix I saw on the forum was d3doverrider but that is just the old fashion way vsync method.

 

Is there a other solution or can it be fixed in the future? Otherwise I think I go back to dx9 because fsx is now not that smooth as it was with 30fps locked and vsync 1/4 = 30. Which was butter smooth.

 

Now it's just like before nvidia made that function.

 

 

Thanks!

I've got the same problem and I agree it is because of the older vSync method. Maybe if the author is still around we can ask if this functionality will ever be supported.

Hi Eef; I have no answer for your dilemma: You are correct in that using a 120 Hz refresh rate, and you're sure that it is at 120 - the native rate of the monitor (the Nvidia Control Panel-->Display-->Change Resolution shows 120), then in order for Inspector to hold the 30 fps you need that RR = 1/4 - as you have posted above.

The only reason that it wouldn't work for anyone that I can think of, is that you didn't click the "Apply Changes" after you had made them. That has been the case in more than one instance - but whether you have some peculiarity that prevents Inspector from using or sensing FSX's start - I couldn't say.

 

I go back to dx9 because fsx is now not that smooth as it was with 30fps locked and vsync 1/4 = 30. Which was butter smooth.

Does DX10 not work as DX9 did when you use those settings? If it worked in DX9 - then why not in DX10?

 

I'm not 100% sure what you're saying here, Eef... " 30fps locked and vsync 1/4 = 30" DX9 or DX10? 30 locked inside the sim , or 30 set in Inspector? Certainly 1/4 = 30 is a must-be.

Im 100% sure that my refresh rate is correctly set at 120hz. I also can confirm that via my build in monitor information menu.

 

Im think it is a dx10 problem. But im not sure, I havent tested in dx9 yet on this new install. But I just follow all the instructions like normal.

 

I applied the settings in nvidia inspector. Maybe it is something with the new driver 306.23. Which driver are u using kannwar?

 

Normally if I unlock fps in fsx.cfg and set 1/4 in nvidia inspector my fps ingame is locked at 30 fps by the nvidia inspector function.

Im 100% sure that my refresh rate is correctly set at 120hz. I also can confirm that via my build in monitor information menu.

 

Im think it is a dx10 problem. But im not sure, I havent tested in dx9 yet on this new install. But I just follow all the instructions like normal.

 

I applied the settings in nvidia inspector. Maybe it is something with the new driver 306.23. Which driver are u using kannwar?

 

Normally if I unlock fps in fsx.cfg and set 1/4 in nvidia inspector my fps ingame is locked at 30 fps by the nvidia inspector function.

 

I'm still using 301.24 and none of my vsync settings work in DX10. Works perfectly in DX9 mode however. I'm really not sure why it doesn't work - the same graphics profile is loaded for both modes surely? Unless DX10 mode uses a seperate executable which I'm pretty sure it doesn't. But I could be wrong.

306.23 here, with 1.9.6.6 for Inspector, but I don't see any change between this version and the earlier 300 series release.

 

Normally if I unlock fps in fsx.cfg and set 1/4 in nvidia inspector my fps ingame is locked at 30 fps by the nvidia inspector function.

That is the wrong setting for FSX, Eef.

 

That 30 needs to be locked in FSX - not locked in Inspector. Inspector should have "Frame-rate Limiter" set to "Off"

 

AF and AA should also both be ticked in FSX. Could this be the problem?

AA and AF are both ticked in FSX. I do also lock 30fps in fsx. But just for checking I changed it to 0. And then the fps jumps from 40-80-50-60. But I needs to be almost constant 30. Because of the nvidia inspector 1/2, 1/4 settings. Could you please post your nvidia inspector settings, the lower part.

 

My settings: It isnt forcing any vsync at all.

 

Same as yours, Eef, (the pic is very small and somewhat difficult to read - but I think it's all correct - except that it should be 1/4 RR in order to match the :-

 

[Display]

UPPER_FRAMERATE_LIMIT=30, as you had earlier mentioned.

Sorry for the misunderstanding.

 

If the vsync settins in NVI is working right. Then it should says in FSX: shift - z FPS 30 (unlimited) (fsx.cfg = UPPER_FRAMERATE_LIMIT=0)

But it didnt do that.

 

BUT.. I fixed it B)

 

I've just created a new nvidia inspector profile and removed the old one. Because of some strange reason it wasnt also working in dx9.

Never had that problem before. But everything is perfect now and smooth as butter and ive set fsx.cfg UPPER_FRAMERATE_LIMIT=30 back.

 

Now I can start to enjoy flying again ^_^

 

New Nvidia inspector settings:

Sorry for the misunderstanding.

 

If the vsync settins in NVI is working right. Then it should says in FSX: shift - z FPS 30 (unlimited) (fsx.cfg = UPPER_FRAMERATE_LIMIT=0)

But it didnt do that.

 

BUT.. I fixed it B)

 

I've just created a new nvidia inspector profile and removed the old one. Because of some strange reason it wasnt also working in dx9.

Never had that problem before. But everything is perfect now and smooth as butter and ive set fsx.cfg UPPER_FRAMERATE_LIMIT=30 back.

 

Now I can start to enjoy flying again ^_^

Yes - for sure!!

Bloody beautiful, Eef!! That's amazing! Thanks for getting back here, because it tells others who have the same problem that you have had - that it can be fixed! :drinks:

No problem :smile:

 

Next thing would be upgrading my graphics card. FSX uses to much ram and gpu load. Even with 1024 clouds textures and all scenery options disabled im getting 30fps at aerosoft Amsterdam with ngx, utx, gex, scenerytech, rex. But my gpu load is most of the time 99% which causes stutters and almost all memory is just just with 4x SGSS <_<

A 580 would be nice.. prices should be coming down about now..

 

Tops:

GTX 580, GTX 685, GTX 785

 

Mid-range:

GTX 570, GTX 670, 680, GTX 770 but you already have a 570...

I think I buy a 660 / 670 in the future. Don't have enough money for that yet. (Just bought my first car B) ) Maybe in about 2 months.

 

Is there any other settings I can change to save some load off my gpu?

 

Clouds and autogen are already resized.

Hummm... clouds, LOD, traffic, .... :lol:

 

The big ones are Road Vehicles, Scenery Complexity, Clouds (inc weather that is set) and, of course - Autogen.

 

I think most folks will want AI or GA aircraft around the airport/airfieldand so road traffic/clouds/AG or SC have to come down. Road at 10 will still give a "visible" density. You could add this one

[Terrain]

 

TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=907

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1376

 

It will ease it up a little. AG can come down to Normal or dense, DX10 "seems" to have a greater amount of scenery than DX9 did, anyway.

I think the 670 will be a big disappointment, as it's in the same "class" of GPU as your existing GPU - aimed at the mid-range, inexpensive gaming market - that is not where a 4.8 gig proc and FSX is. FSX is heavy-duty. You need to match your proc's 4.8 gig with something that's in the same class as that proc, and right now there's only the 580, which I and many others have: it is a brute, and well matches a 4.8 - 5.0 gig proc. The 685 and 785 are not around yet, but you can bet they wont be cheap.

I have a GTX 650 with 1 Gb (brand new), and just flew a nice flight from KABE to KSFB, with ALMOST no problems. All of my NVI settings are correct, but I noticed, during a top-down look, some tearing in the ground textures. See anything out of order here?