All it needed was a websocket server to supply the tracking! With some quick wrapper to export the api to C# i found on these forums, the server code was childsplay, I threw together a quick server. You'll need to have .net 4.0 installed to run it. and source is included (it's not very pretty but it gets the job done)
Be sure to set the parameters correctly (and play with them to see if you can find better ones)
Eye Separation: 65 FOV: 110 Distortion: 0.3 External Tracker: Checked (check after you started the server) WebSocket: ws://127.0.0.1:1981
Wow works great!! There is however a strange feeling with the convergence, like it's making me go cross-eyed. I un-checked the depth setting but there was little change. Using a controller and navigating is so cool, almost like instant teleportation since it loads so quickly...if smoother navigation and some positional tracking can somehow be worked out this will be absolutely amazing. With the increased resolution of the DK2 locations just come to life with so much clarity. Thx matoyan!!
The settings window can be removed by pressing space twice. You can get to the command prompt by entering "cmd" in the windows search bar and double clicking it.
I wish the website author made it possible to go back and forth by using the up and down arrow keys like in the normal version of streetview. That surely would be a lot better than having to press the ctrl key twice every time which is a little immersion breaking. Still, I'm really happy and gateful this is out there!
You could always use Autohotkey or any other key mapping program to make up (or anything else) equal to ctrl-ctrl. You'd run the .ahk as desired, maybe in a .bat with the .jar for the tracker.
Or maybe something browser-side with JavaScript via greasemonkey.
Hi all, the first attempt to adapt the Oculus Street View demo for the DK2 and later is out for the braves 😄 Its still in a study phase, so i'll wait to override the old version till i fix some issues and i receive some feedback. I made the following changes:
- removed the old fragment shader for distorsion: now is uses a pre-distorted mesh with vertex attributes for position, RGB colors and vignette
- The distorsion, IPD and other parameters are taken from the Oculus configuration.
- Removed the vr.js support: it relies on the obsolete NPAPI plugins, but...
- ..added support for WebVR😄 If this will be the standard for VR for the web is yet to be decided but it looks very promising. You don't need any external tracker nor plugins. You have all what you need inside you favorite browser, like WebGL. Brandon Jones made a Chrome custom build to try WebVR in advance. You can download it here https://drive.google.com/folderview?id=0BzudLt22BqGRbW9WTHMtOWMzNjQ&usp=sharing#list. Oculus Street View will recognize that the browser supports WebVR and it will use it. Just press F to go fullscreen and Esc to go back (R for resetting position). The downside is that the "stereo" map disappears in fullscreen and it works only in extended mode yet. Tell me if i should move in this direction only
- The external tracker can support orientation and position and it also should provide all the necessary HMD informations (including the pre-distorted mesh). Without it (and WebVR) you will see the streets in mono. I wrote a simple server in Qt (http://oculusstreetview.eu.pn/DK2/HMDTracker_x64.zip) now only for windows x64, but it will be easy to port it to win32 and OSX (sources:http://oculusstreetview.eu.pn/DK2/HMDTracker_src.zip).
Of course i plan to make the whole experience much better than now, but i wanted to share with you the first results. I think this application gains a lot with the DK2 because the streets are more detailed.
One more thing: looking at what happened at one of the library i used (https://github.com/spite/GSVPano.js) make me think not to invest too much energy in this project. Now i make it for "myself" 😉 and let's see what happens.
