THETA V Now Working with Unity 2017.2.0f3
Process
There’s another virtual driver that needs to be edited.
In Regedit, use the find command to locate all “Data” for THETA V.
Once you find the key with the search feature, click on each Instance.
Prior to editing, you will not see a DevicePath.
You need to add it.
Right-click on the Instance and select New->String Value.
Add DevicePath. Right click on DevicePath again and then modify it. Add a fake path like foo:bar.
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{860BB310-5D01-11d0-BD3B-00A0C911CE86}\Instance\{D36BCC1B-8993-4568-B265-DC5AE05A8C8B}
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{860BB310-5D01-11d0-BD3B-00A0C911CE86}\Instance\{C0A73D6F-A72E-4064-B648-BDCB30C09E6A}
Summary
NEW Info for THETA V 4K
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID{860BB310-5D01-11d0-BD3B-00A0C911CE86}\Instance{D36BCC1B-8993-4568-B265-DC5AE05A8C8B}
Previous fix was limited to this.
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{860BB310-5D01-11d0-BD3B-00A0C911CE86}\Instance{44ADD235-FE8A-42D8-8B18-CF575554AAB1}