MCL-1712Assets not downloading with updated launcher (No Sound - 1.7.2)
An updated launcher does not download missing or new assets. Deleting the launcher and allowing to be re-downloaded corrects the issue. 1.7.2 assets not downloaded when first launching profile uses different directory. Discovered due to sounds not working.
Setup: .minecraft_2 is an existing installation with 1.2.7 launcher, that has never launched 1.7.2
Verifying Test 1 (failure):
(1) Copy .minecraft_2 as .minecraft
(2) Run launcher, allowing update to 1.2.8
(3) Delete assets directory
(4) Run game
Result: Assets are not downloaded, game launches, no sound.
Verifying Test 2 (working):
(1) Copy a backup .minecraft installation with 1.2.7 launcher.
(2) Delete launcher.jar and launcher.pack.lzma
(3) Run Launcher
(4) Delete existing assets directory
(5) Run game
Result: Assets are downloaded, game launches, sound works.
Verifying Test 3 (failure):
(1) Copy a backup .minecraft installation with 1.2.7 launcher.
(2) Run launcher, allowing update to 1.2.8
(3) Create new 1.7.2 profile with alternate directory
(4) Run game
Result: Assets for 1.7.2, such as sounds.json are not downloaded, game launches, no sound.
Verifying Test 4 (working):
(1) Copy a backup .minecraft installation with 1.2.7 launcher.
(2) Delete launcher.jar, launcher.pack.lzma
(3) Run Launcher
(4) Create new 1.7.2 profile with alternate directory
(4) Run game
Result: Assets are downloaded, game launches, sound works.
Environment
Windows 7 Ultimate x64
Java(TM) SE Runtime Environment (build 1.7.0_25-b17)
Created Issue:
Assets not downloading with updated launcher (No Sound - 1.7.2)
An updated launcher does not download missing or new assets. Deleting the launcher and allowing to be re-downloaded corrects the issue. 1.7.2 assets not downloaded when first launching profile uses different directory. Discovered due to sounds not working.
Setup: .minecraft_2 is an existing installation with 1.2.7 launcher, that has never launched 1.7.2
Verifying Test 1 (failure):
(1) Copy .minecraft_2 as .minecraft
(2) Run launcher, allowing update to 1.2.8
(3) Delete assets directory
(4) Run game
Result: Assets are not downloaded, game launches, no sound.Verifying Test 2 (working):
(1) Copy a backup .minecraft installation with 1.2.7 launcher.
(2) Delete launcher.jar and launcher.pack.lzma
(3) Run Launcher
(4) Delete existing assets directory
(5) Run game
Result: Assets are downloaded, game launches, sound works.Verifying Test 3 (failure):
(1) Copy a backup .minecraft installation with 1.2.7 launcher.
(2) Run launcher, allowing update to 1.2.8
(3) Create new 1.7.2 profile with alternate directory
(4) Run game
Result: Assets for 1.7.2, such as sounds.json are not downloaded, game launches, no sound.Verifying Test 4 (working):
(1) Copy a backup .minecraft installation with 1.2.7 launcher.
(2) Delete launcher.jar, launcher.pack.lzma
(3) Run Launcher
(4) Create new 1.7.2 profile with alternate directory
(4) Run game
Result: Assets are downloaded, game launches, sound works.Environment
Windows 7 Ultimate x64
Java(TM) SE Runtime Environment (build 1.7.0_25-b17)
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
Please attach the complete output of the "Development console" tab of the launcher.
Apologies for not having provided the console output sooner, and I see that this is already fixed in launcher 1.3.1
For anyone curious, this will not resolve the far less likely situation of the assets folder being overwritten or deleted while the launcher is open (something I've done quite often in personal mod development to "reset" my environment). Symptoms of missing assets on launch are: Missing game icon(s) such as on taskbar, no sounds or music (or a combination depending on what is missing). Closing and re-opening the launcher will properly download the assets in that situation – only wishful thing might be to have a quick check for missing assets/other files on launch, like the check done on load and similar to checking for the existence of the version being launched on clicking "Play", but it's really just an inconvenience that can be remedied by updating your snapshot of the environment.