No never applied it to my old setup. I did get some micro stutters on that one but only with a few addon aircraft and when using Unlimited framerate so maybe it would have helped in those cases. The new mobo+CPU+videocard completely cured those - if it sais 40 FPS now I actually get 40 FPS, not 10 FPS one second, 60 the next then 20...

Greg,Is it better to put the USB Controller latency to 0? Mine were orignally at 64 each, I changed them to 32 and I was wondering if 0 makes any difference.Dan

A little tip for ATI users who already have ATI Tool installed in their pc's. You can change and keep the latency setting in that program as well.Havent really noticed any difference, still getting stutters when flying over water on high detail with 16xAF.. so its back to just normal water :D

Reading this thread I was hoping to install LtcyCfg2 and discover that I had some higher latency settings that could be adjusted downward, but somehow or someway, my latency settings are already at 32 for everything including my ATI 9600 Pro, except for my PCI Bridge (SiS Virutal PCI to PCI bridge (AGP)) and RAID bus controller, which are both at 64. Do you think its safe to try adjusting those two down to 32? Wonder how the other devices, expecially the video card, got to 32? Thanks in advance.rrk30

I would leave things as they are for any device other than sound, video, NIC, or modem. Before I ran the tool on my own PC, I also ran it on one in my shop for comparison, and like you I found the one in my shop had settings of 32. My home system had settings of 248 for both my modem and VGA card, and I lowered both to 64. I'll probably drop them both to 32 to see if anything becomes better/worse, but anything Motherboard related I left alone.-John

Yea even i noticed a 1% improvement in 3D Mark 2001, my 3D mark 2001 is 9000.

I don't know if I'd go bragging too much on 1 pct. improvement... :)But I'm replying because I noted you were from that land down under. I was reading this afternoon what a contribution your country is making to help the Tsunami victims--the largest of any nation if I read the article correctly. You and your fellow countrymen and women should be very proud and I'm glad to see you displaying your country proudly under your name.Regards,John

Hi Johnno i didnt mean to brag, the contrary, infact this latency thing has done nothing for me, thats what i meant in my initial post, only 1% improvement, zilch in FS.Yes $1 billion over 5 yrs, to help our poor neighbours, but unfortunately you can never put a price on this disaster.

I just took a look at my system using the tool and I have my GF3 Ti200 card set at 248. I am going to try to run some test flights to establish some sort of baseline and then make the change to 32. I might try to buzz KSNA in my PMDG 737 and see what happens. I wonder how smooth things might get with Megascenery loaded!!! My video card will fry for sure!Airbus

Thanks for the advice, John. Appreciate it.rrk30

They were all set to 32 on my system by default - I think the Omega drivers are probably the reason...

Sorry, but I couldn't help changing the title...Not knocking any of the valid points here but there are some things everyone should consider before making timer changes:Namely, there is a reason for the high Latency settings folks, High latency = high effective BandwidthLow Latency = crippled bandwidthThe need to lower the latency timer for the video card is rare, there are reasons why you won't/dont see this reccomended for everyone on any of the legit hardware sites for increasing performance, (stutter or no) as there are other reasons for a system to stutter (you may need to re-shuffle some cards that share IRQ's/polling software/bad driver/bad driver installs etc...you may want to think about that.If your system is using AGP with low Latency settings and you are loading up FS with some demanding scenery on top of FS's normal needs, you will invariably run into "un-painted" areas or delays as your view changes and your flight continues and the video card has to give up the bus when two or more PCI devices are operating simultaneously while it would still like to send a burst down the pipe etc to pleasure your eyes.The new PCI- express bus is so wide open right now for today's needs that it will not suffer this problem and hence it commonly uses low latency timer settings of 32.Though >some< systems can benefit with more balance or depending on what hardware needs you may have above graphics (sound editing, or sound problems, networking etc) a majority of gaming rigs require the high PCI/AGP bandwidth for the graphics card that higher latency timer setting provide.So if you decide to lower the latency timer settings you may want to take it easy...a little at a time.As for me the higher latency has for a long time been a given and one that is most desirable for me as I tend to lean towards the graphics side quite heavily (including in FS) however I do not encounter stutters, but as the scenery grows more dense things are starting to slow down and it is getting near time to retire the old card..sigh.BTW, FS is fully loaded, besides all the photoreal stuff it uses both AD-road's...set as well as USA-roads (not use simultaneously) FS-Genesis 38m-mesh and landclass as well as custom shoreline, Lake and river data.Anyway, nice thread and I hope some of this helps some of you.

"They were all set to 32 on my system by default - I think the Omega drivers are probably the reason..."I hadn't visited Omega's FAQ page in a while, and curious about your observation I just read this at his site:Do Omega Drivers offer users the ability to change the latency of their Radeon like other tools do?They don

"High latency = high effective BandwidthLow Latency = crippled bandwidth"Was thinking it may be something to that effect. I like to compare it to reading a book - the latency timer controls how long a particular page is open. So if it's too high you will have finished reading the page long before you're allowed to turn the page causing unneeded waiting. On the other hand - if it's too low you'll constantly have to "turn back" the page because you didn't finish. The videocard "pages" contain a lot more "text" than e.g. those for soundcards or networking as a *lot* of data needs to be sent for graphics than e.g. sound or networking.It's the same as with the tRAS timing for DRAM - some like to set it as low as possible but in reality it should never really be much lower than 6-7.What surprises me is that I *do* get very slightly better performance with the AGP latency at 32 vs 255, even in 3DMark 05 which certainly is very graphics-intensive.

Probably all very system dependent. I tried moving latency to 32 on my 6800GTOC and seem to have a slight improvement in AUDIO performance--mainly the very slight pauses that sometimes happened when .wav files played (or perhaps it was the loading of the .wav to play) seem to be gone now.Noel