[meta] Application testing

[kvark]

• Native games and apps:
  • Dota2
    • now blocked by Use of pre-recorded command buffers per frame ValveSoftware/Dota-2-Vulkan#335
  • Forsaken Remastered
    • "VK_KHR_get_memory_requirements2" - Support VK_KHR_get_memory_requirements2 #190
    • "VK_AMD_buffer_marker" - Support VK_AMD_buffer_marker #191
    • "VK_KHR_display" - Support VK_KHR_display #192
    • "VK_KHR_display_swapchain" - Support VK_KHR_display_swapchain #194
    • "VK_EXT_debug_report" - Support VK_EXT_debug_report #193
  • TES Online
  • VkQuake
    • named specialization constants - Support composite specialization constants gfx#2059
  • VkQuake2
    • line fill mode - [mtl] expose line fill, fix MSAA views gfx#2687
  • vkQuake3
    • fullscreen support - Port to the new swapchain model #210
  • vkOpenArena
  • GZDoom
    • time queries - vk: Check for the time query support on the graphics queue ZDoom/gzdoom#884
  • filament
    • swapchain out of date - Metal swapchain lost on creation gfx#2400, Port to the new swapchain model #210
  • FPS Infinite (Senkro engine)
  • War War
  • Touch Designer
  • Final Fantasy XIV
  • AeroFly
  • Aurora
    • WIP changes
  • Baldur's Gate 3
  • Warzone 2100
  • Raft
• Engines
  • Flutter
    • basic support - Flutter should use Metal instead of OpenGL on iOS flutter/flutter#18208
  • VGL engine
  • VSand
    • investigation - macOS Support via MoltenVK Ealrann/VSand#13 (comment)
  • Diligent engine
    • submission fixes on our side - gfx-rs update and multiple submissions #177
    • integration - Vulkan on Metal via Vulkan Portability DiligentGraphics/DiligentCore#69
  • Flax
  • FNA
  • Excal
  • NAP
• Samples:
  • vkCube from LunarG SDK
    • blocked since Port to the new swapchain model #210
  • glTF PBR
• Emulators:
  • RPCS3
    • integration: Vulkan Portability code path on MacOS with MVK extensions RPCS3/rpcs3#4996
    • queries: [RFC] Query resolve gfx#1638
    • bigger buffer views: [mtl 2D texel buffer view gfx#2340
  • Xenia
    • tracking issue: Xenia for Mac? xenia-project/xenia#596
    • rectangle lists - Support Xenon's rectangle lists #140
  • Dolphin
    • integration: Vulkan: macOS support via MoltenVK dolphin-emu/dolphin#7039
    • expose surface usage flags: Query image usage capabilities for surface formats gfx#1908
    • expose more device limits: [WIP] Add more physical device limits gfx#2201
    • implement queries: [RFC] Query resolve gfx#1638
    • MSL 2.0 shaders for texture arrays
  • ppsspp
    • VK_FORMAT_B4G4R4A4_UNORM_PACK16 format
  • yuzu
    • basic support - https://github.com/yuzu-emu/yuzu/pull/3593
    • "VK_KHR_get_surface_capabilities2" - Support VK_KHR_get_surface_capabilities2 #212
    • "VK_KHR_storage_buffer_storage_class"
    • "VK_KHR_maintenance2"
    • "VK_KHR_maintenance3"
    • "VK_KHR_shader_draw_parameters"
    • "VK_KHR_16bit_storage"
    • "VK_KHR_8bit_storage"
    • "VK_KHR_descriptor_update_template"
    • "VK_EXT_vertex_attribute_divisor"
    • "VK_EXT_host_query_reset"
  • duckstation
• Not Emulators (wine)
  • Wolfenstein2
  • Doom
  • DXVK
    • "VK_KHR_maintenance1" - Expose VK_KHR_maintenance1 and fix the descriptor allocation fall back #110
    • "VK_KHR_shader_draw_parameters" - Support VK_KHR_shader_draw_parameters #138
    • "VK_KHR_get_physical_device_properties2" - Implement the remaining VK_KHR_get_physical_device_properties2 entry points #102
    • "VK_KHR_descriptor_update_template"
  • VkD3D layer
    • "VK_KHR_shader_draw_parameters" - Support VK_KHR_shader_draw_parameters #138
    • VK_FORMAT_B10G11R11_UFLOAT_PACK32 with RGB1 swizzle
    • "VK_KHR_push_descriptor" (optional)

[alexey-lysiuk]

Could you please give some details about 'minor tweak to WSI' for GZDoom mentioned on 0.7 release notes?
I guess the minimum set of changes is this one.

The thing is I've got VK_ERROR_SURFACE_LOST_KHR from vkQueuePresentKHR() almost every time on launch or after starting a new game. Sometimes, like in 20 to 30% of attempts, everything works fine.
Just of curiosity, did you experience something similar?
Probably, I can even debug Portability, although I'm not familiar with Rust at all. Are you using CLion with Rust plug-in?

I would like to use Portability with GZDoom for testing and benchmarking purposes.
Two Vulkan implementations are better than one anyway.

By the way, the source port is called GZDoom, not gzDoom.

[kvark]

@alexey-lysiuk hi! I wanted to file an issue but your github project doesn't enable issues. Would be best to have this discussion in a more specific place than our meta-issue...

Looks like you figured this out:

MoltenVK allows passing a layer, although Vulkan specs prohibit this

Basically, it's an undocumented behavior of MoltenVK implementation of the "VK_MVK_macos_surface" extension. We understand the reason why it's there, but we don't want to implement undocumented behaviors. Instead, we developed a portability-agnostic extension that would work for both us and MoltenVK and is documented properly: EXT_metal_surface. gfx-portability supports this extension since v0.6 release. MoltenVK should have it in the latest release, they implemented support about a month ago, see KhronosGroup/MoltenVK#653

The thing is I've got VK_ERROR_SURFACE_LOST_KHR from vkQueuePresentKHR() almost every time on launch or after starting a new game. Sometimes, like in 20 to 30% of attempts, everything works fine.

I haven't seen it, although:

• I can see how this could be the case - our presentation mechanics has flaws, and they can manifest differently on different OS versions. For some background, it's complicated because we record command buffers live whenever ONE_TIME_SUBMIT is specified, so we can't naively use CAMetalLayer way of acquiring drawables... We are looking into ways to make it more robust, see Presentation Surface API gfx#2882 .
• I haven't tested the game too much, just played for a few minutes.
• It's not a crash, it's a valid error code the vulkan implementation may return to the app, so GZDoom should be handling this and recreating the swapchain (if it doesn't do so).

Probably, I can even debug Portability, although I'm not familiar with Rust at all. Are you using CLion with Rust plug-in?

People have different setups. I just use Sublime Text 3 with Rust Enhanced plugin.

I would like to use Portability with GZDoom for testing and benchmarking purposes.
Two Vulkan implementations are better than one anyway.

This is great, thank you! We keep our hopes up when talking about benchmarks :)
We just need to find a better place to communicate: this meta-issue is high level for our topic. There is a gitter room, for example. Alternatively, you can just create issues in this project (as opposed to continuing here).

[grovesNL]

Looks like DuckStation attempted to run with portability on macOS https://github.com/stenzek/duckstation/issues/555#issuecomment-648252921