OpenVR-InputEmulator
OpenVR-InputEmulator copied to clipboard
matzman666
Windows 2004
i9-9900kf, 1070ti, htc vive(basic hardware info). After Windows 10 2004 build UPDATE opevr input emulator made vr screen shakey and jittery also KinectToVR had different problem, in steamvr or any other app, input looked like it run at 5~10fps screen was running smoothly (athough with shakyness) other vr oriented apps would probably also have similar problems. Windows's fault but I wonder if other ppl experience similar problems
Note: i'm running an AMD Ryzen 5 1600(non AF) and an Nvidia Geforce GTX 1070 Ti and an the HTC Vive.
Yup this has happened to me aswel!, i uninstalled OpenVR-InputEmulator and the major lag/shakeyness is gone, though for some reason i am experiencing bad performance in VR after the Windows 10 2004 + Nvidia driver update, so ill need to find a fix ASAP as it quite bad.
The same here. Update 2004 brokes vr input emulator. I using device offset functionality and everything worked fine in 1903. My software sets pitch and roll offset to HMD through vr input emulator at 200 Hz rate but it seems that it works in 5-10 Hz. Terrible....
We have same issue, did u guys try different nvidia drivers? or did anyone tried different windows version
windows 1909 worked fine for me, i highly doubt its a graphics driver issue, but i willing to downgrade them to test.
No, it is not driver issue, I tried nVidia 441 drivers. I think that something wrong with openvr input emulator driver lib. Sadly, I’m not very familiar with that low level code but I will try to find out what’s is wrong.
Win 1909 works fine for me too.
i rolled back to 1909 and it works fine(i ended up had to reinstall windows as the rollback messed up the OS) but its working fine.
So, what we will do, guys? Let's hire the programmer who is able to make a fix.
So, what we will do, guys? Let's hire the programmer who is able to make a fix.
I'm listening, where to start? Maybe it's also something in build 2004 that can be turned off or adjusted
I'm listening, where to start? Maybe it's also something in build 2004 that can be turned off or adjusted Seems that it's something wrong with driver lib (openvr emulator lib).
from my testing 2004 broke more than just OpenVR-InputEmulator, so my recommendation is to roll back to 1909 if possible, as for the code base, its not been updated in 3/4 years so you will be lucky if matzman666 updates it.
from my testing 2004 broke more than just OpenVR-InputEmulator, so my recommendation is to roll back to 1909 if possible, as for the code base, its not been updated in 3/4 years so you will be lucky if matzman666 updates it.
Sadly. What is broken else?
well for me my network driver died, it messed up my VR(it was causing major high frametimes in VR) it also broke my microphone(?), and bad overall performance, also broke my full-body(i use KinnectToVR and that requires OpenVR-InputEmulator so it broke my full body), etc, TLDR tried to rollback and that completely messed up my windows so i ended up needing to reinstall it.
well for me my network driver died, it messed up my VR(it was causing major high frametimes in VR) it also broke my microphone(?), and bad overall performance, also broke my full-body(i use KinnectToVR and that requires OpenVR-InputEmulator so it broke my full body), etc, TLDR tried to rollback and that completely messed up my windows so i ended up needing to reinstall it.
Terrible. Microsoft's Q&A is dead.
On a side note and for a quick solution, can you guys give me a good source from which I can download latest 1909 build? I can't roll back (no windows.old file) and after 10 day period. So I need to download one, but surprisingly it's hard to find
https://www.reddit.com/r/Windows10/comments/hjowyv/where_to_get_1909_iso/?utm_source=share&utm_medium=ios_app&utm_name=iossmf
Okay, I found a solution. Let's ask Valve to add native support for motion compensation (and another InputEmulator features) in SteamVR.
Not going to happen, if Valve did that it would allow for easy cheating(making things like rapped fire etc), with this third-party-extension you have to be smart enough to install and know how to use this, long story short, nope, not going to happen, not in a million years
I rolled back to 1909 works fine, btw do all of you guys have 1070ti ? because it could isolate a lot of possible reasons it's unstable
I rolled back to 1909 works fine, btw do all of you guys have 1070ti ? because it could isolate a lot of possible reasons it's unstable
1080ti. Did someone tried this one? https://github.com/openvrmc/OpenVR-MotionCompensation
Seems that driver hooks code is a bit different