Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Launcher 2020.2.2 install wipes out directory on install #19

Open
1st-BrainStormer opened this issue Jun 27, 2020 · 3 comments
Open

Launcher 2020.2.2 install wipes out directory on install #19

1st-BrainStormer opened this issue Jun 27, 2020 · 3 comments

Comments

@1st-BrainStormer
Copy link

1st-BrainStormer commented Jun 27, 2020

I use the custom directory of C:\Program Files\Vircadia Launcher\storage as my install folder.
on installing the 2020.2.2 update on top of 2020.2.1 that folder was deleted, removing my other installs.
Also on running launcher, the launch button is grayed out even though it says the currently selected version is 2020.2.2 Pressing check for update says its at current version. Verified that custom install folder was still set and it was. So on checking for update I had to hit re-install for it to install. It should be automatic, or Hitting Check for update should also check to see if currently selected version is also installed or not and install it if it isn't

@two-one-five
Copy link
Contributor

Buttons being greyed out should not happen, that usually happens if something fails and the state was not updated to release the buttons and controls again.

As for wiping... that also should not happen, as a new install will go into a new folder, exactly what did you do to make that happen? Did you use the check for updates function exclusively?

@1st-BrainStormer
Copy link
Author

Perhaps it isn't scanning the alternate install folder. I think the default install folder should be in the same location the launcher executables are i.e. C:\Program Files\Vircadia Launcher\storage

The wiping was caused by the Launcher installer. As in, I reinstalled the Launcher.

I know its getting confusing as there is the installer for the Launcher, then there is the launcher that also checks for and installs the client/server updates

@two-one-five
Copy link
Contributor

It is very likely that your previous default library folder was not being detected. Try and set your libraries folder to the same that it was previously?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants