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

Mazhurg

Mazhurg
Shigawire said:
Yeah. Tried that too. :)

Btw. when I have closed down wscript.exe and shut down OVRservice_x64.exe, the OculusConfigUtil.exe is showing my DK2 as "disconnected." And anything I do in the OculusConfigUtil is very slow. F.ex. going to Advanced, and down the submenus takes longer than usual.
Click to expand...


Had that issue, and used the Oculus runtime utility (link in the op). Basically, you also need to kill the config utility before you will get a response on the secondary screen.
 

Shigawire

Shigawire
Mazhurg said:
Had that issue, and used the Oculus runtime utility (link in the op). Basically, you also need to kill the config utility before you will get a response on the secondary screen.
Click to expand...

So, I am also supposed to close the config utility? I thought I needed that for positional tracking...

The Oculus runtime utility, you mean Bilago's utility. Yeah I have used it.
 

Mazhurg

Mazhurg
Shigawire said:
So, I am also supposed to close the config utility? I thought I needed that for positional tracking...
Click to expand...

You need to close all 3 processes:

Windows script engine,
OVR service, and
Oculus configuration utilities.


The tool, Oculus service manager at http://www.mediafire.com/download/1i39o786z33xei6/OculusServiceManager_-_By_Bilago.7z makes doing those tasks a simple click on the desktop (both stopping and restarting the services.

--- Did not notice your last sentence. If it still does not work, and it's not a CPU instructions issue, then its probably some other driver interfering. Some people are reporting that the Logitech desktop cam drivers are interfering, and that there might be others also.
 
Last edited:

Shigawire

Shigawire
Ok, I got it working now! :D

It was much easier than I thought.

But some of the guides may need to be rewritten, because they were confusing, and a lot of information was missing or wrong. Easily misunderstood.

Thanks for all the help, and all the fish. So long! Time to land on pad 42.
 

Darth Sidious

Darth Sidious
Shigawire said:
Ok, I got it working now! :D

It was much easier than I thought.

But some of the guides may need to be rewritten, because they were confusing, and a lot of information was missing or wrong. Easily misunderstood.

Thanks for all the help, and all the fish. So long! Time to land on pad 42.
Click to expand...

Congratulations

Here's something almost of topic
Since the Dk2 has a Note 3 screen you guys might find this interesting..http://www.slashgear.com/galaxy-note-4-leaks-confirm-5-7-inch-qhd-screen-16333727/
 

Tankshell

T
Ryder35 said:
OK so, assuming the latest Nvidia drivers may be an issue with frame rates I rolled back to 337.88 but there was no difference. Still getting 35fps in station in rift mode on main display in 1080p
Click to expand...

Oh well, I was going to try a driver roll back tonight but I don't think I will bother!

I am also still getting 35fps in station sat on pad, in DK1 rift mode @ 1080p. :(

I am starting to wonder if the DK1 rift mode was broken (or at least, forgotten about slightly) with the latest beta release, what with all the DK2 hype. They probably focused more on getting it running well in the DK2, at the expense of us poor DK1 users :)

As I have said before, Premium Beta 1/2 seemed to run a LOT smoother on my DK1.

Annoyingly, I didn't order my DK2 until just after the 1st day ended (actually ordered at 02:00am on the March 20th, 2nd day!), and given that that Oculus have still yet to dispatch the majority of orders after 2:30pm on the 1st day, I think I am still in for a bit of a wait.
 
Last edited:

SlackR

Banned
SlackR
Shigawire said:
Ok, I got it working now! :D

It was much easier than I thought.

But some of the guides may need to be rewritten, because they were confusing, and a lot of information was missing or wrong. Easily misunderstood.

Thanks for all the help, and all the fish. So long! Time to land on pad 42.
Click to expand...

What was the issue?
 

SlackR

Banned
SlackR
Tankshell said:
Oh well, I was going to try a driver roll back tonight but I don't think I will bother!

I am also still getting 35fps in station sat on pad, in DK1 rift mode @ 1080p. :(

I am starting to wonder if the DK1 rift mode was broken (or at least, forgotten about slightly) with the latest beta release, what with all the DK2 hype. They probably focused more on getting it running well in the DK2, at the expense of us poor DK1 users :)

As I have said before, Premium Beta 1/2 seemed to run a LOT smoother on my DK1.

Annoyingly, I didn't order my DK2 until just after the 1st day ended (actually ordered at 02:00am on the March 20th, 2nd day!), and given that that Oculus have still yet to dispatch the majority of orders after 2:30pm on the 1st day, I think I am still in for a bit of a wait.
Click to expand...

Try rolling back to the previous SDK and see if that helps?
 

SAB380

SAB380
Mazhurg said:
You need to close all 3 processes:

Windows script engine,
OVR service, and
Oculus configuration utilities.


The tool, Oculus service manager at http://www.mediafire.com/download/1i39o786z33xei6/OculusServiceManager_-_By_Bilago.7z makes doing those tasks a simple click on the desktop (both stopping and restarting the services.

--- Did not notice your last sentence. If it still does not work, and it's not a CPU instructions issue, then its probably some other driver interfering. Some people are reporting that the Logitech desktop cam drivers are interfering, and that there might be others also.
Click to expand...

Maybe this is my problem as well. I get no tracking.
Will have to download this tool.

I can shut down OVR service, and Oculus configuration utilities (straight out of task manager and tool bar) but Windows script engine doesn't appear in the processes list for me....am I doing something wrong?


Also, once I shut down Oculus Configuration Utilities, the blue light on the track camera goes out ....does it still work for people in Elite: Dangerous anyway?
 

SlackR

Banned
SlackR
SAB380 said:
Maybe this is my problem as well. I get no tracking.
Will have to download this tool.

I can shut down OVR service, and Oculus configuration utilities (straight out of task manager and tool bar) but Windows script engine doesn't appear in the processes list for me....am I doing something wrong?


Also, once I shut down Oculus Configuration Utilities, the blue light on the track camera goes out ....does it still work for people in Elite: Dangerous anyway?
Click to expand...

Don't worry about the light... But not closing wscrip will result in the service reopening... If you are on windows 8 it might be easier to use the app :)
 

Herro Zaber

Herro Zaber
OK
Rolled back NVidia drivers to 337.88
Clocked the i7 4770K to 4600MHz
SLI Disabled
Remaining 770GTX
----Core Voltage +1
----Core Clock +310
----Memory Clock +206

High in Elite then:
Shadows Medium + Ambient off

And now judder/jitter is gone except for a bit in stations. CPU is still barely touched. Maybe this will help someone else
 

SAB380

SAB380
SlackR said:
Don't worry about the light... But not closing wscrip will result in the service reopening... If you are on windows 8 it might be easier to use the app :)
Click to expand...

Thank you kind sir.
Yes I am on Windows 8.1
Is that why I can't see it in the processes in task manager? Any other way to close it down without the app ?
 
You must log in or register to reply here.
Back
Top Bottom