56mm is smaller than 70mm is big. The average is 64mm I believe (mine is 63.5)
ED and the Oculus Rift Developers Kit 2 (DK2) Discussion Thread
SlackR
Banned
That is not a DK2 issue its a mouse boundary issue... And should be fixed in the next ED patch. Basically your mouse is getting clicked outside the border of the fame and is effectively mimizing the game. The current workaround I use is to navigate the map with a gamepad.
Yeah, you can't effectively click anything with the mouse anyway as neither eye lines up on where the cursor is clicking.
I mapped all the galaxy map to the HOTAS but if you have a 360 pad lying around you can have that close to hand just for map as it works well, too.
I mapped all the galaxy map to the HOTAS but if you have a 360 pad lying around you can have that close to hand just for map as it works well, too.
Just used that link above to measure my IPD (I do wonder if that site is there to get people's CVVs from their credit cards
I came up with an IPD of 56mm. Quite a difference from your 70. Am I going to have problems from having a small IPD (if 56 is small?!?).
You might do. The problem I'm having with the DK2 is that the lenses seem to only have a very small area in the center of them that's clear, everything else is blurry. In fact, If I keep my head still and glance down at my radar, it's one blurry mess.
Apparently the DK1's lenses weren't as bad, and the hope is that the CV1 will allow you to set the width of the lenses as well as the depth (moving it closer, further away from your eyes). I'm waiting to see if anything can be done, because I love flying inside the rift. But it's just too painful right now, and I don;t want to potato up my vision permanently.
Last edited by a moderator:
Actually you can select with a mouse (within the window boundary) but to do it, you have to search for the system first, then maneuver the system to the centre of your vision and you will be able to select it.
You can then leave the map, line up with the selected system and press the Frame shift button to Hyperspace to that system.
I was having all kinds of trouble wondering why a system that is apparently within range was not showing up on the Navigation panel in the cockpit UI.
I must say, I wasn't all that impressed by the DK2 at FantastiCon. I couldn't notice any significant difference from the DK1. Was still great, just didn't feel like that big a step beyond the previous.
SlackR
Banned
Not sure which one you tried but it almost certainly wasn't set up correctly if that was your experience... The low persistence alone makes the DK1 seem obsolete. Still not where it needs to be, but definitely miles away from where the DK1 left off...
No smearing when you turn your head. Less screen door, higher resolution, deeper blacks.
Less FOV. Some chromatic aberration.
All in all it's quite a different beastie... mostly much, much better surprised you didn't really notice the differences, I did instantly and I sold my DK1 months ago!
Hello everyone,
one old 84er here, recently got my DK2.
Am I correct in assuming that the current beta version of ED does not yet support low persistence with DK2?
Moving my head causes blurryness/unsharp picture, no matter if I decrease graphic options and resolution to an absolute minimum.
While not moving my head the picture is clear enough and my machine should have enough power, I can only imagine non-working low persistence as main cause. I've read comments here of silky head-tracking movement in ED and simply can't believe thats true? Is your experience really that different to mine?
:S
one old 84er here, recently got my DK2.
Am I correct in assuming that the current beta version of ED does not yet support low persistence with DK2?
Moving my head causes blurryness/unsharp picture, no matter if I decrease graphic options and resolution to an absolute minimum.
While not moving my head the picture is clear enough and my machine should have enough power, I can only imagine non-working low persistence as main cause. I've read comments here of silky head-tracking movement in ED and simply can't believe thats true? Is your experience really that different to mine?
:S
SlackR
Banned
Because of all of the workarounds and lack of optimisation, things are pretty GPU intensive at the moment... If you an hit 75 fps then things will be very smooth. Lowering the settings and setting your colour scheme to windows basic are your best options until things get sorted.
Low persistence is automatic when you hit 75fps.
Less than 75fps is not low persistence, so if you can't hit constant 75fps then you won't have constant low persistence (which almost no one has in stations).
For me regardless of settings I get 75fps in space areas and 55 fps in station zones (regardless of 20km or inside the dock).
It seems there are some optimisations required in the engine.
Less than 75fps is not low persistence, so if you can't hit constant 75fps then you won't have constant low persistence (which almost no one has in stations).
For me regardless of settings I get 75fps in space areas and 55 fps in station zones (regardless of 20km or inside the dock).
It seems there are some optimisations required in the engine.
Damn, ok. I think I'll do another test just to be sure, but I didn't realise my eyes are so close together! I guess I look something like this:
I didn't have any difficulties with the B lenses on the DK1, so here's hoping...
Along with a some of the other tips and responses you've already received, there are a few other things you can do to help get rid of some of the judder in ED.
One thing that has improved almost ANY game/demo I've used on the DK2 is disabling your other monitors before launching the game. I get everything setup and then put the ED launcher in the middle of my computer monitor. Then I use Windows + P and only allow the DK2 to be enabled. You have to kind of look out of 1 eye to press play on the launcher.
This vastly improved the judder in ED for me (as well as about any other game I've played on the DK2. This was recommended from reddit / r / oculus).
I think the root cause of that is that you've got a monitor at 60Hz (I'm assuming) and the rift is 75Hz. An alternative to turning the monitor off is to drop the resolution of the monitor till you can also set that at 75hz.
That's how mine is setup.
Soon as I turn my DK2 on it drops the resolution and ups the refresh rate of my main monitor. Soon as I turn my DK2 off it sets the res and refresh rate back up to native.
Not tried benching to see if also turning off the monitor has an affect or not.
What kind of strange monitor is that? :O old CRT? LCD panels(most of them) are locked at 60hz, they cant do any more or less no matter what resolution. Except some special 120hz or 144hz TN-panel gaming monitors.
I have a recent 1440p Monitor.
Check the range of your monitor
Mine is H/V frequency H:30-88.7KHz V:60-75Hz
So I can get 75hz but not at 1440p
If I drop the res I can hit 75hz
The DK2 should behave like a secondary monitor without the need for all that messing about. I don't quite understand what your main monitor has to do with anything? It doesn't matter what resolution it is - it has no relationship with the DK2 at all.
Don't knock it till you try it.
The issue is the difference in refresh rates.
Most monitors are running at 60hz, your DK2 is running at 75Hz
There appears to be some issue that causes more judder in games if you have more than one monitor plugged in and the monitor(s) is 60hz and the Dk2 75hz.
Unplugging monitor(s) is one way to correct this issue (so you just have the DK2 as a display).
Setting the other monitor(s) to 75hz at a lower res is an alternative solution.
Last edited:
If it's running off the same graphics card it does... and it's possible that the graphics card isn't capable of outputting different refresh rates to different monitors connected to it.
So if you want 75hz on the Rift, you have to ensure that all your connected monitors are 75hz.
Oh I see! sorry. I'll give it a try.