I have a "medium end" system - 1.6GHz Athlon1900, 392 Mb of RAM, and GF3.I typically get very fine performance as long as I don't turn much - around 25 to 30 FPS with high/med vis set to 5/15 miles, even in heavy mountainous regions - maybe 15 FPS with downtown Seattle in view on full detail mode. But anything that looks at new terrain, like either turning the airplane, or just switching over to a side view, reads scenery off the disk and causes 2-10 second pauses. This is kinda annoying when flying a pattern with lots of turning.I'm looking to fix this by upgrading my system's RAM (RAM is cheap these days!), but I'm looking for some verification that it will really help. Seems like it should, since Fly could cache more textures in RAM, but I just want to double check before I drop $100 on another 512 Mb just for a flight sim :)Thanks!

John:As you can see, I have a system similar to yours which, by the way, I don't consider it to be "medium range". Since I built it only a year ago, I like to believe it's more towards the "high-end" side... ;-)Anyway, I don't get those pauses. Maybe 1/2 a second at most and just at the beginning, before it's had time to cache the textures. A good trick is to "walk around" with the outside view before "getting on the plane". This forces Fly!II to load all the textures prior to you taking off.You must have something running in the background or maybe you need to tweak your render.ini (could you post it).If you have a GeForce 3 with 64Mb (your message just says GF3), I would invest in one with 128 Mb. In fact, that's what I'm planning to buy in the near future.Take care,Alejandro AmigorenaCheshire, CTFly! II Beta Team MemberAthlon XP 1800ABIT KR7A-RAID768Mb RAMMSI GeForce 3 Ti 500 64MBSB Audigy GamerCH Flight Yoke USBCH Pro Pedals USB