Or use the manual DSR. Much less performance hit
Getting the Best DK2/CV1/Vive VR Experience: Guide/Compendium
- Thread starter drkaii
- Start date
Or use the manual DSR. Much less performance hit
I can't REP because I have less than 3 posts it seems.
Most of the settings in the first page helped. (although I'm not sure if the OP recommended setting AA to off if we complete Step 2?)
I still get cockpit stutter in space stations and sometimes in FSD when near a sun but sometimes no stutter even near a sun so I don't really know.
In battles or normal space I hardly ever get stutter so that's nice.
My GPU usage according to MSI Afterburner is only about 60% and my CPU usage according to System Resources is 80% Core 0 and Core 7 (CPU is i7) but about 20% on all other cores - they are all unparked. The utility Process Lasso (https://bitsum.com/parkcontrol/) helps unpark all CPUs each time you start a game it seems.
So I don't know why the stutter is happening, its the single thing that makes people dizzy when using the Oculus Rift. Graphic settings according to this guide https://forums.frontier.co.uk/showthread.php?t=76013 and there is also another thread with people submitting their experiences but I couldn't find it today. I've set the resource hogs to as minimal as can be.
Anyone know how to display FPS while using the OR DK2?
Most of the settings in the first page helped. (although I'm not sure if the OP recommended setting AA to off if we complete Step 2?)
I still get cockpit stutter in space stations and sometimes in FSD when near a sun but sometimes no stutter even near a sun so I don't really know.
In battles or normal space I hardly ever get stutter so that's nice.
My GPU usage according to MSI Afterburner is only about 60% and my CPU usage according to System Resources is 80% Core 0 and Core 7 (CPU is i7) but about 20% on all other cores - they are all unparked. The utility Process Lasso (https://bitsum.com/parkcontrol/) helps unpark all CPUs each time you start a game it seems.
So I don't know why the stutter is happening, its the single thing that makes people dizzy when using the Oculus Rift. Graphic settings according to this guide https://forums.frontier.co.uk/showthread.php?t=76013 and there is also another thread with people submitting their experiences but I couldn't find it today. I've set the resource hogs to as minimal as can be.
Anyone know how to display FPS while using the OR DK2?
You can't display them using the DK2 (at least, in a way that's visible). Only way is to mirror the display but that in itself reduces the fps..
There are quite a few bugs related to stutter. It's to do with things loading, other ships, planets rendering, the game starting, randomness. The devs are aware and working on it
Quite straightforward with Riva Statistics Server (comes with Afterburner - may also be available separately), just need to target the correct display and fiddle around with the position of the text a bit to make it visible. You will also need to set the desired metrics for on-screen display in Afterburner.
I've got FPS and GPU utilisation showing on the rift, top centre. That way it doesn't interfere too much with normal gameplay but a quick glance up gives you the info that you need.
Right at this moment I wouldn't recommend upgrading to Windows 10. I have everything working but for some reason I can't reset orientation. Using 0.5.0.1 SDK and the latest nvidia drivers. I have tried re-installing the SDK and rebinding the key but its still not working.
E D has some odd performance issues (e.g. changing settings without restarting the game makes performance worse) so it's really hard to say if it performs better on 10 vs 8.1 but I can say that it is definitely way better than the last time I played with the same exact settings.
E D has some odd performance issues (e.g. changing settings without restarting the game makes performance worse) so it's really hard to say if it performs better on 10 vs 8.1 but I can say that it is definitely way better than the last time I played with the same exact settings.
Last edited:
This actually worked, got the FPS to display within the Rift.
Unfortunately it is only one eye.. i.e. the FPS is only displayed on the left screen not both so it is a little of an annoyance.
Secondly, the toggle key to turn it off doesn't seem to work. Does it work for you? The toggle-key is set in MSI Afterburner settings right? I set it to / but nothing ever happens. Or is there a way to set the toggle on Riva Statistics Tuner itself?
- - - Updated - - -
Did you say that playing it on Win 10 felt like a better experience than Win 8? And you are only disrecommending win10 because of the inability to reset orientation?
Windows 10 is a MASSIVE improvement, and the orientation is specific to just Deimos-GOW, I didn't have it. See this thread:
https://forums.frontier.co.uk/showthread.php?t=171061
It especially improves the alt-tab to being as good as borderless. That I love the most!
Last edited:
What I was saying was, I can't recommend it yet. The last time I played on Win 8.1 I was suffering some unusual performance issues and lag. I had a brief test on Win 10, apart from orientation reset it was definitely better than the last time I played on Win 8.1.
As masCh said, this is only affecting me, I'm still working on it, reinstalled Win 10 clean yesterday (and had a major malfunction installing the Oculus SDK). I'm withholding final judgement until I can test it on my current instal, will update when I have done so.
As masCh said, this is only affecting me, I'm still working on it, reinstalled Win 10 clean yesterday (and had a major malfunction installing the Oculus SDK). I'm withholding final judgement until I can test it on my current instal, will update when I have done so.
I hadn't noticed that the info only appears in one eye - mine seems to work without issue.
Also, I don't use the toggle - it just sits there outside of my typical FoV so I don't find it distracting.
If I ever get a chance to play again, I'll have a look to see whether I get the same issue! If not, I'll post my settings here.
^^ this is what i do. Mine is set to roughly 200 x 200 (nvidia statistics server) So the fps and gpu usage sits at the top centre of my dk2 field of fov. I have to really look up to see it so dont notice it really in normal play.
Im sure mine is seen in both eyes but ill check next time i load up elite
Last edited:
i think i do that by going into nvidia control panel yeah? Im having trouble even opening this at the moment! Will try the latest Nvidia drivers see if that helps
Managed to get on for an hour last night after spending 30 minutes messing about with new drivers then head tracking issues(!).
Can confirm that the Riva output is only displayed for the left eye - as I said, I've never noticed this before and even now don't see it as a problem - do you habitually play with one eye closed?
Are you perhaps taking the role-play side of being a pirate too seriously?? Eye patches are optional!!
Didn't get a chance to try the on/off toggle, unfortunately.
I need to narrow this down. I figured out that the oculus view reset is working but ONLY if I use CTRL+F12 on the keyboard. Rebinding the control to anything else will not work. The change is registered but it doesn't function while CTRL+F12 still works. The oddest thing is that creating a macro on my X55 doesn't work even though ED registers the keypress, it just ignores it.
Can anyone else confirm this? or is it just me?
Can anyone else confirm this? or is it just me?
Last edited:
Extremely baffling! Only place I'd start (although this doesn't explain the macro issue??) is look at what happens when you bind it in game. Does it show only the keys you selected or do you get some random crap in there too?
That random crap often crops up, probably associated with other software dealing with the peripherals, and once it does you can often lose the keys or even the whole config
Perhaps I can explain it better. CTRL+F12 ALWAYS works. editing the binding SHOWS the change (for example, just F12, or ANY OTHER KEY INCLUDING buttons on the X55 instead of CTRL+F12) but the new binding will not work.
Oh so even when you rebind CTRL-F12 itself to something else, it doesn't pick up?
Sounds like file corruption most foul! Validate and if necessary reinstall ED!
I played for a good few hours last night and my conclusion is that, in my particular situation (which is by no means unique) Windows 10 is currently a bad idea and I can't recommend upgrading yet. I am considering going back to Windows 8.1 even though I hate that OS with a vengeance, Windows 10 just isn't ready yet.
My specs are below. I think my main issue is the X55. The stick exhibits some serious issues under Windows 10 which make it difficult to fully enjoy ED and I'm pretty sure my X55 is causing some serious judder, I had a couple of bouts of severe judder and loss of framerate. The reason I think it was caused by the X55 is because at the same time this was happening I was getting random keypresses and my throttle was going haywire. If I mashed buttons it would come right after a few seconds.
Apart from the issues I did notice a difference in my experience between the two operating systems. In windows 10 I was able to run high instead of medium to low while inside a space station. While outside there was literally no judder when planetary bodies were loaded in to view but Windows 8.1 was a mixed bad, sometimes judder, sometimes none.
So the question remains, how long will it take for Saitek to come to the party? twitter says "working on it" so time will tell.
My specs are below. I think my main issue is the X55. The stick exhibits some serious issues under Windows 10 which make it difficult to fully enjoy ED and I'm pretty sure my X55 is causing some serious judder, I had a couple of bouts of severe judder and loss of framerate. The reason I think it was caused by the X55 is because at the same time this was happening I was getting random keypresses and my throttle was going haywire. If I mashed buttons it would come right after a few seconds.
Apart from the issues I did notice a difference in my experience between the two operating systems. In windows 10 I was able to run high instead of medium to low while inside a space station. While outside there was literally no judder when planetary bodies were loaded in to view but Windows 8.1 was a mixed bad, sometimes judder, sometimes none.
So the question remains, how long will it take for Saitek to come to the party? twitter says "working on it" so time will tell.
I'd just like to report something I have found.
I have been playing the game with 95-105 FPS according to MSI Afterburner.
It was juddering quite a bit.
The game wouldn't let me adjust vsync from within the game.
So I went into Nvidia and set the Adaptive VSYNC (as in the OP) to VSYNC (normal).
This keeps the frame rate at 75 fps, and all judder is gone!
Only when the FPS drops below 70 again due to lots of things going on in the screen that it can start to judder again.
If you keep your graphics settings low so that it never falls below 71 fps, you won't feel the judder at all.
Now I'm happily Supercruising with no judder in the cockpit!
TL;DR.. the judder on the DK2 is not only due to low FPS, but also due to high FPS. Keep it very close to 75 fps and you won't have any judder.
(if there was a way to set : adaptive vsync for < 75 fps and vsync On for >75 fps, that would be great)
I have been playing the game with 95-105 FPS according to MSI Afterburner.
It was juddering quite a bit.
The game wouldn't let me adjust vsync from within the game.
So I went into Nvidia and set the Adaptive VSYNC (as in the OP) to VSYNC (normal).
This keeps the frame rate at 75 fps, and all judder is gone!
Only when the FPS drops below 70 again due to lots of things going on in the screen that it can start to judder again.
If you keep your graphics settings low so that it never falls below 71 fps, you won't feel the judder at all.
Now I'm happily Supercruising with no judder in the cockpit!
TL;DR.. the judder on the DK2 is not only due to low FPS, but also due to high FPS. Keep it very close to 75 fps and you won't have any judder.
(if there was a way to set : adaptive vsync for < 75 fps and vsync On for >75 fps, that would be great)
During my tests I found that vsync is locked on by the game if using an oculus, the only way to override this is to disable it in the display driver (force off). I also concur with masCh, vsync set simply to on or application controlled provides the best experience, adaptive is worse than just on.