I’m still trying to figure this out, and not getting anywhere.
I thought maybe there was an issue with getting camera world location in a VR project, because after all there are effectively two cameras in VR rendering (one for each eye) so maybe that was confusing things (and might have explained the weird issue with two cones being drawn). So I tried the same setup as above but using the HMD position (from Input -> HMD -> Get Orientation and Position) as the ‘look at’ position for the cone. Exactly the same issues: (1) the same significant lag, and (2) the cone is being drawn twice pointing in two different directions, rather than just once pointing straight at the HMD.
I’ve noticed a few other posts asking about what seem to be similar things, for example:
Attaching HMD Camera to an animated actor (aircraft cockpit) without lag or jitter (Vive)
Camera lag/stutter - how to fix?
UE4 VR Devs : BEWARE
But there doesn’t seem to be any answers. These issues are completely freezing my development, as my project relies on being able to get an accurate position of either the HMD or the midpoint between the two eyes of the VR cameras. This seems like it should be a relatively simple ask, so what is the problem here?
Would really appreciate if someone (perhaps even one of the UE4 devs) could take the time to explain what’s going on here, and how to get an accurate read of the HMD/camera location. Thanks!