Registered Extension Number

436

Revision

1

Ratification Status

Not ratified

Extension and Version Dependencies

None

Contact

Other Extension Metadata

Last Modified Date

2021-12-14

Contributors

  • Daniel Koch, NVIDIA

  • Jonathan Mccaffrey, NVIDIA

  • Aidan Fabius, CoreAVI

Description

This instance extension enables an application to pass application parameters to the implementation at instance or device creation time.

The application parameters consist of a set of vendor-specific keys and values. Each key is a 32-bit enum, and each value is a 64-bit integer. The valid keys, range of values, and default values are documented external to this specification in implementation-specific documentation.

This extension is an instance extension rather than a device extension so that the implementation can modify reported VkPhysicalDevice properties or features as needed.

New Structures

New Enum Constants

  • VK_EXT_APPLICATION_PARAMETERS_EXTENSION_NAME

  • VK_EXT_APPLICATION_PARAMETERS_SPEC_VERSION

  • Extending VkStructureType:

    • VK_STRUCTURE_TYPE_APPLICATION_PARAMETERS_EXT

Issues

  1. How should the key enumerants be assigned?

    RESOLVED: The key enumerants are completely implementation-specific and do not need to be centrally reserved. They should be documented in the implementation-specific documentation. The vendor ID and optionally the device ID are provided to disambiguate between multiple ICDs or devices.

  2. How does an application know what application parameters are valid on a particular implementation?

    DISCUSSION: There is no ability to enumerate device or system properties before an instance is created, however key and values must be recognized by an implementation in order for instance or device creation to succeed. The vendor and optionally the device ID are provided to identify which ICD or device the application parameters are targeted at.

  3. Is it OK if the "valid value" for specified keys is not from static documented values, but must be consistent-with/interdependent-on other VkApplicationParametersEXT?

    DISCUSSION: Yes this is fine. Examples for how this could be used include:

    • a checksum key where the value is computed based on other VkApplicationParametersEXT structures in the pNext chain.

    • an "application key" which either implies or explicitly lists a set of prevalidated key/value pairs.

Version History

  • Revision 1, 2021-12-14 (Daniel Koch)

    • Initial revision

See Also

VkApplicationParametersEXT

Document Notes

For more information, see the Vulkan Specification

This page is a generated document. Fixes and changes should be made to the generator scripts, not directly.

Copyright

Copyright 2014-2023 The Khronos Group Inc.

SPDX-License-Identifier: CC-BY-4.0