So it's been happening to me for some time now - let me explain (as I'm sure others have).
I start the game, everything is fine, I run a good rig so I'm running Elite at 75FPS, I'm happy. Now, sometimes after mere minutes, sometimes an hour, perhaps longer my DK2 screen starts to jump, I think its a FPS drop, its not. The screen just jumps - only slightly - up and down, not your typical low FPS stutter but something else.
Once it's started it does not stop on its own - it will continue until I do one thing. Cover up the front of my DK2 by either looking away from the camera or covering the IR lights with my hands to obstruct them from the camera. After which my game returns to normal for - a few minutes, an hour, sometimes the rest of my play session.
This bug is becoming increasingly annoying, its not my hardware (my DK2 runs fine on everything else), sometimes it doesn't happen at all but then on some occasions it will happen time after time after time.
Does anyone else get this issue? Are the devs aware of it? I would have hoped with the newer SDK support this bug would have gone, last night it was still there and bugged the hell out of me!!!!
I start the game, everything is fine, I run a good rig so I'm running Elite at 75FPS, I'm happy. Now, sometimes after mere minutes, sometimes an hour, perhaps longer my DK2 screen starts to jump, I think its a FPS drop, its not. The screen just jumps - only slightly - up and down, not your typical low FPS stutter but something else.
Once it's started it does not stop on its own - it will continue until I do one thing. Cover up the front of my DK2 by either looking away from the camera or covering the IR lights with my hands to obstruct them from the camera. After which my game returns to normal for - a few minutes, an hour, sometimes the rest of my play session.
This bug is becoming increasingly annoying, its not my hardware (my DK2 runs fine on everything else), sometimes it doesn't happen at all but then on some occasions it will happen time after time after time.
Does anyone else get this issue? Are the devs aware of it? I would have hoped with the newer SDK support this bug would have gone, last night it was still there and bugged the hell out of me!!!!
Last edited: