ED and the Oculus Rift Developers Kit 2 (DK2) Discussion Thread
I uninstalled Logitech Webcam software and drivers. Restarted.. still no positional tracking in ED.
I closed the 3 services in question
SlackR
Banned
When the oculus config is running, is the camera recognised?
Shiga, you did kill wscript AND the Oculus task in the task manager, in that order? (or use the tool?) Because I know that if either are still running, positional tracking will not work in ED at all, and if you don't kill wscript first it will just restart the oculus service. And do make sure DK1 compatibility mode is checked in the oculus mode selection.
Yes you should and yes you will, or you just install the tool for that which has been linked 2-3 pages earlier.
The funny thing is that non-DK2 owners might think your post is offtopic, when it's actually really relevant
Yes you should and yes you will, or you just install the tool for that which has been linked 2-3 pages earlier.
The funny thing is that non-DK2 owners might think your post is offtopic, when it's actually really relevant
Last edited:
Ive been reading several posts about especially logitec webcams causing problems
Perhaps you should Google that in combination with oculus rift.
And there was something with re plugging the cam.
My rift has yet to arive so I have no experience
Just a vague recognition....
Good luck
http://www.reddit.com/r/oculus/comments/2c6qqc/updated_unofficial_oculus_service_manager_by/
Just use that utility. Its dead simple. Once installed just check Enable SSE Fix.
And yes.. installed the SDK Runtime 0.4
After messing around just staring at stuff in awe for the last 2 days - I just finally did some dog fighting and words cannot describe how amazing it is together with my Hortas X.
I felt myself leaning in the cockpit despite there obviously being no g-forces involved! And being able to follow your target by looking around you is so cool.
I felt myself leaning in the cockpit despite there obviously being no g-forces involved! And being able to follow your target by looking around you is so cool.
Can''t wait for direct mode to be enabled.... Still needing the odd camera resets as my neck appear to grows (or sometimes shrink)...
I do remain in the camera box (camera is about 1.5M away on top of the monitor) however, like any good VFR pilot, my head swivel quite a bit
Can't place the camera further away, as the monitor (fixed) will block part of the box.
(or sometimes shrink)...I do remain in the camera box (camera is about 1.5M away on top of the monitor) however, like any good VFR pilot, my head swivel quite a bit
Can't place the camera further away, as the monitor (fixed) will block part of the box.
I followed sepian78 tip from reddit and changed some settings in Nvidia Control Panel under 'Adjust desktop Colour Settings':
For All Channels: Brightness +55% Gamma +0.95 Digital Vibrance +55%
It it not a 100 percent fix, but it is a lot better. For me it resolved the black bleeding issue, but I'm easy to please.
Just a tip for you.. I use VoiceAttack - one of the things you can do is add a voice command to the F12 key. I programmed it to reset on the command Oculus.
Yes I am hoping SDK 0.4 version will improve things a little. Especially the colour seperation in the stars. But I think those issues require SDK fixes from Oculus themselves.
Already am
- I would not dare use the rift without it... Always been a two fingers typist.
I do remain in the camera box (camera is about 1.5M away on top of the monitor) however, like any good VFR pilot, my head swivel quite a bit
Can't place the camera further away, as the monitor (fixed) will block part of the box.
I have the camera at the bottom of the monitor at less than 1 m. No problems at all, i can even look behind me without losing tracking.
Thanks for the info. Question is what benefits will I get using the latest SDK with DK1, any idea?
Sorry just does not seem any point going through the hoops to get it working if it is not going to make a difference
I did kill both of those. Wscript.exe and OVRService_x64.exe, in that order.
I have the monitors set to extended. Rotational tracking is working, positional tracking is not working. Possibly as a result of this, there is slight judder.
Whenever I click "stop service", the blue light on the IR camera goes black. That means that closing down the service ensures that the positional tracking gets turned off. I don't really see any way around this.
Last edited:
So, I'm expecting the DK2 to turn up sometime this month and in anticipation of that happening I've uplifted my PC base and the specs on my machine which I'm hoping will run it are:
Intel XEON X5355 2 x quad core @ 2.67 (8 cores)
8GB RAM
Win 7 64 Bit OS
85GB SSD
GeForce GTX650 TI (1GB)
Scores 7.5 on the experience whotsit.
If that doesn't run it, I'm sticking it all on eBay and buying some drums!
Any feedback on that? (not the drum buying)
Intel XEON X5355 2 x quad core @ 2.67 (8 cores)
8GB RAM
Win 7 64 Bit OS
85GB SSD
GeForce GTX650 TI (1GB)
Scores 7.5 on the experience whotsit.
If that doesn't run it, I'm sticking it all on eBay and buying some drums!
Any feedback on that? (not the drum buying)
:smilie:
Just symbols then
Just symbols then
SlackR
Banned
I'm sure you already tried this, but switching USB ports?
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.
Last edited: