stride
stride copied to clipboard
Vulkan is not usable due to low/inconsistant FPS
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:
- create a new default empty project
- add
<StrideGraphicsApi>Vulkan</StrideGraphicsApi> - add
<PackageReference Include="Stride.Shaders.Compiler" Version="4.2.0.2381" /> - 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.
Mem alloc with Vulkan:
Mem alloc with Direct3D 11:
CPU performance seems to be about the same Im guessing the allocation difference is from the initial shader compilation.