the OP has said this is an ongoing project, and night textures were being an issue in the early releases, make sure you have the most up to date shader fix available from his site.

I have the version 3.0 set up which was used on my Computer.

Glad you got it working! The panel anomaly may be specific to that plane, i have some weird things happening with some panels in dx10 mode (but thankfully not a deal breaker)

 

A couple of questions though...have you tried overriding AA/AF settings with nvidia inspector? instead of doing application controlled? I override application settings..makes me wonder if i should try application controlled, maybe the fsx logo on water thing is somehow related to that.

Hi FsxHd

 

I have an ati card too. I would recommend that you read through my blog entries on ati antialiasing and dx10. i would try setting MultiSamplesPerPixel=8 in fsx.cfg and then enhance in ccc (not override which doesn't work with dx10) plus sent the ssaa slider as you desire.

 

Steve

 

Thanks for the heads up. I saw your post on your site just now and will have a go at experimenting a little with your settings tomorrow.

 

This is something we all will have to work at, Kevin: DX10 is a 'different' simulator: what worked in DX9 doesn't necessarily work when using DX10... and this means that some amount of experimentation is called for, until we reach to point where we can say (for example) "We can use BufferPools=0 when the proc is at 4.5gig+ using a GTX580". This is true. We don't have to experiment. Does it apply when using it with DX10? I'm pretty sure it does, but I've not tried any other figures. Same with FFTF. We - you, me, need to check out all of the combinations that Inspector has, do the same with CCC - and it may be that ATI will rule, with DX10!

 

@Matthew: I don't expect that the older FlyTampa scenery will 'for sure' work, but FT FS9 Seattle (converted) does in FSX, with a bit of jetway flashing, but it's tolerable.

 

Thanks for the explanation Paul! I like the notion that DX10 FSX should be treated like a new sim. I'm going to experiment a little with Steve's settings and research tomorrow and will report back. Feel free to share any of your findings too! By the way, I'm running on an ATI Radeon HD 6700 Series 1GB card.

My gosh, Jim! I just finished a 'Perfect Flight' - OrbX PNW in the 172, from Diamond Point -> KORS -> Anacortes, and then into Skagit. Fair to cloudy, early evening AS2012 + AccuFeel. The secret - your AA and AF Inspector settings. I'll post mine tomorrow, as the vsync is a little different, but man! - I cannot believe the difference! The water is just fantastic!, it's better than REX Sparkling was, with land Complxty & AG as high as I can get them, Bloom on - and 29-30 frames all the way - no dips.

I have to go now, but I have (I hope) lots of pics, and will post later. Jim - this is THEE best! Sometime tomorrow DX9 will be officially dead on my PC. It is SO much better!

 

@Jason: You are right! This is the way to go - application controlled. I have a slight different setting to Jim's, but I think that's the right course to take.

I can´t imagine anyone with an ATI card and a descent computer not taking advantage of DX10. It´s a totally new sim to me. I mean with road traffic, bloom, more autogen, and better performance, makes me a much happier sim pilot! Can´t believe I´m flying a PMDG aircraft as complexed as it is with bloom and traffic and no stutters. For this I give a big THANK YOU to the OP. Keep up the great work!

ok Paul and Jim...i used Jim's nvidia inspector settings, and i have to say it runs even better under his settings than it did mine. I went to KLCM and set it up to a daytime setting, and as2012 was loaded..it brought up current overcast conditions, which is known to bloody up framerate, and my fps was pegged at 30. I have been using the X1 high water setting due to the flashing fsx logo on water texture thing ive been seeing, and i switched to x2 high to test and still having the same issue..so that part was a bust for right now. I actually prefer the X1 high settings over the X2 settings anyway, but if a fix is found then of course ill try it.

 

here is a screenshot of my short test flight...in my fave plane...just north of KLCM

 

 

 

as you can see it was pegged at 30..and this is with EVERYTHING at max except water which is set at x1..and bloom is on, AI set to 60% airliners/35% GA traffic (realistic settings for MyTraffix 5.4a Pro) but there wasnt any AI in the immeadiate area

I had the blue squares with a FSX logo flashing up on water and scenery tiles.

 

The issue was fixed for me by ensuring I had Bufferpools enabled and then gradually increasing the rejectthreshold setting until they were no more. Could be because so much more info is now flowing to the GPU as DX10 is taking load off the CPU. Maybe give that a go.

 

Cheers,

Danny

I had the blue squares with a FSX logo flashing up on water and scenery tiles.

 

The issue was fixed for me by ensuring I had Bufferpools enabled and then gradually increasing the rejectthreshold setting until they were no more. Could be because so much more info is now flowing to the GPU as DX10 is taking load off the CPU. Maybe give that a go.

 

Cheers,

Danny

 

That's very interesting Danny. I also have bufferpools enabled, although I hadn't made the same association that you have. One difference with dx10 (as I understand) is that the gpu takes more responsibility for the management of the texture cache. Running with bufferpools off or a low reject threshold leads to each texture having its own vertex buffer whereas the other way the individual textures get grouped together by fsx. It's possible that this works better with the dx10 loading and caching mechanism so that the best setting is different between the two modes.

I can´t imagine anyone with an ATI card and a descent computer not taking advantage of DX10. It´s a totally new sim to me.

 

Please tell me, do you get vsync issues, i.e. image 'tearing', when you look around. I still assert that my ATI HD5870 doesn't enable vsync ,on, in FSX's DX10 preview. I am dieing to be shown how to stop the tearing. Many thanks.

I'm running an Nvidia card (460) and utilizing the Inspector settings listed previously.

 

The Good:

 

1. Frame rate has sky rocketed.

 

2. Better graphics throughout (sharper images). Even the screen text looks much clearer. (radio popup windows)

 

3. Cockpit shadows are looking good.

 

 

The Bad:

 

1. I'm getting the image tearing still, even with vsync on. It's just too fustrating and is what has me going back to DX9 for the time being.

 

2. I use WOAI for airplane traffic and some of the airline textures are not showing up. All I'm getting on these are white planes.

 

3. The distance that autogen "pops up" is significantly closer. For example, with DX9, autogen buildings would pop up at a further distance from my airplane. With DX10, I need to be significantly closer for the same autogen to appear. Not sure if anyone else has experienced this, as I haven't seen it posted yet.

 

4. I do have some shimmering, particularly with addon airports, so that may be because they are not DX10 compliant.

 

 

The toughest part is keeping track of the all of the changes when testing in DX10, in order to not lose my well working DX9 setup. ;)

I'm running an Nvidia card (460) and utilizing the Inspector settings listed previously.

 

The Good:

 

1. Frame rate has sky rocketed.

 

2. Better graphics throughout (sharper images). Even the screen text looks much clearer. (radio popup windows)

 

3. Cockpit shadows are looking good.

 

 

The Bad:

 

1. I'm getting the image tearing still, even with vsync on. It's just too fustrating and is what has me going back to DX9 for the time being.

 

2. I use WOAI for airplane traffic and some of the airline textures are not showing up. All I'm getting on these are white planes.

 

3. The distance that autogen "pops up" is significantly closer. For example, with DX9, autogen buildings would pop up at a further distance from my airplane. With DX10, I need to be significantly closer for the same autogen to appear. Not sure if anyone else has experienced this, as I haven't seen it posted yet.

 

4. I do have some shimmering, particularly with addon airports, so that may be because they are not DX10 compliant.

 

 

The toughest part is keeping track of the all of the changes when testing in DX10, in order to not lose my well working DX9 setup. ;)

 

The good

 

Thats great news youre having success with it!

 

 

The Bad

 

1. do you have Vsyncs set at 1/2 refresh rate in nvidia inspector? and do you run in full screen or windowed, if so there are fsx cfg entries you have to have in order for vsync to work

 

2. i have read in several places that most of WOAI planes will not work in DX10. I use MyTraffic 5.4a Pro and do not have that prob.

 

3. You might want to check your LOD settings in the fsx.cfg. default is 4.5000, and dont change it higher than 6.5000, or OOM's will occur

 

4. i get some shimmering, and hopefully a fix can be implemented soon.

 

 

i have made 2 fsx.cfg's one for dx10, and for the rare occasion i need to use dx9, i have the cfg for that. i have to manually swap them out by renaming.

 

ok Im going to change the bufferpools setting and bump up the reject threshhold setting...and ill see if that works for the fsx logo/water issue...cross my fingers

Yup - a tiny bit of shimmering under some of the islands around KORS, but I had that in DX9, too. Here are the pics of last night's flight from Diamond Point - KORS - Anacortes - Skagit. You can see the top-left corner - always between 29 and 30 frames. My Inspector settings are here, along with the fsx.cfg and 129 pics.

 

https://www.dropbox.com/sh/z9rqd68nt863lfn/qyI3ufO0AU

 

These pics are all 3840 x 1024, so full screen will perhaps need some scrolling for folks with single monitors.

 

My Inspector settings differ from Jim's only in that I had left the "AA-Setting", "AA - Tranparency SuperSampling" at what they were prior to changing all to "Application Controlled", so I don't know what effect they might - or might not - have on what is now seen.

Please tell me, do you get vsync issues, i.e. image 'tearing', when you look around. I still assert that my ATI HD5870 doesn't enable vsync ,on, in FSX's DX10 preview. I am dieing to be shown how to stop the tearing. Many thanks.

 

Sorry clarkresponse, you already replied you don't get tearing in DX10, how are other ATI users getting on with DX10 preview and vsync?

Just realized that I accidentally had DX10 Preview unchecked. I have now enabled again and it al works fine, no tearing, with exception of one issue. I am getting flashing tiles on water. Flashes between the FSX logo and water textures. Anyone else have this issue?

 

This is very likely to be caused by your BufferPools setting, Mark, or Water is not set at 2X High.

 

Flashing controllers:-

 

Water at 2xH - BP settings will cause your flashing symptom without this mod.

 

HIGHMEMFIX=1 - controls cloud flashing and other anomalies.

 

FFTF - keep it down around .08 - .25 - lower is smoother, but may lead to ground texture blurring.

quick response to the buffer pools setting...

 

i had buffer pools set at 0 and was experiencing the flashing fsx logo with water but only with X2 water.

 

changed the bp setting to 1 and bumped up the reject threshold some and things are alot better, hardly any flashing, fps is great even at water maxed out. I am going to bump up the rejectthreshhold up even more and hope that eliminates all instances of this fsx logo flashing.