November 20, 201312 yr Many reasons certainly, and also now the fact that we run 64 bit, but when I read the forums at FSX and sattelite stuff, I find that one of the main reasosn I never got an OOM since I restarted using that sim last year is the fact I use **only** default scenery. Using photo scenery in FSX is am invitation to experience OOMs, the same going for other detailled scenery areas, airports, etc... We can have that detail in X-Plane 10 without anywhere near the same consequences. When I read that FSX keeps in memory the scenery areas you cross in your flights, and even some of those you don't cross, I think that while I like to be able to go to the Map view and instalntly place my aircraft anywhere over the Globe, that certainly has to have it's consequences, so... While sometimes I wished scenery load was wider in the are covered by the local grid of tiles, at the same time I ask myself if it would really be worth the risk of turning X-Plane 10 into an MSFS.... Flying gliders since 1980 Flightsimming since 1992 AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)
November 20, 201312 yr Virtual Address Space: 32bit application: 4 GB 64bit application: 8 T(!)B ("terrabytes") What happened to AVSIM
November 20, 201312 yr Author Yep, address space certainly matters, but it's not the only source of starvation... As a matter of fact, I have indeed experience OOMs with X-plane 10 64 bit when flying near crowded autogen / OSM areas like some in France and Switzerland, where data abundant ( Paris for instance, with Europe OSM + Autogen ). So, too much processing required to render objects that will most probably be unvisible and certainly not important when we're simulating VFR or IFR flights at some spot, will also cause problems. I was made aware by JonRD463 that we should lower the LOD radius on OSM scenery, but I believe that the algorithm X-Plane uses, based on tilles, may, after all, be the best option to avoid this type of situation. We're all aware that most probably 10.30 will bring some plausible fix for the distance blurrs, and I'll be happy with it, but I also used to complain about the Map view being limited to the tile area, something I am now prepared to accept in turn for stability and smoothness... Flying gliders since 1980 Flightsimming since 1992 AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)
November 20, 201312 yr I had them in x64 before Dan patched the Carenando A36.... As long as EVERY addon is native x64 then there shouldn't be any OOM's. | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
Create an account or sign in to comment