• Advertisement
Sign in to follow this  

All Textures in Use, Cannot Evict Texture

This topic is 4525 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I am getting this error message in my program from Direct3D and I am not sure exactly what is causing it. My textures are created with D3DUSAGE_AUTOGENMIPMAP and D3DPOOL_MANAGED. Is this error coming fomr the graphics card because all the texture memory is full? I thought managed meant it swaped in and out as needed? FYI, I also use Lock to update the texture. Thanks

Share this post


Link to post
Share on other sites
Advertisement
I have an additional question to this. When a texture is set in a texture stage and then drawprimitive is called. When you use the same stage to set a different texture, I assume that if there is not enough video memory it will move the old texture out of video memory if you are using POOL_MANAGED?

Is this correct?

Also, I put an EvictManagedResources call in, which got rid of the problem. My question is, why isn't the direct3d managed pool code removing the old texture from the previous drawprimitive by itself if there is no room in video memory!?

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement