I recently noticed that I no longer have any waves in FS9. I am using FS Water so I posted on the Flight1 support forum and followed the suggestions I received there, but it didn't help. So I'm looking to the brilliant people here for a solution.I'm running a P4 2.6 with 1 gb of RAM and an nvidia FX5600 with 256 Mb of RAM, Windows XP Home with SP2 and FS9 is updated with the 9.1 patch. In fact, I think that may be when I lost my waves. The only other thing I've installed since the update is the American Data Streams, Rails, and Utilities program.The display sliders are correct (as recommended by Flight1 for FS Water), I've completely uninstalled and re-installed FS Water. I've deleted my FS9.cfg file and let it rebuild.I've tried various locations in various weather but still no waves.I also run FS Genesis mesh for the US and the US Landclass, Ultimate Traffic, and FSHotSFX. If anyone has run into this and has a solution or suggestions, I'd really appreciate it. Thanks,Jim

Did you turn your Autogen off? Waves normally will only appear when autogen is on (at any density level)...-John

Autogen is set to Extremely Dense.Jim

I also have the same problem and am running the default water textures. No waves on the shorelines. Hoping someone comes up with some ideas.Chuck

Jim,Check your "Special Effects" slider in Display Settings. The waves are not controlled by the Autogen slider, but by this one.I don't have FS Water, so I don't know if that has something that would override the wave effect.That may not solve your problem, but it needs to be cranked up to get wave action.Wilson

Thanks for the reply. I do have the Special Effects Detail slider all the way to the right, and also the Water Effects slider is set to High. Someone also suggested that I check to see that the file wavecontroller.fx is present in the Effects folder, which it is.Jim

One other issue--and this was an issue with contrails, is whether your .fx file is the correct version. Some overzealous add-on writers were including old FS2002 contrails files with their packages, which didn't work right in FS2004. That may be the case with your wave fx file...-John

Just for kicks, try changing Terrain Detail to "Land & Water" and Water Effects to "Low".See if that gives you waves. I don't know the exact interaction of these two slider.Just a thought . . .Wilson

Courtesy of JDK2, ensure that you have the following "Effect=" in your terrain.cfg.Jon// Ocean Shorelines - Perennial [Texture.1026] // ocean / white sand / perennial Type=2 Size=4 ExcludeAutogen=1 MaskClassMap=3 Textures=o_whitesand_ls.bmp Effect=wavecontroller [Texture.1027] // ocean / tan sand / perennial Type=2 Size=4 ExcludeAutogen=1 MaskClassMap=3 Textures=o_tansand_ls.bmp Effect=wavecontroller [Texture.1028] // ocean / black sand / perennial Type=2 Size=4 ExcludeAutogen=1 MaskClassMap=3 Textures=o_blacksand_ls.bmp,o_blacksand_ls_hw.bmp,o_blacksand_ls.bmp,o_blacksand_ls.bmp,o_blacksand_ls.bmp Effect=wavecontroller

I think you may have hit the problem, Jon! I have to leave for work but I took a quick glance at my terrain.cfg file and did not see those entries. Now I'm thinking that maybe the American Data program made changes to the terrain.cfg. I'll investigate when I get home today.Thanks!Jim

This is a suspected problem with AD. More info at www.fsgenesis.net.Jon

Belay my previous post, there are actually many more places that the EFFECT=WAVECONTROLLER or EFFECT=LAKEWAVECONTROLLER need to be added.See http://portal.fsgenesis.net/index.php?name...pic&p=9538#9538where it is pointed out that it is easiest to compare your current terrain.cfg with your original terrain.cfg (off your distribution disk, if necessary) to find all these occurances.Jon

That fixed my waves. Thanks to all who offered suggestions, here and at the FS Genesis Forum.Jim

Jon:If these problems have, in fact, been caused by installing ASD, wouldn't it be more appropriate that a patch be released quickly that will make the proper corrections?I noticed that the original terrain.cfg was backed up. Shouldn't it be the responsibility of the seller to correct this problem if they were the ones who introduced it? Why should I have to manually go in with my pooper scooper, so to speak, and clean up after messy programmers?This sounds like a case where a file (terrain.cfg) was not modified, but rather, replaced with a new one -- a new one that was incorrect. That means that any other modifications that may have been made earlier are no longer active. Is that what you are telling us here?This is a programming blunder, if I am reading your posting correctly.If I have misunderstood, please provide more detail and accept my apologies.Wilson

Makes sense to me Wilson. In this case, I'm just another user trying to figure it out like everyone else (and I was a beta-tester); I don't know what he has done to the terrain.cfg so I'm not in a position to comment on other effects.I expect Markus will fix this up, and best to follow that over at FSGenesis.Jon