July 1, 200817 yr Thanks for taking a swing at it.-- Then FSX's Vram "observation" is only used to build the initial fsx.cfg file. -- FSX's observation of Vram is only used as surrogate: This Vram observation is only used to suggest that the Vcard's GPU might be more capable (because it has more onboard ram) and thereby the system can use a higher "bucket." I'm lead to this premise by the comment that Vram above 512 can Not be "seen" by FSX. So then (I pondered), why else observe it at all? This suggests that any Vram above 512M will not be used by FSX under Any in-game circumstance. Right?Also, these OOM's may not be over, even with the 64bit system. I got a CTD just as VS (the OOM stuff) ticked over 4Gs. I also got a CTD with the dreaded "Your computer had run out of memory" at a VS of ~ 3.8G and a physical ram load of ~ 3.4. Note: VS hadn't just ticked-up to 3.8. It had been over 3.5G for a while. The "tick-up" may have been to > 4G and triggered this OOM. This was with a 512 Vcard.I had the system intentionally uberloaded for these test flights. The intent is Not to try to break the sim. It's to observe the future. These loads are available NoW, it's just that No player would be willing to hammer along at 3 FPS. However 3FPS is going to become 30 FPS with the next-gen and these are the loads it will Have to deal with. These 64bit OOMs are because the 64bit op system is running a 32 bit program. I'm thinkin' it'll definitely be TiMe for a 64 bit program option with FS11.
Create an account or sign in to comment