The solution to this problem is to change the DCS VR code so that no uncommanded realignment of the two coordinate systems is performed. This is easily confirmed by moving away from the normal player position to reposition the VR headset as close as possible to, which looks pretty much like a normal cockpit perspective again: Therefore, one would assume that the head position in DCS should be roughly where it was before the intermittent tracking loss.īut this is not the case, because DCS has realigned the two coordinate systems so that =, which makes no sense, because there is no reason to assume that the headset coordinate system has changed.
When the position tracking is later reestablished by the headset, the headset starts reporting valid coordinates again:Īs it can be seen in the picture, the coordinates are again very close to the ones that were reported before the position tracking was lost intermittently. Then, whenever the position tracking is lost, the headset stops reporting any (valid) coordinates. Here is a picture of the initial position in the cockpit, with VR coordinates : These coordinates are aligned to when everything is working properly (in other words, = ). In my case, the VR coordinates for my normal head position in the cockpit are roughly. This is also essentially what the "View - Recenter VR headset" function does. For a normal cockpit view in VR, whatever coordinates the VR headset is reporting when the player's head is in its normal position must be aligned with the game coordinates. Let's call the head position coordinates in the game world and the VR coordinates, and let's assume that the normal head position in the cockpit is at coordinates. There are two sets of coordinates, one in the game world and one that is reported by the VR headset. In both cases, the position tracking is lost intermittently and later reestablished, and the effect on the head position in the cockpit is the same. I could reproduce the same problem that I had with intermittent tracking problems by taking the headset off, waiting for it to reset itself, and then putting it on again.
Tl dr: The problem is caused by an uncommanded realignment of coordinate systems by DCS, explanation below. I have attached a video capture of what the problem looks like. I tried "recenter VR headset", resetting the camera position, saving the cockpit angles, and a few other view-related things, but all to no avail. I first encountered this problem a couple days ago, so it may be caused by one of the last updates. To rule out the possibilty that this is yet another problem of the extremely buggy Oculus drivers, I flew a turboprop around for over an hour in the same region in another flight simulator, but encountered no VR problems at all, so I am convinced that this bug is in the DCS VR code. On average, it happens every 10 minutes - sometimes it would happen twice per minute, sometimes it would work for 20 minutes before failing again. I tested this by resetting my position so that I would fly the aircraft from behind the seat (as if I were in a backseat). The position jump is not relative to the current head position, it is absolute, meaning that even if I intentionally reset my headset position so that I end up in a different position in the cockpit while flying, I still end up in the same location after the sudden jump. This seems to happen with all aircraft (so far, I have tested with the F-16 and the Su-33), and the location that it jumps to is the same every time, but is a different for each aircraft (e.g., into a forward-left position of the cockpit in the F-16, straight forward way in front of the HUD in the Su-33). Without any apparent reason, the head position suddenly jumps to a different and nonsensical location in the cockpit.
0 kommentar(er)
