Vision Latency Resets (Positional Tracking Lost) for split second - FIX!!

[saviornt]

So.. MarkD is the man! After his suggestion for another fix, I decided to disable hyperthreading, and oh my.. what a change that made.

Oddly enough, my framerate is consistent now, no juddering or lag, no positional tracking lost constantly. Everything is silky smooth, even with all settings on high (except AA)

 

[ButtonDeity]

So.. MarkD is the man! After his suggestion for another fix, I decided to disable hyperthreading, and oh my.. what a change that made.

Oddly enough, my framerate is consistent now, now juddering or lag, no positional tracking lost constantly. Everything is silky smooth, even with all settings on high (except AA)

how is this done?

 

[saviornt]

Through your bios settings.

 

[Sanderson]

I'll have to try this tomorrow.

 

[Mark D]

So.. MarkD is the man! .....

Cheers man, that's made my day and it's only 8am. Lol however I can't really take any credit as until you told me yesterday - I didn't know what 'vision latency changes' even meant

Just to manage others expectations who see this thread and hope it might solve misc issues. I've only seen this problem with my rig so it could be specific to any combination of my setup.

The history is : I've always been very lucky with ED2 / DK2 being stable. Early on I took the advice of the more experienced forum users on here and aimed for a steady 75 fps in stations etc. The only way my Nvidia GTX 770 could do this was by choosing the preset LOW and turning down the Oculus quality slider. For me this made text hard to read (physically hurt my eyes).

Others with the same card were running on high so before upgrading I wandered if my PC had a setup issue. ED Beta 2.x Eagle, Windows 7, Intel I7 920 OC, DK2 (direct mode), Nvidia GTX 770 OC.

Most elements were over clocked so I considered if my CPU was bottle necking. My limited understanding is with a quad core processor like mine it had 4 physical cores. By turning on Hyper threading (took 2 mins in BIOS settings on PC boot) in windows task manager this jumped to 8. As a direct result my benchmark 3Dmark 11 went through the roof. However ED became unusable with a regular white pulse/flash effect so I turned it off again. For me personally the solution was an upgrade to a GTX 970. I still only use preset LOW but with the Oculus quality on full I find the game very playable (doesn't hurt my eyes).

 

[ket halpak]

So.. MarkD is the man! After his suggestion for another fix, I decided to disable hyperthreading, and oh my.. what a change that made.

Oddly enough, my framerate is consistent now, no juddering or lag, no positional tracking lost constantly. Everything is silky smooth, even with all settings on high (except AA)

OMFG so much man love for you right now, my rift is buttery smooth on high settings!!!!

 

[Ryder35]

So are people implying that this solves the stuttering in SC as well? If so it should be posted in that thread. I'm gonna give it a try tonight as I also get loss of tracking but usually it is when the game stutters in SC.

 

[the_wretched]

Great to hear HT off fixed your problems, we should really collect all these valuable tips somewhere for people having problems in a sticky!

I find the last few patches and Gamma helped immensely with performance in general and the SC stuttering (which is very minimal for me now, much better than early Beta 3). And even with the fixed rendering bug from 1.01 (which gave me hugely increased frmarate) I can still have pretty much everything on high (except shadows on medium) with my 970 (perviously had to have many settings on low to maintain 75fps in stations).

 

[jumbobreakfast]

I'll have to try this but I really shouldn't have to disable HT. My experience with Gamma 1.0 was great, I could set graphics at Mid and had very few problems. 1.01 was broken so I didnt play Elite but 1.02 has brought back many of the same problems that I had in some versions of the betas. I now use Low settings and still get image doubling in stations and super cruise is doing that horrible micro-second stalling when planets pop into view. I thought it might have been due to the telemetry logging that was added in 1.02 so I didnt raise a ticket.

There is too much guesswork going on here so it would be nice to get some guidance from Frontier on how to optimise. it would be nice to know:
Details about telemetry logging - Does this impact performance? (just so we know)
Which settings cost the most - shadows, AA...?
On first run of Gamma, what does the "autodetect" do - does it just decide on Low, Mid and High or does it modify other non-graphical settings? Can we trigger this to run again?
Will rift direct mode make a big difference once Oculus improve the SDK?
Is image doubling related to network problems?

i7 4770k, 780GTX (clean nvidia driver install last night didnt help)

 

[Smack332]

Cheers man, that's made my day and it's only 8am. Lol however I can't really take any credit as until you told me yesterday - I didn't know what 'vision latency changes' even meant

Just to manage others expectations who see this thread and hope it might solve misc issues. I've only seen this problem with my rig so it could be specific to any combination of my setup.

The history is : I've always been very lucky with ED2 / DK2 being stable. Early on I took the advice of the more experienced forum users on here and aimed for a steady 75 fps in stations etc. The only way my Nvidia GTX 770 could do this was by choosing the preset LOW and turning down the Oculus quality slider. For me this made text hard to read (physically hurt my eyes).

Others with the same card were running on high so before upgrading I wandered if my PC had a setup issue. ED Beta 2.x Eagle, Windows 7, Intel I7 920 OC, DK2 (direct mode), Nvidia GTX 770 OC.

Most elements were over clocked so I considered if my CPU was bottle necking. My limited understanding is with a quad core processor like mine it had 4 physical cores. By turning on Hyper threading (took 2 mins in BIOS settings on PC boot) in windows task manager this jumped to 8. As a direct result my benchmark 3Dmark 11 went through the roof. However ED became unusable with a regular white pulse/flash effect so I turned it off again. For me personally the solution was an upgrade to a GTX 970. I still only use preset LOW but with the Oculus quality on full I find the game very playable (doesn't hurt my eyes).

Are you not able to go above low with the 970? I have the same card with everything on high and SMAA. Steady at 75 fps except a (very) few times inside stations. My CPU is an I5 3570K@4.2. I realize that mileage will vary, but I'd think you could do better than low settings. If it'll help, these are my Nvidia CP settings (in Norwegian, but you should be able to figure it out ):

View attachment 2858
View attachment 2859

 

[Il_Kildeer]

Hi,

it is not necessary to disable HT. The problem occurs, because Win7 is set up to use core parking for HT cores.

This can easily disabled without rebooting.

Open regedit and find the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\0cc5b647-c1df-4637-891a-dec35c318583

then change the parameter "Attributes" from 1 to 0.


this exposes the core parking management in the power plan settings. Then you can control it on the fly without rebooting. Change it to 100% to disable core parking.

 

[Phier]

You know I turned off core parking ages ago for another game. I wonder if thats why I'm one of those lucky "no issues" players.

 

[mickeeie mouse]

You know I turned off core parking ages ago for another game. I wonder if thats why I'm one of those lucky "no issues" players.

same here brother, core parking went waaay back on BF 3 i think it was now hahaaa, and elite has always been good for me in the rift

happydays, glad yall gota fix for this

MM