First off I want to thank everyone who has been working on this and that has given tips and help to set this all up. I am extremely happy with the way FSX and DX10 runs.

 

I do have a question though. What settings via REX, or an outside source or tweak do you guys know/use that makes the water a little more alive? While the colors now of my water is absolutely beautiful, I am wondering what setting you use to make the waves more pronounced. Maybe it is just me, but it seems that the only side effect of running DX10 that I am having is that my water looks way calmer than before, maybe slower? Maybe less pronounced in wave animation.

 

I am running REX-E, with Sparkling, and have water inside FSX set to X2 High as recommended.

 

Thanks for any reply.

Does it look like this, William?

 

https://www.dropbox.com/sh/ad5ydxa2gfenq2j/n-4trNO0Lx

 

The waves now have proper whitecaps, and are also indicative of the wind direction. From an aircraft, each whitecap does slowly build and then equally slowly diminishes and disappears. The waves also slowly move in the correct direction, and impact shorelines with good and correct motion. To me, an ardent wave-watcher this is correct behavior, however - it's a new sim, with everyone re-learning their own preferences, and though I did use Sparkling in DX9 and early DX10 - I moved away from REX water, in favour of AS2012, as the inland water colors were very configurable. I still use REX clouds (nothing else, though), as REX textures are noticeably much more detailed, even at the lowest settings. I would suggest looking at a different WaterConstants.xml file - copied from a post here or there. Here are three:-

 

https://dl.dropbox.com/u/52676345/Ron%27s%20Waterconstant.xml

 

https://dl.dropbox.com/u/52676345/WallyDog%27s%20WaterConstants.xml

 

All that being said - I don't know if that WateConstants.Xml is actually used by DX10, or whether some other file is used.

 

Post some pics - let's have a look. Water at 2x High will give rise to shimmering in the water on the shores of islands, so if you have that happening just go to 2x Medium - there's precious little difference!

Hello and thank you for the reply. Here is a picture that I took last night.

 

About those Water Constraint files, all I will have to do is backup my current correct? I finally got this running good and don't want to mess it up....lol

 

I will give X2 Mid a go, but always thought that would make flashing? Or is that only with UsePools=0....lol. So many tweaks I can't keep up. That is one of the reasons I run a Vanilla CFG. with nothing added but LOD=5.0, and HIGHMEMFIX=1.

Correct - just rename it as "WaterConstants.ORI" will do it, William. Leave it where it is. I would make a new folder named "WaterConstants" somewhere on the PC, so that you can keep these three - or any others you may pick up - as backup copies. You might even put a copy of the original one there, too.

 

Water at 2.x Med works just fine, William. The problem with running an "untweaked" cfg is that it doesn't allow for those dense settings that a properly-configured cfg will. For example - TBM. It began life at something like 20, or so, and was moved to 40 with FSX SP2. That was in 2006/7 - when the 8800 and the C2D were kings. This doesn't apply any more because of the high-speed procs and the very wide bandwidth of the modern GPU. Why on earth would anyone throttle back a system which is developed to - and capable of - running at 4.5 gig and more??? One might say that DX10 is a "tweak" of DX9!, or that Windows 7 is a "tweak" of Vista (which I believe it is!).

Besides, not to belabor the point - there are only four or five "tweaks" anyway, and what they do is to enhance the ability of the system as a whole to handle the heavier load that DX10 now permits. These are, with the exception of TBM - all hidden, but valid and viable parameters which one can easily add to the fsx.cfg.

 

 

[GRAPHICS]

MultiSamplesPerPixel=4

MultiSampleQuality=8

HIGHMEMFIX=1

 

 

[bufferPools]

BufferPools=1

PoolSize=10485760

RejectThreshold=524288

 

[Display]

TEXTURE_BANDWIDTH_MULT=100 (mine)

 

[Main]

FIBER_FRAME_TIME_FRACTION=0.1

 

[scenery]

MAX_ASYNC_BATCHING_JOBS=3

 

Anyway - I hope this sheds a little light, and gets rid of the feeling that there are "So many tweaks I can't keep up. " :wink:

Lol

 

Thank you for the insight.

After reading a little about this Fiber Frame Fraction, and as me, only flying in Orbx area pretty much, would a value of .44 or .55 make stuff better? I am not loosing performance and my rig is almost at 5GHZ, currently at 4.8 stable.

 

Just wondering as it says anything lower than .1 will cause blurries. So if low is slower loading the highest you think I could make would be what?

" .1 will cause blurries"

 

That's probably correct, though it depends upon your speed and the amount - density of the terrain below you. I use 0.1 when (most of the time) I'm flying low and slow around the PNW - CRM - NRM areas. (The only place I fly).

If I were to see blurries - and I did, back in the Core2Duo days - I will just move it up a bit - to 0.12 or 0.14. No big deal. When landing the Maddog into KSEA / 34R, the approach speed starts at around 200, being stable 9 or 10 or so miles south, and 2500 - 2800 feet. There are lots of houses, roads, cars, buildings, etc, and the ground textures don't blur at that setting. A Spitfire at 350 and 100 feet might be different, of course!

 

Just picture it as a means to make the sim smoother, William. Lower is smoother - higher is jitters. .33 is default. I have no idea why anyone would move it in the opposite direction. I first used this many years ago, (E6600) and it gave me a 23 fps smoother flight over SEA, as I lowered it. The frames started at around 18 - 19, and got better as I lowered it, I think ending around 0.2 at that time. We now have higher-speed GPU's, so yes - no reason not to lower it - even just as an experiment.

Ok, I guess there is the confusion for me, or I am dense as my autogen.

We now have higher-speed GPU's, so yes - no reason not to lower it - even just as an experiment.

 

I would think, .1 or .14 is lower than .33, seeing as how .99 would almost make 1.0. Just here what you said, and elsewhere on the net that I have read also refer to this as lowering. I guess you and everyone else is talking about it relatively, as lowering it as in, lowering the speed at which you would make your GPU pick up the slack, not as in lowering it in the speed your CPU spends on it.

 

That is just the issue that I have. I may have to leave mine as .33 then, as I will from time to time fly low and slow, fly the Duke at 220+ around 8K, the NGX into KSEA or KLAX, and whatnot. I am pretty diverse in what I fly, and I guess I could change it for each flight, that is if I remember.

 

About my picture, did you think that looks pretty much normal then? You didn't really comment on it, so that makes me a little at ease as it must just be my mind.

 

Does FSWC work with DX10? Have you every used it with success?

 

Again, thanks for all the hand holding you are having to do here with me.

No problem, William. Time is the only enemy! It's a pleasure to help someone become successful! Just look at Les and his new movie career!

 

The pic is a bit on the high side for a good look, William - but it does look ok, for sure. Color is good, and the waves look very much like my own. As mentioned earlier - wave motion is very likely set in the WaterConstants.xml - but I don't know that. It would be a matter of replacing the existing one with someone else's, looking for a difference. Just follow the above method and replace it with WallyDog's xml. It was the one I liked the best in FSX - DX9, and it's probably the one I'm using right now.

 

If any doubt about the FFTF, William - simply make it 0.2 and then forget all about it. I merely suggest 0.1, as it is the lowest I could go with pretty good speed and a low-ish altitude, and not have any blurries. .14 is safe, .16, .18, .2 - all fine - no blurring and no stuttering. It's quite a wide range, but .33 is kinda high, and when this one was 'found' - lowering it was mandatory, if one wanted a smooth ride. I wouldn't waste my time with "another look at FFTF set a 0.33, to see what effect it will have on a 580 and 4.9 gig". My setting is 0.1, and it works just fine!

 

FSWC does not work with DX10. I have it, and have worked with it but no, it made no changes that I could see. I'm not sure whether one can change the water color with REX, but I did change it with AS2012.

 

All the Best,

 

pj

Will try the water edit and see.

Thank you for the info and insight! I will post up with what I find.

_{Sorry for the thread necromancy, but since this is a DX10 water thread...}

 

_{Last night, after much frustration with the profound lack of DX10 preview white caps with REXE water animations I tried restoring the original FSX water textures and animation and, Viola!, consistent and beautiful white caps blowing gracely across the SF bay (after all kpao is my home) that are visible from several hundreds of feet up. In DX10 preview, the default FSX wave action is plenty good enough for me; now it's just a matter of dialing the water type textures...any advice using REXE or UTX or ? BTW, I don't own AS2012 and don't plan to either. Thanks for reading.}

Rod, I have the same issue.

Default FSX waves work - other waves..nope.

Any help guys?

Phil - Rod - did either of you guys play with the WaterConstants.xml in DX9 - the one which Bojote` worked with when he did his Shader3 mod?

 

and a quick edit to my earlier (September 30) post #30 above - FSWC Lite - does work with DX10, and it's free.

 

pj

Phil - Rod - did either of you guys play with the WaterConstants.xml in DX9 - the one which Bojote` worked with when he did his Shader3 mod?

 

and a quick edit to my earlier (September 30) post #30 above - FSWC Lite - does work with DX10, and it's free.

 

pj

 

Question sir, I added this line to my .cfg file:

 

[scenery]

MAX_ASYNC_BATCHING_JOBS=3

 

I also changed mine from 80 to 100 to match this:

 

[Display]

TEXTURE_BANDWIDTH_MULT=100 (mine)

 

I added:

HIGHMEMFIX=1

to the [GRAPHICS] section.

 

Everything else I had already set in the .cfg file.

 

I downloaded and ran the FSWC:Lite, it backed-up my original files and then I selected the custom FSWC+DX10 option.

 

The water looks AMAZING! I was previously using REX 2.0 textures for everything so I assume that included the water.

I'm mainly flying around KHQM as that is my home base for AirHauler in my C172 (career mode). Now I can see depth in the water, sandbars, waves, all sorts of awesome stuff.

 

My question is, when I load up at KHQM prior to making the above changes it would show some AI traffic (I have the Orbx NA AI traffic loaded) it would show different planes parked with me a the GA parking, it would show all their textures. Now when I load up after making the above changes it shows all the planes except 2 properly. Both now have greyed out textures. One looks like a Cessna 177 the other looks like a Cessna 310.

 

Would this have anything to do with these recent changes I made to the .cfg file or is it that FSX is just now loading these planes randomly and these happen to be planes I have on my HD that are not DX-10 compatible? They look like planes I have that do not work with DX-10 (where the textures are greyed out).

 

The other AI planes are working properly, I see them as normal.

Last night, after much frustration with the profound lack of DX10 preview white caps with REXE water animations I tried restoring the original FSX water textures and animation and, Viola!,

 

How did you restore the original FSX water animations? I am using REX-E as well and the "sparkling".

Thanks!

Examples of improvement:

 

Old water picture using REX 2.0

 

 

New water textures with FSWC Lite using the FSWC+DX10 option:

 

 

 

 

 

 

Thank you Paul for the heads up on the FSWC Lite free download. :Applause:

Edited November 14, 201213 yr by firehawk44
Images removed. Exceed 400KB limit. Please repost with proper size limits.