Using a gamepad to control the cursor
Ah thanks. Did you have to set anything up in the config menu?
So I think after much discussion with other users, the reason for the massive FPS drop I am seeing (to recap, 35fps at 1080p on a DK1, whilst sitting on pad in station) may be down to my 2500k only having 4 physical cores and no HT (Hyper Threading).
It is unusual for games to make use of HT, which is why there is virtually no difference between 2500k vs 2600k or greater in 99.9% of games, when they are clocked at the same speed, however in the case of Elite, this seems to break that trend.
It seems that most other users who are also experiencing this kind of performance are also on 2500K CPU's or similar CPU's that do not offer Hyper Threading.
It looks like having 2 threads per physical core (so 4x2 = 8 threads in total) is making a MASSIVE difference to performance in Elite Dangerous, espeically when using a DK1 and around stations in particular.
Anyone who can back up this theory by testing (ie disabling HT on their CPU)?
So I think after much discussion with other users, the reason for the massive FPS drop I am seeing (to recap, 35fps at 1080p on a DK1, whilst sitting on pad in station) may be down to my 2500k only having 4 physical cores and no HT (Hyper Threading).
It is unusual for games to make use of HT, which is why there is virtually no difference between 2500k vs 2600k or greater in 99.9% of games, when they are clocked at the same speed, however in the case of Elite, this seems to break that trend.
It seems that most other users who are also experiencing this kind of performance are also on 2500K CPU's or similar CPU's that do not offer Hyper Threading.
It looks like having 2 threads per physical core (so 4x2 = 8 threads in total) is making a MASSIVE difference to performance in Elite Dangerous, espeically when using a DK1 and around stations in particular.
Anyone who can back up this theory by testing (ie disabling HT on their CPU)?
I am currently getting my DK2 to work in the game by terminating the processes etc, as earlier outlined, but it still seems somewhat blurry (outside the cockpit) and jerky. I get the feeling that it needs to be adjusted i.e. config utility and whatnot.
Do we have any idea when ED will be patching us so that the DK2 works with the utility, (sorry I know it's a bad question) or will they be installing some settings to enable us to tune the ipd etc in game?
I'm sorry to ask, but I just can't read all the 161 pages of this thread for the info. Perhaps someone would be patient enough to answer a couple of questions for me:
I am currently getting my DK2 to work in the game by terminating the processes etc, as earlier outlined, but it still seems somewhat blurry (outside the cockpit) and jerky. I get the feeling that it needs to be adjusted i.e. config utility and whatnot.
Do we have any idea when ED will be patching us so that the DK2 works with the utility, (sorry I know it's a bad question) or will they be installing some settings to enable us to tune the ipd etc in game?
thanks![]()
Apparently there are issues with the SDK that need to be resolved with Oculus before E: D can fully support it. They're on the case, and it'll happen when it happens... we just have to wait.
In the meantime, if you have it working, you might want to try the supersampling trick to see if that makes things less blurry for you.
make sure you have allot of headroom on your gpu if you want to try down sampling. Trying to render ED at 1440p downsampled to 1080p in rift mode ripped my GTX770 a new one.
http://www.neogaf.com/forum/showthread.php?t=509076
That is a good guide on how to do it.
March 19, 2014 at 05:45 PM PDT
Received email just under 2 hours ago (at 14:05 PDT) saying my card was billed; my status is now Processing. Looks like I just missed out in the previous batch with my order date/time.