Brightness and saturation shift when losing positional tracking, DK2

onesungmirror

O
I noticed when the camera loses positional tracking, elite gets displayed with less saturation and brighter than normal.
Since at the moment I lose pos-tracking every few seconds but only for the fraction of a second I get regular flashes while playing (in the image ;) ).
I wouldn't notice the tracking dropouts if it weren't for display issue. Is this coming from the rift or from ED? Can I turn it off?
 

saviornt

saviornt
elkar said:
And I thought its the feature to let you know you are out of tracking zone.
Click to expand...

The game does this when it is not detecting that there is positional tracking. This can happen when you move outside the frustum of the camera or when the tracker resets the Vision Latency. This is what is causing the effect.

You could also try setting the OVRServer CPU affinity so that it can only use 1 cpu. That might work in theory.
 
Last edited:

onesungmirror

O
saviornt said:
The game does this when it is not detecting that there is positional tracking. This can happen when you move outside the frustum of the camera or when the tracker resets the Vision Latency. This is what is causing the effect.

You could also try setting the OVRServer CPU affinity so that it can only use 1 cpu. That might work in theory.
Click to expand...

Yeah, the frustrum detection is clear to me. The thing is, I never leave the frustrum and I get dropouts even if I hold my head very still. They always come in pairs about a half second apart. and only for a fraction of a second. It feels like some other process is interfering, maybe also core switching or whatever one may call it. So setting the core affinity seems a good idea, I'll try it. As I said I'm playing on an amd fx8350 so the hyperthreading option some other people have doesn't apply, but maybe the issue is the same.

Thanks for the tip.

Edit: Setting CPU affinity didn't help. I only found while playing with affinity combinations for the or server and the elite process, that it is possible to decrease tracking performance massively by restricting the elite process to one core ;).
I'm still looking for a way to disable the color/brightness shift because this is much more noticeable than the tiny tracking dropouts.
 
Last edited:

Apec Valorian

Apec Valorian
onesungmirror said:
Since at the moment I lose pos-tracking every few seconds but only for the fraction of a second I get regular flashes while playing (in the image ;) ).
Click to expand...

This had been bugging me, too, until I read somewhere that it might be caused by a hyperthreading-related feature called "core parking". Ever since I've effectively disabled core parking on my machine I'm fine. If you can read German, this link might be helpful: http://www.heise.de/ct/hotline/Bitte-nicht-parken-1100682.html
 

saviornt

saviornt
Thanks for testing that and coming back to state your results, much appreciated. About "core parking", in my VR settings thread, I have the two settings in there to disable core parking. One is through the power management settings and the other is a registry edit change. For me though, that didn't "solve" the positional tracking reset; or perhaps, it could have been caused by both the HT and core parking. I disabled HT after I disabled core parking.
 

onesungmirror

O
Again, I'm not using an intel processor.
Today I tested a few other demos, which are of course mostly for direct mode and none ad them had tracking issues as far as I could notice. Of course they don't flash when losing track but there also is almost never a studder or judder. I think the whole problem is indeed performance related which is not optimized in elite. There is much more to it than the power of the graphics card! I think with some optimization one could get very smooth headtracking and framerates even with card a bit below specs.
I also noticed that reducing quality settings may result in higher framerates but not in less studder, because tracking seems not to be computed by the card entirely (I may be wrong here) but mostly on the cpu which is why cpu settings have more effect than quality settings. Sadly I don't have much options with my amd. I only have one intel I7 which is my workstation and the gtx 970 is needs to many slots for it. I will try the oculus on this system anyway if I have time but only with a gtx 760.
 

JMC002

J
I don't know about losing positional tracking but I know that one potential cause of judder when using the Rift in extended mode is your primary display being set to a different refresh rate than the Rift.
 

onesungmirror

O
JMC002 said:
I don't know about losing positional tracking but I know that one potential cause of judder when using the Rift in extended mode is your primary display being set to a different refresh rate than the Rift.
Click to expand...

But that should be the case for all rift enabled demos and products the, shouldn't it?
 

grodenglaive

grodenglaive
Some users with that tracking issue have reported faulty USB cable on camera. Another post I recall someone reinstalled the oculus drivers (not just the runtime) to fix that.
 

onesungmirror

O
atlas974 said:
@OP try setting high priority for OVRServer_.exe
Click to expand...

Good idea, thanks, I'll also check the cable.

Still if there was an option to turn off the visual warning it would do as well because the jerking and lags from elite istelf are much worse than the dropouts which I could perfectly live with if it wasn't for the flashing. ;)


Edit: I played with the process priority and found that only setting it to "realtime" reduces the positional dropouts. They are not gone but not as frequent as before.
 
Last edited:

onesungmirror

O
Sorry to bump that up again but I want to add something I noticed just today. I accidentally started ED in direct mode which is capped at 37 fps for some reasons. The funny thing is I have not more or less tracking dropouts rotational and positional that with 75 fps. The tracking error have nothing to do with the graphics performance.
 

Malic

Malic
If you have any bright lights in your room or the sun shining through a window they might be interfering with the Rifts IR lights that light up for positional tracking, and give false readings, which default to "being out of view".

View attachment 4962
 

onesungmirror

O
Malic said:
If you have any bright lights in your room or the sun shining through a window they might be interfering with the Rifts IR lights that light up for positional tracking, and give false readings, which default to "being out of view".

View attachment 4962
Click to expand...

I haven't. I'm playing in a dark room. Even when I'm staring at the rotationg ship I get those two annoying flashes. I am certain this is another process interfering but even with any background application, virusscanner off, orserver process set to realtime I can only improve it, not get rid of it. I'm also certain the number of objects in my environment have an influence like a ship showing up in SC seem to be accompanied by tracking flashes for a short time. I wish there was a setting that would simply turn the effect off.
 
Last edited:

Zulubear

Zulubear
I don't know if you've tried this already, but I had a similar issue with my setup. I found that moving the tracking camera connector from a USB3 port to a USB2 port stopped the flashing for me. I think this might have been posted elsewhere on this forum.
 
You must log in or register to reply here.
Back
Top Bottom