Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
As a test, I deleted a library assets of DLCs that I knew were not previously included in my assets.vdf file. I then let Steam re-download the library assets for those DLCs by looking at the DLC tab in the game properties dialog.
When the library assets were downloaded, the asset update data was added to the assets.vdf file, but after restarting Steam, the update data was discarded and removed from the file.
This seems to happen because the asset update data version value is set to 0 when new library assets are downloaded.
One of the DLCs added to assets.vdf file:
To confirm that the incorrect version number is what is causing this, I manually changed the version number to 3 and Steam no longer discarded the update data from the file.
https://steamcommunity.com/groups/SteamClientBeta/discussions/3/3814034023684775265/
Also, there appears to be one extra closing bracket at the end of the assets.vdf file, which seems to be fine now, but could cause problems at some point.
Example assets.vdf file created by Steam.
Same file in text format:
Like I said before, this problem will only get worse over time, and no doubt developers have already filed support requests about library assets not updating on the client side when they update them on the backend.
After a quick test, new library assets are no longer removed from the assets.vdf file after a client restart, and existing library assets that are missing from the assets.vdf file are re-downloaded and added to the assets.vdf file (so any previously outdated library assets get updated).