Vulkan is not usable due to low/inconsistant FPS
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report in a new default empty project on Windows with Vulkan and the listed Stride.Shaders.Compiler package. Compare its frame rate and memory allocation with Direct3D 11; done means Vulkan no longer has unusably low or inconsistent FPS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100