Hi everyone.
I have recently built a very good gaming computer and I though that I wouldn't have any problems anymore for running fsx with addons and with maxed out settings. But something is still wrong since I still don't get the performance that I expected (a smooth and fast flight without lags and high FPS).

Please please please help me if you know how to fix this. It would be really appreciated!

my specs are:

core I7 3770k [email protected]

16gb of ram @1600mhz

Nvidia Geforce GTX670

128GB SSD (even though the FSX is not on the ssd)

liquid cooling

 

 

Gonna need much more information.

 

Have you added any tweaks to the .cfg? What addons do you use? What FPS are you experiencing? In what areas?

 

Don't panic. That system will more then run FSX, even with a bunch of addons in heavy scenery areas. Just need to add a few tweaks most likely.

 

Also, before you even touch FSX, make sure your computer is optimized as you would with any game. Stop all unnecessary background processes, don't run an always on anti-virus while playing, etc.

hey thank you for reply!

as for tweaks, I have used http://www.venetubo.com/fsx.html and nothing else.

I use REX, Uterrainx, Utrafficx, and bunch of cities and airports like FSDT o'hare and us-cities chicago. The frame rates are not stable. they go anywhere from 16-17 to about 30 (for example over chicago with the addons that I mentioned) but it's laggy because they aren't stable. I have also limited my frames to 30 using the nvidia inspector.   

You will want to set your Nvidia frames lock to unlimited, and use the fsx limiter. 

I tried that but it just made it worse! :(

Venotube isn't really the way to go anymore. It adds several things that are no longer necessary.

 

For starters, to get the internal limiter to work correctly (at good framerates) it has to be balanced with FFTF. With your setup I'd set it at .10. That's what I run. What you'll find is that by lowering FFTF, you'll eliminate the need to use unlimited frames as they'll converge to the same performance point.

 

This is a silver bullet many people miss. They set internal to the 30 and then freak out because their frames dropped. Well, you have to balance it. And when you do it it gives you the same performance as unlimited but without all the side effects.

 

If you leave it default (.33) then you'll see serious framerate drops with the internal limiter at 30.

 

That tweak and adding BP=0 will get you 95% of the way there. Our systems are fairly similar so I'll just show you what I'm running.

 

Delete your fsx.cfg and let it rebuild default to get rid of the stuff venotube did. Now add these:

 

[Main]
FIBER_FRAME_TIME_FRACTION=.10

 

and

 

[GRAPHICS]

HIGHMEMFIX=1

 

and

 

[bufferPools]

PoolSize=0

 

I would also add the jobscheduler tweak to get FSX off Core 0. This setting will be dependent on your processor. For my quad core, I use Affinitymask=14 with my quad core, which tells FSX to utilize Core 1,2,3 but not 0 (even though it does use 0 some). That way 0 can run windows, background processes, weather programs, etc. Depending on how many cores you have, that setting will be different for you.

 

Those tweaks take about 2 minutes to add and will make the most difference and should get you up and running. Don't waste your time chasing older outdated tweaks. They are mostly snakeoil at this point.

 

Also, setting up Nvidia inspector is important. If you don't have it, go download and install it.

 

Settings to change (I may miss some, but these are the mains ones):

 

Set AA to override any application setting, set it to 8xsq or 16xs (I use 16xs with no performance difference) and Transpareny SS to 2x Supersampling (helps eliminate shimmering).

 

Set Antistropic filtering to user defined. Set it to 16x. Set negative LOD bias to clamp.

 

And finally, set VSYNC to Force on (it should default in standard mode and that's fine).

 

Some will recommend the adaptive 1/2 refresh vsync but for guys like us who want to use heavies into highly detailed airports, holding 30 FPS locked at all times is impossible at all times and that makes that tweak unusuable. In heavy scenery in the NGX into an FSDT airport you are going to dip into the mid-20's and that's fine as it's perfectly smooth in FSX. But, the adaptive VSYNC tweak is taken out of play under locked 30 FPS.

 

If you still have questions, see Word Not Allowed's guide on this site. It's good.

 

And again, make sure your computer itself is setup correctly. Shut down all startup/background processes that aren't necessary and don't run AV software all the time. I have no real-time protection and simply scan once a week with Malwarebytes. It gets rid of all the conflicts you get with multiple games using always on AV software.

Hey!! Thank you very much!! My frames are way better now. my flights are, however, still a little bit shimmering! is there a way to make it smooth? I also had about 18-19 fps in orbx Melbourne with the orbx scenery and airport installed is this normal?

There are certain areas of the FSX world and whatnot that are probably never going to run well on any computer - just a fact unfortunately. The Seattle and Chicago areas are a couple that come to mind for me.

Hey!! Thank you very much!! My frames are way better now. my flights are, however, still a little bit shimmering! is there a way to make it smooth? I also had about 18-19 fps in orbx Melbourne with the orbx scenery and airport installed is this normal?

 

What plane are you using in that situation? I'd say with your setup, properly tuned, you should be getting better then that in Melbourne.

 

I get locked 30 pretty much everywhere unless I'm in the NGX (usually puts me in the mid-low 20's at a detailed airport in a heavy city area) and that's with a lesser system then yours (2500k at 4.5ghz, 8 gigs of ram, GTX570).

 

As for the shimmering, that's dependent on your AA settings. You have 16xS and 2x SGSS set in Nvidia Inspector (that's a 3rd party program that needs to be downloaded). I run those settings with pretty much no shimmering.

 

Here's a sampling of what mine looks and performs like with these settings. This is Orbx AU and Canberra, heavy clouds, and 100% commercial traffic.

 

I am aware of that but I am experiencing this shimmering in all the areas that I have tested (dubai, london, frankforth, san francisco, and chicago)! :( 

I was using project airbus a380

Another thing. What are you FSX sliders at?

I run autogen and scenery density both on the second highest settings. Water is a big deal as well. Use 2xLow, not the higher settings. It looks more natural anyway. Rest of the sliders on that page can pretty much be maxed out.

 

I run cars on 15%. Boats, etc. at 40%. In Orbx or UTX regions, this is plenty anyway as they produce more traffic by default.

 

Cloud draw distance at 70 miles, maximum coverage.

 

I'd suspect you have water higher then 2xLow.

I am aware of that but I am experiencing this shimmering in all the areas that I have tested (dubai, london, frankforth, san francisco, and chicago)! :(

I was using project airbus a380

 

Odd. 16xS and 2xSGSS should not show much of any shimmer.

 

But for kicks, bump up SGSS to 4x. If that doesn't stop the shimmering something else is going on.

 

Try posting a picture if you can.

Ok so I was running 2x SS not SGSS and I also use AES for my weather and Ultimate traffic X. I just did the adjustments in the settings and will test to see how it performs.

Thank you!

Wow, this is making my head spin. You can spend a lifetime sifting through all of these piecemeal suggestions, but the truth is that BALANCE is king. I have a setup that is almost identical to yours and I couldn't be happier. I'm running Orbx, UT2 at 100%, AS2012 with 2048/4096 textures and multiple addon airports in my NGX and Majestic Q400. Life is good.

 

You shouldn't short change yourself by following one-off suggestions. Instead head over to Word Not Allowed's FSX/P3D hardware and software setup blog. Follow that to the letter, and they will need a spatula and sulphuric acid to get the smile off your face.

I will try that one. At least I know that my system isn't the problem! thank you

Man, it may be better to stick with 2*4GB RAM Dual-Channel.

Aim to at least 1600MHZ and CAS9 Latency.

 

maybe not the best suggestion i can make, but your rig specs seems so damn good i need to tell you this. Remember: FSX NEVER uses more than 4GB and Windows may not need 4GB at all.

 

Go buy them as a kit, not the two separately.

Hope to help (first post in this forum! )

 

Dual-Channel doubles the data rate between the memory controller and the RAM themselves. that's why 2*4GB is the best bet. It's no use having 16GB in a single stick

Edited June 17, 201312 yr by ltnicolas