>I think it would be a mistake to not look at what nVidia and ATI >have planned for their future graphics cards. End of next year 2GB >and 4GB will be the norm for VRAM -- why not leverage this?I think there are going to be difficulties with going to even 1G of video ram, due to the way PCI-E works in terms of memory mapping.PCI-E maps the entire VRAM of the graphics card into the process virtual address space, unlike AGP that does a partial mapping thru the AGP aperture. The app itself gets 2G out of the 4G determined by 32-bit pointers. The OS gets the other 2G. As memory on graphics cards increases, this puts some pressure on the OS and its 2G of the 4G per-process address space. It has to service all of its needs, the needs of the applications it manages, and all the hw needs out of that 2G. So as graphics memory gets added, this removes room for per-application space and reduces what the OS can get out of the machine in that aspect.This is even more true if you use the /3G switch since with a 768M graphics card as that leaves 256k for the kernel. None with a 1G graphics card.Over time we will all migrate to 64-bit because of this very issue. If it doesnt happen for FS11, it will for FS12.

Phil,Lets assume 64bit -- also glad to hear Microsoft have indicated no more 32 bit OS and the push for 64bit migration (long overdue) -- not sure where that leaves you for FS11? If you have to follow this mandate, seems to me you will have to make FS11 64bit ;)Anyway, I hope you folks seriously consider the possibilities of heavy texture caching for the graphics hardware that has room to spare. As it stands now, the scenery morphing (aka texture swapping) approach does feel very "dated" and will most likely cause a big debate if it survives in your planned DX10 version.But all tolerance issues aside, I don't think anyone would argue against removing the texture swapping approach for a future version? If it is there for LCD only, dump it! If a product is that good, people will upgrade, they always do -- they might complain along the way, but eventually they buy the hardware.Robin

I did not post to debate features, or talk FS11, or 64-bit migration.I posted to simply to point out that 2g or 4g graphics cards will not be availble on Win32. So your point there is not correct.Given I havent even talked about DX10 yet, its way premature to state anything about FS11.

Well, for some reason I am not getting blurries. Increasing texture bandwidth to 200 from 40 seemed to work for me. I have Fiber Frame at 0.22 and bufferpools at 5 million. I added the PerfBucket line as well, per Phils blog. Other than that, I guess I'm a happy camper, as I now fly locked at 30fps all the time. I fly online as well, so traffic settings are all zero for me, as I do not do free flight anymore. Danon O.

Good work with SP1 BTW.2GB graphics cards have already been available on Win32 for some time?? nVidia 7950 in SLI 1GB + 1GB (4 GPU) -- where ya been Phil?Sure you've talked about DX10 -- I've read some detailed discussions about it with you and others -- good read for the most part. DX10 API is finite so not really any speculation there, how you folks plan to leverage it all sounds good.

I dont believe both sets of memory are fully mapped in the SLI case. There is driver magic going on there, I believe, but not 2 sets of fully addressable 1g memory mapped into the process address space at the same time. Where would it go if it was? Think about it.I have made a commitment to talk to DX10 in detail, once we get a bit further down the pike. End of next month or so. Thats what I am referring to. I like to keep my commitments :-).