schellingb / pseudovive

Simulate device names for any SteamVR driver to increase compatiblity

PseudoVive

This driver for SteamVR/OpenVR forces any loaded device driver to return Vive model names for HMD and controllers so that any application with an explicit check for it runs regardless of the used VR headset or motion controller.

Install

1. Download the archive from here.

2. Right click SteamVR in the Tools or VR section in the Steam library. Click on 'Local Files' and then 'Browse Local Files...'.

3. Extract the '2vive' folder from the PseudoVive master ZIP into the 'drivers' folder of SteamVR.

4. Restart SteamVR

You can check if the installation was successful by opening the 'Create System Report' window with the SteamVR menu or by right-clicking the SteamVR systray icon. Then under the 'Devices' tab it should list your devices with a different model name.

Toggle Variation

This repository also includes a variation of the driver inside the '2vive_toggle' folder.

If you extract the '2vive_toggle' folder instead of '2vive' you will have a 'PV' icon next to the SteamVR icon in the windows system icon tray. This 'PV' icon allows you to activate and deactivate PseudoVive at runtime.

Make sure not to extract both '2vive' and '2vive_toggle' into the 'drivers' folder of SteamVR.

Notes

SteamVR loads its drivers in alphabetical order so our driver is named in a way that makes sure it is loaded first (with a leading number).

Even though the PseudoVive driver itself does not offer any devices, it makes sure that all drivers loaded after it will return the forced device model names.

So far it only changes the values for 'ManufacturerName' and 'ModelNumber' which seems enough for the applications that are out there at the moment. In theory a more elaborate check could be made that checks the format of the serial number or other fields.

Dependencies

• MinHook by Tsuda Kageyu (included in this repository)
• OpenVR SDK by Valve (included in this repository)

License

PseudoVive is available under the zlib license.

pseudovive's Issues

Doesn't seem to work with Rift

I load up 2vive or 2vive_toggle and this doesn't seem to work with the Rift. It would be nice so I can get games to launch in OpenVR mode instead of OculusVR mode.

This works well for the pimax - what a great tool! Thanks!

I'm not liam nissan. I can't find you. I don't have the right tools, but I can thank you for making this tool!

• [*] Thanks!!!

Build from source

When I trying to build it I get

1>driver_2vive.obj : error LNK2001: unresolved external symbol __Init_thread_epoch
1>driver_2vive.obj : error LNK2001: unresolved external symbol __Init_thread_footer
1>driver_2vive.obj : error LNK2001: unresolved external symbol __Init_thread_header

and in debug mode something like
error LNK2001: unresolved external symbol _CrtDbgReportW

I tried to change MinHook to v1.3.3 same error

Visual Studio 2017 (v141) and 2017 (v140)

Please help

Upgrade solution to VS2019

Platform Toolset: Visual Studio 2019 (v142)
WinSDK: 10.0.18362.0

1>------ Build started: Project: driver_2vive, Configuration: Release Win32 ------
1>   Creating library C:\Program Files (x86)\Steam\SteamApps\common\SteamVR\drivers\2vive\bin\win32\driver_2vive.lib and object C:\Program Files (x86)\Steam\SteamApps\common\SteamVR\drivers\2vive\bin\win32\driver_2vive.exp
1>driver_2vive.obj : error LNK2001: unresolved external symbol __Init_thread_epoch
1>driver_2vive.obj : error LNK2001: unresolved external symbol __Init_thread_footer
1>driver_2vive.obj : error LNK2001: unresolved external symbol __Init_thread_header
1>C:\Program Files (x86)\Steam\SteamApps\common\SteamVR\drivers\2vive\bin\win32\driver_2vive.dll : fatal error LNK1120: 3 unresolved externals
1>Done building project "driver_2vive.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Emulate other devices

Could you make it so it can emulate other devices (Especially the Reverb G2 because that will be requires in the beginning of Flight Sim 2020 and many people are eager to play it in VR but don't have a G2)

A bonus would be if we can switch between which device is emulated in the toggle menu.

If you need infos like the HMD names or system reports just ask the community they'll happily provide them for you. I for example can give you the quest device names and soon the Quest 2 ones

Sent from my TAB 2 A10 using FastHub

Feature Request: change device role

To use Vive Trackers as a controller you need to reflash the firmware, which is not even allowed with version 2.0 of Vive Trackers, and is still not a viable option for many users

I wondered if your driver could change the Device Class of Vive Trackers to be seen as a controller

Since SteamVR introduced the new SteamVR Input, I can no longer use Trackers with Beat Saber.

https://www.reddit.com/r/beatsaber/comments/99r4k1/tracker_saber_darth_maul_upgrade/

Seems not work

Seems like not work with Samsung HMD Odyssey.Im not sure if it's because the version is too old

not work wih driver4vr

driver4vr not detect my hmd if i use pseudovive.. why??

Cant be remove ever

It cant be deactivated for good. Cant be remove. I have tryied to delete every single peices of this code and every single time I reopen steamVR is magicly reapear in the task bar and regreate it self from thin hair....

Feature request: Ability to selectively enable/disable or opt-in or out by default per application

WMR support is growing. Some applications recognize and work with the remotes fine now while some others do not. This driver has been absolutely fantastic and incredibly useful. I'd love an easier way to control when and if it's leveraged for games requiring the layer of compatibility mode.

Is this at all possible? Could it be controlled in the overlay somehow? via command?

Could not find factor function in driver 2vive

DLL placed as per instructions, however Vserver log shows the following error.

Sun Jun 25 2017 16:27:44.047 - Could not find factor function in driver 2vive from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\2vive\bin\win64\driver_2vive.dll.
Sun Jun 25 2017 16:27:44.048 - Unable to load driver 2vive because of error 104. Skipping.