ArivenGemini wrote:
Rothgar wrote:
Kulanae@Blackburrow wrote:
So you need to flush Hall textures and let us have longer load times to get in when we want to get in.....which for most people who are not raiding will only be 2 times a night most likely.
This is already being done. The memory that you're noticing is memory that Windows is holding on to in order to optimize performance for the application. I assume you're looking at the "Working Set" value in Task Manager?
http://msdn.microsoft.com/en-us/lib...28VS.85%29.aspx
From the recent tests we've done, the EQ2 client is not holding any references to guild hall resources when you leave. The working set generally does not get decreased in size until Windows needs the ram for something else.
One of the old school "tricks" to get eq2 to release some ram was to go windowed mode and then minimize the window. Does it keep the "working set" memory when you do that?
When you minimize a window, by default, Windows trims the Working Set of unused pages. In the case of an application that uses DirectX, you also lose the rendering context which causes other resources to be unloaded as well. But all of this is done at the system level. EQII isn't specifically freeing any resources when you minimize. Most of what you are losing are resources and memory pages that EQII has already "released".
Here's some more reading if interested.
http://support.microsoft.com/defaul...kb;en-us;293215
LINK
(Rothgar) Re:Re:Re:Re:EverqQuest2.exe 1.8gigs of memory usage?!?!?
