OpenVR-InputEmulator icon indicating copy to clipboard operation
OpenVR-InputEmulator copied to clipboard

[Crash] 1.3 and current master no longer work, immediately crash/exit after launching SteamVR

Open DevNMY opened this issue 6 years ago • 3 comments

I am no longer able to get a self-compiled version to work, neither the 1.3 source from the release page, nor the current master as of today. However, the 1.3 installer from the release page works as intended! I did everything according to the installation guide, installing boost, ignoring Leap SDK, launching VS (I am using Community 2017), retargeting to Windows 8.1 (and VS 14.1), building as Release, and using the NSIS installer. Note, however, that the "download .zip" option from master, as well as the 1.3 Source Code .zip from the release page contain an empty openvr directory, I had to manually grab it from the referenced https://github.com/ValveSoftware/openvr/tree/167e26e4b9b352614c5f3a83a8434b185f63ed0f This was not necessary in an earlier version (tried 1.0.3 last year), and is not documented in the install/build readme.

I compared all Steam logs between the 1.3 release installer and the 1.3 compiled source, and there aren't any indicators on what went wrong. The module launches, but immediately exits a few 100ms later with "Closing pipe OpenVR-InputEmulatorOverlay (2104) because it was broken from the other end". I attached a vrserver.txt logfile from a clean SteamVR restart up until I try to open the menu: vrserver.excerpt.txt

The previous version I tried last year was 1.0.3, and it worked nicely! But that one no longer seems to work with the current Steam(?)

Can you please help? Any ideas? Any way to figure out what exactly is going wrong? We need to modify the motion compensation to our purposes, so the 1.3 release installer is of no use to us :-(

Thanks a lot! Best regards, Wolfram

DevNMY avatar Mar 28 '18 16:03 DevNMY

I just tried with VS Community 2015 (=v140 instead of v141), from a clean 1.3 source tree and with cleared VS cache, with the same results. :-/

DevNMY avatar Mar 29 '18 14:03 DevNMY

OK, it seems that either the windeployqt or the NSIS installer script no longer work correctly. We can now work around the problem mentioned above by manually copying all Qt files from the 1.3 release installer into our NSIS-installed version, as several hundred Qt files are no longer being copied/included correctly. Our Qt installation did NOT change from last year, neither did the windeployqt.bat. Also, the windeployqt.bat did work (as in "it copied several things and did not interrupt with an error").

DevNMY avatar Apr 17 '18 12:04 DevNMY

Umh. OK, it seems the ACTUAL answer to this problem is that you NEED Qt 5.9 since 1.3, NOT Qt 5.7. Didn't anybody ever try to build+run this thing since then, and could have updated the project page accordingly? :-/ See also #162, which is probably now a duplicate of this.

DevNMY avatar May 29 '19 12:05 DevNMY