I know there is no support yet (since it not even got release oficially).

But I got the pre-order for Rift S and I plan to contribute with OpenHMD to support.

So I'm just adding this issue so I do not forget about it, and if someone also have one (or will have) and want to help, it can use this issue.

This patchset adds basic support for the VR-Tek WVR3 and WVR2 headsets made by Direkt-tek. There is also a WVR1 that could be supported, but I don't have access to a WVR1 so for now only the two higher-end models are supported.

The distortion coefficients and aberration coefficients still need work (although to be honest the display output doesn't look too bad right now), but rotational tracking is working.

These are cheap and cheerful 3DoF headsets sold by Walmart in the US: https://www.walmart.com/ip/VR-Tek-Windows-VR-Glasses-Ultra-HD-Resolution-1440x1400-Black/56206938

Emdoor VR is the actual OEM for the headsets, with:

• WVR1 -> SpearI FHD
• WVR2 -> SpearI 2K
• WVR3 -> SpearII http://vr.emdoor.com/en/products/PC_VR/

The headsets are reusing the USB ID of the Oculus DK1, so I added a quick test to the rift driver to check for "Oculus VR, Inc." as the manufacturer. This was just a guess though based on what I could find online. So, some input from folks who know about Oculus gear would be greatly appreciated.

Any feedback is welcome. Thanks!

After compiling OpenHMD from master with cmake in debug mode, I ran the simple example with the headset plugged in and got a segmentation fault. Here's my backtrace from ddd:

in main () at simple.c:58
in ohmd_ctx_probe () at openhmd.c:120
in get_device_list () at rift.c:1081
wcscmp () at wcscmp.S:207

The relevant line in rift.c is:

if((wcscmp(cur_dev->manufacturer_string, L"Oculus VR, Inc.") == 0) &&

I figure something is wrong with cur_dev->manufacturer_string. The relevant line from lsusb is:

Bus 001 Device 007: ID 2833:0001

It looks like the name is empty. I hope that isn't the source of the segfault.

I should also note that I have installed OpenHMD from apt and the experimental SteamVR drivers from Valve. I also added their udev rules from here but didn't mess with OpenHMD udev rules. xrandr --props reports the headset as non-desktop.

EDIT: When I prepend if(cur_dev->manufacturer_string && to the above, the segfault moves to vrtek.c where it checks cur_dev->manufacturer_string against L"STMicroelectronics". It's pointless to keep kicking this can down the road, so I would suggest assigning manufacturer_string (and others?) to an empty string if null earlier so as to avoid segfaulting wcscmp.

EDIT 2: Hmm. What's hid_enumerate?

Hypereal Pano is a multi camera IR blob tracking based VR headset, this headset start selling from June 2017, Include dual or triple camera, sens controller and the HMD. dual camera provide 240° and triple camera provide 360° tracking. The manufacturer also released compatible tools on Windows to work with SteamVR at that time. but after January 2018, the manufacturer was transformation to other industry and no longer to support this headset. With tons of updates from SteamVR, the compatible tools are not work with the latest SteamVR(can not detect the key press event in game ). Now this VR headset can only work perfectly with old version SteamVR (such as macos_beta, 1.3.23). Does anyone interested to support this devices? For necessary, I can giving a triple-Camera headset with the latest client drivers from manufacturer and old version SteamVR macos_beta for reverse engineering.

Hello,

I get a oculus CV1. I work with open HMD to generate image (ready for VR) but i can't display this image on the oculus CV1 screen.

Have you any idea, tricks to help me ?

Thanks

Hello devs,

I m on gentoo and I installed openhmd on my computer with PSVR, but when I run openglexample, all test is good on my headset. When I exit squares round, I have no fullscreen on my psvr. My left eye haven't good resolution (scaled) and right eye is scaled to and display it to my screen. Can I make an resolution with Openhmd ? Is it Normal I have scale view on my Desktop ? How can i set openhmd resolution for my psvr...?

PS: I Missing to say, I turn it with a strange machine, PS4. All driver installed and my resolution screen is 1960x1080.

Please help me, is it cool idea to make psvr on PS4 with linux.

The image on the Oculus Rift CV1 is pretty distorted for me. In the log it says that is does use distrotion settings. Is the standard setting just fairly bad or is something not working as intended?

I'm trying to use OpenHMD and simple.c to understand the tracking information. My oculus is connected to my ubuntu 15.10 system via usb. the output of simple is only 0.0 coordinates. The vendor/device/path is OpenHMD/Dummy Device/path (none).

I enabled usb support across different users, althought i'm doing this via 'root' (please withhold judgement).

i'm not seeing the samples track any headset movement - they always registering 0.00 0.00 0.00 1.00

any help is appreciated.

I made a comment on a different thread but it was an oculus thread so that is my bad anyways

I need to know if openHMD has full camera access for WMR headsets

if it does, how do I access said cameras

then, I have only worked in python. is there someway to integrate it or should I work on learning C

thanks

This fixes weird resolution distortion on the vrtek wvr3. Other headsets may require a fix as well, but I don't have other headsets to test and fix other parts of the driver.

Hello,

Awesome work! I have just a question regarding mixed reality headsets support.

I found no documentation indicating that mixed reality headsets are supported by OpenHMD, however there is some code and drivers for them in the repositorie. Just for curiosity I tried to run the simple example with a Dell Visor connected to a mac. It detects the capabilities of the headset as a hololens sensor (and for the two positional controller sensors as well). However the software fails to open the device. Is there any kind of way to get rotation information on mac?

Because these new headsets are cheaper and very easy to setup, it would be great to have support for then in future.

Thanks

Thanks for great work!

I am trying to test HP Reverb G2 controllers and I see that the WMR controllers are currently only supported for linux (as indicated on http://www.openhmd.net/index.php/devices/).

Do you have plans to extend the support to MacOS, and/or have an idea on what would be needed for this?

Hello, good afternoon, I am contacting you, to ask you for a little help, I have seen your work on the “OpenHMD” website.

I am making a modification to a VR viewer the WVR3 VRTEK, the modification is simply to adjust the angles of the screens to have a much larger FOV, from the 90º degrees of FOV I can now have 135º FOV, you can follow the MOD in the Realovirtual website here:

https://www.realovirtual.com/foro/topic/51245/mod-visor-vr-los-90o-fov-135o-fov-anonymous-vr

The issue is that I have no way to configure the angles of the screens in the configuration file of the driver "default.vrsettings" in steamVR, I do not know what is the command or line that must be added to be able to tell SteamVR to change the screen angles.

Unfortunately I don't know how to create and compile new drivers with the OpenHMD API.

I need help to get the screens to rotate at my choice, I ask you for help in this MOD, you who know how to program.

I hope you can help rotate the screens, we would be very grateful in the Realovirtual ROV community. Thank you very much for your attention. https://github.com/OpenHMD/OpenHMD/tree/master/src/drv_vrtek

This project seems pretty direction less, while on many repos / branches there are interesting things.

The last 0.3.0 release is > 3 Years old, wouldn't maybe giving some goals and or deadlines / plans of release change that, even if it would only be some 0.3.99.1 or 0.4.0 pretest release.

I mean there are huge steps not production ready but close like initial wmr controller support, pretty close hp reverb (g1+g2) + other headset support. Do they have to stay another 5 years in some 99% finished forked repository?

Not really and issue but an information. Hopefully some shortcut for other Rift users in Linux.

I got the CV1 working after ages of "black image, organge LED". In Ubuntu 18.04 OpenHMD worked, but not the rest of the chain. The switch to 22.04 resolved that.

Here my configuration

• Ubuntu 22.04 installation, older AMD CPU, nVidia 1050Ti graphics card, HMD connected directly to the HMD port. (Adpaters and extensions lead to black image)
• fully offline copy of the standard Ubuntu 22.04 repository (with apt-mirror)
• many nvidia-drivers do not work. Nouveau is missing vulkan. I had success with the Ubuntu repository packet "nvidia-driver-450". The default one for 22.04 (V515) did definetively no work (black Screen).
• Installation OpenHMD compiled from source, installed with "sudo make install". With the repository packet it did not work
• Installation Monado compiled from source with all dependencies, installed with "sudo make install". The repository packet did not work as its missing the OpenHMD driver.
• Installation OpenXR packages from the 22.04 repository, except "openxr-monado" - this again is missing the openHMD driver
• Making the symlink point to the self compiled monado-service driver (as per instructions)

Thats it. I did not install SteamVR because I had an offline PC and it would not install. Its not required. The CV1 only shows an image after starting the monado-service and when the xrandr non-desktop=0 (which should be default)

The experience Its not fully smooth yet, but usable. Can't comment on rendering quality, though How run:

1. start monado-service in a separate terminal. This only worked for me with these settings export XRT_COMPOSITOR_FORCE_XCB=1 export XRT_COMPOSITOR_XCB_FULLSCREEN=1 monado-start # note: no "sudo"
2. open the nvidia-settings tool and rearrange the screen such, that the Monado fullscreen window is on the monitor "Rift". This is required each time the service is starting and the only annoying issue.
3. Start an application, e.g. Blender, enable VR in the preferences and start the VR mode in the SidePanel. The user manual describes that quite well done.

The frame rates are rather low, but I guess thats to expect with the hardware. However I am very pleased with the result. Btw, I do not have any controllers to test.

To debug the whole chain bottom up works great. Thtas why Im posting this here: If OpenHMD does not get an image in to the HMD with its "opengl" demo, there is no need to even look at Monado or OpenXR-SDK. Monado is crashing or giving erros with the default settings and with other parameter settings. For compilation I did not use any cmake flags, but when not all dependencies are installed the required "XCB" support will be missing.

If someone has an idea how to get rid of step 2 above I would say CV1 in Linux could be really ready for day-to-day use.

On the Oculus Rift CV1, I have some heavy "input lag"-like latency issues with the IMU. On OpenHMD master branch (3DOF CV1 support), I only see that while turning my head in the hmd, the whole thing turns late, and seems to be choppy. On Thaytan's branches with 6DOF CV1 support I see the following message being spammed when I open one of the demos:

[WW] Exposure timestamp 2396847104 was more than 1.5 IMU samples earlier than IMU ts 2396857332 by 10228 µS

It seems like the difference increases until it reaches around 19000 µS then it jumps down and climbs up again. Am I the only one experiencing this? It is not a performance issue as it happens with the simple example too (no 3d rendering), and the cpu can easily handle it (i5-12400f)