DX10 water shadows.

[Ianrivaldosmith]

Hi, I am using water 2x max. I have noticed the reflections of the clouds and land and autogen seem to flicker a LOT? Even the reflections off ships.... Anything I'm doing wrong?

 

Il using fsx +ftxg + Rex overdrive.

 

I have a i5 4670k @4.2ghz

16 GB ram

770gtx 4gb

 

Cheers Ian

[Cai Zicheng]

Are you using BP=0?

If yes it might be your GTX770 is incompetent of handling 2x max.

[Ianrivaldosmith]

Hi, yes I am using that setting.

Incompetent of handling it? It's like the third best graphics card available behind Titan and 780!? So I hope that's not the case! Ian

[Cai Zicheng]

Hi, yes I am using that setting.

Incompetent of handling it? It's like the third best graphics card available behind Titan and 780!? So I hope that's not the case! Ian

Well... Obviously a GTX770 is powerful. However, FSX is a real resource hog...

[Ianrivaldosmith]

Hmmm it seems to be handling everything pretty good to me. I can't see it being that? I mean it just seems the reflections that go on to the water just seem to flicker a lot and looks worse from high altitude. Maybe it's one of my settings?

 

Also is there a new version of the DX10 fixer out? What does it change/fix?

 

Ian

[ZKOKQ]

Also is there a new version of the DX10 fixer out? What does it change/fix?

Fixes the Dawn Dusk issue and there is another updated with fixes coming later in the week, according to Steve.

Read this thread regarding how to re install a new version. http://forum.avsim.net/topic/423059-dx10-bliss-thank-you-steve-and-paul/

As far as your problem with water goes, I am now using default water and wave animations, and looks darn good.

[Paul J]

Hi, I am using water 2x max. I have noticed the reflections of the clouds and land and autogen seem to flicker a LOT? Even the reflections off ships.... Anything I'm doing wrong?

 

Cheers Ian

 Hi Ian: It's caused, in part by the water setting being at 6, I think, in the fsx.cfg. This will cause the water to reflect everything. I would suggest dropping it to 4 or 5: The second cause of flickering - it's also called Shimmering, is to set Nvidia's Inspector "Antialiasing  - Transparency Supersampling" to 4x SGSS - even 8x if the GPU will allow it without stuttering.

 

This number has to be the same number as the Fixer sets (in the FSX.cfg) as "MultiSamplesPerPixel" .ok!

 

Her's a shot of mine, using the 780.

 

windows screenshot

Hope this helps,

 

pj

[Ianrivaldosmith]

So does no one use the water setting at 6 due to this? I can lower it to 4 or 5 and it does eliminate it, but also eliminates autogen reflecting on the water. Is this the only compromise? Does anyone run 6?

 

Cheers

Ian

[Mork]

I think at 4 you only get cloud reflections, at 5 you get cloud and terrain reflections and at 6 you get cloud, terrain and autogen refections.

For me the clouds only are fine, so I run at 4 at the moment. Although I haven't been flying for over 2 months or so now, lol.

[Guest]

So does no one use the water setting at 6 due to this? I can lower it to 4 or 5 and it does eliminate it, but also eliminates autogen reflecting on the water. Is this the only compromise? Does anyone run 6?

 

Cheers

Ian

 

 

The solution lies in the used wave animation. Use REX to reinstall the default wave animation (restore your entire initial backup and then install your REX textures again but now with the wave animation unticked on the options screen). You of course also could try another REX wave animation but a lot of them result in problems with DX10. I reverted to default FSX water when I switched to DX10 and as Badfinger said already, it looks darn good.

 

I use High (5) but only because Max (6) hurts performance too much. I've love to be able to run 6!

[Paul J]

It's all about expectations, Ian - a juggling contest! You may well believe that your machine is pretty much "very capable" of running FSX, with all sliders cranked up: I can tell you - it's not, and neither is mine:

 

Yours:                                                                Mine:

I have a i5 4670k @4.2ghz.......................................i7-2600K @ 5 gig HT off
16 GB ram...............................................................8 gig Corsair Vengc @ cl-8
770gtx 4gb...............................................................780gtx 3 gig

 

..I still have to pull a number of sliders back in order to get visual satisfaction, and a continuous 30fps without issues, so -

 

Here are my compensations:

 

Water is 5

AG is 4

LOD is 4.5

Max AG Trees/cell is 1376

Max AG Buildings/cell is 907

AI density is 35 when flying tube, with 0 GA

Road Traffic 10 - 20

No ship, no boats

Image Complexity is 5, no lensflare

Cloud ensity is 8

Cloud draw distance is 3 

TML is 1024 , sometimes using 2048, but never higher

 

And here is the fsx.cfg:

[Ianrivaldosmith]

Thanks for all the suggestions and replies. I've fixed it, by using the default fsx 10 water.... Looks great!

 

I must also say, I have followed all the info you have given me, and it has helped a lot. I'm running autogen at max in ftx eng and to be honest dropping the slider has no effect for me. I get the same fluid Locked 30fps with it maxed out. What's the biggest fps killer in dx10? My road traffic is only at 15%......

[wulfbindewald]

The biggest DX10 frame rate killer is dificult to answer, because each simmer has his favourite sceneries, aircraft, weather and traffic tools and probably a combination of all.

 

Example for Vancouver BC (8 x CSAA):

  FTX PNW above Vancouver, cloudy: 30 fps

  FTX PNW + FSDT Vancouver airport, FTX lights switched to "day", cloudy: 23 fps

  FTX PNW + FSDT Vancouver airport, FTX lights switched to "night", cloudy: 16 fps

I accept the 16 fps, because I like the FTX lights.

 

For the enthusiast there is no way out: To toggle the sliders or activate/deactivate features up to an acceptable value. It´s a bit time consuming, but this exercise will be done one time. 

 

Wulf 

[Paul J]

Wulf is right, although more money thrown at the hardware makes life a bit easier!

 

Any one slider pulled all the way back will fix almost any "overload" issue, but the trick is to find out which are the ones which make any difference, and then ask "How important is this one, to me?". I know which are the biggees, and so set them in accordance with my "needs" - I want some airport traffic - but "2" has a significant impact, so it sits at "1": same with road traffic: it's important that I see cars, trucks, etc, but 25 will force my clouds, or SC, or AG, or SGSS, or GA to take second place.. so down to "10" it goes. I'd like to see more, but it's "in balance" if I can see some. None is not acceptable. Clouds: we need clouds - detailed, too, but at 80 miles... ? so set it at 60, because when flying an aircraft... well... this is at 60..and this, this too, Vancouver testing for constant 30 frames with heavy load. 60 miles is quite acceptable. I did a bit of a guide here, if anyone's interested - for known frame killers. Because I have to fix cfg's on a daily basis, I see the same issues crop up time and time again, and it's comparing one to the other, tying it to an Inspector setting, and judging the machine, and it's worked for a good while.

 

Anyway - gotta go - boss-lady calls!  B)

 

All the Best,

 

pj

[SolRayz]

For me the biggest dx10 frame killer above all is AI. For some reason I can run much more AI in dx9 that dx10. This is with a default install of UT2.