ED and the Oculus Rift Developers Kit 2 (DK2) Discussion Thread

andygood

A
SlackR said:
Should be set to F12 by default... But you can change it to whatever you want in the graphics settings. I use voice attack and just says 'oculus' to reset.
Click to expand...

Doesn't work for me. Binding is set to F12 but the view doesn't reset. I get a CTD when I try to change a key binding.

Right now I seem to have a two foot neck in-game... :eek:

PS. I'm getting the 'Day-Glo' colour effect as well!
 

SlackR

Banned
SlackR
Distance said:
Confirmed. I can navigate galaxy map now, even if it is a bit finicky but can't read anything in the panel, if there was a way to zoom to it it'd be fine.



You're best off waiting as the 8 series cards are due in a month or so.
Click to expand...

So it works with the Dk1 ? Or did you get it with DK2?
 

Mazhurg

Mazhurg
Mazhurg said:
For all of those with AMD CPUs and older Intel chips (well - so far).

It appears that the camera drivers use a newer instruction set not supported by the above CPUs and there is currently no way to enable the camera tracking as the service fails as soon as it sees the HMD move.

As I am currently waiting for parts on my main rig, I was experimenting with the Rift on my AMD A8 laptop and initially came across this problem (and yes it's only for basic testing as this machine does not get anywhere near the required framerates...)

On can still get the default tracking by disconnecting the camera but only legacy tracking is available at that point.

Anyway, the thread at https://developer.oculusvr.com/forums/viewtopic.php?f=34&t=10994 has more details.
Click to expand...


Further to this, for those who care ;) :

The camera driver requires SSE4.1+ instruction set support. So any older CPUs that do not support this (e.g my laptop A8 - SSE 4.a) will be unable to get the camera going properly.

Unknown if Oculus will (or can) fix this, and if not, it also will eventually limit the minimum specs on E: D with OR.
 

Deric Lee

Deric Lee
Wokawidget said:
Finally got it working. Thanks everyone.

One thing I noticed is the sidewinders holographic displays were illuminous, as were all lights in the cockpit.
I changed the brightness in the Option->Graphics menu, and while this did reduce the brightness the colours were still day glow orange, like contrast was set to 100%.

When I was looking around the cockpit I moved my head outside of the OR tracker sat on my monitor. As soon as I went outside the tracking range all colours in the cockpit turned normal. No day glow this time, but instead normal soft colours, the same as when playing on my monitor. When I brought my head back into tracking range...*poooof* day glow neon colours again.
Asteroid etc all look fine...it's purely the holographics and lights.

I raised a thread here about it and will raise a ticket: http://forums.frontier.co.uk/showthread.php?t=28832
Click to expand...

Have you tried adjusting the in-game brightness setting for your cockpit/holo overlay?
 

Cmdr Snuffler

Cmdr Snuffler
Deric Lee said:
Have you tried adjusting the in-game brightness setting for your cockpit/holo overlay?
Click to expand...

Yes:

I changed the brightness in the Option->Graphics menu, and while this did reduce the brightness the colours were still day glow orange, like contrast was set to 100%.

It also seems f12 does nothing to reset the look. I even bound f12 to reset head look and nothing.
 
Last edited:

SlackR

Banned
SlackR
Wokawidget said:
Yes:

I changed the brightness in the Option->Graphics menu, and while this did reduce the brightness the colours were still day glow orange, like contrast was set to 100%.

It also seems f12 does nothing to reset the look. I even bound f12 to reset head look and nothing.
Click to expand...

Its not the head look you are trying to reset ... It's the oculus orientation :)
 

Balmung

Balmung
Thx, I know about the GTX870/880 but I don't want to wait 3 Months for it (my Info says Nov).

RiftFlyer said:
I'm using a gtx780 msi overclocked. No issues with fps that I can tell. Can I display the actual fps somehow?
Click to expand...
ctrl/strg + f

Could you activate the Oculus Mode in Graphic Settings and look for the FPS on a Station?
 

derus

D
Hello everybody.
Sorry if it was already answered in the thread, but I'm getting:

1)chromatic aberration everywhere, even in the center of the lens and even more visible on bright stars.

2)stuttering only when I move my head and the image is doubled for me in motion (vsync is on ingame and forced in CCC). The stutters only go away when I start the game with the lowest settings possible. I have AMD HD7970 and on my monitor I'm getting constant 60 fps with max settings.

I don't know what's wrong. Is that normal? Is it a fault from Oculus? Me? Frontier?
Help...
 

smackaholic

S
derus said:
Hello everybody.
Sorry if it was already answered in the thread, but I'm getting:

1)chromatic aberration everywhere, even in the center of the lens and even more visible on bright stars.

2)stuttering only when I move my head and the image is doubled for me in motion (vsync is on ingame and forced in CCC). The stutters only go away when I start the game with the lowest settings possible. I have AMD HD7970 and on my monitor I'm getting constant 60 fps with max settings.

I don't know what's wrong. Is that normal? Is it a fault from Oculus? Me? Frontier?
Help...
Click to expand...

1) It shouldn't be that bad if your Rift has been properly calbrated so something's up here. I get minor aberration but not as bad as you describe

2) I have this same issue, but I'm also one generation behind (6970's). I'm also assuming the system can handle 1920x1080 @ 75ps, as it's locked at 60fps (nearly no drops) on the desktop, but you never know.

As others have suggested, I'm going to try running it on the desktop in Rift mode without vsync to see if my system can even sustain 75ps minimum.

Only other thing I can think of is the system can't properly detect the Rift as an extended display and thus doesn't know what the refresh rate should be or in my case, I can't set the refresh rate due to no entries in display properties.
 

justh3nn3

J
Oculus DK2 - Space looks strange

So this problem is not easy to describe, i cant take a screenshot of it because it is something you need to see by yourself when you are in the game with the DK2.

Everything that is in the far distance, like stars and the milky way, looks like just a texture on a big surface around the spaceship.

It's like sitting in a simulation cockpit which is in a projection cave:
Aermacchi%20-%205.jpg

The space is right in front of my cockpit and the only things that really looks 3D are things in the near distance, like space station, planets in SC and so on. Since the space is right in front of the cockpit, it looks very odd when i fly to something like a space station, because it seems the space station is further afar then the space itself.

I think that is some sort of graphic optimization to keep the FPS high. I can imagine that problem is not noticeable on a monitor.

I didn't had that problem with the DK1 and PB2 and people with the DK2 said they didn't experience that in PB2 too, so it must be something which came with the Beta.

I posted that already on the oculus subreddit and it seems i am not the only one who feels that way:

http://www.reddit.com/r/oculus/comments/2c2yuw/elite_dangerous_beta_1_available_for_download/cjbgczk

My graphic settings are on high and i use a GTX 780 Ti with the latest driver (340.52) on Windows 8.1
 
You must log in or register to reply here.
Back
Top Bottom