"Imeleon" wrote:
I use a 2dof motion sim with the dk2 and I don't have any issues with that at all. I can crank the motion right up and it all stays smooth. I don't though as you only need smaller movements in vr. I did turn the bump simulation down a bit as it shook the screen too much.
I've been dk2 and motion driving in iracing for months now.
Well, I can easily provoke a really clear stutter by simply moving the camera and Rift in 1-DoF. I made the following simple setup, where I fixed both the Rift and camera to a wooden board (the blue thing to the right is a inertial sensor):
When I exerted some simple yaw motions (rotating the board back and forth) and logged the orientation from the Oculus SDK. If I plot the yaw signal I get the following:
Note, since the camera and Rift are fixed on the board the yaw signal should be zero. . And we can clearly see when the camera decides to correct for error in estimated yaw angle.
But I have found a solution that works decently. Since I know the external inertial forces I can compensate for the in my draw loop. I integrate the external inertial forces and subtract the external rotations from the orientation signal from the rift. This integrated signal will grow in the same rate as the error from the Rift SDK. This works well until the camera does its corrections. This correction can be detected by looking at the derivative of the angle from the Rift SDK. When I detect a camera correction I reset the integrator, since we can assume that the Rift camera has eliminated the error build up.
This strategy works surprisingly well, although I have to disable "Time-warp", since the time warp algorithm does its calculations inside the SDK and is unaware of the data from my correction algorithm.
