Hello everybody. I am new here, thanks in advance for welcoming me
I have a project that i started up as TopDown template, then I have migrated it into VR Template, because i wanted to try a topdown game with a VR camera.
The version I use is Unreal 5.3.2
When I try and use the Nodes āSphere Traceā or any āTraceā node, that messes up the camera.
I have tried the nodes in all the other non-VR templates (FPS, ThirdPerson, Topdown,etcā¦) everything works.
But in the VR Template and in my TopDown migrated into VR Template, that doesnt work at all.
Sometimes it crashes the game preview (in selected viewport), this is the log i get after pressing X for my āSphere traceā action crashing :
I dont know yet what is custom depth stencils, but i need to understand how and why its configured in VR Template, and if i need it in my project, because Debug Drawing for Sphere Trace functions seems really useful .
Custom Depth Stencils are primarily used for masking objects through walls or changing the way the depth of that masked object appears on the depth map. Itās often used for highlighting things through other meshes. I am going to set up a test bed to replicate this to see if I can discern where the depth buffer is being altered. Which HMD are you using for reference?
I am very interested in the results of your tests.
Regarding the HMD, i dont use yet a HMD.
The purpose is to build a prototype before getting the HMD. (the prototype needs only the VR camera, and no VR interactions like VRGrab etc.)
The fail occurs in 2 projects :
the vanilla VR template. When i add my nodes into the blueprint āVRPawnā, and press assigned key in game preview for event to launch
my own project which i started from TopDown template and then migrated to VR Template. The main Blueprint remains my TopDown blueprint, with its own classic camera. And i placed a VRPawn camera (slighly customized) that is quite useless for the moment, until i can try with the future HMD. I added the nodes in the main blueprint (TopDownCharacter). The game runs decently (character, non-VR camera, etcā¦), until i try Sphere trace with Debug Draw.
Iām getting reports of this error in other contexts, but still canāt replicate it. Trying to dig a bit deeper, though this might be an environmental concern.
No, i dont use Metahumans.
Have you tried to reproduce it on VR template without HMD ?
Because it really seems related to VR template, and i have not installed any third party driver for VR (like Windows Mixed Reality or other) :
VR template
No HMD
No third party VR driver
No MetaHumans
Sphere trace with Debug Draw on VRPawn (or in topdown character)
Iāve tried with a Quest 2 through OpenXR, standalone without the HMD, and PIE without the HMD in windows 10 and DX12. After firing the debug draw there are no errors, stalls, or anything. It might be best to report the bug as itās likely something environmental.
