Screen Jumping

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!!!!
 
Last edited:
I've never got this. When it jumps, it jumps once. This is very unlikely to be an ED thing. I know you probably haven't changed anything on your rig, but you never know if things have changed by themselves.

It's very likely related to the HMD camera in some way. Either it's connection is a bit loose, the cables are being knocked by your feet, the power source it gets is developing a fault of some kind. Fiddle around :)
 

SlackR

Banned
Had this occur periodically... A restart of the game and drivers always fixes it :)
 
Last edited:
I've never got this. When it jumps, it jumps once. This is very unlikely to be an ED thing. I know you probably haven't changed anything on your rig, but you never know if things have changed by themselves.

It's very likely related to the HMD camera in some way. Either it's connection is a bit loose, the cables are being knocked by your feet, the power source it gets is developing a fault of some kind. Fiddle around :)

Oh no - I'm not the only one suffering from this issue.. I have read about others.
 
i get this problem lately,
i need to unplug the oculus ir cam and rteplug and it resets it for me, it works most of the time
 
I reported this as a bug. I think you are explaining the same thing as I have...the view will stutter jump behind the chair for a small period of time and then calm down.
 
does it flicker back and forth between 2 positions or is it like the camera is 'zooming' in and out trying to get a fix on your head? Or is it something else
 
It almost has a bounce like effect - like the image is bouncing ever so slightly up and down. Kind of how I image your head would move while in a Saturn V rocket during launch. Except my head is perfectly still. It's 100% a tracking issue in Elite - it's the only game that does this so no it's not hardware related. It also did it on my old rig, but as of late the problem seems more frequent to me.
 
OK, I think I have had this issue as well. When the screen is 'jumping', does putting your hands in front of the Oculus to block the IR emitters from the camera for a moment fix it temporarily?

For me, I think this problem was resolved by attaching the Oculus camera to a powered USB hub.
 
I had similar problems several times. I sorted it the most obvious by closing the door of my gaming room so the cat cannot jump in the desk between the camera an me and shake the monitor and the camera, and then, secondly I pushed forward all cables on the ground I was touching with my feet (small short circuit somewhere), and then I plugged the camera in an USB 3.0 port. Each of those steps fixed the "jump" problem. I still have from time to time (let's say one per hour) a jump and the colors changes saying I lose the tracking during a short period (less than half a second) but I'm pretty sure this is ED and/or SDK and/or computer related, when a thread or a software are too busy and grab too much cpu time to let the camera thread or drivers enough time to compute its values (it should probably run real time without any cut in frequency). The specs for CV1 say explicitly than the new Constellation tracking camera should be plugged in a USB 3.0 port, probably to ensure a good bandwidth without noticeable interruption, so I guess they improved this part.
 
Hey Steves, for some reason this problem seems to go away when you connect the camera to a powered usb HUB, with external power not supplied by your computer. I don't know why, nobody else seems to either, but this does in fact seem to magically resolve several headtracking issues. Could be a Windows USB issue, could be some kind of issue with the hardware.
 
Hey Steves, for some reason this problem seems to go away when you connect the camera to a powered usb HUB, with external power not supplied by your computer. I don't know why, nobody else seems to either, but this does in fact seem to magically resolve several headtracking issues. Could be a Windows USB issue, could be some kind of issue with the hardware.
You are always supposed to run the DK2 off a powered USB2 hub
 
So it looks like a few of us have this issue. Some say adding a powered USB hub resolves it, others say not. Personally my view is that the issue is with Elite and its DK2 implementation and not USB ports on PC's or any other hardware - if it were USB port related then every DK2 compatible game I own would do the same and simply put, they don't, only Elite does.

So... are the devs aware of this, is there a ticket open? If not, I'm happy to open one.
 
Last edited:
who knows... I do know that it is commonly documented that the rift has a higher power demand than what can typically be supplied by two motherboard mounted USB ports... so you can potentially experience all kinds off issues. Running on a powered port is just something to put in place ahead of all others, so you know you're getting plenty of juice to the unit, and so you don't waste your time troubleshooting to the end of earth, only to find out it was a power issue. I think they are $12 on amazon.
 
This is something that only happened after the last patch and/or because of updating to the 0.5 beta runtime
 
Last edited:
it also spontaneously happened to me all of a sudden one day and never went away until I put the camera on a powered usb hub. I also did not believe that would resolve the problem. It did.
 
Back
Top Bottom