-
Notifications
You must be signed in to change notification settings - Fork 437
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
QueueIter returned by Device::new
is confusing
#559
Comments
I'm not sure where the confusion is. Creating a device generates queues, and this iterator returns them. |
Currently
Maybe I misunderstood something? |
So I think the |
If you want multiple queues from the same family, you're supposed to pass the same family to Eg. |
Wouldn't passing the same family multiple times return the same queue (the first queue in the family) multiple times? I thought that |
BTW it seems to be not recommended to feed multiple vkDeviceQueueCreateInfo with the same queue family. |
Maybe what's confusing is that vulkano's API is higher-level than the raw vkCreateDevice: https://github.com/tomaka/vulkano/blob/24fe5b18975c401d70f1aecf444317fc49a5c2f7/vulkano/src/device.rs#L205-L243 It was designed this way so that the elements of the iterator returned by |
oh, I finally understand the code here.... Maybe some documentation is needed here. Thanks for your quick explanation. |
Currently
Device::new
returns aQueueIter
which is documented as the queues produces when creating a device. However it seems that the iterator is just the first queue in the queue family used to create the device. Is it intended to be this?The text was updated successfully, but these errors were encountered: