In case of broken picature see link: https://www.dropbox.com/s/jsbozosec3fb4 ... t.png?dl=0
The image part where it says NONE with white letters(/characters) contained translated text and i don't want to share my country with the whole forum.
Steam won't auto-update
Steam won't auto-update
Steam doesn't automaticly download the new update but sees it as a beta.
In case of broken picature see link: https://www.dropbox.com/s/jsbozosec3fb4 ... t.png?dl=0
The image part where it says NONE with white letters(/characters) contained translated text and i don't want to share my country with the whole forum.
In case of broken picature see link: https://www.dropbox.com/s/jsbozosec3fb4 ... t.png?dl=0
The image part where it says NONE with white letters(/characters) contained translated text and i don't want to share my country with the whole forum.
Re: Steam won't auto-update
Have you tried restarting Steam and verifying the game cache?
-
TruePikachu
- Filter Inserter
- Posts: 978
- Joined: Sat Apr 09, 2016 8:39 pm
- Contact:
Re: Steam won't auto-update
The proper solution to this would be to both keep a version-numbered branch for the current experimental, and to push the new experimental atop the `experimental` branch.
As an example, assume we currently have a branch identical to `experimental` and named `0.13.2`. This means that the "Beta" list would allow one to opt into the current stable (`public` or `0.12.35`), any specific experimental (`0.13.0`, `0.13.1`, or `0.13.2`), or the latest experimental (`experimental` being identical to `0.13.2`).
When a new experimental is available, it is added to the `experimental` branch (so people subscribed to `experimental` get an update, while `0.13.2` doesn't), then `experimental` is cloned into `0.13.3`.
If you rename `experimental` to `0.13.2`, then push the new build as `experimental`, the renamed branch (now `0.13.2`) is what people would still be subscribed to, and they wouldn't automatically update to 0.13.3 i.e. `experimental`; this is what the current system might be.
As an example, assume we currently have a branch identical to `experimental` and named `0.13.2`. This means that the "Beta" list would allow one to opt into the current stable (`public` or `0.12.35`), any specific experimental (`0.13.0`, `0.13.1`, or `0.13.2`), or the latest experimental (`experimental` being identical to `0.13.2`).
When a new experimental is available, it is added to the `experimental` branch (so people subscribed to `experimental` get an update, while `0.13.2` doesn't), then `experimental` is cloned into `0.13.3`.
If you rename `experimental` to `0.13.2`, then push the new build as `experimental`, the renamed branch (now `0.13.2`) is what people would still be subscribed to, and they wouldn't automatically update to 0.13.3 i.e. `experimental`; this is what the current system might be.
Re: Steam won't auto-update
As far as I know, we do it the way you described as "proper solution".
This step in deploy process is not automated and doesn't have to be done by the same person every time, so it is possible it was done differently when deploying 0.13.2
This step in deploy process is not automated and doesn't have to be done by the same person every time, so it is possible it was done differently when deploying 0.13.2
Re: Steam won't auto-update
1) That's how it's always been done.TruePikachu wrote:The proper solution to this would be to both keep a version-numbered branch for the current experimental, and to push the new experimental atop the `experimental` branch.
As an example, assume we currently have a branch identical to `experimental` and named `0.13.2`. This means that the "Beta" list would allow one to opt into the current stable (`public` or `0.12.35`), any specific experimental (`0.13.0`, `0.13.1`, or `0.13.2`), or the latest experimental (`experimental` being identical to `0.13.2`).
When a new experimental is available, it is added to the `experimental` branch (so people subscribed to `experimental` get an update, while `0.13.2` doesn't), then `experimental` is cloned into `0.13.3`.
If you rename `experimental` to `0.13.2`, then push the new build as `experimental`, the renamed branch (now `0.13.2`) is what people would still be subscribed to, and they wouldn't automatically update to 0.13.3 i.e. `experimental`; this is what the current system might be.
2) You cannot rename Steam beta branches.
You could try reinstalling the game on Steam, or switching branches or something.
As this is not a we can do anything about, moving to not a bug.
Re: Steam won't auto-update
I don't care how the beta's are organised, I just prefer to let the game automaticly update, like all my other steam games, instead of new versions of the game being added to the list of beta's.
Re: Steam won't auto-update
If you want to play the latest version, no matter how buggy it is, select experimental. If you want to play version that is pretty much stable, opt out of beta.
If for some reason the latest experimental branch becomes unplayable for you, or you want to play on server that has not been updated yet, you can select specific version.
We cannot contol time it takes Steam to download an update, but usually if you resteart you Steam client after we release an update, it queues the update right away.
If for some reason the latest experimental branch becomes unplayable for you, or you want to play on server that has not been updated yet, you can select specific version.
We cannot contol time it takes Steam to download an update, but usually if you resteart you Steam client after we release an update, it queues the update right away.