the asset i purchased got stuck during the initializing phase. restarting the epic games launcher doesnt fix it. Shutting it doen and deleting the localappdata webcache_4430 folder doesnt fix it either.
What type of bug are you experiencing?
Purchasing
Steps to Reproduce
the asset i purchased got stuck during the initializing phase. restarting the epic games launcher doesnt fix it. Shutting it doen and deleting the localappdata webcache_4430 folder doesnt fix it either.
Adding the asset to a different UE installation, even a different UE version.
Canceling and restarting the download.
Deleting the items in the vault cache.
Restarting the Epic launcher.
Restarting the computer.
Hard drive space is in the hundreds of Gigabytes and other, larger assets continue to download. It doesnât happen with any other asset pack. Iâve downloaded hundreds. Just this one.
Iâm having the same problem ever since they released 5.5 I havnt been able to add any assets to none of my folders âŚdid they try to fix this issue?
If it is just a mesh assset or similar and not a plugin just go to your cache directory that is under settings in your launcher - find the most recent folder as thats most likely the one you just downloaded and go into the content folder of it - copy everything in there into your project content folder and it should work. Bit of a workaround but I didnt want to wait on an official response.
My account is new and i canât download my purchase assets, i the see this post and work for me, just open the editor from the launch button, restart the editor and i can download the asset
Several different assets. Closing the Editor helps sometimes. Other times, the asset folder is mysteriously there on the second (or later) attempt.
EDIT: On the third (?) restart of the Launcher, the asset finally installed (this one was âcreate projectâ). But this did not happen until the Fab Library search was complete (spinner stopped).
Is this happening within the plugin as well as on the launcher? It would help us understand the issue in more depth if we can confirm whether or not this issue is isolated to the launcher or not.
Same Issue for me. I only use the launcher. I have waited unto overnight with no change from âINITIATINGâ. I have also had the same issue where an asset would magically appear after restarting my system. I tested to see if the issue affected what had already been downloaded to my local cache or a new asset. Both reacted the same and stalled on âINITIATINGâ. I thought to see if Admin Priviledges was the problem by manually running the launcher and giving it admin, and it seemed to work, but I could not duplicate the success either manually or automatically through Windows task system for autostart. NOTHING has worked to any degree of success. I hope sharing my observations will help bring this issue to a quick resolution. Thank you
Hey dude i had the same problem but i fixed, i restored the settings of the download to default, after this, i select againg the folders on the disk that i prefer, close the program, open it again and it will be fix.
FIXED! I found that going into APPs Manager and Uninstalling the âEpic internet Servicesâ Resolves the problem. It makes the Launcher flip out, but files get downloaded and installed. The launcher want to reinstall the services but you can ignore the badge and the launcher functions as usual.
Cause is conflicting asset, namely Content \ __ExternalActors__\ThirdPerson\Maps\ThirdPersonMap\D\SY\Z4CTQ4LG3YV10EKPD0UE8Q.uasset
It happens when you try to install asset pack which has demo made of Third person template into project that itself is made from that template or already has some other pack with similar-made demo. Launcher stumbles over this conflict and probably wants to consult Epic about what to do but Epic keeps silence (as usual ) so launcher awaits.
You may find and delete this file in your project (backup for safety first) and retry to install the pack, usually it goes well.
Alternatively you may install it manually by copying files from AssetVault and overwriting this and possibly other conflicting .uassets
Hey everyone! We appreciate all the additional information you have each provided when seeking a workaround to the issue. Iâve passed on all the relevant information to the team that will be investigating this issue further.
