ThePlainsman
Charter Member
Cool. My results are completely different. If set up my graphics to get 75 fps in DX9, the exact same settings would get me at minimum 150 fps in DX10 preview mode.
Frame Rate Test: It's For Real!
- Thread starter ThePlainsman
- Start date
Cool. My results are completely different. If set up my graphics to get 75 fps in DX9, the exact same settings would get me at minimum 150 fps in DX10 preview mode.
I wish DirectX10 mode worked well on my system (W7x64 i7-920 ATI5870x2), while it does bump up FPS 2X or 3X, I get a lot of microstutters and inconsistent FPS. I tried lots of tweaks to try and get DX10 mode stable but nothing worked.
So I think DX10 mode is probably very hardware dependent, glad you got it working well Plainsman, most of us are not so lucky.
So I think DX10 mode is probably very hardware dependent, glad you got it working well Plainsman, most of us are not so lucky.
Daube
SOH-CM-2025
Ok. This is strange.
I'm running a Intel E8500 3,16ghz, Win 7, Nvidia GTX460 OC, 4gig ram installed (win says 3,5 usable). Im using Nvidia inspector with the settings i found in another thread here.
I did another test:
This time i flew from my local airport since i have ORBX pnw installed and that covers the Friday harbour area. The flight was from ESGP (save AB) with the default c172. The only addon is FS9 REX clouds.
In DX9 with unlimited FPS i get a lot of stuttering and the fps jumps from 30 to 150. If i limit the framerate to 30 it is smooth as silk and looks great.
In DX10 with unlimited fps im getting a stable 66-68 fps and very little stuttering, with fps limited to 30 i get 20 fps and bad stuttering. Also, in DX10 mode i have a bad case of jaggies and shimmers, and the runway markings flicker on and off.
peter12213
FSX Acceleration!
Im getting exactly the same results as Peter describes above!
kilo delta
Charter Member 2015
Btw..there is a "fix" for the DX10 induced runway/taxiway flickers... http://forum.avsim.net/topic/267998-dx10-runwaytaxiway-flickering-fix/
Plainsman, I applaud you enthusiasm, but there is a saying that goes. . ."never say never" and if it applies anywhere at all it would be in the differences between your rig and every other rig on the planet. You should make your finding known and be proud of what your rig can accomplish, but never be so smug as to suggest that yours is the last word and everyone simply must get the same results you do. I have had similar results to what others have noted, lower fps with DX10 and I fly non-native aircraft in FSX because I can.
peter12213
FSX Acceleration!
What about the jaggy textures though it's like anti analising won't work also I get funny things happening with the water textures can anyone help?
Thoe6969
Charter Member
anti alaising don't work fork me either ,thats why the framerate is so much better with DX 10 but it looks like crap.
a hundred and fifty, huh? that must be one hell of a rig you got there.
ThePlainsman
Charter Member
Always fly unlimited fps with DX10. Don't put a fps limit on the DX10 preview. You bottle it up.
ThePlainsman
Charter Member
I was trying to make a point to that other poster who insisted his DX9 fps was twice as high as DX10 preview. My point is whatever I get with DX9, I get 100% to 600% higher in DX10 preview. But you have to do DX10 preview with target frame rate set at unlimited to get the best results.
When I did the comparison test, I also had DX9 target fps set at "unlimited." Apparently, someone has discovered that selecting a target frame rate number (like 30) in DX9 mode gets much better results than "unlimited." DX10 is the exact opposite. Set DX10 preview to unlimited target frames and it will beat DX9 easily.
ThePlainsman
Charter Member
That's interesting. I don't have any jaggies in DX10. I have the anti-aliasing box checked in the game menu screen, although I don't know if it is actually working. But I don't have any jaggies. I am running at 1920 X 1200 X 32.
These are my settings: Aircraft = medium high; global texture resolution = very high; Scenery complexity = extremely dense; autogen density =dense; water effects = 2.X; level of detail radius = high; mesh complexity = 100; mesh resolution = 10m; texture resolution = 7cm; special effects detail = high; cloud cover density = maximum (detailed clouds); road vehicles = 40%; ships and ferries = 40%; boats = 40%; airline traffic density = 100%; general aviation traffic density = 100%; airport vehicle density = low; all shadows = on; high resolution 3D virtual cockpit = on; lens flare and light bloom = off.
I also have installed Traffic X, GEX USA & Canada, GEX Europe, GEX Middle East and AFrica, ORBX Australia SP4; REX 2.0 + Overdrive.
What resolution are you running in DX10? That could be why you're seeing crap/jaggies.
WOW!!! I nearly trippled my FPS,The only negative so far are flickering lights and square boxes on a few aircraft lights,and no tool tips.But the extra performance is fantastic!! THX for the info!! Cheers:salute:Naruto-kun
Charter Member
Some FS9 aircrafts will work, though.
For example, the DR400 from Yannick Lavigne will work, you just need to convert some textures.
Also, the CR-42 frm Manuele displays perfectly
There must be some other examples, and I don't have any explanation/precise criteria, but the fact is that some FS9 planes will NOT be white in DX10 mode
And a proof:
Indeed. There is a cure for this, but it requires an edition of each airport :/
The answer to why some FS9 birds go white in FSX is Bloom. Some non FSX materials will put out like full bloom which is so bright that it whites out the screen. I still run on winXP32 so i dont have the DX10 preview option available. But I have tested several FS9 aircraft and every time the screen went white it turned out that bloom was the culprit.
Just to clarify, and I admit that I haven't read every post in the thread, but when others state that some aircraft (FS9 ports) turn white, they don't mean the screen goes white, they mean the aircraft textures show up as white when running DX10 Preview. I've actually had a few airplanes where only some of the aircraft was white while other areas looked fine. I've read earlier explanations for why some ports turn white in DX10 and it wasn't related to bloom which a lot of folks don't use anyway because of the fps hit.