<p><cite>Kcep wrote:</cite></p><blockquote><p>Someone want to load up Vanguard and /or EQ2 and tell me how much their .exe are using.&nbsp; From what recall it&#39;s certainly wasn&#39;t even close to .5 gig, more like .05... I could be wrong.</p><p>There is either a memory leak and/or a programming architecture problem due to the years of "spaghetti code".</p></blockquote><p>They use considerably more than .5 gig.&nbsp; On my home machine I believe EQ2 usually uses around .9Gig.&nbsp; The advantage both those engines have is that they have dynamic resource management systems, which EQ does NOT.&nbsp; This is something I&#39;d like to add, but it&#39;s a VERY big project that will undoubtedly produce all kinds of problems when implemented (remember proximity?) despite all the QA and testing we can muster.&nbsp;</p><p>Again, make SURE you&#39;re looking at VM Size in task manager (in XP anyway).&nbsp; What Task Manager displays as "Mem Usage" is what&#39;s called the "working set" and represents only the amount of memory taken up by the process physical ram (roughly).&nbsp; This value can change drastically at the whim of the OS and has only an indirect relationship (not linear) with the amount of actual memory the process is using.</p><p>This comes up over and over again.&nbsp; Darn Microsoft!&nbsp; <img src="/eq/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" /></p><p>I&#39;m not saying we aren&#39;t using more memory than a year ago, but EQ hasn&#39;t consumed only .05 gig in a really long time, if ever.</p>

More...