For some reason the Chaperone bounds are very floaty compared to the rest of the geometry. So they seem to lag behind. This happens on my own project as well as VR templates that I have found.
This only happens when there is a camera in the scene. So if i just open a empty project and try ‘VR preview’ the bounds seem solid.
I can’t find anyone else with this problem so i guess the issue is at my end. I have tried reinstalling UE4 and steamVR but the problem persists. Any ideas? The same problem also happens on 4.10.
I’m also having exactly this issue. The Chaperone bounds lag a centimeter or two behind geometry. Causes an unpleasant swimmy effect when the chaperone is visible.
As you say, deleting the player camera fixes it.
Found this other question which has a code solution…
If you implement the camera the old way like this the chaperon is locked solid to the world and everything is okay. However, if you implement it the new way that was recommended for 4.11 the chaperon lags behind the world noticeably.
The new 4.11 method is far more convenient and powerful, but unfortunately while the world is running great I find the bounds sloshing about to be very nauseating.
The symptom is very similar to buffered frames issue Springularity mentioned. However, the code was modified in 4.11 just as ChadTaylor said so the source is probably something else.
Ok, after further investigation. I now cannot use the camera attached to my VR character to get location or rotation of the HMD if I turn off “Auto Manage Active Camera Target.” So not a perfect fix. There a way round this?
…10. Select the Player Start and position it so that the center of the Player Start is just above the Static Mesh used for the ground. In this example we used a Z height of 1.0 CM for the Player Start.
Ran into the same issue with this flag set. While the player pawn seems to spawn in the same orientation, the camera is rotated (in my case it was 90 degrees counter clockwise).
You can rotate the player start entity so that the camera and pawn align, but it’s not a good fix. It looks like if you use the Auto Manage Camera flag you don’t use the pawns camera, but the camera from the controllers camera manager which has a separate rotation from the pawn.
In the meantime i spent some more time with this issue. I had the best result with removing the camera. Yes you heard correctly. Remove the camera from the pawn and you will still have lag free images in your HMD.
The world is locked solid again!
