Debug drawing glitched in VR with Instanced Stereo in 4.13

[anonymous_user_f6e9085c]

Steps:

1. Make a new project in 4.13
2. Enable Instanced Stereo rendering
3. Draw debug lines somewhere
4. Look at it in VR and notice how the lines are not drawn correctly.

Here are screenshots from my project:

Incorrect image, instanced stereo ON. Notice how both debug lines originate from right eye

Correct image, instanced stereo OFF

[anonymous_user_e729f54e]

Hello AadarshPatel,

This issue sounds similar to a known issue. I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

1. What VR device are you currently using?
2. Are you using the new VR Template in 4.13?
3. If so, can you reproduce this issue in a clean blank project (not VR template)?
4. If so, could you provide a detailed list of steps to reproduce this issue on our end?

[anonymous_user_f6e9085c]

1. We tested on both Oculus RIft and , and both had glitched debug lines when Instanced Stereo rendering was enabled.
2. It was glitched in our existing project that we upgraded from 4.12.5, a new VR Template project, and a clean blank project
3. Yes!
4. Enable Instanced Stereo rendering, draw debug lines (drawing them from motion controllers makes it easy to test), run in VR Preview

I attached the clean project: [link text][2]

With Instanced Stereo enabled on a clean project:

With Instanced Stereo disabled on the same clean project:

[anonymous_user_afa9edf11 (anonymous_user_afa9edf1)]

I have something that may be similar.

If you add a collision box to the BP_PickupCube under StaticMeshComponent inside the new VR Template on the MotionControllerMap in 4.13 release, and select HiddenInGame = false/check under Rendering section, you will get some very bad line rendering where the box is being shown

Quick questions:

What VR device are you currently using?
**HTC **

Are you using the new VR Template in 4.13?
Yes

If so, can you reproduce this issue in a clean blank project (not VR template)?
Yes

If so, could you provide a detailed list of steps to reproduce this issue on our end?

**If you add a collision box to the BP_PickupCube under StaticMeshComponent inside the new VR Template on the MotionControllerMap in 4.13 release, and select HiddenInGame = false/check under Rendering section, you will get some very bad line rendering where the box is being shown. Set Rendering Box Extent to (X=94.000000,Y=128.000000,Z=68.000000) if having issue reproducing. I get very unexpected results, that does not happen in my current non template project from 4.12 **

May be related…

[anonymous_user_e729f54e]

Hello AadarshPatel,

I was able to reproduce this issue on our end. I have written up a report and I have submitted it to the developers for further consideration. I have also provided a link to the public tracker. Please feel free to use the provided link for future updates.

Link: https://jira.ol.epicgames/browse/UE-35513

Make it a great day

[anonymous_user_8b5b8fa8]

as of 4.16.2 still there the problem!!!

[anonymous_user_e729f54e]

I have retested this issue an it appear to still be occurring. I have reopened this issue.

Make it a great day

[Ecnassianer]

This got Won’t Fixed