Rua
Rua
What do you think of making `video::h264` and `video::h265` submodules, to keep the specifics for these encodings separate from the generic stuff? Regarding those constants, I'm not really sure what...
Are those constants something that the Vulkano user would be expected to use directly? If so, then they could be re-exported in Vulkano.
Are you still working on this?
At first glance it looks ok, but acceleration structures aren't supported on my device yet (still waiting on Mesa 23.2) so I can't test it. The code should not crash...
But is it necessary to *wait* for the submission? That means the whole execution stalls until the fence is signalled. A semaphore, or just putting them all in the same...
Absolutely!
Do you get any validation errors before the crash?
I mean, if you activate the validation layer, does it say anything?
There is unfortunately no way to check the state of a semaphore, nor is there a way to make it be in a particular state. All Vulkano can do is...
You can't prevent `drop` from being called. It happens automatically when there are no more references to the object.