Hello ,
This product is absolutely magnificent tough it seems to have a memory usage problem..
I have compered it to other major sceneries which use a large amount of memory and YYZ is using the most memory among all.
With Low Tex installed and all settings are unchecked I keep getting OOMs ; when flying around with the PMDG 777 or when Descending to the Airport from somewhere else , I have no any other Scenery that uses as much as memory as Fly Tampa YYZ...
On first load , only with the default Ultra-light the VAS memory riches 2 GB of usage and When I load a big jet and start flying it riches 2.8 - 3.2 and OOM occurs..
Any thoughts ?
Thanks, Amir
VAS and OOMs
- martin[flytampa]
- Site Admin
- Posts: 5288
Re: VAS and OOMs
I have spent the last 2 weeks prior to release mostly measuring VAS and looking for ways to improve it. Attached 2 shots of my results. Default Toronto seems to be very heavy on VAS, showing 1.74, compared to 2.27 with Fly-Toronto running on top.
Note the shots are both without AI, clear skies and default Cessna. Each after slewing around and looking in all directions for 5mins to let VAS build up until it peaks. Fly-Toronto is running with the LITETEX pack but all Animated Traffic and 3D people as well as other options turned On.
I don't know what else to do about it, other then to strip the wider Toronto area of its "stock vector data" details etc, which is probably whats eating all this RAM. For comparison, loading Fly-Dubai and slewing around for 5mins under the same condition I get a reading of 1.85 In Process Explorer and with stock Dubai I get 1.30. In that sense its the same as Toronto, each adding 500MB on top of stock.
Note the shots are both without AI, clear skies and default Cessna. Each after slewing around and looking in all directions for 5mins to let VAS build up until it peaks. Fly-Toronto is running with the LITETEX pack but all Animated Traffic and 3D people as well as other options turned On.
I don't know what else to do about it, other then to strip the wider Toronto area of its "stock vector data" details etc, which is probably whats eating all this RAM. For comparison, loading Fly-Dubai and slewing around for 5mins under the same condition I get a reading of 1.85 In Process Explorer and with stock Dubai I get 1.30. In that sense its the same as Toronto, each adding 500MB on top of stock.
- Attachments
-
- vas-addon.jpg (518.86 KiB) Viewed 2995 times
-
- vas-default.jpg (512.96 KiB) Viewed 2995 times
Re: VAS and OOMs
Hi Martin thank you for your answer..
Ill try to see if I can improve the memory usage by disabling some vector and LC data in Toronto area..
Thx.
Ill try to see if I can improve the memory usage by disabling some vector and LC data in Toronto area..
Thx.