Edit: Just read Mark's post - Thank You! I think you're on the way to get some kind of promotion around here, my friend!

 

See how much we agree, Kyle!

 

Ok, in the order that I find them:

 

Inspector:

1). AntiAliasing Mode should really be set to Application-controlled

2). AntAliasing - Setting is a little high for that 560.

3).Anisotropic filtering setting must be 16, otherwise a yellow taxy line, for e.g, will blur within 15 feet of the nose. 

- Otherwise - all is good'

 

FSX.cfg: Not far out of line, Kyle - I've made some small changes which will improve the overall feel, evening out the load a tad. Try it - do some testing to get BP right. 

 

 

 

I hope this helps,

 

All the Best,

 

pj

Hi Kyle,

 

I am curious to see how you went this setup... any feedback? I am trying to get mine sorted as well... cant wait for the fixer to arrive!

Heya, Doug! I can guarantee Steve is working pretty intensely on getting it out as fast as possible. There are just a couple of minor    :db:issues :db:   that need sorting out....  :Waiting: 

Hi Kyle,

 

I am curious to see how you went this setup... any feedback? I am trying to get mine sorted as well... cant wait for the fixer to arrive!

 

With your hardware you should have great results with DX10 as well. And I'm very eager for the fixer too!

 

Heya, Doug! I can guarantee Steve is working pretty intensely on getting it out as fast as possible. There are just a couple of minor    :db:issues :db:   that need sorting out....  :Waiting: 

In other words, if you had not tested it as thorough(ly?) as you did, we would already have it by now... Well....thanks.... :girl_devil:

 

I actually was a professional software tester myself, so you should be 'proud'. But I know it never makes you feel that way, lol. :lol:

 

It's a good thing we already know it's going to be great, that makes the waiting a little easier.

It even has "slow snow", Mark.... :lol:

Edit: Just read Mark's post - Thank You! I think you're on the way to get some kind of promotion around here, my friend!

 

See how much we agree, Kyle!

 

Ok, in the order that I find them:

 

Inspector:

1). AntiAliasing Mode should really be set to Application-controlled

2). AntAliasing - Setting is a little high for that 560.

3).Anisotropic filtering setting must be 16, otherwise a yellow taxy line, for e.g, will blur within 15 feet of the nose. 

- Otherwise - all is good'

 

FSX.cfg: Not far out of line, Kyle - I've made some small changes which will improve the overall feel, evening out the load a tad. Try it - do some testing to get BP right. 

 

Kyle_fsx_chgd.txt

 

I hope this helps,

 

All the Best,

 

pj

 

 

Thanks! I just got around to having the time to test it our (sorry!) and so far I can say the blurries are gone in DX10! I also noticed the frames are better than before! Not a night and day difference (yet) but I don't drop below 20 in the NGX VC at FSDT KLAX! Before, I wasn't getting much more than 15 in DX10. (I do still need to defrag the drive...)

 

I do have another question though... are the REX textures still enabled for DX10? It seems the water is back to looking like the default water. And I'm still not sure if the "fix" installed correctly... the water is like liquid silver/gold at night. And the one thing that I notice is happening again that drives me nuts... the buildings and trees don't pop up until about 1/4 mile from my plane. It's really distracting and annoying. Is that what the LOD RADIUS=6.5000 suppose to eliminate?

 

As far as the BP's go, I've read the guide a few times over and still don't know how to calculate what I need to put for those numbers. That's one thing I will most likely need help with on how to figure it out.

 

 

As far as the BP's go, I've read the guide a few times over and still don't know how to calculate what I need to put for those numbers. That's one thing I will most likely need help with on how to figure it out.

 

Here's some excellent guidance from NickN's recent update to his Fsx.cfg settings.  He has a section just for Bufferpools with recommended settings - http://www.simforums.com/forums/drivers-nv-inspector-fsxcfg-complete-guide_topic36586.html.  Personally I would not use any BP but that's because I have a very powerful system.

 

In regards to Autogen not popping up until about a quarter mile out, it could be caused by the density setting.  The higher the density, the more likely the Autogen will not be rendered fast enough.  If you have Autogen loading further away, you are going to take a major performance hit.  To reduce that impact on your system, I recommend the following tweak to your Fsx.cfg:

 

Under the TERRAIN section:

 

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1000
TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=800

 

Best regards,

Jim

 

 

To reduce that impact on your system, I recommend the following tweak to your Fsx.cfg:

 

But take note that this lowers the amount of maximum autogen to around 25% of what you get without that tweak! Default max trees is 4500 and default max buildings is 3000. So this tweak might help but at a cost. ^_^

Please - before everyone takes Nick's Bible as "Gospel" - it is Gospel ONLY for DX9 - many of the settings in his list of tweaks are different - or not used - when using DX10, the one quoted below, as an example.

 

 

 

I have tested just about every combination possible and the value I posted here is the one I use for every single system I have set up ..slower system may need to raise the value if they see WHITE boxes and other strange glitches like that.

 

 

I would not knock myself out trying different values as they will provide LITTLE to NO change in performance.. all a higher value does is trim glitches if the value is set too low and the higher you go the less help it provides.

 

Tuning this, along with TBM and FFTF will make the difference between your frames continuously bouncing up and down around 23 - 29 in heavy scenery - or getting a solid 29.9. DX10 can and will carry a heavier load than DX9 when properly tested. The change over of the ram management model from DX9 to DX10 is the main feature of DX10.

 

Lastly - AA cannot be controlled by Inspector - so the two settings - 

 "Anti-Aliasing - Mode" should be set to "Application-controlled"

and

"Anti-Aliasing - Setting" should be set to ""Application-controlled / Off".

 

In fact, using the new DX10 Fixer - this function is explicitly managed by the Fixer, with the chosen AA set into the fsx.cfg. 

 

Here is the current "best" profile, with the .cfg entries below, exactly as the Fixer made them:

 

MultiSamplesPerPixel=4

MultiSampleQuality=8, 

 

- this being the equivalent of 8xCSAA

 

Cheesh!

But take note that this lowers the amount of maximum autogen to around 25% of what you get without that tweak! Default max trees is 4500 and default max buildings is 3000. So this tweak might help but at a cost. ^_^

But you can move the Autogen slider up to max with little or not hit on fps.  If you keep it at the default the number of trees and buildings per cell is massive and performance will be reduced.

 

Best regards,

Jim

I, too use a lowered tree and building count, using the figures which Holger Sandemann (who should know!) has defined on a couple of forums in the past.

These are pretty close to Jim's figures, too:-

 

TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=907

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1376

But you can move the Autogen slider up to max with little or not hit on fps.  If you keep it at the default the number of trees and buildings per cell is massive and performance will be reduced.

 

Yes, but what's the use of being able to set the slider up to Extremely dense if that results in Normal dense autogen where there should be huge forests...?

 

 

I, too use a lowered tree and building count, using the figures which Holger Sandemann (who should know!) has defined on a couple of forums in the past.

These are pretty close to Jim's figures, too:-

 

TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=907

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1376

 

 

What should Holger know...? What is best or what he simply likes? ^_^

 

I am beginning to understand why you guys have such good performance with DX10: you have the sliders maxed out but the actual settings are below normal..!!!

 

Seriously though: I know the use of that autogen tweak (limiting the autogen in extemele dense area's but showing it all in area's with less autogen) but you can't advice it to someone without saying it will have a HUGE impact on what you see in the game. It's not just that performance will be better (in certain area's only btw) but you will also see (far) less autogen. It's not a tweak that improves performance miraculously: there is a reason and a cost for that improvement.

 

I have autogen at Extremely dense without that tweak (so I use the default 4500 trees and 3000 buildings) and that's exactly what I want to see in the game!

 

P.S. I wonder why Holger advices such odd numbers...? Why not simply 900 and 1350...?

 

EDIT

Just did a quick and simple test and in a medium forest a cfg setting of 1000 trees (and autogen at Extremely dense) is similar to an autogen setting (without the tweak) between Normal and Dense (which you can't set but that's how it is ^_^ ). That's why I say that if you advice someone to use this tweak, you should always mention the cost of using it!

Jeroen,

 

When someone suggests a "tweak" to someone to help them with their performance, one should not get too negative.  The Autogen tweak is a well-known tweak that is provided by Microsoft and other experts such as in this blog - http://flyawaysimulation.com/news/3806/fsx-performance-tips-and-tweaks/ (please note the info regarding Autogen provided by Paul from the Aces Team).  I don't think individuals who have high-powered systems need this tweak but it certainly is useful for those who have lessor machines.  Go ahead and have your 4500 trees and 3000 buildings if that suits you and your computer runs fsx well.  Some others are having issues and we are trying to help them.  If you want, you can even turn those settings up even higher to a max of 6000 for either if you want but the "tweak" has to be in your Fsx.cfg for that to work.  It's just one of those things you can put in your config to manipulate your enjoyment of flight simming.

 

Best regards,

Jim

Well, we are doing a couple of things, Jeroen:

 

1). FSX will bring any pc on the market, built, overclocked - whatever have you - to it's knees.

 

2). We need some way to reduce one or more of the loads in order to get the pc running as smoothly, with a heavy load, showing the kind of picture to us that we desire - not the highest framerate.

 

3). We can set "All road vehicles to 10" - some guys might like 20 - or 50. Well - 50 will kill most pc's, (when run with the NGX and New York, for e.g.). We can set "Download weather" - "Distance to 110", "Detailed=1", we can set many other parameters that will destroy the immersion factor for many people, and still not get that desired "picture".

 

4). Those other 4000 trees and 3000 (whatever) houses are way down at the bottom of the "important visual candy" that we, folks like me, and (obviously Jim) others need to see, and so they fill the bill for a "standard" reduction, one that I can forget once it's set. 

 

The point being that in order to quantify what is necessary versus what we love to see, we need some "fire and forget" parameter, that doesn't make our sim look bare, nor that will kill the pc when it's at max value. Very fortunately, AG - set to 4, and those trees and buildings set to Holger's minimum values - do display a very good amount of forestation, with a nice amount of buildings, so it fits "fire and forget" just perfectly, and without detracting from that 'immersion". (I believe AG adds more than just buildings and trees, but that's a different discussion).

 

There's absolutely no point in killing off the much more important cloud textures: cockpit textures: general AA-AF-IQ: city-scapes: airport details: AI aircraft: GSX: EFB: PlanG, NGX: REX: Orbx Global, and so on, (plus fight to get rid of shimmering using SGSS) - just to see a few more trees and a few more houses! Reduce any of those and it's immediately noticeable!

 

I want waves with whitecaps: I want heavy dense overcast, and clouds and sunsets and scenes like these: - yes - I know you've seen them before - it's just a quick example, but there are still people out there who can't accept compromise, and want for some magic bullet.......but there isn't one: there's only compromise. Owning, managing and running FSX is always a compromise.

Where and how we do this is a matter of the best gain for the least pain.

 

I get high figures, not because I've chopped down a slew of trees and bulldozed a bunch of houses: I get high figures because I've worked my &@($* off getting the absolute utmost last cycle out of my proc and memory, and have tweaked the pc the way I know it has to be tweaked. I buy the right part for the job, and one which will give me the performance needed - which is not necessarily the most expensive part.

 

These are only parts of an FSX management philosophy, Jeroen. It's a hobby, and though tweaking may be a b**** sometimes, it can also be fun and rewarding.

 

All the Best,

 

pj    :wink: 

Well I must be doing something wrong... I can't get above 20fps at FSDT KLAX with NGX VC. In fact, it bounces between 15-20 and has more stutters. I have used all the tweaks listed in this thread including the most recent "TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=907

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1376"

 

And even tried disabling bufferpools to see if there were any difference but didn't notice any at all. It's frustrating! I liked how I had DX9 running the sim except I got tired of getting the OOM while on final into KLAX and was hoping DX10 would solve this. I'll keep trying to figure this out but so far it's not been much of an improvement.