Vulkan captures are not portable cross-vendor · Issue #814 · baldurk/renderdoc ·...
source link: https://github.com/baldurk/renderdoc/issues/814
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Vulkan captures are generally not portable between even different hardware on the same platform. Things like memory type index selection and allocation offset/requirements are baked into the capture, so it won't replay correctly on a different driver that reports different memory types or requirements for resources.
You might be lucky if you capture and replay on similar nvidia GPUs, since it's the same driver on both windows and linux.
In future I'm hoping I can add some system to remap memory types, and report worst-case requirements (regardless of what the implementation reports) for resources, so that captures made on one system can be replayed on a different system. It's not a trivial issue to solve though, and until then vulkan captures are generally not portable.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK