Tweet
originally posted by waterman:
Last night I mentioned to Kalo that I had switched to DirectX 10, and was getting 30 FPS with it. To do this I followed a guide posted on AVSIM, where there has been a lot of work and discussion regarding DX10.
The Guide can be found here: http://forum.avsim.net/topic/384221-...o-go-dx10-doc/
So I completely followed the guide, starting with a brand new fsx.cfg file. The guide mentions BufferPools, which I tried to find better information of but only got how to, so I decided to implement it. And since it was a new CFG file I also needed to add multicore lines, so I also added (at the very top of the CFG):
[JOBSCHEDULER]
AffinityMask=14
[BUFFERPOOLS]
PoolSize=0
The only other setting I changed from the guide is:
TEXTURE_MAX_LOAD=4096
***Note, every time you make a single change to your graphics settings this value gets changed back to 4096. I found a great tip where I basically made multiple CFG files that you can switch on the fly. For example go in and check Bloom, then SAVE that as a graphic setting… You'll then go and double check that the Texture setting is 4096 in that saved CFG and viola! In flight you go to Options, Graphics, Load (or save) to load that configuration. Once these are set up it's a quick way to change your settings, while keeping HD (4096) textures. ***
With the rest of the default settings from the guide and those other entries I was right at 30 FPS.
At the bottom of the guide it does mention there are some problems still using Dx10. One not listed there is aircraft NAV lights. There is an experemintal fix for that here: http://forum.avsim.net/topic/377635-...ntal-fix/ The unfortunate part of that is it has to be applied to every aircraft individually.
I had 30 FPS, but I wanted a litte more detail. I had bought REX Essentials yesterday and thought I had it set up correctly, but didn't run it as Admin, so the textures didn't go over correctly. This morning I got it running right and things look great. I did take a FPS hit though.
Last night I also realized that multiplayer without tags can suck, so I enabled them with just names, and took a 3 FPS hit for that.
I also upped some other graphic settings. So with everything I've changed from the starting point, with REX, I average between 15 (in rain)-30 FPS, depending on what's going on. I'll continue to tweak my settings, but I felt the guide was a good starting point for anyone. Hopefully this helps others!
For reference here's my system:
Intel Core i7 920 (1st gen)
12GB RAM
ATI Radeon HD6850 1GB
900GB HD space (4 500GB drives in RAID 10, so that does affect hard disk IO)
TrackIR 4
My all out graphic settings – by category then just values.
Graphics (Global Setting: Custom)
Device Specific Options
30
1920x1080x32
Anisotropic
checked
Global Options
Very High
All checked
Aircraft (Global Setting: Ultra High)
Scenery (Global Setting: Custom)
Terrain and water
Large
100
2m
7cm
Max 2.x
Checked
Scenery Objects
Extremely Dense
Extremely Dense
Unchecked
High
Weather (Global Setting: Ultra High)
Traffic (Global Setting: Custom)
Aviation Traffic
35
20
medium
Aircraft Lables I only have Show Aircraft Lables and User Aircraft checked
Land and Sea traffic
20
0
0
And finally, here are some screen shots of my results. They are from Dillingham and Honolulu, Hawaii, and one from Washington state using the OrbX PNW demo.
and in a later reply:
I installed REX correctly, but when running it I was just opening it normally. Apparently you need to right click and "run as admin" which makes sense. Otherwise UAC would prevent it from making any changes to files inside of "Program Files". I searched through the manual and didn't see a reference to that, but saw it in the REX forums. I've now set it to always run as admin so I shouldn't have a problem with it again.
In those screen shots I had:
REX Essentials
OrbX PNW demo (only for image 61.jpg as the others were Hawaii, and default scenery)
The four REX freebies (Roads, grass, etc…)
TreeX (http://flyawaysimulation.com/downloa...687/fsx-treex/) which I don't really know how much of a difference it made.
I think that's it…
Last night I mentioned to Kalo that I had switched to DirectX 10, and was getting 30 FPS with it. To do this I followed a guide posted on AVSIM, where there has been a lot of work and discussion regarding DX10.
The Guide can be found here: http://forum.avsim.net/topic/384221-...o-go-dx10-doc/
So I completely followed the guide, starting with a brand new fsx.cfg file. The guide mentions BufferPools, which I tried to find better information of but only got how to, so I decided to implement it. And since it was a new CFG file I also needed to add multicore lines, so I also added (at the very top of the CFG):
[JOBSCHEDULER]
AffinityMask=14
[BUFFERPOOLS]
PoolSize=0
The only other setting I changed from the guide is:
TEXTURE_MAX_LOAD=4096
***Note, every time you make a single change to your graphics settings this value gets changed back to 4096. I found a great tip where I basically made multiple CFG files that you can switch on the fly. For example go in and check Bloom, then SAVE that as a graphic setting… You'll then go and double check that the Texture setting is 4096 in that saved CFG and viola! In flight you go to Options, Graphics, Load (or save) to load that configuration. Once these are set up it's a quick way to change your settings, while keeping HD (4096) textures. ***
With the rest of the default settings from the guide and those other entries I was right at 30 FPS.
At the bottom of the guide it does mention there are some problems still using Dx10. One not listed there is aircraft NAV lights. There is an experemintal fix for that here: http://forum.avsim.net/topic/377635-...ntal-fix/ The unfortunate part of that is it has to be applied to every aircraft individually.
I had 30 FPS, but I wanted a litte more detail. I had bought REX Essentials yesterday and thought I had it set up correctly, but didn't run it as Admin, so the textures didn't go over correctly. This morning I got it running right and things look great. I did take a FPS hit though.
Last night I also realized that multiplayer without tags can suck, so I enabled them with just names, and took a 3 FPS hit for that.
I also upped some other graphic settings. So with everything I've changed from the starting point, with REX, I average between 15 (in rain)-30 FPS, depending on what's going on. I'll continue to tweak my settings, but I felt the guide was a good starting point for anyone. Hopefully this helps others!
For reference here's my system:
Intel Core i7 920 (1st gen)
12GB RAM
ATI Radeon HD6850 1GB
900GB HD space (4 500GB drives in RAID 10, so that does affect hard disk IO)
TrackIR 4
My all out graphic settings – by category then just values.
Graphics (Global Setting: Custom)
Device Specific Options
30
1920x1080x32
Anisotropic
checked
Global Options
Very High
All checked
Aircraft (Global Setting: Ultra High)
Scenery (Global Setting: Custom)
Terrain and water
Large
100
2m
7cm
Max 2.x
Checked
Scenery Objects
Extremely Dense
Extremely Dense
Unchecked
High
Weather (Global Setting: Ultra High)
Traffic (Global Setting: Custom)
Aviation Traffic
35
20
medium
Aircraft Lables I only have Show Aircraft Lables and User Aircraft checked
Land and Sea traffic
20
0
0
And finally, here are some screen shots of my results. They are from Dillingham and Honolulu, Hawaii, and one from Washington state using the OrbX PNW demo.
and in a later reply:
I installed REX correctly, but when running it I was just opening it normally. Apparently you need to right click and "run as admin" which makes sense. Otherwise UAC would prevent it from making any changes to files inside of "Program Files". I searched through the manual and didn't see a reference to that, but saw it in the REX forums. I've now set it to always run as admin so I shouldn't have a problem with it again.
In those screen shots I had:
REX Essentials
OrbX PNW demo (only for image 61.jpg as the others were Hawaii, and default scenery)
The four REX freebies (Roads, grass, etc…)
TreeX (http://flyawaysimulation.com/downloa...687/fsx-treex/) which I don't really know how much of a difference it made.
I think that's it…
