Sign in to follow this  

Is there a need to store Texture2D object for render targets?

This topic is 679 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

In my current GBuffer implementation, for each render targets, I store 3 objects as class members:

 

Microsoft::WRL::ComPtr<ID3D11Texture2D> m_t0; //Normal

Microsoft::WRL::ComPtr<ID3D11RenderTargetView> m_rtv0;

Microsoft::WRL::ComPtr<ID3D11ShaderResourceView> m_srv0;

 

?

I found that I don’t use ID3D11Texture2D object in my code after RTV and SRV initialization.

I am thinking on releasing the texture object right after RTV and SRV creation.

 

But I am not sure about usage of the texture object in other use cases.

Anyone has an idea, when keeping texture object for render target is useful?

Edited by Happy SDE

Share this post


Link to post
Share on other sites

This topic is 679 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.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this