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

Would you give me some suggestion about how the command buffers work or any link would be helpful. ? #35

Closed
vedon opened this issue Jun 8, 2019 · 2 comments
Assignees
Labels

Comments

@vedon
Copy link

vedon commented Jun 8, 2019

No description provided.

@LukasBanana LukasBanana self-assigned this Jun 9, 2019
@LukasBanana
Copy link
Owner

LukasBanana commented Jun 9, 2019

The CommandBuffer interface mimics the API of D3D12, Vulkan, and Metal. For these APIs, the interface merely forwards the calls to underlying API (for the most part). For D3D11 and OpenGL, the implementation emulates the features of a command buffer. The default command buffer is very similar to the "Immediate Context" in D3D11, where the calls are submitted to the driver immediately. A "deferred" or "secondary" command buffer must guarantee to store commands in a buffer before they are submitted to the GPU. D3D12, Vulkan, and Metal support this feature natively, but for D3D11 and OpenGL it must be emulated, i.e. the actual API calls are executed when CommandQueue::Submit is called.

@vedon
Copy link
Author

vedon commented Jun 10, 2019

thx ,that helps me a lot .LOL.

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

No branches or pull requests

2 participants