03-29-2017 03:00 AM
03-31-2017 09:56 PM
04-01-2017 12:46 AM
04-01-2017 02:33 AM
04-01-2017 06:46 AM
04-01-2017 08:30 AM
rkodey said:
I'm also having tracking issues after the update, in Elite Dangerous. But not all the time... In areas of lower CPU utilization, tracking is solid. But, going into a conflict zone where CPU increases noticeably, that's when the tracking issues started. As soon as I left the CZ, the CPU usage dropped again, and the tracking was solid again.
So... smooth tracking somehow bound to CPU?
(I have a 6700k @ 4.4Ghz, GTX 1080, so plenty of horsepower.)
04-02-2017 04:23 AM
04-02-2017 07:24 AM
davastatin_dave said:
Seeing the exact same issues in elite dangerous since the update, doesn't manifest itself in much else that is super obvious, I'm running 2 sensors however so not sure if related but the "bounce" and "grey out" in ED that indicates loss of tracking are exactly what I'm experiencing. Wish I could easily roll back, 1.12 was perfect.
04-02-2017 08:17 AM
04-02-2017 01:24 PM
04-03-2017 06:54 AM
rkodey said:
I think I found a temporary solution that works for me (so far): process affinity.
I restricted "EliteDangerous64.exe" to cores 1-6, and "OVRServer_x64.exe" to cores 7-8. After that, the tracking problems disappeared in my first test! I'll try a couple more test runs today to make sure it remains stable. But, thought I'd throw this idea up to see if it helps anyone else.
Note: I'm running 1 sensor.