Really need a way to go back to 1.7.15

[kakek]

Hello.

Tl:DR : Can't play my games anymore since 1.8 update.

You can guess how frustrating it is to have something that worked, then an update break it, and the update is forced on you and you can't downgrade.

Ever since 1.8 update, I have a problem where I can't do custom binding of my controller for any non-steam VR titles. When I try, it tells me that there's no controller connected.

The thing is, I'm on WMR, and custom binding is what allow me to play many games that don't have official support of WMR.

And I was right in the middle of playing Revive titles. And since they don't work on 1.8 and later version, the only way I can play them now would be to go back to 1.7.15

Please help ...

[Draz]

The following tutorial assumes you are on Windows. Using SteamDB's history data on the SteamVR app, you can download old builds using manifest IDs. 250820 is the SteamVR AppID and the following six digit number is another subpackage.

1. Press the Windows key and the R key

2. Type "steam://open/console" and press enter

3. Enter the following commands, one by one to download the old files

download_depot  250820 250821 3461183669501960878
download_depot  250820 250824 896611946591664039
download_depot  250820 250827 7405209456960741105
download_depot  250820 250830 8255214014436030582
download_depot  250820 250831 8065879212735109331
download_depot  250820 250833 7725354146120744174

You will not see any loading indicators, but you can monitor your network usage from task manager, for example.

4. Once the files have been downloaded, the console window will inform you where the files are located, copy the path and open it in Windows explorer

5. Fully close down Steam so that it's not running

5.5. Delete all files inside the SteamVR installation directory

6. You should see multiple "depot_XXXXXX" folders, go inside each one and copy the contents to the SteamVR installation directory

7. Delete your steamvr.vrsettings config file to regenerate a new config file on the next launch. The file is inside your Steam installation folder, inside the config folder

8. Launch Steam and SteamVR, you should see you are now on version 1.7.15!


Edit: Also make sure you disable high priority updates for SteamVR. Right click the app from your library, select "Properties", then navigate to the "Updates" tab and change the "Automatic updates" preference

Edit 2: Added step 5.5. I would recommend you to delete the current files as any new files that have been added since 1.7.15 could cause problems.

[kakek]

THANKS A LOT !

I already tried something like that, but was not 100% sure of the depot I had downloaded/ Also did not delete config file, and might have forgotten to disable update BEFORE doing all that ...

In the meantime I have reinstalled my whole system, just to be sure I'm on something 100% clean. (I'm that kind of user. ) But if, as I'm pretty sure, my bug is linked to 1.8 update and not something else, I'll try your method to downgrade and be able to finish Aasgard wrath :D

[Draz]

Originally posted by kakek:

THANKS A LOT !

I already tried something like that, but was not 100% sure of the depot I had downloaded/ Also did not delete config file, and might have forgotten to disable update BEFORE doing all that ...

In the meantime I have reinstalled my whole system, just to be sure I'm on something 100% clean. (I'm that kind of user. ) But if, as I'm pretty sure, my bug is linked to 1.8 update and not something else, I'll try your method to downgrade and be able to finish Aasgard wrath :D

Let me know how it works for you. I tried it out just to try out the old build but don't have AW or your setup to see if it really solves the problem.

[kakek]

Edit :
since I still had the bg with a fresh system install, I followed your instructions, and succefully reverted to 1.7.15.
Wich fixed my problem, at least with revive and some old non-steam demo that stopped working. It IS a 1.8 issue :(

Also, do you know of a way to prevent steamVR from updating at all ? As I see it, the option only stop it from automatically updating every time I launch steam, but it will eventually update itself at some point.

Anyway, thanks a lot for your help !

[Draz]

Sorry, I do not. I recently did this to downgrade Beat Saber, and even though the setting says it would update on launch, after multiple reboots and Steam restarts it never did. So, hopefully it just never will update...?

[kakek]

Well, worst case scenario, I just have to keep a copy of my steamVR 1.7.15 directory, and just re-arase and copy back the files if it happens. As long as it's not every day, it will allow me to finish the games I was playing for now.
After all, I still hope it's a temporary workaround. It's only a question of time because something require newest update anyway. If by then the issue is not fixed, I'm screwed :/

You still were a big help. Thanks again.

[Draz]

Originally posted by kakek:

Well, worst case scenario, I just have to keep a copy of my steamVR 1.7.15 directory, and just re-arase and copy back the files if it happens. As long as it's not every day, it will allow me to finish the games I was playing for now.
After all, I still hope it's a temporary workaround. It's only a question of time because something require newest update anyway. If by then the issue is not fixed, I'm screwed :/

You still were a big help. Thanks again.

You're welcome! Make sure to use the bug report form if you haven't already, I'm sure the devs would look into it if you explained the problem in detail!

[rjdemaree]

Originally posted by Draz:

The following tutorial assumes you are on Windows. Using SteamDB's history data on the SteamVR app, you can download old builds using manifest IDs. 250820 is the SteamVR AppID and the following six digit number is another subpackage.

1. Press the Windows key and the R key

2. Type "steam://open/console" and press enter

3. Enter the following commands, one by one to download the old files

download_depot  250820 250821 3461183669501960878
download_depot  250820 250824 896611946591664039
download_depot  250820 250827 7405209456960741105
download_depot  250820 250830 8255214014436030582
download_depot  250820 250831 8065879212735109331
download_depot  250820 250833 7725354146120744174

You will not see any loading indicators, but you can monitor your network usage from task manager, for example.

4. Once the files have been downloaded, the console window will inform you where the files are located, copy the path and open it in Windows explorer

5. Fully close down Steam so that it's not running

5.5. Delete all files inside the SteamVR installation directory

6. You should see multiple "depot_XXXXXX" folders, go inside each one and copy the contents to the SteamVR installation directory

7. Delete your steamvr.vrsettings config file to regenerate a new config file on the next launch. The file is inside your Steam installation folder, inside the config folder

8. Launch Steam and SteamVR, you should see you are now on version 1.7.15!


Edit: Also make sure you disable high priority updates for SteamVR. Right click the app from your library, select "Properties", then navigate to the "Updates" tab and change the "Automatic updates" preference

Edit 2: Added step 5.5. I would recommend you to delete the current files as any new files that have been added since 1.7.15 could cause problems.

So, what happens if you get a message, "Depot download failed : Manifest not available?"

[GuppyFacesAreCute]

you can block update of SteamVR putting

StateFlags = 4

in "appmanifest_250820.acf" under steamapps folder.

[karavision]

Yeah, I may be doing that once this problem is fixed. SteamVR worked when I first downloaded it years go. There was nothing more that I wanted from it and there is nothing that has been added to in that I consider a benefit. I am basically just waiting, each patch, to see if things have gotten worse. Even the ui update just boiled down to not being able to remove the floor grid anymore and losing the ability to stack that holodeck door on top of my existing vr surroundings. I am not insulting the people who work on it. I am just saying that this is one of those programs that only need to work. Nothing extra that they have to offer is worth bricking these expensive devices that we all bought.