Skip to content

Vulkan is not usable due to low/inconsistant FPS #2811

Open
@Doprez

Description

@Doprez

Release Type: Official Release and GitHub

Version: 4.2.0.2381 and master

Platform(s): Windows

Describe the bug
When the Graphics backend is set to Vulkan the performance makes it unusable.

To Reproduce
Steps to reproduce the behavior:

  1. create a new default empty project
  2. add <StrideGraphicsApi>Vulkan</StrideGraphicsApi>
  3. add <PackageReference Include="Stride.Shaders.Compiler" Version="4.2.0.2381" />
  4. witness performance issues

Expected behavior
Frame rate should not be bad.

Log and callstacks
Sadly there is nothing being logged but I can say Im not seeing anything crazy with the VS2022 debugger or Task Manager that would poit to anything specific.

Image

Mem alloc with Vulkan:
Image

Mem alloc with Direct3D 11:
Image

CPU performance seems to be about the same Im guessing the allocation difference is from the initial shader compilation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions