6 replies to this topic

[Spudman]

I am using 'D3DXCreateTextureFromFileEx' to load textures straight into
Video Ram ( D3DPOOL_DEFAULT ). However I noticed that when I release
the textures the memory does not seem to be returned to the pool....
( using GetAvailableTextureMem() shows that this is the case! ).

HOWEVER... If I use D3DPOOL_MANAGED then the memory appears to be
returned....

Why should this be ?

[roel]

Did you check the output from directx when it is placed in debug mode (using the option in the control panel and dbmon, assuming that you have the sdk installed)? Usually it provides useful information in cases like this.

[Goz]

It can take several frames before the runtime has actually finished with that "Released" resource and hence it can remain resident longer than you may expect...

[Spudman]

The debugger don't give no clues.... the memory is definately not available
(even after many frames...), guess I'll just make do with the MANAGED pool at the moment until I can work out why DirectX isn't returning the video memory when the texture is in the D3DPOOL_DEFAULT.... problem is I want
stuff forced into video mem. to avoid long upload times on a laptop....

[MePHyst0]

just curious, how do you release your texture?

[Goz]

and does the Release() call return 0?

[Spudman]

Yes - I release with the usual .com Release method, and the expected return value is 0.... I'm still stumped....