Virtual Reality template example doesn't work using vulkan renderer
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: Github versions
Version: Happens on latest stable (using master-4.0 branch) and on latest master
Platform(s): Windows
Describe the bug
When trying to run the VR template using the vulkan renderer the example freezes and starts to leak memory until it crashes
To Reproduce
Steps to reproduce the behavior:
- Compile GameEditor from any of the indicated branches adding Vulkan to
StrideGraphicsApiinStride.Build.propshttps://github.com/stride3d/stride/blob/master/build/Stride.Build.props - Create a new example from the VR template
- Change the
StrideGraphicsApito vulkan in the new example by adding:<StrideGraphicsApi>Vulkan</StrideGraphicsApi>to the fristPropertyGroupinVRSandbox.Windows\VRSandboxWindows.csproj - Run the example
- The window appears, the console shows how the shaders are compiled but the output doesn't appear on the VR device and starts to leak memory until it crashes with a corrupted memory error.
Expected behavior
The example should run correctly and show the output in the VR device as it works when using directx instead of vulkan.
Additional context
This happens when running the application using the steam VR null driver by setting it up in Program Files\Steam\config\steamvr.settings using :
"driver_null" : {
"enable" : true,
"id" : "Null Driver",
"windowHeight" : 1080,
"windowWidth" : 1920,
"windowX" : 100,
"windowY" : 100
},
The same device setup works fine when using direct x, when running the example the steam vr window appears and the output of the application shows up in the monitor emulating the VR device.
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
Reproduce the freeze with the VR template and SteamVR null driver, enabling Vulkan in build/Stride.Build.props and VRSandbox.Windows\VRSandboxWindows.csproj. Compare the Vulkan run with the working DirectX path, then verify that the VR device receives output without memory growth or a crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- computer-graphics, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100