November 6, 20169 yr For me the culprit was ORBX VECTOR How did you configure Orbx Vector? In my P3D guide here on AVSIM I provide some good examples on how to config Vector to make it VAS friendly. Enabling everything in Vector will use a lot of VAS. Based on the point you referenced, perhaps it was the "Frozen surfaces" option in Vector that may have triggered it as Vector will swap out water tiles for frozen texture tiles. Cheers, Rob.
November 6, 20169 yr No one tried disabling FTX Global2010? Thanks Michael Moe i did it and that save some VASi keep alive only region i fly,and deactivate other Frédéric Giraud
November 13, 20169 yr How did you configure Orbx Vector? In my P3D guide here on AVSIM I provide some good examples on how to config Vector to make it VAS friendly. Enabling everything in Vector will use a lot of VAS. Based on the point you referenced, perhaps it was the "Frozen surfaces" option in Vector that may have triggered it as Vector will swap out water tiles for frozen texture tiles. Cheers, Rob. Had everything checked in vector with the exception of the frozen water so it could not have simply been the frozen water but maybe other stuff unchecked may help, I will experiment with that sometime but for now I'm fine without vector.
March 4, 20188 yr On 2/13/2016 at 9:02 PM, chad556 said: Loading up at the default CYYZ or CYOW in the default piper cub starts with a VAS of nearly 3.1gb! Thank you for posting this! It definitely helped me narrow down the cause of my problem as well. FTX Global / Vector / OpenLC combo is also giving me an Out of Memory error, when taking off at night from CYYZ. Am surprised that this has not been patched by OrbX yet, since many other people probably fly through there. Has a workable solution been found other than completely disabling Vector?
Archived
This topic is now archived and is closed to further replies.