Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-render-target textures interop #49

Open
lien0n opened this issue Dec 21, 2020 · 0 comments
Open

Non-render-target textures interop #49

lien0n opened this issue Dec 21, 2020 · 0 comments

Comments

@lien0n
Copy link

lien0n commented Dec 21, 2020

Hi @jherico, thanks for the helpful example.

I am having a GL app, which uses big amount of 3D textures (e.g., thousands of 48x48x48 texture objects). There is a situation that I need to release all the GL textures to make room for another App. However, the GL texture release is delayed (even with glFinish() calls) by the driver to a time point that's unknown to me, and the other app's GPU RAM allocation would fail from time to time.

Given your example, I am thinking to have Vulkan taking care of the device memory allocation/deallocation. Am I on the right track with this? If I am, given that my 3D textures are not rendering targets and they are read-only to shaders, do I still need the two semaphores and layout-changing command buffer?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant