Big memory problem (executable size growing very fastly)
There is a way to name all D3D objects you create. See http://seanmiddleditch.com/journal/2014/02/direct3d-11-debug-api-tricks/
This helps with determing what you're looking. I highly recommend making your wrappers and helpers require debug names and ensuring that every object you create has a meaningful name attached to it. e.g., the source image for textures, or names like "normal buffer", or so on. Vertex/index buffers can likewise be named according to the data source they're filled from. Shaders and so on as well.
This helps with determing what you're looking. I highly recommend making your wrappers and helpers require debug names and ensuring that every object you create has a meaningful name attached to it. e.g., the source image for textures, or names like "normal buffer", or so on. Vertex/index buffers can likewise be named according to the data source they're filled from. Shaders and so on as well.
Ok but when I see that a type of object "lives" 48 times for example, how can I know if it normal or not ?
Between rendered frames themselfs, one cannot create any resource at all - even if it was being managed and freed. (opose game further routine though)
PIX is a good dx commands dogy
Isn't this just as simple as not Release'ing your command list? You appear to be creating one per frame and nowhere in the code snippet do you ever release your reference to it.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement