Revert to old version for oculus killer.

[Orangutangfisher]

I need oculus killer as it boosts my performance by ALOT but it doesn't work with the 2.0 version of steam. Is there a way to revert back to the old version of steamvr? EDIT: forgot to clarify, in steam menu everything works fine with controller inputs but as soon as you go into a game controller inputs stop working

[Orangutangfisher]

I feel bad for everyone else also having this issue

[The_Holy_Bird]

it does work with SteamVR 2.0, atleast for me it wont launch Dash.

[Orangutangfisher]

I forgot to clarify it works PERFECTLY in steam menu but when you enter a game your controller inputs do not work

[Vaizor]

the dev of oculus killer said they will look into this, but i really wish valve would at least give us answers instead of brushing us off simply because we use Meta Quest headsets. I wish I didnt have to stay on steamVR 2.0 i might see if i can find the old repo

[eliminater74]

anyone wanting to go back to Steam Regular, all they need to do is manage app, and remove your self from the beta, then it will redownload the original steamVR and if you want to bo back to beta then put it back on Beta.. its that simple.. you dont have to stay on a Beta.. and I have been trying like crazy to track down this issue.. and I am starting to think the issue is with SteamVR it self. Because it worked on the SteamVR 1.x with no problems. just 2.x are the problems.. and I have turned on Console logging of the oculus Runtimes and so on.. and I cant see much Dif between Using SteamVR with Original OculusDash and SteamVR using OculusKiller. but if you use SteamVR 2.x Beta with the Original OculusDash.exe it will work perfect.. but I just dont get what is causing it to screw up without the Original OculusDash.exe,

I did add a Warning to my Oculus VR Dash Manager, the next release will check which version of SteamVR your using and tell you that some problems have been reported with it if your using beta.. Otherwise you wont see that warning popup.

I am going to add a few Oculus Debugger routines that will allow you to start the OVRServer in debug console mode, and turn it off if so desire.. I will also add the ability to view all Oculus Logs, and if I am not mistaking I think SteamVR logs alot too.. I already have OculusKiller to log everything to your username/AppData/local/OculusKiller
but next version of Oculus VR Dash Manager will have a button that will be enable as long as the log is there otherwise it will be disabled. also a Delete button. Once we figure out what the deal is, I will back off on some of the logging methods..

My only other option is to install the Steam SDK and run it into my Project to access certain things. and I really dont want to do that.. because with that I also have to run a Wrapper since all SDK is written for C++ while all my programs are written in C#, I am thinking about Running a wrapper for the Oculus SDK, to have Better handling of the Controllers, and that might Work OculusKiller. but again, No wrapper exists as of current date, at least none that I know of, and writing a wrapper is not that easy and very time consuming. as I said, All SDK is written for C++ and all my work is written in C#, so I have to create a wrapper to allow the C++ to communicate with the C#, Wrapper is also known as Shem.. but it just might come down to that. Not that I want to do that.. and I cant seem to get any logs from anyone else. and I truly want this to work again.. I just might have to do that.

Understand, its not easy for me to test and go between 2 rooms to keep testing my headset and the computer.. I was in a bad motorcycle accident back in July 31st. I crushed my knee and broke 12+ ribs including the one next to my neck. I am lucky to even still be alive. but I had to have surgery on my Knee, have 7 rods in my knee and cant walk on that leg for 3 months. Nov 13th should be the last day.. then I can prob test better and get things done......