-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Vulkan multiple renderers #5291
Comments
Interesting, thanks for the bug report! This is something we should be able to support. |
The problem with idea #2 is that the swap chain might not exist at the time that the default render target is set. We actually had an internal discussion about this on Feb 16 and we decided not to change the Driver API. I think it's possible to fix it without changes to the Driver API, it won't be as beautiful as possible but that's okay. I'll take a look. Note to self: this issue can be produced with our |
we didn't need one per Renderer, and doing so created complexity in the backends. fixes #5291
we didn't need one per Renderer, and doing so created complexity in the backends. fixes #5291
Vulkan backend doesn't support 2 or more Renderers / SwapChains
When creating 2 renderers, an assert will trigger in
void VulkanDriver::createDefaultRenderTargetR(Handle<HwRenderTarget> rth, int)
because the Vulkan driver stores the default render target in the context member - and assumes only one swap chain.The
defaultRenderTarget
is used in themakeCurrent
calls, to bind it to the swap chain buffers.There are 2 simple solutions:
The text was updated successfully, but these errors were encountered: