-
Notifications
You must be signed in to change notification settings - Fork 504
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
Does Falcor support create a new Vulkan <-> CUDA shared buffer? #402
Comments
Yes, The better way is to use We don't have many Linux users yet, but I think we do run a few tests with shared buffers on internal Linux CI, so this should work. |
true, that is windows only it seems |
can you try just adding this? #if FALCOR_WINDOWS
case Device::Type::Vulkan:
desc.type = cudaExternalMemoryHandleTypeOpaqueWin32;
break;
#elif FALCOR_LINUX
case Device::Type::Vulkan:
desc.type = cudaExternalMemoryHandleTypeOpaqueFd;
break;
#endif Edit: nope sorry, that won't work, you'd also need to set the handle on the correct field |
|
I have a training task running on linux,and need to get buffers from falcor. but when i tried to run the InteropBuffer::createInteropBuffer, it fails and i wonder if it only supports DX->CUDA?
The text was updated successfully, but these errors were encountered: