I do. I'm pretty sure it is a deliberate indication to show you're going out of range of the head tracker.
ED and the Oculus Rift Developers Kit 2 (DK2) Discussion Thread
I do. I'm pretty sure it is a deliberate indication to show you're going out of range of the head tracker.
Ah yeah that's possible, I will see tomorrow if I can arrange some things better to have more distance between myself and the camera to improve this.
SlackR
Banned
Updated...
1. Download the runtime and (optional) SDK
2. Set up the Rift by following the instructions ...
http://static.oculusvr.com/sdk-downl...ion_Manual.pdf
3. Make sure you update the firmware.
4. Test using the small room demo and / or oculus world using direct mode.
5. If they work, calibrate your IPD and tracking zone using the config app and small room. I find putting the camera on the back wall and moving the desk forward allows for more wiggle room.
6. If everything is cool, switch to extended mode inside the config app. For the moment keep the monitor set to primary.
7. Not sure about AMD, but for NVIDIA cards you will need to change the orientation of the screen, so that it appears the correct way round. This can be done in the NVIDIA control panel. Whilst you are in there, create a 3d settings profile for ED and set antialiasing and triple buffering to on. if you get stuttering, try disabling the triple buffering
8. Lastly in the NVIDIA control panel, set the Rift refresh rate to 75 hz.
9. Ok now open up the oculus config file again and hit Ctrl , Alt and Del. in task manager, close wscrip.exe and ovservice.exe in processes.
10. If its NOT Elite Dangerous you are wanting to play at this point, you will need to set the rift now as the primary monitor. If its Elite Dangerous you want, just open the game.
11. In options / graphics make sure the refresh rate is set to 75 hz and v sync is on. Switch to oculus mode and set display to secondary monitor.
12. Once in game, lean back in your chair and hit F12 to reset the rift and avoid clipping. If you are still not happy, move your desk away from the wall and reset again. (Assuming you have the camera mounted in the wall behind the desk.)
*If you are getting a message saying oculus service not available, go to your oculus folder and open the inside the services folderovrservice_x86 or x64. Then open the config.exe inside the tools folder.
* it's also worth mentioning that its worth spending some time setting up your IPD and playing with the lens distance (via the screws on the sides of the rift)... Especially if things seems overly blurry.
* if still no joy, try disabling / unplugging peripherals, particularly logitech devices and drivers.
* if things are stuttering this is possibly a vsync issue and you should check that you have forced it through in NVIDEA for Elite. Make a profile and switch vsync, AA and triple buffering to on. Note* if juddering occurs try switching off the triple buffering as your first trouble shooter Also make sure your rift is set to 75 hz in the NVIDIA panel in screen res section. Lastly set the colour scheme to windows basic. This disables Aero, which for some reason can play havoc with the rift monitor.
* also try switching input to PC from HDMI to DVI or VICE VERSA... No idea why this makes a difference but it has for me twice now!
* if it STILL doesn't work go back and try again, chances are you missed something or did them out of order.
* update the firmware a few times just to rule it out ... Again this one worked for me
* setting colour scheme to window basic (from aero) also has been reported to make a difference.
* some people with windows 8.1 x64 are still having no luck! One guy installed win 7 and it worked fine. Another back dated to previous win 8 version and it also worked.
* those with the no camera working found switching between USB 3.0 and 2.0 brought it to life, whilst another found that the powered USB hub worked.
1. Download the runtime and (optional) SDK
2. Set up the Rift by following the instructions ...
http://static.oculusvr.com/sdk-downl...ion_Manual.pdf
3. Make sure you update the firmware.
4. Test using the small room demo and / or oculus world using direct mode.
5. If they work, calibrate your IPD and tracking zone using the config app and small room. I find putting the camera on the back wall and moving the desk forward allows for more wiggle room.
6. If everything is cool, switch to extended mode inside the config app. For the moment keep the monitor set to primary.
7. Not sure about AMD, but for NVIDIA cards you will need to change the orientation of the screen, so that it appears the correct way round. This can be done in the NVIDIA control panel. Whilst you are in there, create a 3d settings profile for ED and set antialiasing and triple buffering to on. if you get stuttering, try disabling the triple buffering
8. Lastly in the NVIDIA control panel, set the Rift refresh rate to 75 hz.
9. Ok now open up the oculus config file again and hit Ctrl , Alt and Del. in task manager, close wscrip.exe and ovservice.exe in processes.
10. If its NOT Elite Dangerous you are wanting to play at this point, you will need to set the rift now as the primary monitor. If its Elite Dangerous you want, just open the game.
11. In options / graphics make sure the refresh rate is set to 75 hz and v sync is on. Switch to oculus mode and set display to secondary monitor.
12. Once in game, lean back in your chair and hit F12 to reset the rift and avoid clipping. If you are still not happy, move your desk away from the wall and reset again. (Assuming you have the camera mounted in the wall behind the desk.)
*If you are getting a message saying oculus service not available, go to your oculus folder and open the inside the services folderovrservice_x86 or x64. Then open the config.exe inside the tools folder.
* it's also worth mentioning that its worth spending some time setting up your IPD and playing with the lens distance (via the screws on the sides of the rift)... Especially if things seems overly blurry.
* if still no joy, try disabling / unplugging peripherals, particularly logitech devices and drivers.
* if things are stuttering this is possibly a vsync issue and you should check that you have forced it through in NVIDEA for Elite. Make a profile and switch vsync, AA and triple buffering to on. Note* if juddering occurs try switching off the triple buffering as your first trouble shooter Also make sure your rift is set to 75 hz in the NVIDIA panel in screen res section. Lastly set the colour scheme to windows basic. This disables Aero, which for some reason can play havoc with the rift monitor.
* also try switching input to PC from HDMI to DVI or VICE VERSA... No idea why this makes a difference but it has for me twice now!
* if it STILL doesn't work go back and try again, chances are you missed something or did them out of order.
* update the firmware a few times just to rule it out ... Again this one worked for me
* setting colour scheme to window basic (from aero) also has been reported to make a difference.
* some people with windows 8.1 x64 are still having no luck! One guy installed win 7 and it worked fine. Another back dated to previous win 8 version and it also worked.
* those with the no camera working found switching between USB 3.0 and 2.0 brought it to life, whilst another found that the powered USB hub worked.
For a slacker you sure aren't slacking in your ability to help people get into the wonderful world of EDVR. +1
SlackR
Banned
I'm on holiday ... Dk2 + Elite is my little project to keep me busy
My raspberry pi is all ready to get going now... Am teaching a coding class in my school next year, so once I start on that in a few weeks you wont see me!
MUST KEEP BUSY!
If I was at home with my DK2 right now I'd be playing. It's cool that you're so helpful for others.
I'd warn against enabling triple buffering for any VR stuff. That just adds extra frames of latency between head movement and display.
SlackR
Banned
Lol
As soon as the wife goes shopping I'll be back to Eranin... Just got my Lakon 6 last night so time to make some serious money!
SlackR
Banned
Am playing around with this today on a few different systems and will feedback later... I seem to be getting different results on different GPU's, but I have included in the notes to switch it off if stuttering occurs.
Oculus DK2 Performance
I've not seen any existing threads about this, so I thought I'd drop a query in here for other DK2 users.
My machine has a fairly beefy setup with SLI GTX 770s, but I still find it really struggling to pull off a smooth experience with the Oculus Rift. I have to drop down absolutely everything to the lowest possible settings in order to get 75fps when out in space and even so, in a lot of docks the framerate drops down to about sixty and causes juddering - as well as in the galaxy map.
Even so much as enabling FXAA, which is just about the cheapest thing to switch on, seems to drop the framerate below 75.
Yet I've also read a few people using similar hardware get smooth results at medium and high settings, so I'm curious if anyone's found tips or tweaks that get the game to run better for them?
I've not seen any existing threads about this, so I thought I'd drop a query in here for other DK2 users.
My machine has a fairly beefy setup with SLI GTX 770s, but I still find it really struggling to pull off a smooth experience with the Oculus Rift. I have to drop down absolutely everything to the lowest possible settings in order to get 75fps when out in space and even so, in a lot of docks the framerate drops down to about sixty and causes juddering - as well as in the galaxy map.
Even so much as enabling FXAA, which is just about the cheapest thing to switch on, seems to drop the framerate below 75.
Yet I've also read a few people using similar hardware get smooth results at medium and high settings, so I'm curious if anyone's found tips or tweaks that get the game to run better for them?
AFAIK, ED only uses one of your 770's. It doesn't have SLI supported yet, which is why you're getting bad rates. Also, word is that Oculus does suffer from SLI rigs over single cards.
SLI doesn't work because it generates frames alternately per graphicscard and that makes it juddery from what I have read.
Also Ars has a article about an iFixit teardown according to that we are all buying Galaxy Note 3s when we buy OR *g*
Also Ars has a article about an iFixit teardown according to that we are all buying Galaxy Note 3s when we buy OR *g*
SlackR
Banned
I think the latency is caused by the SLI config... Try running on one card and see if there is a difference. As far a frame rate goes... I am running a 780 ti on max setting and my average fps is between 65 and 75 fps!
Yes, I've noticed that enabling and disabling SLI doesn't offer a performance advantage, but I would have thought even a single 770 should pull some more weight ^^ I'm mostly wondering if there aren't some other settings - either in the game's config or in terms of nVidia's configuration that other people haven't found helpful to tweak/causing unreasonable slowdown.
AFAIK with the DK2 SLI adds <10ms latency.
When they're talking of shooting for <20ms (IIRC) silicon -> photon anything in the realms approaching 10ms actually sounds pretty big!
SlackR
Banned
There no doubt that performance is taking a huge hit when running through the DK2... I hope that it is one of two things...
1. Standard Beta is optimised to the same degree as the last release...
2. The workaround is affecting performance.
With the 708 ti I am averaging 74.5 on medium settings and 70 fps on high!
Really disappointed with the performance so far from my OC'd rig
Will be playing with the NVIDIA settings today to see what can be done from our end...
EDIT* hitting 74.9 fps in station now with everything maxed out except AA which is off.
1. Standard Beta is optimised to the same degree as the last release...
2. The workaround is affecting performance.
With the 708 ti I am averaging 74.5 on medium settings and 70 fps on high!
Really disappointed with the performance so far from my OC'd rig
Will be playing with the NVIDIA settings today to see what can be done from our end...
EDIT* hitting 74.9 fps in station now with everything maxed out except AA which is off.
Last edited:
This is an interesting reddit thread:
http://www.reddit.com/r/oculus/comments/22sm56/whats_the_real_overhead_on_stereo_rendering/
It discusses the oversized render target that you have to write to in order to render an oculus-distorted 1080p image with a sensible field of view.
If you press space on a few of the unity demos that are out there that have the oculus stats panel left enabled you can see that a lot of them are rendering at 2560x1440, which is what I imagine ED is rendering at (1280x1440 per eye).
in the DK1, it would have been rendering at (guessing here) something like 1600x1000, or around 800x1000 per eye, which is significantly less strain on the old GPU.
Direct rendering might come with it's own improvements from a driver perspective, so when that's enabled and we no longer need the hack I'm sure we'll see some minor speed-ups. I think the biggest improvements, however, will come from an optimisation pass by frontier later down the line. Qe might need to prompt that (and other things) by raising appropriate tickets.