vulkan 扩展:由谁支持? [英] vulkan extension : which are supported by whom?

查看:53
本文介绍了vulkan 扩展:由谁支持?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

EXTKHRAMDNV 扩展.也许还有其他一些.我知道 NV 意味着 Nvidia 并且它的 nv 扩展不太可能被 AMD 支持.但是 khr 的还是 ext 的呢?每个人都必须支持它们吗?

There is EXT, KHR or AMD or NV extensions. Maybe there are some others. I know that NV means Nvidia and that it nv extensions are unlikely supported by AMD. But what about khr ones or ext ones? Are they mandatory supported by everyone?

推荐答案

有一个 网站 专门跟踪这个信息.

There's a website devoted to tracking this information.

也许还有其他的

大量

但是 khr 的还是 ext 的呢?每个人都必须支持它们吗?

But what about khr ones or ext ones? Are they mandatory supported by everyone?

KHR 扩展通常是将被折叠到规范中的东西(例如 VK_KHR_external_memory 如何成为 1.1 中核心 Vulkan 规范的一部分)或者是可能被广泛的供应商和硬件支持的东西,但不一定所有硬件(如 VK_KHR_swapchain).

KHR extensions are typically things that will be folded into the specification (like how VK_KHR_external_memory became part of the core Vulkan specification in 1.1) or are things that are likely to be supported by a broad range of vendors and hardware, but not necessarily all hardware (like VK_KHR_swapchain).

KHX 扩展基本上是 KHR 扩展的实验版本.它们可能会成为 KHR 扩展或被纳入规范,但它们也可能在此之前发生巨大变化.

KHX extensions are basically experimental versions of KHR extensions. They might become a KHR extension or get folded into the spec, but they also might change drastically before they do.

EXT 扩展不是特定于供应商的,但它们通常针对一些不太常见的用例,或者更具实验性的东西.它们通常永远不会成为规范的一部分,并且它们是您在依赖之前需要检查的那种东西,并且如果它们不受支持,则计划退回到其他一些机制.有时 EXT 扩展可以演变成 KHR 扩展.

EXT extensions aren't vendor specific, but they're typically targeting some less common use case, or something more experimental. They typically won't ever become part of the specification, and they're the kind of thing you need to check for before relying on, as well as having a plan to fall back on some other mechanism if they're not supported. Sometimes EXT extensions can evolve into KHR extensions.

供应商特定扩展基本上与 EXT 扩展在同一条船上,但由特定供应商控制.它们还可以演变为 KHR 扩展或核心规范.例如,KHR_external_memory 最初是 NV_external_memory.

Vendor specific extensions are basically in the same boat as EXT extensions, but controlled by a specific vendor. They can also evolve to become KHR extensions or core specification. For instance, KHR_external_memory started out as NV_external_memory.

每个人都必须支持它们吗?

Are they mandatory supported by everyone?

他们只有核心规范所说的强制性内容才是强制性的.

They only thing that's mandatory what the core specification says is mandatory.

这篇关于vulkan 扩展:由谁支持?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆