Paul.

 

I will set it back to 30 fps. Inspector, don't do anything with the Frame Rate Limitor? You are correct when it will run pretty good and then have a hickup and stutter. I have looked into the SSD and the ones that had them said they were great but the longevety of them were short and they had problems and had to be reformatted and start over. If SSD were more dependable I would deffently have one. When ever you put something into ram it runs like grease lighting! In the beginning I had messed with ram drives and it is amazing. Got to make my changes and see if I can get it back to normal. Half of the fun in FSX is the tweaking and running Inspector! It's a fun tool to have. Now I do have a question and that is the "over clocking" on Inspector. Has anyone ever over clocked thier cards through Inspector? Now, I do understand the ins ant outs of over clocking as far as over heating and the rest. But, in Inspector you can see the temp of the card. Enough to digest for now. Thanks for the help!

 

PS: Changed my avatar to a Waco

Les

Yep - that will always happen on any pc during the first load. In DX9 it's black, whether scenery takes longer or the aircaft or airport. The Waco has a lot going on, so the blue "DX10 business card" (my name for it) shows until the loading is complete. Having FSX on an SSD would get rid of it.

Frame rate is pretty subjective, Les: Unlimited frames: - there is a parameter or two that is ignored when this is the case, and the problem you might find with unlimited is that, as sometimes the graphics load is light - and the frames shoot up :dance: but within a few seconds - a heavy load occurs, and frames drop, :( sometimes accompanied by a hiccup - a hesitation. To even it out I set 30 as the target frame, and control the load distribution that way. 30 is very smooth, and now works with Inspector to stop the vsync tearing.

Set to 30 and use the "1/2 Refresh Rate" and "Standard" settings for vsync control (this is a new feature for Inspector) - BUT - if it's working the way you want it to -

leave it alone! :lol:

 

Paul,

 

I made the changes in Inspector as you suggested and everything went good.

 

 

Here are my FSX SETTINGS

30FPS

AA CHECKED

LENS FLARE CHECKED

LIGHT BLOOM CHECKED

ADVANCED CHECKED

 

SCENERY

COMPLEXITY MAXED

AUTOGEN MAXED

GROUND SHADOWS UN CHECKED

SPECIAL EFFECTS MAXED

 

With the changes you suggested and with the settings above I get a whole lot better flight and no stutter! There was only once while in the air got a pollygon redraw but lasted about 1 second but notiable. While flying it seemed like I was in real time flying; it seemed like I was floating in the air @ 120KNs! Just like full scale flying. FANTASTIC!!! I am still having the issue with the Waco as far as the MS label popping up when I go from the outside view to the VC mode. I will have to email tje company on this one and I am possitive they will be scratching theie heads on this one. I could figure out how to put a short video up on this page I would show you what is happening. It s weird to say the least. Thanks for the recommendations on Inspector they did make a huge differnce!

 

Les

Glad to be able to help you, Les! There's such a lot to understand, and not many places to find it. I learned from "the Grunt" this morning, that

It is only because of the fact that with DX10 and 11 you don't have to map whole VRAM to memory and this saves considerably VAS and memory.

Also, continuing that thread:

SGSS is pretty similar to SSAA, which has the highest IQ, but it is also the toughest to calculate. For example with 4xSSAA your GPU calculates 4 times the pixel amount of your set resolution and averages the colour of one represented pixel. It is heavy, because in this example your GPU consumes the bandwidth and calculation power of 7680 x 4320 regular pixels, if you are running on 1080p. With tripleview systems and 3D systems you really hit tremendous amounts of pixels to count and it brings your GPU on its knees for sure.

SGSS is a compromise where algorithm "estimates" where this same technique is wise to use, that is for example, it doesn't calculate multiple pixels for pixels comprising completely vertical or horizontal lines. This saves strain on GPU considerably, but IQ is also a bit worse. SSAA is actually called, if I remember correctly, RGSSAA or Regular Grid Super Sampling, and thus SGSSAA is Sparse Grid.